3:43 a.m.
Hi,
When we issue the command "sudo dnf upgrade" and it updates the
nvidia drivers, does the update of those drivers remove them from memory
and load the nouveau drivers?
I'm trying to understand why after doing the update a html 5 game
that requires hardware acceleration to run complained that hardware
acceleration was needed even though the browser was configured to use
hardware acceleration if available, but after a reboot the game then ran
fine in the browser.
regards,
Steve
4:13 a.m.
Hi.
On Sun, 25 Jun 2023 18:43:27 +1000 Stephen Morris wrote:
When we issue the command "sudo dnf upgrade" and it
updates the
nvidia drivers, does the update of those drivers remove them from memory
and load the nouveau drivers?
The kernel drivers no. They are most probably in use, for example by Xorg (if
you use Xorg) and cannot thus be unloaded / reloaded.
I'm trying to understand why after doing the update a html 5
game
that requires hardware acceleration to run complained that hardware
acceleration was needed even though the browser was configured to use
hardware acceleration if available, but after a reboot the game then ran
fine in the browser.
During the upgrade, the Xorg nvidia drivers may have been updated. Example:
/usr/lib64/xorg/modules/drivers/nvidia_drv.so
/usr/lib64/xorg/modules/extensions/libglxserver_nvidia.so
If your application start after the upgrade or dynamically link those drivers
it may fail due to mismatched version with the kernel modules.
You may see something like that in the journal:
NVRM: API mismatch: the client has the version 410.79, but
NVRM: this kernel module has the version 415.25. Please
NVRM: make sure that this kernel module and all NVIDIA driver
NVRM: components have the same version.
--
francis
7:20 a.m.
On Sun, Jun 25, 2023 at 5:43 AM Stephen Morris <samorris(a)netspace.net.au>
wrote:
Hi,
When we issue the command "sudo dnf upgrade" and it updates the
nvidia drivers, does the update of those drivers remove them from memory
and load the nouveau drivers?
Nvidia updates can be messy. Did you reboot after the dnf upgrade?
It can take several minutes of background processing to prepare the nvidia
drivers, so it is recommended to wait 5 minutes after running "dnf upgrade"
before rebooting. If you boot before the nvidia drivers are installed the
system
may use the older nvidea drivers or fall back to nouveau (maybe depending
on
how far the update progressed before you rebooted). If you didn't reboot,
the
system should continue running the old nvidia drivers until you reboot.
I'm trying to understand why after doing the update a html 5
game
that requires hardware acceleration to run complained that hardware
acceleration was needed even though the browser was configured to use
hardware acceleration if available, but after a reboot the game then ran
fine in the browser.
You should check the version of the nvidea drivers you are currently using.
If you don't want to wait 5 minutes there are ways to determine that the
installation
has finished, e.g, using journalctl.
--
George N. White III
12:47 p.m.
On 25/06/2023 13:20, George N. White III wrote:
You should check the version of the nvidea drivers you are currently
using.
If you don't want to wait 5 minutes there are ways to determine that
the installation
has finished, e.g, using journalctl.
The way I use to figure out its safe to reboot is to check for an
running jobs using:
systemctl list-jobs
That will show the akmods service running after you do the dnf update.
Once list-jobs is empty you can reboot.
I have that scripted into into code I use to update and reboot my fedora
machines.
Barry
3:07 a.m.
On 26/6/23 03:47, Barry Scott wrote:
On 25/06/2023 13:20, George N. White III wrote:
> You should check the version of the nvidea drivers you are currently
> using.
> If you don't want to wait 5 minutes there are ways to determine that
> the installation
> has finished, e.g, using journalctl.
The way I use to figure out its safe to reboot is to check for an
running jobs using:
systemctl list-jobs
That will show the akmods service running after you do the dnf update.
Once list-jobs is empty you can reboot.
I have that scripted into into code I use to update and reboot my
fedora machines.
Barry
Thankyou for the responses everyone. I'm using the kmod and akmod nvidia
drivers from the rpmfusion repositories and I didn't do a reboot after
the upgrade, I accessed an email containing a link into one of the games
I play through firefox, but it would not run because it could believed
hardware acceleration was disabled, and I know hardware acceleration for
this game doesn't work with the nouveau drivers.
I was just expecting the kmod/akmod nvidia drivers the system was using
when I did the upgrade would still be being used until I rebooted, but
that seemed to not be the case.
regards,
Steve
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
5:17 a.m.
On 26 Jun 2023, at 09:08, Stephen Morris
<samorris(a)netspace.net.au> wrote:
I was just expecting the kmod/akmod nvidia drivers the system was using when I did the
upgrade would still be being used until I rebooted, but that seemed to not be the case.
The upgrade does not do anything to the already loaded kernel modules.
You must reboot to be able to use the new drivers.
Until then the system uses the old, already loaded, drivers.
Maybe there is user mode code that was upgraded that caused the issue?
Barry
Barry
3:45 a.m.
On 26/6/23 20:17, Barry wrote:
> On 26 Jun 2023, at 09:08, Stephen Morris <samorris(a)netspace.net.au> wrote:
>
> I was just expecting the kmod/akmod nvidia drivers the system was using when I did
the upgrade would still be being used until I rebooted, but that seemed to not be the
case.
The upgrade does not do anything to the already loaded kernel modules.
You must reboot to be able to use the new drivers.
Until then the system uses the old, already loaded, drivers.
Maybe there is user mode code that was upgraded that caused the issue?
Barry
Thanks Barry, that could have been the case but I'm not aware of any
component like that, but that doesn't mean there isn't.
regards,
Steve
Barry
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
5:33 a.m.
Hi.
On Wed, 28 Jun 2023 18:45:51 +1000 Stephen Morris wrote:
On 26/6/23 20:17, Barry wrote:
> Maybe there is user mode code that was upgraded that caused the
issue?
Thanks Barry, that could have been the case but I'm not aware of
any
component like that, but that doesn't mean there isn't.
As I said, in
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
During the upgrade, the Xorg nvidia drivers may have been updated. Example:
/usr/lib64/xorg/modules/drivers/nvidia_drv.so
/usr/lib64/xorg/modules/extensions/libglxserver_nvidia.so
This is user mode code yes.
--
Francis
8:32 p.m.
On 28/6/23 20:33, Francis.Montagnac(a)inria.fr wrote:
Hi.
On Wed, 28 Jun 2023 18:45:51 +1000 Stephen Morris wrote:
> On 26/6/23 20:17, Barry wrote:
>> Maybe there is user mode code that was upgraded that caused the issue?
> Thanks Barry, that could have been the case but I'm not aware of any
> component like that, but that doesn't mean there isn't.
As I said, in
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
During the upgrade, the Xorg nvidia drivers may have been updated. Example:
/usr/lib64/xorg/modules/drivers/nvidia_drv.so
/usr/lib64/xorg/modules/extensions/libglxserver_nvidia.so
This is user mode code yes.
Does this mean that these drivers are replaced and accessed on the fly
but the associated kernel modules do not become active until after a reboot?
If that is the case, and that mismatch is causing the browser html 5
game to think hardware acceleration is not available, how does anything
that requires hardware acceleration to function properly ever work after
an update?
regards,
Steve
9:36 p.m.
On Sat, 2023-07-01 at 11:32 +1000, Stephen Morris wrote:
Does this mean that these drivers are replaced and accessed on the
fly
but the associated kernel modules do not become active until after a reboot?
That's generally the case. Various library updates can only be used
after ones in memory are purged, and a reboot can be the only way to
achieve that.
For certain module updates, they're not even a binary install. They're
compiled on your computer. For thinks like akmods, that was somewhere
in the boot-up process. I think some things, now, compile somewhere in
the shutdown process before a reboot. Either way, there's a delay you
need to wait for, and interrupting it causes some chaos. Made all the
more harder by there being little indication on-screen what's going on,
and some people will hard reset in the middle of things thinking the
computer has crashed.
If that is the case, and that mismatch is causing the browser html 5
game to think hardware acceleration is not available, how does anything
that requires hardware acceleration to function properly ever work after
an update?
That is a problem that just about requires a reboot.
--
uname -rsvp
Linux 3.10.0-1160.92.1.el7.x86_64 #1 SMP Tue Jun 20 11:48:01 UTC 2023 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
306
days inactive
312
days old
9 comments
6 participants
participants (6)
-
Barry -
Barry Scott
-
Francis.Montagnac＠inria.fr -
George N. White III -
Stephen Morris -
Tim