Hello Andreas, Thanks, but it doesn't help:
# dpkg -l '*nvidia*' | grep ii ii libgl1-nvidia-alternatives 260.19.44-1 simplifies replacing MESA libGL with GPU vendor libraries ii libgl1-nvidia-glx 260.19.44-1 NVIDIA binary OpenGL libraries ii libglx-nvidia-alternatives 260.19.44-1 simplifies replacing Xorg module libglx.so with GPU vendor library ii nvidia-common 20110213+1 NVIDIA binary graphics driver support files ii nvidia-glx 260.19.44-1 NVIDIA binary Xorg driver ii nvidia-kernel-common 20110213+1 NVIDIA binary kernel module support files ii nvidia-kernel-dkms 260.19.44-1 NVIDIA binary kernel module DKMS source ii nvidia-kernel-source 260.19.44-1 NVIDIA binary kernel module source ii nvidia-vdpau-driver 260.19.44-1 NVIDIA vdpau driver # dpkg-reconfigure nvidia-kernel-dkms -------- Uninstall Beginning -------- Module: nvidia Version: 260.19.44 Kernel: 2.6.32-5-686 (i686) ------------------------------------- Status: Before uninstall, this module version was ACTIVE on this kernel. nvidia.ko: - Uninstallation - Deleting from: /lib/modules/2.6.32-5-686/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod.... DKMS: uninstall Completed. ------------------------------ Deleting module version: 260.19.44 completely from the DKMS tree. ------------------------------ Done. Loading new nvidia-260.19.44 DKMS files... Building only for 2.6.32-5-686 Building initial module for 2.6.32-5-686 Done. nvidia.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/2.6.32-5-686/updates/dkms/ depmod.... DKMS: install Completed. # less /lib/modules/2.6.32-5-686/modules.dep ... updates/dkms/nvidia.ko: kernel/drivers/i2c/i2c-core.ko # lsmod Module Size Used by nls_koi8_r 3978 2 nls_utf8 908 5 cifs 235173 9 nvidia 9225131 0 ... #modinfo /lib/modules/2.6.32-5-686/updates/dkms/nvidia.ko filename: /lib/modules/2.6.32-5-686/updates/dkms/nvidia.ko alias: char-major-195-* supported: external license: NVIDIA alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: i2c-core vermagic: 2.6.32-5-686 SMP mod_unload modversions 686 ... alias: char-major-195-* - is this correct? Xorg doesn't start Many thanks for your help, best regards, Alexandr On Fri, Apr 1, 2011 at 2:05 PM, Andreas Beckmann <[email protected]>wrote: > Please uninstall nvidia-kernel-2.6.32-5-686 (and the other > nvidia-kernel-* packages can be removed as well). > > Thanks. > > Andreas > > > The actual bug seems to be that the prebuilt module > /lib/modules/`uname -r`/nvidia/nvidia.ko > takes precedence over the dkms module > /lib/modules/`uname -r`/updates/dkms/nvidia.ko > I need to verify this and see if anything can be improved in that setting. > > > On 2011-04-01 07:52, Alexandr Bravo wrote: > > Package: nvidia-kernel-dkms 260.19.44-1 > > > > In testing distribution after last update package nvidia-kernel-dkms > > 260.19.44-1 produces NVIDIA kernel module with wrong version number > inside. > > As a result Xorg can't start with nvidia because old kernel module > version > > 195.* mismatches with version 260.* of other packages. > > > ii nvidia-kernel-2.6.30-1-686 > > 185.18.36-2+2.6.30-6 NVIDIA binary kernel module for Linux > > 2.6.30-1-686 > > ii nvidia-kernel-2.6.32-5-686 > > 195.36.31+2+4+2.6.32-24 NVIDIA binary kernel module for Linux > > 2.6.32-5-686 > > ii nvidia-kernel-2.6.32-trunk-686 > > 190.53-1+2.6.32-5 NVIDIA binary kernel module for Linux > > 2.6.32-trunk-686 > > ii nvidia-kernel-common > > 20110213+1 NVIDIA binary kernel module support > files > > ii nvidia-kernel-dkms > > 260.19.44-1 NVIDIA binary kernel module DKMS source > > ii nvidia-kernel-source > > 260.19.44-1 NVIDIA binary kernel module source > > # modinfo /lib/modules/`uname -r`/updates/dkms/nvidia.ko > > filename: /lib/modules/2.6.32-5-686/updates/dkms/nvidia.ko > > alias: char-major-195-* > > ... > > > > Looks like this string is not ok: alias: char-major-195-* > > I guess it should be 260 there. > > No. It's just a coincidence that an old upstream version (195.36.31) > matches the device major number (which is the same for all driver > releases). > > Andreas >
