Re: DMESG Messages after Sudo DNF Upgrade

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

>      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.

-- 
francis
-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux