Hi,
during the last update via the CVP the following part is received:
https://prnt.sc/s-YC2zPIZkIF
which is part of the whole message.. .Other updates go through without problems...
BR
Venty
There is nothing at your link that display's :-\
Updates usually happen around 0300, and don't show in the control panel while they are updating.
Did you do this update manually, because even that just give a spinning circle, then you have to manually restart the cpwsrv service.
Quote from: Starburst on October 18, 2025, 08:54:05 PM
There is nothing at your link that display's :-\
Updates usually happen around 0300, and don't show in the control panel while they are updating.
Did you do this update manually, because even that just give a spinning circle, then you have to manually restart the cpwsrv service.
Hi,
sorry, this is the image...:
https://prnt.sc/7BlUhvTLOoBl
...several times when updating I get this...
BR
Venty
I don't see that error on AL8. You could try setting install_weak_deps=False in /etc/dnf/dnf.conf
Quote from: overseer on October 19, 2025, 12:56:52 PM
I don't see that error on AL8. You could try setting install_weak_deps=False in /etc/dnf/dnf.conf
https://prnt.sc/Bu91kkLy-Aij ???
Do you have Rocky or AL 9.6 installed?
Are you doing BIOS or UEFI boot?
Quote from: Starburst on October 20, 2025, 11:04:19 PM
Do you have Rocky or AL 9.6 installed?
Are you doing BIOS or UEFI boot?
Hi,
the installation is AL 9.6...
BR
Venty
Run:
depmod -a
Should take scare of the notification.
Quote from: Starburst on October 22, 2025, 01:30:14 AM
Run:
depmod -a
Should take scare of the notification.
Should take scare of the notification. - ?!?
typo -- "Should take care of the notification."
It's almost Halloween here in the US.
So either works. ;D
All you should have to do is run
depmod -a
And any future kernel updates should not give an error.
Quote from: Starburst on October 23, 2025, 11:17:50 AM
It's almost Halloween here in the US.
So either works. ;D
All you should have to do is run
depmod -a
And any future kernel updates should not give an error.
but... https://prnt.sc/WikTePoeV2aL
BR
Venty
I would think you could just do:
mkdir -p /lib/modules/5.14.0-570.55.1.el9_6.x86_64/weak-updates/
and be done with fretting about the warning.
On my system, I have three different dir versions in /lib/modules, but the newer versions of the dirs's weak-updates subdirs just contain symlinks that point to the contents of the oldest dir's weak-updates dir.