171–180 of 411 posts
Earlier quoted context omitted.
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.
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.
I have a Dell XPS with an Nvidia 1050, running Fedora 29. The Nouveau driver was so bad here that I blacklisted all the drivers and just use the Intel GPU. It's the difference between 3 hours or 6 hours of battery. It apparently ran the Nvidia power on even when no program wanted to use it.
Are you sure you didn't install nvidia drivers? That is a common symptom with nvidia binary drivers. Nouveau on the other hand is fine with powering the device off when not used. For nvidia drivers, the bbswitch method is more reliable, but is apparently deprecated by distros these days.
Earlier quoted context omitted.
>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.
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.
Try Arch with the 4.20 kernel.
Earlier quoted context omitted.
Obviously it’s not that Google doesn’t have the resources. They have enough resources to fund whole new OSes. Of course they could fund testing. Chrome team, on the other hand, does not have the resources. Which is to say that this is not the thing they believe is most important to work on at the margin, and given the amount of engineers Google will fund for the project.
If the chrome team doesn't have the resources for testing the most common Linux configurations, it's not a good sign. Linux market share is low but it's a useful signifier.
they are also saying their that driver may work fine on some less common linux configurations, and the chrome team does not have the resources to test those.
you are literally saying they are saying the opposite of what they said, then blaming them for it.
What is nouveau?
A reverse-engineered driver for Nvidia GPUs on Linux that is open source. Since it is reverse engineered, it tends to be buggy. Most Linux distributions use this driver by default, since it is open source. There is an arguably superior driver supplied by Nvidia. It is faster, has better hardware support, and is arguably more stable (1). However, it ships as a closed source binary blob with a source-based shim layer t…
Thank you! I think you might have just solved an issue for me that happens intermittently with my linux mint 18.3. At least we'll see once i dive into output of stack traces, etc.
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
Wait, this isn't just rendering bugs a la "some WebGL things will show green instead of red", it kills your system entirely?
I thought the only effect this blacklisting had was making WebGL unavailable for everyone instead of buggy for a small minority. This just flipped my opinion.
Related, this might also explain the strange bluescreen bug my girlfriend had with Windows 8 + Firefox on her laptop. She switched to Google Chrome a few years ago because every time she used Firefox, her laptop would bluescreen within a few hours (either while Firefox was still running, or at some point later). I didn't know bugs outside of the OS could still do that kind of thing (I thought they started squashing such bugs with Windows 95 and finished somewhere around Vista) and wrote the Firefox thing off as triggering some extremely obscure Windows OS-level issue. Maybe I should check if there is a driver blacklisted by Chrome, though it seems more likely Chrome just doesn't happen to trigger it (like all other software running on it, it really is only Firefox).
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…
Unless you are paying my salary, any emails sent to me with "I expect..." go straight into the trash.
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
Earlier quoted context omitted.
It's free in the sense you don't pay for it with money, but considering how much Google pays apple to use Google as the default search engine, I would say the Google Browser is a big money maker.
No, Chromium is free in the GNU sense, which is what I meant. You don't whine at open source providers to support features you want, it's bad form. Go fix it yourself, or use hardware that doesn't require this kind of hacky reverse engineering.