Comment 19 for bug 137432

Sorry about the late reply. I don't have the time at the moment to mess around with my machine. I'm currently running the working 2.6.22.10 kernel:

$ uname -a
Linux atlas 2.6.22-10-386 #1 Wed Aug 22 07:43:24 GMT 2007 i686 GNU/Linux

$ dpkg -l linux-restricted-modules-\* | grep ii | tr -s " " | cut -d" " -f2-3
linux-restricted-modules-2.6.20-15-386 2.6.20.5-15.20
linux-restricted-modules-2.6.20-16-386 2.6.20.5-16.29
linux-restricted-modules-2.6.22-10-386 2.6.22.3-10.1
linux-restricted-modules-2.6.22-10-generic 2.6.22.3-10.1
linux-restricted-modules-common 2.6.22.3-11.3

$ dpkg -l linux-image\* | grep ii | tr -s " " | cut -d" " -f2-3
linux-image-2.6.20-15-386 2.6.20-15.27
linux-image-2.6.20-15-generic 2.6.20-15.27
linux-image-2.6.20-16-386 2.6.20-16.31
linux-image-2.6.20-16-generic 2.6.20-16.31
linux-image-2.6.22-10-386 2.6.22-10.30
linux-image-2.6.22-10-generic 2.6.22-10.30
linux-image-2.6.22-11-386 2.6.22-11.32
linux-image-386 2.6.22.11.12

$ grep linux-restricted /var/log/dpkg.log* > /tmp/linux-restricted.log

I'll post the modprobe stuff when I reboot into the 2.6.22-11.12 kernel. Maybe the problem will be fixed by now.

> What might be the problem is a hidden file in /lib/linux-restricted-modules/ try running:
> sudo rm /lib/linux-restricted-modules/.nvidia*

jmd64: I have no such files on my system:

$ ls -a1 /lib/linux-restricted-modules/
.
..
2.6.20-15-386
2.6.20-16-386
2.6.22-10-386
2.6.22-10-generic