Re: nvidia problem F37->F38 update

On Sat, May 6, 2023 at 4:04 AM Barry wrote: > > > > On 5 May 2023, at 21:48, Jeffrey Walton wrote: > > > > On Fri, May 5, 2023 at 4:04 PM Tim via users > > wrote: > >> > >> Tim: > Are you falling foul of the recent Gnome change that puts a machine > to sleep if it considers that it's

Re: nvidia problem F37->F38 update

> On 5 May 2023, at 21:48, Jeffrey Walton wrote: > > On Fri, May 5, 2023 at 4:04 PM Tim via users > wrote: >> >> Tim: Are you falling foul of the recent Gnome change that puts a machine to sleep if it considers that it's been idle for about 15 minutes? One of the all-tim

Re: nvidia problem F37->F38 update

On Fri, May 5, 2023 at 4:04 PM Tim via users wrote: > > Tim: > >> Are you falling foul of the recent Gnome change that puts a machine > >> to sleep if it considers that it's been idle for about 15 minutes? > >> > >> One of the all-time *DUMB* moves by Gnome. > > George N. White III: > > Not at all

Re: nvidia problem F37->F38 update

Tim: >> Are you falling foul of the recent Gnome change that puts a machine >> to sleep if it considers that it's been idle for about 15 minutes? >> >> One of the all-time *DUMB* moves by Gnome. George N. White III: > Not at all.  Large organizations are trying to reduce power > consumption by wo

Re: nvidia problem F37->F38 update

On Thu, May 4, 2023 at 6:50 PM Todd Zullinger wrote: > Tim via users wrote: > > On Thu, 2023-05-04 at 16:20 -0400, Neal Becker wrote: > > > >> I may have another problem but time will tell (running on the newer > >> kernel connecting via ssh several times I've walked away and then the > >> machin

Re: nvidia problem F37->F38 update

On Thu, May 4, 2023 at 5:22 PM Neal Becker wrote: > > > On Thu, May 4, 2023 at 3:09 PM Tim Evans wrote: > >> On 5/4/23 14:37, Neal Becker wrote: >> > Just updated my server F37->F38. The display doesn't start (black >> > screen after boot). >> > >> > journalctl shows many messages like: >> > >>

Re: nvidia problem F37->F38 update

On 05/04/2023 04:13 PM, Neal Becker wrote: This is used as a server and only usually accessed remotely. In that case, why have a GUI active at all unless you're on site? Having it boot to a CLI eliminates the problem, doesn't it? ___ users mailing

Re: nvidia problem F37->F38 update

On 5/4/23 15:14, Neal Becker wrote: On Thu, May 4, 2023 at 6:13 PM Neal Becker > wrote: On Thu, May 4, 2023 at 5:50 PM Todd Zullinger mailto:t...@pobox.com>> wrote: This doesn't affect Fedora Server, so if the system is only used as a server, ins

Re: nvidia problem F37->F38 update

On Thu, May 4, 2023 at 6:13 PM Neal Becker wrote: > > > On Thu, May 4, 2023 at 5:50 PM Todd Zullinger wrote: > >> Tim via users wrote: >> > On Thu, 2023-05-04 at 16:20 -0400, Neal Becker wrote: >> > >> >> I may have another problem but time will tell (running on the newer >> >> kernel connecting

Re: nvidia problem F37->F38 update

On Thu, May 4, 2023 at 5:50 PM Todd Zullinger wrote: > Tim via users wrote: > > On Thu, 2023-05-04 at 16:20 -0400, Neal Becker wrote: > > > >> I may have another problem but time will tell (running on the newer > >> kernel connecting via ssh several times I've walked away and then the > >> machin

Re: nvidia problem F37->F38 update

Tim via users wrote: > On Thu, 2023-05-04 at 16:20 -0400, Neal Becker wrote: > >> I may have another problem but time will tell (running on the newer >> kernel connecting via ssh several times I've walked away and then the >> machine is nonresponsive to ping, have to force power cycle to >> recove

Re: nvidia problem F37->F38 update

On Thu, 2023-05-04 at 16:20 -0400, Neal Becker wrote: > I may have another problem but time will tell (running on the newer > kernel connecting via ssh several times I've walked away and then the > machine is nonresponsive to ping, have to force power cycle to > recover.) Are you falling foul of

Re: nvidia problem F37->F38 update

On Thu, May 4, 2023 at 3:09 PM Tim Evans wrote: > On 5/4/23 14:37, Neal Becker wrote: > > Just updated my server F37->F38. The display doesn't start (black > > screen after boot). > > > > journalctl shows many messages like: > > > > May 04 14:32:00 nbecker8 kernel: nouveau :01:00.0: bus: MMI

Re: nvidia problem F37->F38 update

On 5/4/23 14:37, Neal Becker wrote: Just updated my server F37->F38.  The display doesn't start (black screen after boot). journalctl shows many messages like: May 04 14:32:00 nbecker8 kernel: nouveau :01:00.0: bus: MMIO read of FAULT at 616330 [ PRIVRING ] nouveau?  This was r

Re: nvidia problem F37->F38 update

On 05/04/2023 12:37 PM, Neal Becker wrote: nouveau?  This was running nvidia driver before the update (from rpmfusion). Any ideas? Do you run kmod-nvidia or akmod? If the former, the appropriate kmod might not be ready yet. Just boot into the previous kernel, and stay there until the new k

Re: nvidia problem F37->F38 update

On Thu, May 4, 2023 at 2:38 PM Neal Becker wrote: > > Just updated my server F37->F38. The display doesn't start (black screen > after boot). > > journalctl shows many messages like: > > May 04 14:32:00 nbecker8 kernel: nouveau :01:00.0: bus: MMIO read of > FAULT at 616330 [ PRIVRI

nvidia problem F37->F38 update

Just updated my server F37->F38. The display doesn't start (black screen after boot). journalctl shows many messages like: May 04 14:32:00 nbecker8 kernel: nouveau :01:00.0: bus: MMIO read of FAULT at 616330 [ PRIVRING ] nouveau? This was running nvidia driver before the update (f