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

Re: NVIDIA Problem

On Wed, 01 Apr 2020 22:32:47 +0100 Patrick O'Callaghan wrote: > On Wed, 2020-04-01 at 18:49 +0200, t_pol wrote: > > Yes I have ffmpeg and No I don't have vlcextras. (I'll install it > > right away). Yes I have rpmfusion repos but the driver has been > > installed from official NVIDIA site. > > A

Re: NVIDIA Problem

On Wed, 2020-04-01 at 18:49 +0200, t_pol wrote: > Yes I have ffmpeg and No I don't have vlcextras. (I'll install it right away). > Yes I have rpmfusion repos but the driver has been installed from > official NVIDIA site. As has been noted, the recommendation is to uninstall the "official" Nvidia p

Re: NVIDIA Problem

On Wed, 1 Apr 2020 08:52:21 -0300 "George N. White III" wrote: > On Tue, 31 Mar 2020 at 23:25, t_pol wrote: > > > Hi list, > > > > I've decided to switch from nouveau to Nvidia drivers. > > Everythings seems ok but I cannot play anymore h24 videos. > > Both VLC & SMPLAYER just play sounds but

Re: NVIDIA Problem

On Tue, 31 Mar 2020 at 23:25, t_pol wrote: > Hi list, > > I've decided to switch from nouveau to Nvidia drivers. > Everythings seems ok but I cannot play anymore h24 videos. > Both VLC & SMPLAYER just play sounds but no video. > > this is the error message: > > Codec not supported: > VLC could no

Re: NVIDIA Problem

Try this: https://rpmfusion.org/Howto/NVIDIA On 3/31/20 9:22 PM, t_pol wrote: On Tue, 31 Mar 2020 21:54:25 -0500 Richard Shaw wrote: On Tue, Mar 31, 2020 at 9:25 PM t_pol wrote: Hi list, I've decided to switch from nouveau to Nvidia drivers. How did you install the nvidia drivers? D

Re: NVIDIA Problem

On Tue, 31 Mar 2020 21:54:25 -0500 Richard Shaw wrote: > On Tue, Mar 31, 2020 at 9:25 PM t_pol wrote: > > > Hi list, > > > > I've decided to switch from nouveau to Nvidia drivers. > > > > How did you install the nvidia drivers? Did you download them from > Nvidia or use the RPM Fusion akmod? I

Re: NVIDIA Problem

On Tue, Mar 31, 2020 at 9:25 PM t_pol wrote: > Hi list, > > I've decided to switch from nouveau to Nvidia drivers. > How did you install the nvidia drivers? Did you download them from Nvidia or use the RPM Fusion akmod? I have not had an issue when running the RPM Fusion packages. Thanks, Richa

NVIDIA Problem

Hi list, I've decided to switch from nouveau to Nvidia drivers. Everythings seems ok but I cannot play anymore h24 videos. Both VLC & SMPLAYER just play sounds but no video. this is the error message: Codec not supported: VLC could not decode the format "h264" (H264 - MPEG-4 AVC (part 10)) Befo

Re: gnome, maybe fedora, or maybe nvidia problem

On Tue, 1 Mar 2016 06:31:37 -0600 sb...@mississippi.com wrote: > Anyone know of what I might do to get rid of this annoyance? A KVM switch always suggests problems with EDID info from monitors being forgotten. See the kernel docs at: https://www.kernel.org/doc/Documentation/EDID/HOWTO.txt Ther

Re: gnome, maybe fedora, or maybe nvidia problem

On 03/01/16 20:31, sb...@mississippi.com wrote: > Have an issue that I've been living with for awhile now, more annoyance but > I'd like to find a fix for it. > > I have an up to date Fedora 23 install, the system has an nvidia quadro K420 > card and I'm (at the moment) running the NVIDIA-Linux

gnome, maybe fedora, or maybe nvidia problem

Have an issue that I've been living with for awhile now, more annoyance but I'd like to find a fix for it. I have an up to date Fedora 23 install, the system has an nvidia quadro K420 card and I'm (at the moment) running the NVIDIA-Linux-x86_64-361.28.run drivers locally compiled. I have a dua

Re: Nvidia problem after kernel 2.6.32.9-70.fc12 update

On Friday 12 March 2010, Marcel Rieux wrote: > On Thu, Mar 11, 2010 at 4:02 AM, Dario Lesca wrote: > > The nvidia module is missing. > > I haven't updated yet because I'm still waiting for kmod-nvidia, > the module needed by the kernel for nvidia cards (proprietary > driver only, I'm not sure. I

Re: Nvidia problem after kernel 2.6.32.9-70.fc12 update

Il giorno gio, 11/03/2010 alle 17.51 -0500, Marcel Rieux ha scritto: > Once again NVIDIA drivers are creating a mess. Go to Google, enter > 2.6.32.9-70 and fedora, you'll see. This should not happen. The kernel's dependencies should be linked with any additional

Re: Nvidia problem after kernel 2.6.32.9-70.fc12 update

Howdy. Just to add my $0.02, we've got a couple of dual-monitor systems around here, both running Fedora 12, 64-bit. We're using akmod-nvidia on both systems, and both systems are fully patched and rebooted with the latest kernel. Our experience is that the video works flawlessly on both syste

Re: Nvidia problem after kernel 2.6.32.9-70.fc12 update

On Thu, Mar 11, 2010 at 4:02 AM, Dario Lesca wrote: > The nvidia module is missing. I haven't updated yet because I'm still waiting for kmod-nvidia, the module needed by the kernel for nvidia cards (proprietary driver only, I'm not sure. I suppose so,) Now, when I do "yum update", kmod-nvidia is

Re: Nvidia problem after kernel 2.6.32.9-70.fc12 update

On Thu, Mar 11, 2010 at 09:16:55AM -0600, Andre Goree wrote: > I am also having these issues after the recent kernel update. I even > installed the up-to-date akmod-nvidia package, to no end. > > I was able to boot into the previous kernel and it worked though, so > that is my temporary workaro

Re: Nvidia problem after kernel 2.6.32.9-70.fc12 update

Doron Bar Zeev wrote: > > > I have the same problem ( X won't startup ) with the new kernel. > There are these lines in /var/log/messages that seem to indicate what > serguei wrote: > > Mar 11 16:39:17 DoronPc kernel: NVRM: this kernel module has the version > 190.53. Please > Mar 11 16:39:17

Re: Nvidia problem after kernel 2.6.32.9-70.fc12 update

I have the same problem ( X won't startup ) with the new kernel. There are these lines in /var/log/messages that seem to indicate what serguei wrote: Mar 11 16:39:17 DoronPc kernel: NVRM: this kernel module has the version 190.53. Please Mar 11 16:39:17 DoronPc kernel: NVRM: make sure that this k

Re: Nvidia problem after kernel 2.6.32.9-70.fc12 update

On Thursday 11 March 2010, Dario Lesca wrote: > This morning, after kernel + nvidia driver update I get this error: > > Mar 11 08:46:45 lesca kernel: NVRM: API mismatch: the client has > > the version 195.36.08, but Mar 11 08:46:45 lesca kernel: NVRM: > > this kernel module has the version 190.53.

Nvidia problem after kernel 2.6.32.9-70.fc12 update

This morning, after kernel + nvidia driver update I get this error: > Mar 11 08:46:45 lesca kernel: NVRM: API mismatch: the client has the version > 195.36.08, but > Mar 11 08:46:45 lesca kernel: NVRM: this kernel module has the version > 190.53. Please > Mar 11 08:46:45 lesca kernel: NVRM: mak