nVidia (driver) strikes back yet another time
Friday, 4. July 2008, 02:16:00
As usual, I'm here again to blog about... guess what? Problems with nvidia driver.
Right now I have an Asus M51Sn notebook, which has nvidia GeForce 9500M GS card. I'm using 64-bit Gentoo/Linux with vanilla kernel 2.6.25.5. At the time I installed it, the 2.6.25.x versions were not marked as stable in Gentoo, but I chose to install it anyway. However, the then stable x11-drivers/nvidia-drivers-169.09-r1 did not compile with those kernel versions (bug 218178).
Solution? Well, I just installed the next version (x11-drivers/nvidia-drivers-169.12) and it worked pretty well.
In fact, it worked very well until this week, when x11-drivers/nvidia-drivers-173.14.09 was marked stable (but 169.12 was still ~testing). After this update, my 3D desktop simply stopped working. Well, it starts, I can start one app or two, but things are frozen or almost frozen in a weird way that it is simply not usable.
Solution? I'm going back to 169.12 version.
This comment on bug 218178 was a bit scary for me:
What does that mean? Does that mean that 169.x series were not designed for 2.6.25? Or just that 169.09 was not designed, but 169.12 is ok (because it was left "undefined" in his comment)?
Well, anyway I'm masking 173.14.09. I'm going to stick with 169.12, at least this version works for me... until the next nvidia strike.
Right now I have an Asus M51Sn notebook, which has nvidia GeForce 9500M GS card. I'm using 64-bit Gentoo/Linux with vanilla kernel 2.6.25.5. At the time I installed it, the 2.6.25.x versions were not marked as stable in Gentoo, but I chose to install it anyway. However, the then stable x11-drivers/nvidia-drivers-169.09-r1 did not compile with those kernel versions (bug 218178).
Solution? Well, I just installed the next version (x11-drivers/nvidia-drivers-169.12) and it worked pretty well.
In fact, it worked very well until this week, when x11-drivers/nvidia-drivers-173.14.09 was marked stable (but 169.12 was still ~testing). After this update, my 3D desktop simply stopped working. Well, it starts, I can start one app or two, but things are frozen or almost frozen in a weird way that it is simply not usable.
Solution? I'm going back to 169.12 version.
This comment on bug 218178 was a bit scary for me:
Which is why you use the latest stable version, 173.14.09 which is designed for
2.6.25.
What does that mean? Does that mean that 169.x series were not designed for 2.6.25? Or just that 169.09 was not designed, but 169.12 is ok (because it was left "undefined" in his comment)?
Well, anyway I'm masking 173.14.09. I'm going to stick with 169.12, at least this version works for me... until the next nvidia strike.
By qlue, # 5. July 2008, 15:46:30