have to reinstall nvidia drivers on every reboot

You shouldn't need to reinstall, run 'jockey-gtk --enable kmod:nvidia_new' instead. It would be nice to get the Xorg.0.log.old and see why it fails after a reboot.

Is there a way this can be done without resorting to the command line?

> It would be nice to get the Xorg.0.log.old and see why it fails after a reboot.

It does'n fail after the reboot - it just does'n know to load the nVidia driver...

anyway the Xorg log is attached: as you can see it tries to load the NV driver instead

> run 'jockey-gtk --enable kmod:nvidia_new' instead.

Unknown driver: kmod:nvidia_new
Use --list to see available drivers

What about adding 'nvidia' to my /etc/modules?

Same thing is happening to me with fglrx.

dpkg -i /var/cache/apt/archives/linux-restricted-modules-2.6.24-16-generic_2.6.24.12-16.34_amd64.deb

After I do that, I can modprobe fglrx, restart X and its good.

When I reboot, the fglrx.ko is gonzo and I have to reinstall.

sudo modprobe fglrx
FATAL: Could not open '/lib/modules/2.6.24-16-generic/volatile/fglrx.ko': No such file or directory

> What about adding 'nvidia' to my /etc/modules?

This doesn't work.

Steve
> Same thing is happening to me with fglrx.

Please file a new bug to avoid confusion. This bug is regarding the proprietary NVIDIA driver.

I started a new bug here for fglrx https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/220430 in case our problems are not related.

What happens when you try

modprobe nvidia

after a restart? Do you get "Could not open '/lib/modules/2.6.24-16-generic/volatile/nvidia.ko'"

My Hardy system was working fine up to and including the 2.6.24-18 kernel. Yesterday I upgraded to 2.6.24-19, and I got this same problem. I did the install and the reboot, and afterwards X came up in failsafe mode. I switched to a console and poked around and saw that (a) lsmod showed no nvidia kernel module installed, and (b) the Xorg.0.log file showed an error that the nvidia driver could not be loaded.

After some head-scratching I ran "sudo dpkg-reconfigure linux-restricted-modules-2.6.24-19-generic", then I looked and I saw that the nvidia.ko file existed, just as you'd expect.

So, I ran "sudo reboot" to reboot the system... and it came up in failsafe mode AGAIN! I switched to a console and checked, and the nvidia.ko module had disappeared! In fact, all three nvidia*.ko files from /lib/modules/2.6.24-19-generic/volatile were gone; the other .ko files in volatile still existed.

In fact I've tried this three times and every single time it behaves the same. Something during the shutdown or startup (not sure which) is causing those .ko files to be deleted.

Note that I can kill the failsafe mode, run the dpkg-reconfigure, then run /etc/init.d/gdm start, and everything comes up normally. But when I reboot, those .ko's disappear and I have to do it all over again.

Any pointers, tips, etc. are welcome; I'd be happy to debug what is going on.

Oddly enough, on my system the fglrx.ko file (which I don't use, but is part of the restricted drivers) is NOT deleted on reboot. Only the nvidia*.ko files. However, it seems like this must be some kind of scripting problem with the linux-restricted-drivers package... no?

FYI I had to reboot yesterday and I still see this problem. Those .ko files are gone every time I reboot.

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

It happened every time I rebooted my system with Hardy, right up until the day (about two weeks ago) that I upgraded to Intrepid. Now it no longer happens. The issue was something to do with the tmpfs that is mounted as /lib/modules/2.6.24-21-generic/volatile. For some reason whatever was supposed to repopulate that tmpfs on boot wasn't working; I had to dpkg-reconfigure every single time.

Just to say: I would have been happy to provide more details and help anyone who was interested debug the issue and get to the bottom of it... but no one ever responded.

Even though the original reporter has moved to 8.10, and isn't experiencing the issue any longer I'm leaving open for now.

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.