restricted modules for 2.6.20-4 causes boot to hang

Bug #78148 reported by Nathan Jones
This bug report is a duplicate of:  Bug #76294: atheros oops. Edit Remove
8
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.20 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: linux-restricted-modules-2.6.20-4-generic

Installed linux-image-2.6.20-4 and linux headers(same).--> No boot problems. Installed linux-restricted-modules-2.6.20-4 and now boot hangs giving error about nvram and then /sbin/modprobe fails. Alt-control-del and then alt-control-F(1-5) brings up bash login, but cannot sudo etc.

NVidia GForce FX 5200 graphic card
Athlon XP 2500MHz
512MB Ram
D-link DWL-G510 (uses madwifi from restricted modules)

No problems with 2.6.19 or previous kernels and restricted modules drivers.

Revision history for this message
Nathan Jones (neato-2001) wrote :

To confirm this I removed the restricted modules package and the computer managed to boot as expected.

Revision history for this message
David Rasch (rasch) wrote :

I've run into this same bug.

I was able to trace it to a null pointer exception when loading the ath_pci module.

To reproduce:
1. moved madwifi drivers out of the way
2. boot
3. move madwifi drivers back
4. modprobe ath_pci
5. see kernel NULL pointer dereference in kmesg

attached are /proc/interrupts and output to kmesg

aamukahvi (aamukahvi)
Changed in linux-restricted-modules-2.6.20:
status: Unconfirmed → Confirmed
Revision history for this message
aamukahvi (aamukahvi) wrote :

Same here,

Core 2 Duo
Asrock 775Dual-VSTA
D-Link DWL-G520 (madwifi)
Nvidia Geforce 6200 AGP 256MB (non-tc)

Removing restricted modules makes the system bootable again.

Revision history for this message
aamukahvi (aamukahvi) wrote :

And yes, blacklisting ath_pci also allows me to keep using restricted modules and boot normally.

Revision history for this message
Nathan Jones (neato-2001) wrote :

Same deal with 2.6.20-5

Revision history for this message
anachreon (anachreon-) wrote :

Same thing happens to me basically every time I update the restricted modules. I assume the problem is that I use nVidia's proprietary drivers, and the restricted modules seem to always overwrite them or disable them. Thus, when I update the restricted modules, KDE doesn't start I'm stuck ata command prompt.

To solve the problem I simply run "sudo envy" from the command line (Alberto Milone's very convenient script, at http://albertomilone.com/nvidia_scripts1.html) which automatically re-connects to nVidia's server and gets the drivers again, if needed. If I already have the most up-to-date drivers it just sets them up again. Annoying, but not I'm a little wary of getting rid of the restricted modules because of the dependencies.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.