*From:* francis.montag...@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...@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 are
already 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
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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
