Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chromium blacklists Nouveau

lists.freedesktop.org

Post reply on HN
Print view View original

131–140 of 411 posts

Re: Chromium blacklists Nouveau

#131

Post by bubblethink »

mikewhy wrote: post #110
StavrosK wrote: post #76

Earlier quoted context omitted.

I don't know, I upgraded to 18.10 and my XPS's brightness control doesn't work. The Prime switchy thing can't change cards without a reboot, and if the screen goes to sleep between switching cards and rebooting, it never comes up again. Actually, with 18.10, it never comes up again anyway. I have a whole host of issues with nVidia cards, my next card is going to be AMD.

18.10 isn't even supported by Dell.

That's not the point. The switching issue at least is present on 18.04 as well. Basically, ubuntu changed the mechnanism from bbswitch in 16.04 to a different one in 18.04. The 18.04 one is buggy and inferior at the moment.

Re: Chromium blacklists Nouveau

#132

Post by techntoke »

This is another reason why we shouldn't let current web browsers decide the future of the web... which to them will become a proprietary black box of slow JavaScript spyware and horrid markup languages.

Re: Chromium blacklists Nouveau

#133

Post by canttestthis »

techntoke wrote: post #132

This is another reason why we shouldn't let current web browsers decide the future of the web... which to them will become a proprietary black box of slow JavaScript spyware and horrid markup languages.

> which to them will become a proprietary black box of slow JavaScript spyware and horrid markup languages

Did you read the bug report?

Re: Chromium blacklists Nouveau

#134

Post by SquareWheel »

ddevault wrote: post #26

From: Drew DeVault To: graphics-dev@chromium.org Subject: nouveau blacklisted in Chromium I'm writing to complain regarding the decision to blacklist nouveau in Chromium. You're creating a hostile relationship with one of the most important projects on Linux. If you do anything about this problem, you should be using your influence to pressure Nvidia into being a better citizen on Linux. Hell, you could even sponsor…

Wow, what a conceited message.

If you want to support nouveau, then you can put the work in. You have no right to demand that others do work for you. Especially when they already have a functioning alternative solution in software rendering.

Re: Chromium blacklists Nouveau

#135

Post by slacka »

richardwhiuk wrote: post #98

Isn't this the key quote: > I did run the WebGL CTS suite, but that resulted in some > hangs from the the max-texture-size-equivalent test, and some > browser-level weirdness after some tests where later tests all fail > (due to what I have to assume is a browser bug). Isn't it more likely that they are noveau bugs, and are part of the problem here?

> hangs from the the max-texture-size-equivalent tes

I reported this bug back in 2015 and they have made no progress on it. It seems Nouveau just doesn't have the resources or man power. I can't really blame Google here. You don't want the browser to be able to hard lock system(not even a Magic SysRq will reboot it)

[1] https://bugs.freedesktop.org/show_bug.cgi?id=92136

Re: Chromium blacklists Nouveau

#136

Post by blihp »

lultimouomo wrote: post #72
nolok wrote: post #9

For anyone interested, the link really should be the full bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=876523 The current link says it as if Chrome was not being fair, but reading their reasoning it makes total sense. Key quote from said bug report: > We thought about blacklisting nouveau driver long time ago, and decided to let more adventurous users to play around. Now that Ubuntu ships with no…

>> Unfortunately we don't have the resources to test every variation of every GPU/driver combination on linux So Google doesn't have the resources to test the default driver on the most widespread linux distribution for one of the two most widespread GPU producers in the market.

Unfortunately, 'the most widespread Linux distribution' is rounding error in the overall scheme of things from a desktop standpoint so it's actually pretty good that they support it as well as they do. Adding Nouveau to the mix is rounding error on the rounding error. So from Google's standpoint, sure they don't have the resources to test it relative to the number of impacted users. Looking at it another way: it's not like Apple or Microsoft will (ever) provide better support so they can get away with it.

I solved the Chrome/Chromium on Linux problem long ago by switching to Firefox. I'll still fire up Chromium for Google sites and a handful of other sites, but for the most part Firefox has been getting it done for me.

Re: Chromium blacklists Nouveau

#137

Post by ddevault »

SquareWheel wrote: post #134
ddevault wrote: post #26

From: Drew DeVault To: graphics-dev@chromium.org Subject: nouveau blacklisted in Chromium I'm writing to complain regarding the decision to blacklist nouveau in Chromium. You're creating a hostile relationship with one of the most important projects on Linux. If you do anything about this problem, you should be using your influence to pressure Nvidia into being a better citizen on Linux. Hell, you could even sponsor…

Wow, what a conceited message. If you want to support nouveau, then you can put the work in. You have no right to demand that others do work for you. Especially when they already have a functioning alternative solution in software rendering.

I am not demanding that they do work. I'm demanding that they do not deliberately sabotoge the nouveau driver. If they find the nouveau driver lacking, they should improve it, not sabatoge it. If they don't want to put the work in, then they should just leave well enough alone.

Re: Chromium blacklists Nouveau

#138

Post by bootloop »

zanny wrote: post #109
larkeith wrote: post #96

> One idea is to flip GL_VENDOR to some random string if chromium is running. What? Don't do this - never do this. Regardless of whether or not you agree with Chromium's decision, it is their decision to make as the project maintainers; trying to trick the software with falsified data is overstepping your bounds, and both corrodes trust in your driver and leads to whitelists. I thought we had moved past the days of f…

The problem is that the Nouveau (and Ubuntu) devs have no way to overturn Googles decision in Chrome . Ubuntu can compile Chromium with a modified blacklist but Google distributes Chrome in a deb. You would need some special logic to catch the Chrome .desktop on install and add in the unblacklist flag.

The user can decide on his own if he wants the application to run on an unsupported driver or not.

The application decided by default not to offer support for it.

Who should absolutely not decide for the user is the unsupported driver itself so I think the hierarchy is just fine as it is.

Re: Chromium blacklists Nouveau

#139

Post by wbond »

emersion wrote: post #31

Nouveau are doing their best to reverse-engineer cards. NVIDIA doesn't help at all, not providing any docs and not interacting with the rest of the community. On the other hand, Intel and AMD have high-quality drivers and are part of the open-source community.

I see it repeated all the time that AMD has great open source drivers, but their latest drivers on their 5xx line card couldn’t run my 4K display at 60hz over Display Port without splitting the screen into two separate X displays. Nvidia’s proprietary driver can handle it no problem.

Needless to say I have an AMD card, with awesome open source drivers, sitting in a bin. While the horrid binary-blob Nvidia actually drives my display.

Re: Chromium blacklists Nouveau

#140

Post by staktrace »

Sir_Cmpwn wrote: post #60
freedomben wrote: post #52

Earlier quoted context omitted.

While I mostly agree with what your email says, if I received a message that said, "I expect it to be rolled back as soon as possible" and accused me of being "a bad actor on Linux" I would probably be quite put off. You make some good points, but rather than coat them in honey, you soaked them in vinegar. Might get a better result by improving your tone, and maybe giving them credit for at least open sourcing their…

Firefox supports GPU accelleration on nouveau and all Mesa drivers from Mesa 8.0 forward.

Not by default. GPU acceleration is off by default in Firefox on Linux. Distros may change that in their bundles, but the official builds have it turned off.
Post reply on HN