https://www.phoronix.com/news/Avoid-Nouveau-Linux-6.3
On Thu, 15 Jun 2023 07:55:10 -0400 Neal Becker wrote:
I give nouveau a chance every time I install a new fedora, eventually (2 hours, 2 weeks, it varies) I get a video crash and frozen desktop, then I install the rpmfusion nvidia drivers.
I don't remember how many releases ago nouveau was actually reliable.
On Thu, Jun 15, 2023 at 8:23 AM Tom Horsley horsley1953@gmail.com wrote:
On Thu, 15 Jun 2023 07:55:10 -0400 Neal Becker wrote:
I give nouveau a chance every time I install a new fedora, eventually (2 hours, 2 weeks, it varies) I get a video crash and frozen desktop, then I install the rpmfusion nvidia drivers.
Yeah the akmods MOSTLY worked fine. Sometimes I would have to rm -f the package and let it rebuild for some reason and occasionally builds would fail. Not a good end user experience especially if you're not that technical.
I switched to AMD and for the most part it's just "worked". Previously with a RX580 and now with a RX 6550XT.
Other than the crazy graphics card prices, I have no regrets and have no plans to switch back.
Thanks, Richard
On Thu, 15 Jun 2023 10:00:20 -0400 Tom Horsley wrote:
On Thu, 15 Jun 2023 08:45:38 -0500 Richard Shaw wrote:
Yeah the akmods MOSTLY worked fine.
I never had any problems as long as I waited for the module build to finish after installing new kernel before I rebooted.
+1 but I suggested recently a "bad hack" to fix that:
https://bugzilla.redhat.com/show_bug.cgi?id=2011120#c21
On Thu, Jun 15, 2023 at 10:23 AM Tom Horsley horsley1953@gmail.com wrote:
On Thu, 15 Jun 2023 07:55:10 -0400 Neal Becker wrote:
I give nouveau a chance every time I install a new fedora, eventually (2 hours, 2 weeks, it varies) I get a video crash and frozen desktop, then I install the rpmfusion nvidia drivers.
I don't remember how many releases ago nouveau was actually reliable.
You can't expect perfection from reverse engineering, but open source means you get the benefit of "given* enough* eyeballs, all bugs are shallow".
The previous problem I had was about a year ago caused by a simple mistake. A patch was already available by the time I encountered the problem. The current issue has been difficult to pin down.
From https://gitlab.freedesktop.org/drm/nouveau/-/issues/213: 2 weeks ago:
A post at https://lore.kernel.org/nouveau/CACrD=+-DUomkWxe0X5M5vMFS_JijjPGNqVXuq+qimie... has what seems to be a very plausible explanation for the cause of the problem, identifies and analyzes the source code responsible, and provides patches inline and via links. Can these be reviewed and if acceptable merged into the project?
This doesn't solve the issue, but today Dave Airlie posted:
0001-nouveau-fix-client-work-fence-deletion-race.patch https://gitlab.freedesktop.org/drm/nouveau/uploads/150dc8a040dc18aee72fa12d7c506bc3/0001-nouveau-fix-client-work-fence-deletion-race.patch: "This seems to have existed for ever but is now more apparant[SIC]" It is sad how many people switch to proprietary drivers or change distros rather than helping pin down the conditions that trigger a bug and then helping test proposed fixes.