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

161–170 of 411 posts

Re: Chromium blacklists Nouveau

#161

Post by zanny »

bhaak wrote: post #48
nickysielicki wrote: post #32

Earlier quoted context omitted.

> 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-...

Ouch, that's mean. IMHO the only way to react to that is to close down shop. Ideally including Linux throwing out support for Nvidia cards. I have a strong opinion on this as I was involved a few years ago in the Kindle homebrew community. After a while I decided that my time could be used better than on a product by a company that tries to prevent us from making his product better and more interesting to its users.…

I've personally actively avoided buying anything with Nvidia hardware in it for 8 years now because of how awful their software business is. That has meant I've even skipped over tablets and phones using their chips and will never buy a Nintendo Switch because... well... firstly consoles are bullshit crippling perfectly good computers with proprietary OSes but secondly because it has an Nvidia chip in it.

I tell everyone I know not to buy Nvidia, I have built gaming computers both professionally and for family that I've actively advised against buying Nvidia parts for because of their business practices, and when I buy notebooks its a real PITA to get one without some Nvidia GPU in it but I do that too.

But Linux cannot "throw out" support for Nvidia. Nvidias driver is wholly independent of Linux, its why its such a PITA to work with. Its a DKMS blob driver and way too much other useful stuff depends on that interface to break it just to stop Nvidia. Fortunately nobody is going out of their way to support Nvidia either, such as their stupid attempt to fragment Wayland development with eglstreams nonsense.

The most valuable thing any of us can do is constantly decry Nvidia for being the reprehensible company they are and use what influence we have over those we know to distance them from buying their products the same way you should distance friends and family from buying Nestle or Exxon products or should avoid shopping at Walmart.

Re: Chromium blacklists Nouveau

#163

Post by ddevault »

SquareWheel wrote: post #160
ddevault wrote: post #137

Earlier quoted context omitted.

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.

>I am not demanding that they do work. Sure you are: >If they find the nouveau driver lacking, they should improve it, not sabatoge it. Not supporting a buggy driver is hardly "sabotaging it". It's not their job to make it work. >If they don't want to put the work in, then they should just leave well enough alone. And in doing so, their least-technical Linux users will suffer from sudden crashes that they don't under…

Did you deliberately omit the end of that quote to make your point look better? I gave them an out: a demand with an out is not a demand.

>If they don't want to put the work in, then they should just leave well enough alone.

nouveau doesn't crash, but some cards may experience occasional glitches. That's something you need to take up with Ubuntu, not Chromium.

Re: Chromium blacklists Nouveau

#164

Post by microcolonel »

Buy an AMD or Intel GPU. They're cost-effective (or non-negotiably bundled, sometimes), they're well supported, and the vendors make a considerable effort to ensure that stable, compliant drivers are available on every major operating system, and that the free ones are no less stable nor any less compliant.

AMD's performance is competitive dollar-for-dollar, and the top of their lineup is about 80% as good the absolute highest-tier competitor most of the time.

Re: Chromium blacklists Nouveau

#165

Post by mav3rick »

dleslie wrote: post #159
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, let alone investigate & fix bugs in drivers. This is a lie. Google could easily undertake such an act, but is choosing not to. It's not that they _lack the resources to do so_, but that the value proposition of doing so did not weigh favourably towards undertaking the action. Google isn't incapable of this ta…

Feel free to use other browsers that do test this.

Re: Chromium blacklists Nouveau

#166

Post by zanny »

ac29 wrote: post #29
bubblethink wrote: post #10

This 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…

You can get native GPU buffers via enabling zero copy rasterizer in flags and passing --enable-native-gpu-memory-buffers via chromium-flags or as an argument.

They work on ChromeOS the same way they do on desktop Linux and I've been using them for months without issue.

Re: Chromium blacklists Nouveau

#167

Post by zanny »

cmurf wrote: post #40
ac29 wrote: post #29

Earlier quoted context omitted.

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

You need a VAAPI build of Chromium, it isn't on by default.

Arch has a PKGBUILD in the repo: https://aur.archlinux.org/packages/chromium-vaapi/ and I think there are builds for most popular distros out there nowadays.

If you are on Arch or one of its family you can get a -bin version in the AUR or use ArchlinuxCN that builds it in their repo.

Re: Chromium blacklists Nouveau

#168

Post by Operyl »

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…

I get you have an axe[0] to grind with NVIDIA, but is attacking people trying to mitigate around a broken driver really the right direction? By your message, we should also be "pissed off" at you for disabling a driver that "works" in your project too.

[0]: https://drewdevault.com/2017/10/26/Fuck-you-nvidia.html

Re: Chromium blacklists Nouveau

#169

Post by jmgao »

geofft wrote: post #155
vetinari wrote: post #63

Earlier quoted context omitted.

llvmpipe is the gpu part, not the display part of the graphic card. Otherwise, when using it in KVM VM, it can run the desktop compositor quite nicely.

But that's the part that's crashing. I'm suggesting Chrome use llvmpipe to do whatever they needed hardware acceleration for, generate a single boring texture on a single big rectangle, and pass that through to the graphics driver. That way Chrome itself isn't loading the Nouveau libGL and is much more insulated from incompatibilities between Chrome and Nouveau, whosever fault it might be.

That's what swiftshader does.
Post reply on HN