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.
Chromium blacklists Nouveau
31–40 of 411 posts
Re: Chromium blacklists Nouveau
#32Both projects seem to put the blame on the other project. IMO, there are at least two other factions that can be blamed equally well. First, nvidia for not providing OSS drivers and second, the user who runs an OS on hardware that can't be properly supported on this OS at the moment. For years I have the rule that I prefer hardware that has proper Linux support. Even going a bit further that I try not to buy hardware…
> nvidia for not providing OSS drivers
It's worse than this. Nvidia does not merely not provide open source drivers, they actively preclude work on Nouveau.
Phoronix link: https://www.phoronix.com/scan.php?page=news_item&px=Nouveau-...
Re: Chromium blacklists Nouveau
#33Will this make Firefox the best browser on Linux by default then? Also, as mentionned in the bug thread, if nouveau is actually stable on Newer versions, similar to User Agents, the newer nouveau versions could change their name to bypass the blacklisting. No need to pretend to be NVIDIA, just something different that nouveau, like 'nuevo' or something.
Can't they also use GL_VENDOR / GL_RENDERER and parse version numbers out of it?
Re: Chromium blacklists Nouveau
#34Earlier quoted context omitted.
>Now that Ubuntu ships with nouveau on default, maybe it's time to blacklist it in Chrome. I don't get this. All linux distros under the sun ship with nouveau, and always have. It is a kernel driver afterall. What else are they going to ship ?
> What else are they going to ship ? Including Nvidia's binary driver by default. Obvs Debian, gNewSense, and GUIX can't do that, but since when have corps cared about them? Like, don't get me wrong, I'm a FOSS or GTFO kind of guy, running Debian and Replicant, but shipping proprietary drivers by default is what chrome is hinting at obviously.
Beyond the whole foss aspect, there are good technical reasons too. For instance, blob won't work with wayland (at least right now AFAIK), and ubuntu was (is) debating switching to wayland as default.
Re: Chromium blacklists Nouveau
#35Meh, I typically use Chrome through a virtual machine with Spice which has broken OpenGL support, so I wasn't getting hardware acceleration anyway. I still get screen tearing in Firefox, for Christ's sake.
Re: Chromium blacklists Nouveau
#36From: 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…
> 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-agent strings to work around known bugs, right? It's okay for a user to override their user-agent string, and fine for browsers to mention other browsers for compatibility, but uncool for a browser to not identify itself at all and steal another browser's user-agent string.
The OpenGL API includes vendor strings for a reason. Chrome isn't doing `strings` on the library or anything.
Re: Chromium blacklists Nouveau
#37Doesn't seem like Nouveau wants to own up.
Re: Chromium blacklists Nouveau
#38For 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…
>Now that Ubuntu ships with nouveau on default, maybe it's time to blacklist it in Chrome. I don't get this. All linux distros under the sun ship with nouveau, and always have. It is a kernel driver afterall. What else are they going to ship ?
> What else are they going to ship ?
That's not the point. The point is that it results in brokenness, and the easiest way to mitigate that for the bulk of non-technical users is to use software rendering instead (i.e. blacklist it). They're open to more refined solutions, but these will take some effort.
Re: Chromium blacklists Nouveau
#39From: 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…
> 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 deliver a good experience in the domains for which they are responsible.
>It's no different from websites looking at user-agent strings to work around known bugs
This is also a very dumb anti-practice.
Re: Chromium blacklists Nouveau
#40This sucks. Chromium doesn't do accelerated video decode for intel on linux either. And now this. What's the AMD scene like ?
Chromium seems to do accelerated video decode with Intel GPU on Linux for me: Graphics Feature Status Canvas: Hardware accelerated Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Native GpuMemoryBuffers: Software only. Hardware acceleration disabled Out-of-process Rasterization: Disa…
I have Chrome Version 65.0.3325.162 (Official Build) (64-bit)
on 4.19.13-300.fc29.x86_64 with i915 graphics
00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller])
And chrome://gpu says Video Decode: Unavailable
And it points to this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=137247