Chromium blacklists Nouveau

Post by nl » Sun, Jan 06, 2019, 12:06 AM UTC

ddevault wrote: post #39

geofft wrote: post #36

Earlier quoted context omitted.

> It's not the browser's place to have any code whatsoever which even so much as glances at the graphics vendor to make meaningful decisions. I'm curious why you hold this position. I think it makes sense for the browser to attempt to deliver the best experience it can to users, and they may believe they get better performance and behavior from unaccelerated rendering. It's no different from websites looking at user-…

Note: I edited my comment to simply be a copy of the email I sent to the devs. You quoted the original text. >I think it makes sense for the browser to attempt to deliver the best experience it can to users, and they may believe they get better performance and behavior from unaccelerated rendering. So should they also blacklist Windows because it's spying on its users? No, of course not. They should do their best to…

Post by [deleted] » Sun, Jan 06, 2019, 12:06 AM UTC

drb91 wrote: post #86

geofft wrote: post #36

Earlier quoted context omitted.

> It's not the browser's place to have any code whatsoever which even so much as glances at the graphics vendor to make meaningful decisions. I'm curious why you hold this position. I think it makes sense for the browser to attempt to deliver the best experience it can to users, and they may believe they get better performance and behavior from unaccelerated rendering. It's no different from websites looking at user-…

> I think it makes sense for the browser to attempt to deliver the best experience it can to users Are you talking about chrome, the least user friendly of all browsers? This is just corporate talk for “we don’t care about making our software work with nouveau”.

Post by jenscow » Sun, Jan 06, 2019, 12:14 AM UTC

Sir_Cmpwn wrote: post #66

zokier wrote: post #56

Earlier quoted context omitted.

> If you do anything about this problem, you should be using your influence to pressure Nvidia into being a better citizen on Linux. By making Chrome significantly slower on nvidia systems they effectively are pressurizing nvida to act better. Trying to work around the problems would be more like supporting the status quo instead of driving change.

That would be true only if they weren't rewarding the proprietary driver. If their goal was to pressure Nvidia into being a better player in FOSS they'd disable GPU accelleration on the proprietary driver.

Post by willtim » Sun, Jan 06, 2019, 12:15 AM UTC

izacus wrote: post #90

willtim wrote: post #70

Earlier quoted context omitted.

We have Thinkpad Linux laptops running with NVidia at work. The proprietary driver has quality issues, the biggest of which for us is power management and poor battery life. Nouveau performs much better in this regard, even though they had to reverse engineer the hardware (!) I will be advising my IT department not to continue to buy NVidia.

On all my laptops, nouveau never outperformed the proprietary driver in battery life. It didn't even support power management on most GPUs - when did that change?

Post by geofft » Sun, Jan 06, 2019, 12:19 AM UTC

drb91 wrote: post #86

geofft wrote: post #36

Earlier quoted context omitted.

> It's not the browser's place to have any code whatsoever which even so much as glances at the graphics vendor to make meaningful decisions. I'm curious why you hold this position. I think it makes sense for the browser to attempt to deliver the best experience it can to users, and they may believe they get better performance and behavior from unaccelerated rendering. It's no different from websites looking at user-…

> I think it makes sense for the browser to attempt to deliver the best experience it can to users Are you talking about chrome, the least user friendly of all browsers? This is just corporate talk for “we don’t care about making our software work with nouveau”.