EnvyNG problem with kernel 2.6.24-17
I am experiencing what seems to be a bug in EnvyNG. However, it may also be the result of me doing something wrong. Either way, I would like to solve the issue.
Here is the Ubuntu forum thread where I described my problem with EnvyNG:
Here are my notes about exactly what happened to me:
I installed Ubuntu beta Hardy clean. I used EnvyNG to install nvidia drivers. I had to hand edit my xorg.conf to get my Twinview dual monitor setup working, but that wasn't a problem. Everything was working fine. However, Ubuntu System > Admin > Hardware Drivers (a.k.a. "jockey" I believe) always told me "No propriety drivers are in use on your system" even though they were in use and were working correctly. I just decided to live with that minor issue.
After the Hardy release, I removed older unused kernels (2.6.24-12, 2.6.24-14, 2.6.24-15) and left only 2.6.24-16. I didn't reboot immediately.
When I did reboot a couple days later, I had problems with X. There was no nvidia proprietary driver. (I suspected that might happen when I removed the older kernels. I don't know how to remove older kernel images without this messing up the nvidia restricted driver.)
At exactly the same time this happened, Ubuntu updater offered kernel 2.6.24-17. I accepted and installed the updated kernel. I figured that since I had to reinstall the nvidia drivers, I might as well do it on the latest kernel image.
However, when I tried to use EnvyNG to install the nvidia driver, it installed kernel image 2.6.24-16-386. I tried several times after several reboots and I always got the same result no matter what options I tried. I had to remove the -16 kernel after each try and go back to the -17 kernel. But then I was always without the nvidia drivers I needed for Twinview, etc.
In the end, I followed the advice at this thread (http://