Hi, With the systemd message below, are they known issues that are already in hand, or do I need to raise a bug report? With the NVRM messages, I'm assuming they are because the update, as the last thing done, produced error messages about something under a /run path getting "permission denied" (I was running the upgrade under sudo and I don't have the exact message and /var/log/dnf.log - dnf.log.4 nor /var/log/dnf.rpm.log - dnf.rpm.log.4 have the log for the dnf process I just did), but why did multiples of that message occur. The update did upgrade akmod-nvidia from 570.153.02 to 575.57.08 and there were several corresponding Xorg nvidia modules upgraded as well, but I was expecting those to not be activated until I rebooted, is that not the case?
[ 2110.087680] systemd-sysv-generator[24541]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file, automatically generating a unit file for compatibility. [ 2110.087685] systemd-sysv-generator[24541]: Please update package to include a native systemd unit file. [ 2110.087687] systemd-sysv-generator[24541]: ! This compatibility logic is deprecated, expect removal soon. ! [ 2110.087707] systemd-sysv-generator[24541]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file, automatically generating a unit file for compatibility. [ 2110.087709] systemd-sysv-generator[24541]: Please update package to include a native systemd unit file. [ 2110.087711] systemd-sysv-generator[24541]: ! This compatibility logic is deprecated, expect removal soon. ! [ 3231.490969] NVRM: API mismatch: the client has the version 575.57.08, but NVRM: this kernel module has the version 570.153.02. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version.
regards, Steve
*From:* Stephen Morris steve.morris.au@gmail.com
*Sent:* Tuesday, 10 June 2025 at 08:18 UTC+10
*To:* fedora users@lists.fedoraproject.org
*Cc:* steve.morris.au@gmail.com
*Subject:* DMESG Messages after Sudo DNF Upgrade
Hi, With the systemd message below, are they known issues that are already in hand, or do I need to raise a bug report? With the NVRM messages, I'm assuming they are because the update, as the last thing done, produced error messages about something under a /run path getting "permission denied" (I was running the upgrade under sudo and I don't have the exact message and /var/log/dnf.log - dnf.log.4 nor /var/log/dnf.rpm.log - dnf.rpm.log.4 have the log for the dnf process I just did), but why did multiples of that message occur. The update did upgrade akmod-nvidia from 570.153.02 to 575.57.08 and there were several corresponding Xorg nvidia modules upgraded as well, but I was expecting those to not be activated until I rebooted, is that not the case?
[ 2110.087680] systemd-sysv-generator[24541]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file, automatically generating a unit file for compatibility. [ 2110.087685] systemd-sysv-generator[24541]: Please update package to include a native systemd unit file. [ 2110.087687] systemd-sysv-generator[24541]: ! This compatibility logic is deprecated, expect removal soon. ! [ 2110.087707] systemd-sysv-generator[24541]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file, automatically generating a unit file for compatibility. [ 2110.087709] systemd-sysv-generator[24541]: Please update package to include a native systemd unit file. [ 2110.087711] systemd-sysv-generator[24541]: ! This compatibility logic is deprecated, expect removal soon. ! [ 3231.490969] NVRM: API mismatch: the client has the version 575.57.08, but NVRM: this kernel module has the version 570.153.02. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version.
Sorry, I forgot to mention that this is on F42.
regards, Steve
regards, Steve
Hi
On Tue, 10 Jun 2025 08:18:22 +1000 Stephen Morris wrote:
With the systemd message below, are they known issues that arealready in hand, or do I need to raise a bug report?
No, but your machine is using I guess an old version of livesys.
The current one in F42 is provided by the livesys-scripts RPM that defines properly the service as a systemd unit file,
I suggest to suppress the RPM defining /etc/rc.d/init.d/livesys (see rpm -qf /etc/rc.d/init.d/livesys) and install if you need it the livesys-scripts F42 RPM.
With the NVRM messages, I'm assuming they are because the update,as the last thing done, produced error messages about something under a /run path getting "permission denied"
I don;t think so. See below.
(I was running the upgrade under sudo and I don't have the exact message and /var/log/dnf.log - dnf.log.4 nor /var/log/dnf.rpm.log - dnf.rpm.log.4 have the log for the dnf process I just did),
dnf is currently dnf5, but dnf4 still exits. The logs of dnf are in /var/log/dnf5.log* :-(
but why did multiples of that message occur. The update did upgrade akmod-nvidia from 570.153.02 to 575.57.08 and there were several corresponding Xorg nvidia modules upgraded as well, but I was expecting those to not be activated until I rebooted, is that not the case?
I think that some no X11 programs like nvidia-settings produces that.
[ 2110.087680] systemd-sysv-generator[24541]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file,
...
[ 3231.490969] NVRM: API mismatch: the client has the version 575.57.08, but NVRM: this kernel module has the version 570.153.02. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version.
*From:* Francis.Montagnac@inria.fr
*Sent:* Wednesday, 11 June 2025 at 00:54 UTC+10
*To:* Community support for Fedora users users@lists.fedoraproject.org
*Cc:* steve.morris.au@gmail.com
*Subject:* RE: DMESG Messages after Sudo DNF Upgrade
Hi
On Tue, 10 Jun 2025 08:18:22 +1000 Stephen Morris wrote:
With the systemd message below, are they known issues that arealready in hand, or do I need to raise a bug report?
No, but your machine is using I guess an old version of livesys.
The current one in F42 is provided by the livesys-scripts RPM that defines properly the service as a systemd unit file,
I suggest to suppress the RPM defining /etc/rc.d/init.d/livesys (see rpm -qf /etc/rc.d/init.d/livesys) and install if you need it the livesys-scripts F42 RPM.
Thanks Francis. Livesys could be old, this instance of Fedora started life as F38, and has been upgraded to F42 through all the intermediate versions when they were announced as being stable available versions. If livesys is the issue, that raises the question of why was it not upgraded when the upgrades to each new version was done? Just relative to livesys as well, I ran sudo rpm -qf /etc/rc.d/init.d/livesys and that came back with the message that "file /etc/rc.d/init.d/livesys is not owned by any package".
With the NVRM messages, I'm assuming they are because the update,as the last thing done, produced error messages about something under a /run path getting "permission denied"
I don;t think so. See below.
(I was running the upgrade under sudo and I don't have the exact message and /var/log/dnf.log - dnf.log.4 nor /var/log/dnf.rpm.log - dnf.rpm.log.4 have the log for the dnf process I just did),
dnf is currently dnf5, but dnf4 still exits. The logs of dnf are in /var/log/dnf5.log* :-(
Thankyou, I did look at the wrong log files, I missed the dnf5 ones when I looked. But having looked at the relevant dnf5 log file I can find the error message displayed when I did the update.
but why did multiples of that message occur. The update did upgrade akmod-nvidia from 570.153.02 to 575.57.08 and there were several corresponding Xorg nvidia modules upgraded as well, but I was expecting those to not be activated until I rebooted, is that not the case?
I think that some no X11 programs like nvidia-settings produces that.
[ 2110.087680] systemd-sysv-generator[24541]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file,
...
[ 3231.490969] NVRM: API mismatch: the client has the version 575.57.08, but NVRM: this kernel module has the version 570.153.02. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version.
I've booted my machine this morning after putting on the update and the graphic contrast in the desktop background is horrendous, but this is also normal the last few times the nvidia drivers have been updated, but it reverts to normal with time. I have also just done another update which put on a host of mesa packages as the only updates, so I'll see if the display is back to normal on the next reboot.
regards, Steve
On Tue, Jun 10, 2025 at 6:04 PM Stephen Morris steve.morris.au@gmail.com wrote:
From: Francis.Montagnac@inria.fr
Sent: Wednesday, 11 June 2025 at 00:54 UTC+10
To: Community support for Fedora users users@lists.fedoraproject.org
Cc: steve.morris.au@gmail.com
Subject: RE: DMESG Messages after Sudo DNF Upgrade
Hi
On Tue, 10 Jun 2025 08:18:22 +1000 Stephen Morris wrote:
With the systemd message below, are they known issues that arealready in hand, or do I need to raise a bug report?
No, but your machine is using I guess an old version of livesys.
The current one in F42 is provided by the livesys-scripts RPM that defines properly the service as a systemd unit file,
I suggest to suppress the RPM defining /etc/rc.d/init.d/livesys (see rpm -qf /etc/rc.d/init.d/livesys) and install if you need it the livesys-scripts F42 RPM.
Thanks Francis. Livesys could be old, this instance of Fedora started life as F38, and has been upgraded to F42 through all the intermediate versions when they were announced as being stable available versions. If livesys is the issue, that raises the question of why was it not upgraded when the upgrades to each new version was done? Just relative to livesys as well, I ran sudo rpm -qf /etc/rc.d/init.d/livesys and that came back with the message that "file /etc/rc.d/init.d/livesys is not owned by any package".
livesys is used on the livecd boot ISOs (I believe) and may not actually be owned by anything, but get copied across when installing from a livecd. Several of my systems have given those messages from time to time and I have just ignored them for the most part.
The nvidia errors is because you upgrade to a new nvidia driver and probably did not reboot. So the loaded nvidia driver is a slightly older version than the nvidia part being loaded in X/Wayland and it reports this issue.
*From:* Roger Heflin rogerheflin@gmail.com
*Sent:* Wednesday, 11 June 2025 at 09:11 UTC+10
*To:* Community support for Fedora users users@lists.fedoraproject.org
*Cc:* Francis.Montagnac@inria.fr
*Subject:* RE: DMESG Messages after Sudo DNF Upgrade
On Tue, Jun 10, 2025 at 6:04 PM Stephen Morris steve.morris.au@gmail.com wrote:
From:Francis.Montagnac@inria.fr
Sent: Wednesday, 11 June 2025 at 00:54 UTC+10
To: Community support for Fedora usersusers@lists.fedoraproject.org
Cc:steve.morris.au@gmail.com
Subject: RE: DMESG Messages after Sudo DNF Upgrade
Hi
On Tue, 10 Jun 2025 08:18:22 +1000 Stephen Morris wrote:
With the systemd message below, are they known issues that arealready in hand, or do I need to raise a bug report?
No, but your machine is using I guess an old version of livesys.
The current one in F42 is provided by the livesys-scripts RPM that defines properly the service as a systemd unit file,
I suggest to suppress the RPM defining /etc/rc.d/init.d/livesys (see rpm -qf /etc/rc.d/init.d/livesys) and install if you need it the livesys-scripts F42 RPM.
Thanks Francis. Livesys could be old, this instance of Fedora started life as F38, and has been upgraded to F42 through all the intermediate versions when they were announced as being stable available versions. If livesys is the issue, that raises the question of why was it not upgraded when the upgrades to each new version was done? Just relative to livesys as well, I ran sudo rpm -qf /etc/rc.d/init.d/livesys and that came back with the message that "file /etc/rc.d/init.d/livesys is not owned by any package".
livesys is used on the livecd boot ISOs (I believe) and may not actually be owned by anything, but get copied across when installing from a livecd. Several of my systems have given those messages from time to time and I have just ignored them for the most part.
The nvidia errors is because you upgrade to a new nvidia driver and probably did not reboot. So the loaded nvidia driver is a slightly older version than the nvidia part being loaded in X/Wayland and it reports this issue.
Thanks Roger, I thought that might be the issue. I don't normally see those messages in dmesg as I don't normally issue that command after an update, it was just this time I say those messages because I was trying to see why I was getting an "access denied" error on a /run path, but I couldn't find anything.
regards, Steve
*From:* Stephen Morris steve.morris.au@gmail.com
*Sent:* Wednesday, 11 June 2025 at 09:28 UTC+10
*To:* users@lists.fedoraproject.org
*Subject:* RE: DMESG Messages after Sudo DNF Upgrade
*From:* Roger Heflin rogerheflin@gmail.com
*Sent:* Wednesday, 11 June 2025 at 09:11 UTC+10
*To:* Community support for Fedora users users@lists.fedoraproject.org
*Cc:* Francis.Montagnac@inria.fr
*Subject:* RE: DMESG Messages after Sudo DNF Upgrade
On Tue, Jun 10, 2025 at 6:04 PM Stephen Morris steve.morris.au@gmail.com wrote:
From:Francis.Montagnac@inria.fr
Sent: Wednesday, 11 June 2025 at 00:54 UTC+10
To: Community support for Fedora usersusers@lists.fedoraproject.org
Cc:steve.morris.au@gmail.com
Subject: RE: DMESG Messages after Sudo DNF Upgrade
Hi
On Tue, 10 Jun 2025 08:18:22 +1000 Stephen Morris wrote:
With the systemd message below, are they known issues that arealready in hand, or do I need to raise a bug report?
No, but your machine is using I guess an old version of livesys.
The current one in F42 is provided by the livesys-scripts RPM that defines properly the service as a systemd unit file,
I suggest to suppress the RPM defining /etc/rc.d/init.d/livesys (see rpm -qf /etc/rc.d/init.d/livesys) and install if you need it the livesys-scripts F42 RPM.
Thanks Francis. Livesys could be old, this instance of Fedora started life as F38, and has been upgraded to F42 through all the intermediate versions when they were announced as being stable available versions. If livesys is the issue, that raises the question of why was it not upgraded when the upgrades to each new version was done? Just relative to livesys as well, I ran sudo rpm -qf /etc/rc.d/init.d/livesys and that came back with the message that "file /etc/rc.d/init.d/livesys is not owned by any package".
livesys is used on the livecd boot ISOs (I believe) and may not actually be owned by anything, but get copied across when installing from a livecd. Several of my systems have given those messages from time to time and I have just ignored them for the most part.
If the systemd warnings are because livesys hasn't been updated, and with the specified file not being owned by any package, how do I upgrade livesys given that standard system version upgrades haven't refreshed it?
regards, Steve
The nvidia errors is because you upgrade to a new nvidia driver and probably did not reboot. So the loaded nvidia driver is a slightly older version than the nvidia part being loaded in X/Wayland and it reports this issue.
Thanks Roger, I thought that might be the issue. I don't normally see those messages in dmesg as I don't normally issue that command after an update, it was just this time I say those messages because I was trying to see why I was getting an "access denied" error on a /run path, but I couldn't find anything.
regards, Steve
Stephen Morris wrote:
If the systemd warnings are because livesys hasn't been updated, and with the specified file not being owned by any package, how do I upgrade livesys given that standard system version upgrades haven't refreshed it?
You can simply remove those initscripts (IIRC, there are two of them, but it's been a long time since I looked and removed them locally).
If you look at the contents, they don't run on a system that isn't a Live image. They just exit straight way. And now they don't even do that without a warning.
It's vestigial cruft.
P.S.: Please trim your quotes. :)
-
Francis.Montagnac＠inria.fr -
Roger Heflin -
Stephen Morris -
Todd Zullinger