Re:Chromium blacklists Nouveau
by bubblethink on Saturday January 05, 2019 @06:17PM
(#18834999)
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.
[ Parent
| on HN ]
If Nouveau isn't working all that well, then clearly a switch to a new graphics stack that would require it is waaay premature, given how prevalent NVIDIA graphics hardware is.
It does actually work fairly well for non gaming uses.
Re:Chromium blacklists Nouveau
by pantalaimon on Sunday January 06, 2019 @06:35AM
(#18837812)
> blob won't work with wayland (at least right now AFAIK)
AFAIK it works with Gnome's Wayland Implementation, but not with the one from KDE.
My impression was that the 17.10 Weyland stuff was kind of a mess so the switch is probably premature at this point.
Fedora is Wayland-by-default for several releases already.
I had a handful of laptops at work that were briefly on 17.10 (because 16.04 had a showstopping bug for them) and the graphics were a complete headache until I switched them to X. Luckily 18.04 reverted to X and made my life easier.
I've never had problem with it; but then, my laptops have all Intel GPU and my only desktop with AMD GPU handles it nicely too.
Chances are, that you are using modesetting X driver anyway (i.e. the KMS driver, the same driver/backed, that is used by Wayland).
Re:Chromium blacklists Nouveau
by pantalaimon on Sunday January 06, 2019 @06:33AM
(#18837804)
Fedora is a bleeding edge distribution whose sole purpose is to test out new features.
Sort of. It falls back to X for drivers that don't support Wayland, which has included nvidia for a long time. (Maybe there is some progress there more recently.) And the proprietary nvidia driver is widely used.
Does it really? I had grotesque lag when installing Fedora on a System76 laptop with an Nvidia card and had to switch to X manually.