NVIDIA's 302 Linux Driver Finally Has RandR 1.2/1.3

[Gusar]

Actually, high-res console is not really an issue, as you can simply use vesa modes (vga=0xXXX) which is close enough (minus flicker and very-slow-switch).

Minus native resolution if it's not in the vbios of the card, which in many cases it isn't (particularly widescreen resolutions tend to be absent).

However, at least in theory (read: in the future), KMS should give you an option to see OOps message while in X.

Not in theory, the future is now . Has been here for some time now. Check your dmesg, you'll see "drm: registered panic notifier" in there - if you're using a KMS driver that is . Nvidia could easily implement their own such notifier, I doubt drm and KMS are strictly needed for that.

[asdx]

Do you realize pretty much all your posts are you demanding you get all sorts of stuff "right nao!"? Without doing anything on your part to make them happen?

Nvidia will surely support Wayland once it's actually usable. By that I mean once you'll be able to run a full system on it. But getting there takes time. If this process isn't going fast enough for you, then do something about it, instead of just demanding things like a spoiled kid.

And about KMS, this has already been explained before: KMS is an implementation detail, it's one possible way of doing modesetting. Nvidia has no reason to support it, they already have their own implementation of kernel modesetting. The people demanding KMS from Nvidia don't actually want KMS, what they want is a high-res console. Which Nvidia probably could provide, if they had incentive (read: if one of their high-paying customers wanted it).
I have to ask though: Why is a high-res console so important? I bet most of the people demanding KMS from Nvidia are using X all the time.


Anyway, rather than whining about what isn't there, my reaction to this news was OMG!! I think this is quite something. While I didn't mind setting up Twinview, being able to use standard xrandr tools is quite welcome.

Why would you say that I don't do anything to make things happen? I can tell you that in the last years I have been running bleeding edge Linux on my main computers and reporting all bugs I could find, trying to reproduce issues, and getting them fixed.

Is that nothing? Maybe.

I don't demand things to be done "right now", I only express my ideas and what I think is important to do.

Quite frankly, I wouldn't be able to contribute to the blob even if I wanted to, since it's all closed-source software. That's why I contribute to nouveau instead, at least with bug reporting and heavy testing.

[Gusar]

Is that nothing? Maybe.

It's not nothing. But it won't make the things you want done faster. That requires writing code. And repeating "does it have KMS, Wayland?", won't get that code written faster.

I don't demand things to be done "right now", I only express my ideas and what I think is important to do.

Your posting history shows a different picture. An example, there's more: click. Basically, your tone is... off, to say it mildly.

Quite frankly, I wouldn't be able to contribute to the blob even if I wanted to, since it's all closed-source software.

True, but you could contribute to Wayland and Mesa and such. And by contribute I mean more than just bug reports. I can do that with the nvidia driver too, I did in fact, and Nvidia confirmed the report and fixed the issue in one of the next driver versions.

[Mystro256]

Can anyone confirm a fix for the older card slow downs that was introduced in 295.40?

And about KMS, this has already been explained before: KMS is an implementation detail, it's one possible way of doing modesetting. Nvidia has no reason to support it, they already have their own implementation of kernel modesetting. The people demanding KMS from Nvidia don't actually want KMS, what they want is a high-res console. Which Nvidia probably could provide, if they had incentive (read: if one of their high-paying customers wanted it).
I have to ask though: Why is a high-res console so important? I bet most of the people demanding KMS from Nvidia are using X all the time.

A flicker free boot would be nice, though I'm still generally very impressed with nvidia's effort.

[johnc]

There's no such thing as an nvidia story without somebody complaining about so-called lack of KMS support.

[asdx]

Your posting history shows a different picture. An example, there's more: click. Basically, your tone is... off, to say it mildly.

Sorry about that, I agree that my tone went up a bit sometimes but that's mostly because other people (trolls) would bash Linux for no reason, I will try to remain calm. Sorry.

[Delgarde]

And about KMS, this has already been explained before: KMS is an implementation detail, it's one possible way of doing modesetting. Nvidia has no reason to support it, they already have their own implementation of kernel modesetting. The people demanding KMS from Nvidia don't actually want KMS, what they want is a high-res console.

Actually, no. You're right, it's an implementation detail, but it's a significant one. For the open drivers, KMS provides a single consistent method of mode setting, meaning that we have a solution that works for the console, for X, for Wayland, and anything else that might come up. It means that even lacking a decent hardware-accelerated driver, there's always the option to fall back to framebuffer.

By not supporting KMS, Nvidia can't do that. You can't write a system that, e.g switches to a high-res mode for a bootsplash screen, then seamlessly hands over to X. Nor can you switch between X and a console without a mode switch. It can't even co-exist with the KMS support that the Nouveau guys have added. And that's because all that Nvidia provide is an X driver - a very good one, to be sure, but one which provides no integration with the standard way of doing things on Linux.

[tuke81]

Can anyone confirm a fix for the older card slow downs that was introduced in 295.40?
...

Not sure but those should be fixed according to nvidia driver team:
http://www.nvnews.net/vbulletin/show...4&postcount=31

[Mystro256]

Not sure but those should be fixed according to nvidia driver team:
http://www.nvnews.net/vbulletin/show...4&postcount=31

Thanks a lot!

[johnc]

Actually, no. You're right, it's an implementation detail, but it's a significant one. For the open drivers, KMS provides a single consistent method of mode setting, meaning that we have a solution that works for the console, for X, for Wayland, and anything else that might come up. It means that even lacking a decent hardware-accelerated driver, there's always the option to fall back to framebuffer.

By not supporting KMS, Nvidia can't do that. You can't write a system that, e.g switches to a high-res mode for a bootsplash screen, then seamlessly hands over to X. Nor can you switch between X and a console without a mode switch. It can't even co-exist with the KMS support that the Nouveau guys have added. And that's because all that Nvidia provide is an X driver - a very good one, to be sure, but one which provides no integration with the standard way of doing things on Linux.

Are those deficiencies really significant to the average user base though?

I even get flicker during boot on Windows 7 (XP is far worse) and it's not really a popular complaint.