Nije bilo problema dok nisam trebao da pokrenem X.
Imam GeForce2 Go sa 32 MB RAM i monitor podrzava rezoluciju 1400x1050.
Oki skinem NVchooser i da mi on koje fajlove da skinem, ja to uradim kopiram na disk i uradim kako oni kazu medjutim kod kernel-a se sve zezne uvek mi daje cudnu gresku oko "headers" itd.
Nesto u fazonu:
"You should not include /usr/include/{linux,asm}/ header files directly for the compilation of kerner modules"
blablablabla
To build kerner modules please do the following:
HAve the kernel sources installed
Make sure that the symbolic link /lib/modlules/'uname'r/build/include/linux/version.h
When compiling make sure to use the following compiler option to use the correct include files
-I/lib/modules/'uname -r'/build/include"
instead of
-I/usr/include/linux"
Please adjust the makefile accordinly"
blablabla...
Jos jednom se ponavlja ova poruka...
Fazon je sto je pola ekrana
/usr/include/linux/version.h:35:2: #error
a pola ekrana ovaj text :)
To se sve fino objasnjava ovde:
"
Q: I can't build the NVdriver kernel module, or I can build the NVdriver
kernel module, but modprobe/insmod fails to load the module into my
kernel. What's wrong?
A: These problems are generally caused by the build using the wrong kernel
header files (ie header files for a different kernel version than the
one you are running). The convention used to be that kernel header files
should be stored in "/usr/include/linux/", but that is being deprecated
in favor of "/lib/modules/`uname -r`/build/include". The NVIDIA_kernel
Makefile should be able to determine the location on your system; however,
if you encounter a problem you can force the build to use certain header
files by doing: 'make SYSINCLUDE=/path/to/kernel/headers'. Obviously,
for any of this to work, you need the appropriate kernel header files
installed on your system. Consult the documentation that came with your
distribution; some distributions don't install the kernel header files
by default, or they install headers that don't coincide properly with
the kernel you are running.
"
medjutim pravo da vam kazem ne znam o cemu pricaju :(
( ne zbog nedostatka engleskog vec zbog nepoznavanja Linux-a )
Oki posle taga sam pokusao i sa tarballs i sa svim cudima, medjutim uvek dobijem neku cudnu gresku...
Nestao sam kao fol skidao medjutim nisam siguran da li sam to dobro uradio...
E uradio sam XF86Config-4 kako treba i sve ostalo medjutim kad treba da pokrenem X
dobijem
(EE) NVIDIA(0): Failed to initialize the NVdriver kernel module!
Screens found but none have a usable configuration.
To se takodje objasnjava ovde:
: My X server fails to start, and my XFree86 log file contains the error:
"(EE) NVIDIA(0): Failed to initialize the NVdriver kernel module!"
A: Nothing will work if the NVdriver kernel module doesn't function
properly. If you see anything in the X log file like "(EE) NVIDIA(0):
Failed to initialize the NVdriver kernel module!" then there is
most likely a problem with the NVdriver kernel module. First, you
should verify that if you installed from rpm that the rpm was built
specifically for the kernel you are using. You should also check
that the module is loaded ('/sbin/lsmod'); if it is not loaded try
loading it explicitly with 'insmod' or 'modprobe' (be sure to exit the
X server before installing a new kernel module). If you receive errors
about unresolved symbols, then the kernel module has most likely been
built using header files for a different kernel revision than what
you are running. You can explicitly control what kernel header files
are used by building NVdriver from the NVIDIA_kernel tar file with:
'make install SYSINCLUDE=/path/to/kernel/headers'.
Please note that the convention for the location of kernel
header files is in a state of transition, as is the location
of kernel modules. If the kernel module fails to load properly,
modprobe/insmod may be trying to load an older kernel module (assuming
you've upgraded). cd'ing into the directory with the new kernel
module and doing 'insmod ./NVdriver' may help.
Finally, the NVdriver may print error messages indicating a problem --
to view these messages please check /var/log/messages, or wherever
syslog is directed to place kernel messages.
Medjutim ni toga pola ne mogu da provalim o cemu pricaju :(
NVdriver ne postoji kad uradim lsmod
niti modprobe moze da ga nadje...
Trazio sam kofiguracije drugih ljudi i njih sam kopirao medjutim nista uvek ista stvar...
Ima li iko bilo kakvih ideja sto se ovoga tice?
Svaka pomoc je dobro dosla!
Unapred zahvalan!