2.6.24-16.30 kernel update - nvidia module fails to load

[firmit]

Binary package hint: linux-image

Just did an update - and the computer won't boot with the new kernel-update. When I try to start in recovery mode, it halts at:

[44.130821] nvidia: module license 'NVIDIA' taints kernel.

I had to choose the 2.16.24-15 kernel in GRUB to boot into Gnome.

Log file from synaptic Commit Log for Fri Apr 11 18:02:07 2008 - as attachment.

How to fix this?

[firmit (firmit)]

Attachment...

[firmit (firmit)]

This just happened ... the ball is rolling!
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/215792

[rosencreuz (rosencreuz)]

I have same problem. Xserver only starts in recovery mode now. Below is what I get, please look at the time difference!
This happened after I upgraded to kernel 2.6.24-16-386

[ 31.167603] nvidia: module license 'NVIDIA' taints kernel.
[ 31.473851] saa7130/34: v4l2 driver version 0.2.14 loaded
[ 212.150120] lp0: using parport0 (interrupt-driven).

[xtknight (xt-knight)]

Yes, there is definitely a problem with the nvidia module. Hardy amd64.

[xtknight (xt-knight)]

Happening with the following config:

linux-image 2.6.24-16.30
linux-restricted-modules 2.6.24.12-16.34
nvidia-glx-new 169.12+2.6.24.12-16.34
linux-ubuntu-modules 2.6.24-16.22

[Harvey Muller (hlmuller)]

In Bug #215833, Herbert identifies the solution:

https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/215833/comments/9

which is simply to install the latest Nvidia driver. The version we are using is probably good also, but most likely needs to be built against the latest kernel.

When the devs update/rebuild the nvidia driver I expect our 'suffering' will cease.

Regards,

Harvey

[Timo Aaltonen (tjaalton)]

it should not be necessary to rebuild anything.. the l-r-m is already built against the current kernel.

[Harvey Muller (hlmuller)]

The attached Xorg.0.log is attached per D. Chen's request. This was obtained by booting, and selecting "continue" in the resulting displayconfig-gtk.

[Harvey Muller (hlmuller)]

Attaching Xorg.0.log per D. Chen's request. This copy is produced with kernel version *-15, which is working normally.

[firmit (firmit)]

The update ( as noted here https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/215833 ) fixed the boot-problem, but created a new one! The Hardware Drivers /Jockey does not work anymore. I am not able to set correct resolution on my screen, nor set the nvidia driver.

[xtknight (xt-knight)]

Seems to be primarily a 64-bit issue.

[xtknight (xt-knight)]

Taints kernel is a normal message so I changed the title a little.

[Timo Aaltonen (tjaalton)]

The reason why it fails is that you have a broken modules.dep file for the kernel, due to a broken l-u-m release (which is now fixed). At least booting an older kernel and reinstalling -16 should make it work again. It works fine here, since I upgraded straight to the current versions.

Closing the bug.

[xtknight (xt-knight)]

Timo: you're absolutely correct. Thanks a lot.

[firmit (firmit)]

The update does not work for me!
Hardware manager still crashes, no nvidia driver active - and the correct screenresolution is not in the "new" set-screenres-thingy. I will have to change this the hard way I guess...

firmit@beta:~$ sudo jockey-gtk
Traceback (most recent call last):
  File "/usr/bin/jockey-gtk", line 300, in <module>
    sys.exit(u.run())
  File "/usr/lib/python2.5/site-packages/jockey/ui.py", line 266, in run
    self.ui_init()
  File "/usr/bin/jockey-gtk", line 93, in ui_init
    self.update_tree_model()
  File "/usr/bin/jockey-gtk", line 240, in update_tree_model
    is_enabled = handler.enabled()
  File "/usr/share/jockey/handlers/nvidia.py", line 50, in enabled
    devices = self.xorg_conf.getSections('device')
AttributeError: 'tuple' object has no attribute 'getSections'
firmit@beta:~$

[xtknight (xt-knight)]

firmit: As long as the nvidia module loads, you do not have this bug. Jockey bug is Bug 215027.