Hacker News new | ask | show | jobs
by cookiecaper 5115 days ago
I've always harbored the hope that nVidia is working behind the scenes on a release that supports KMS/Wayland, and that the release of Optimus support will be released simultaneously. It makes sense when you consider that Optimus support is probably a pretty big change and putting that investment in the legacy X11 non-KMS driver would be a waste when KMS will be a requirement for all new distros in 2 years' time.

It's worth noting that just last night they released a stable driver that (finally) supports RandR 1.2. From what I understand this was also a significant change and it may bode well for future standardization improvements like KMS (moves multi-monitor management away from the proprietary TwinView driver components into standard xrandr, for instance, so that is complexity the KMS version will not have to handle).

Fingers crossed that they release this imaginary driver soon. :)

1 comments

> It's worth noting that just last night they released a stable driver that (finally) supports RandR 1.2

The XRandR support in the driver is not yet stable [1]. The 302.xx line is currently in beta, but will support both XRandR 1.2 & 1.3 at the same time. That part also works flawlessly, however, your mileage may vary in regards to suspend/hibernate, since both I and multiple others on the nvidia forums experience serious problems with resume from either, i.e. the computer hard locks (and doesn't even respond to ssh etc.), which requires you to powercycle it. So while the XRandR is a huge step forward, it is not without problems yet.

[1]: ftp://download.nvidia.com/XFree86/Linux-x86_64/latest.txt shows you the latest stable driver, which is 295.59

Please see http://www.nvnews.net/vbulletin/showpost.php?p=2564605&p... ; as of June 16, 302.17 is classified as a "new official release" in the "Current NVIDIA Linux graphics driver releases" thread. 295.xx is now classified the "long-lived branch release".

ArchLinux has already sent out packages for this release in its stable update channel: https://projects.archlinux.org/svntogit/packages.git/commit/...

Ah, you are of course right, I apologise. The update just hadn't been pushed to the ftp yet.

(As an aside, it still hardlocks my computer...but according to their forums, they "are working on a fix" for the soon-to-come 304.*)