[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: when will nvidai-glx and nvidia-kernel-source hit etch? {Scanned} {Scanned} {Scanned}



(==) Using config file: "/etc/X11/xorg.conf"
Error: API mismatch: the NVIDIA kernel module has the version 1.0-8774, but
this X module has the version 1.0-8776.  Please make sure that the kernel
module and all NVIDIA driver components have the same version.
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please ensure
(EE) NVIDIA(0):     that there is a supported NVIDIA GPU in this system, and
(EE) NVIDIA(0):     that the NVIDIA device files have been created properly.
(EE) NVIDIA(0):     Please consult the NVIDIA README for details.
(EE) NVIDIA(0):  *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration.

Ok, I have a Leadtek PX6800GT video card installed in this system so I don't think the
supported NVIDIA GPU line is the issue must be the API mismatch....not sure how
that would have happened.  Think I'll cc Randall Donald the nvidia maintainer....

andy:/usr/X11R6/bin# lspci
0000:01:00.0 VGA compatible controller: nVidia Corporation NV40 [GeForce 6800 Ultra/GeForce 6800 GT] (rev a2)

I'll give kdm a whirl and see if it does better than gdm...


/usr/X11R6/bin was dumped and symlinked with the XOrg transition about
18 months ago. Nothing should be using /usr/X11R6, period. Especially on
an Etch system.

The error message you're getting is right in front of your face:
"the NVIDIA kernel module has the version 1.0-8774, but this X module
has the version 1.0-8776" means your nvidia kernel module has version
1.0-8774 but your nvidia-glx has version 8776. Don't try and mix and
match versions.

And for reference, you can't "just" add lines to unstable. Apt will
automatically use the most recent mirror it sees for *ALL* packages,
unless you prepare accordingly. "-t unstable" is redundant unless you
prepare apt for another default. As such, large chunks of your system
are likely to have been moved to unstable.

Let's try this again.

Installing Nvidia:

1) Nvidia is made from two main components - a binary driver
("nvidia-glx") and a kernel module (package name varies a lot). The
kernel module must be built against your EXACT, RUNNING KERNEL; the two
components must MATCH PRECISELY.

2) To install the kernel module, you must compile it. This requires
kernel headers for your running kernel ("linux-headers-$(uname -r)") and
the module source code ("nvidia-kernel-source").

3) To compile it, you can mess around by hand, or use the
"module-assistant" tool. "m-a a-i nvidia" will retrive a C compiler (if
needed), kernel headers for your running kernel (if needed) and the
nvidia-kernel-source package (if needed), AS LONG AS THEY ARE AVAILABLE
FROM YOUR SOURCES.LIST. If not, then you'll need to install the above by
hand.

4) When module-assistant has built and installed your kernel module,
install the "nvidia-kernel-common" package (useful Init scripts to make
nvidia behave) and "nvidia-glx" package (the actual driver). At this
point, you can reconfigure your X server to use "nvidia" rather than
"nv".

5) If given packages are unavailable on your release (e.g. Etch), then
you *might* be able to get away with downloading the .deb files from
Unstable and installing them with "dpkg -i". However, adding unstable to
sources.list is a sure-fire way to move to unstable, unless significant
time, care & attention is taken.

Yeah it was already pointed out to me that I must have compiled under
2.6.17-amd64 instead of booting into 2.6.18-amd64 first and then running
the m-a stuff.  Lots of steps, boy my butt is getting tired.

Anyway, now I'm up against more missing executables in /usr/bin so I removed
the unstable lines from sources.list and ran:

dpkg -l | grep ii | cut -d " " -f 3 | xargs -n 1 apt-get --reinstall install

to brute force rebuild all the missing binaries/symlinks I deleted from /usr/bin last week.

So far I've added 20 new executables I had previously missed 1884 --> 1904  on a 'ls /usr/bin | wc'.


--
Henry Hollenberg
hgh@rcwm.com

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.



Reply to: