This may also be relevant to all the video breakage reports on Gutsy from yesterday.
I'm running HH, updated, with KDE4.
I have verified by experiment that the nvidia-glx-new packaged driver (169.09) no longer functions, post update. KDM puts up some interesting screen noise, in the process of trying to run, and sometimes you end up "black-screened". Usually it's just back to the CLI. I didn't try to go back and install nvidia-glx -- I'm not sure that driver would even work with my 8800GTS card.
However, when I ran the (new and much abbreviated) dpkg-reconfigure xserver-xorg routine, and restarted KDM, I got my desktop at 1280x1024/85Hz. It says "VGA" -- not sure what that means. No Compiz, of course, and the System Settings won't let me change it back to 1600x1200, or anything else. I suspect the devs are trying to improve the auto-detecting function in *buntu, and this is "collateral damage". Just a guess.
EDIT: So, I just downloaded the Nvidia driver 169.09 (64-bit), and followed my own directions here and the driver is working fine now. Dunno what happened to screw up the packaged driver, but it's a dead duck until something changes.
I'm running HH, updated, with KDE4.
I have verified by experiment that the nvidia-glx-new packaged driver (169.09) no longer functions, post update. KDM puts up some interesting screen noise, in the process of trying to run, and sometimes you end up "black-screened". Usually it's just back to the CLI. I didn't try to go back and install nvidia-glx -- I'm not sure that driver would even work with my 8800GTS card.
However, when I ran the (new and much abbreviated) dpkg-reconfigure xserver-xorg routine, and restarted KDM, I got my desktop at 1280x1024/85Hz. It says "VGA" -- not sure what that means. No Compiz, of course, and the System Settings won't let me change it back to 1600x1200, or anything else. I suspect the devs are trying to improve the auto-detecting function in *buntu, and this is "collateral damage". Just a guess.
EDIT: So, I just downloaded the Nvidia driver 169.09 (64-bit), and followed my own directions here and the driver is working fine now. Dunno what happened to screw up the packaged driver, but it's a dead duck until something changes.
Comment