yep clean all and then update appears to have worked.
I got 2 possible gremlins…one for grub2 scriplet failing and the other maybe missing packages relating to network
but I have rebooted OK
and I have ethernet OK
thanks for reading
snip
Transaction Summary
Install 1 Package
Upgrade 27 Packages
snip
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
snip
Upgrading : grub2-efi-2.04-3.znver1 16/55
Upgrading : grub2-2.04-3.znver1 17/55
Running scriptlet: grub2-2.04-3.znver1 17/55
Updating /boot/grub2/locale..
Generating grub configuration file ...
Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
Found background: /boot/grub2/themes/OpenMandriva/terminal_background.png
warning: %triggerin(grub2-2.04-3.znver1) scriptlet failed, exit status 1
Error in <unknown> scriptlet in rpm package grub2
snip
dracut: dracut module 'ifcfg' depends on 'network', which can't be installed
dracut: dracut module 'cifs' depends on 'network', which can't be installed
dracut: dracut module 'nfs' depends on 'network', which can't be installed
Updating /boot/grub2/locale..
Generating grub configuration file ...
Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
Found background: /boot/grub2/themes/OpenMandriva/terminal_background.png
snip
Running scriptlet: grub2-2.04-2.znver1
snip
Generating grub configuration file ...
Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
Found background: /boot/grub2/themes/OpenMandriva/terminal_background.png
Generating grub configuration file ...
Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
Found background: /boot/grub2/themes/OpenMandriva/terminal_background.png
snip
Upgraded:
cpupower-5.5.2-1.znver1 cryptsetup-2.3.0-1.znver1 grub2-2.04-3.znver1
grub2-efi-2.04-3.znver1 kpmcore-4.0.1-2.znver1 lib64EGL_mesa0-19.3.4-1.znver1
lib64GLX_mesa0-19.3.4-1.znver1 lib64cryptsetup12-2.3.0-1.znver1 lib64dri-drivers-19.3.4-1.znver1
lib64dri-drivers-intel-19.3.4-1.znver1 lib64dri-drivers-nouveau-19.3.4-1.znver1 lib64dri-drivers-radeon-19.3.4-1.znver1
lib64dri-drivers-swrast-19.3.4-1.znver1 lib64dri-drivers-virtio-19.3.4-1.znver1 lib64dri-drivers-vmwgfx-19.3.4-1.znver1
lib64gbm1-19.3.4-1.znver1 lib64glapi0-19.3.4-1.znver1 lib64kpmcore8-4.0.1-2.znver1
lib64vdpau-driver-nouveau-19.3.4-1.znver1 lib64vdpau-driver-r300-19.3.4-1.znver1 lib64vdpau-driver-r600-19.3.4-1.znver1
lib64vdpau-driver-radeonsi-19.3.4-1.znver1 lib64vdpau-driver-softpipe-19.3.4-1.znver1 lib64vdpau-drivers-19.3.4-1.znver1
lib64xatracker2-19.3.4-1.znver1 oma-welcome-2.1.23-1.noarch x86_energy_perf_policy-5.5.2-1.znver1
Installed:
kernel-release-desktop-5.5.2-1.znver1
Complete!
dracut: dracut module 'ifcfg' depends on 'network', which can't be installed
dracut: dracut module 'cifs' depends on 'network', which can't be installed
dracut: dracut module 'nfs' depends on 'network', which can't be installed
Those are warning produced by dracut command and you will see them every time dracut runs. dracut will run every time a kernel is installed. They don’t mean anything and are left over from past, those modules would only be used on really ancient computers.
Developers have been asked if they could please remove those warnings but so far they haven’t. No idea why they don’t remove those. But we keep having to explain this over and over.
Now to next part where
What you posted does not show any boot-able entry created by grub2 but I see you snipped the output:
snip
Generating grub configuration file ...
Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
Found background: /boot/grub2/themes/OpenMandriva/terminal_background.png
Generating grub configuration file ...
Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
Found background: /boot/grub2/themes/OpenMandriva/terminal_background.png
snip
The part after that second snip is where we could see if the script actually did what it should or failed. So if you could run this command which will run that script again and post all the output here we could perhaps get this sorted:
So to explain: For each kernel you have installed you should see 2 lines of code like this:
Found linux image: /boot/vmlinuz-5.5.2-desktop-1omv4001
Found initrd image: /boot/initrd-5.5.2-desktop-1omv4001.img
These lines you would only see on a multi-boot system and they are entries for other operating systems on other partitions:
Found OpenMandriva Lx 4.2 (4.2) on /dev/nvme0n1p5
Found OpenMandriva Lx 4.2 (4.2) on /dev/nvme0n1p7
Found OpenMandriva Lx 4.2 (4.2) on /dev/nvme0n1p9
Hoping this is helpful for you and other users. Please let us know what you find on your system and if there is a problem it should be fairly easy to get corrected. Sometimes when a kernel is installed there is a script failure and normally it is corrected by either reinstalling the kernel package or re-running dracut and update-grub2 commands.
Post-edit-FWIW: The command to see what kernel you a using is uname -a. For an updated Rock system likely you would see:
$ uname -a
Linux ben-Lx41-64 5.5.2-desktop-1omv4001 #1 SMP Mon Feb 10 17:03:42 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
I decided to do this first. And IMHO I have now decided to get fussy!
reason is your first command now done as my second command shows
ls -lh /boot
total 127M
-rw-r--r-- 1 root root 223K Jan 28 07:28 config-5.5.0-desktop-1omv4001
-rw-r--r-- 1 root root 223K Feb 11 01:18 config-5.5.2-desktop-1omv4001
drwxr-xr-x 3 root root 4.0K Feb 2 02:13 efi
-rw-r--r-- 1 root root 181K Apr 30 2019 elf-memtest86+
drwxr-xr-x 6 root root 4.0K Mar 15 11:58 grub2
-rw------- 1 root root 51M Mar 12 16:21 initrd-5.5.0-desktop-1omv4001.img
-rw------- 1 root root 48M Mar 15 11:58 initrd-5.5.2-desktop-1omv4001.img
-rw-r--r-- 1 root root 179K Apr 30 2019 memtest.bin
-rw-r--r-- 1 root root 3.0M Nov 28 11:40 microcode.img
-rw-r--r-- 1 root root 331K Jan 28 07:28 symvers-5.5.0-desktop-1omv4001.zst
-rw-r--r-- 1 root root 331K Feb 11 01:18 symvers-5.5.2-desktop-1omv4001.zst
-rw-r--r-- 1 root root 4.4M Jan 28 07:28 System.map-5.5.0-desktop-1omv4001
-rw-r--r-- 1 root root 4.4M Feb 11 01:18 System.map-5.5.2-desktop-1omv4001
-rw-r--r-- 1 root root 7.6M Jan 28 07:28 vmlinuz-5.5.0-desktop-1omv4001
-rw-r--r-- 1 root root 7.6M Feb 11 01:18 vmlinuz-5.5.2-desktop-1omv4001
but the second kernel is not getting into my grub.cfg.
so then I did another update-grub2 with root powers and got this
sudo update-grub2
Updating /boot/grub2/locale..
Generating grub configuration file ...
Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
Found background: /boot/grub2/themes/OpenMandriva/terminal_background.png
so then I search for 5.5.2 get no hits for the following command
true|cat /boot/grub2/grub.cfg | grep 5.5.2
but if I change it to search if true for hits of 5.5.0 I get heaps.
this time a screen shot as it shows up better IMHO
I have reversed the order so you can see no hits for 5.5.2 at bottom of konsole.
Yes that update where grub2 script runs now shows you with normal looking out put for both kernels so you should have boot entries for both in /boot/grub2/grub.cfg and you should be able to boot to both kernels. So this problem is fixed.
Note about your repositories. Normally people just use the main, unsupported, restricted, non-free and the update repos for those 4. All that debug stuff is for developers and is not hardly used in Rock/Lx 4.1. My Rock systems all look like this screen shot:
Also so you and other users know the restricted repos that return 404 Cannot download error don’t have any packages in them. So they are empty and dnf does not have a metadata file to find so it will list those as 404 Cannot download. No worries for those.
@aus9 in view of some of the weird things we have seen with your system you could try to disable all the debug repos and leave only the ones in my screen shot enabled and then do this to maybe straighten out your system (hopefully):
Before I post my output…for my own selfish benefit I looked at the timestamps for files under /etc/yum.d
all are older dates of Mar 13…my install date except this one
-rw-r–r-- 1 root root 10080 Mar 15 13:52 openmandriva-rock-znver1.repo
Is that the correct file to have been adjusted?
IMHO there is still something going on if true. I can upload my contents to a file sharing site if you like but
first here is my command output
sudo dnf clean all && sudo dnf --best --allowerasing distro-sync
[sudo] password for gordon:
60 files removed
OpenMandriva Rock - znver1 1.6 MB/s | 12 MB 00:07
OpenMandriva Rock - znver1 - Updates 50 kB/s | 95 kB 00:01
OpenMandriva Rock - znver1 - Debug 774 kB/s | 4.9 MB 00:06
OpenMandriva Rock - znver1 - Updates - Debug 20 kB/s | 32 kB 00:01
OpenMandriva Rock - znver1 - Testing - Debug 28 kB/s | 53 kB 00:01
OpenMandriva Rock - Unsupported - znver1 - Debug 503 kB/s | 1.7 MB 00:03
OpenMandriva Rock - Unsupported - znver1 - Updates - Debug 3.4 kB/s | 4.3 kB 00:01
OpenMandriva Rock - Unsupported - znver1 - Testing - Debug 4.6 kB/s | 5.8 kB 00:01
OpenMandriva Rock - Restricted - znver1 - Debug 28 kB/s | 45 kB 00:01
OpenMandriva Rock - Restricted - znver1 - Updates - Debug 269 B/s | 344 B 00:01
OpenMandriva Rock - Restricted - znver1 - Testing - Debug 99 B/s | 153 B 00:01
Errors during downloading metadata for repository 'rock-testing-znver1-restricted-debuginfo':
- Status code: 404 for http://abf-downloads.openmandriva.org//rock/repository/znver1/debug_restricted/testing/repodata/repomd.xml (IP: 185.184.176.69)
Error: Failed to download metadata for repo 'rock-testing-znver1-restricted-debuginfo': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
OpenMandriva Rock - Non-free - znver1 - Debug 6.2 kB/s | 7.7 kB 00:01
OpenMandriva Rock - Non-free - znver1 - Updates - Debug 264 B/s | 344 B 00:01
OpenMandriva Rock - Non-free - znver1 - Testing - Debug 99 B/s | 153 B 00:01
Errors during downloading metadata for repository 'rock-testing-znver1-non-free-debuginfo':
- Status code: 404 for http://abf-downloads.openmandriva.org//rock/repository/znver1/debug_non-free/testing/repodata/repomd.xml (IP: 185.184.176.69)
Error: Failed to download metadata for repo 'rock-testing-znver1-non-free-debuginfo': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Ignoring repositories: rock-testing-znver1-restricted-debuginfo, rock-testing-znver1-non-free-debuginfo
Dependencies resolved.
Nothing to do.
Complete!
as you can see rock-testing-znver1-restricted-debuginfo, rock-testing-znver1-non-free-debuginfo are allegedly disabled?
and so should show enabled=0 in the file I named?
but snippets show
[rock-znver1-restricted-debuginfo]
name=“OpenMandriva Rock - Restricted - znver1 - Debug”
…enabled=1
Look I think you get the idea. …Maybe I should grab the file off the usb install media and see if that is the same…or does it suggest
somehow I inherited a dev’s configs?
@aus9 in view of some of the weird things we have seen with your system you could try to disable all the debug repos and leave only the ones in my screen shot enabled and then do this to maybe straighten out your system (hopefully):
Meaning that first you disable all the unnecessary (and possible problem causing) debug repositories and then run that command. Simply running the command won’t change anything.
Second point:
Very important question: So where did you get the ISO file you are using?
Normally when you install OM Lx 4.1/Rock you would have only 2 repositories enabled (and only 2). This is very well and strongly established protocol by our developers. When you first boot into a freshly installed system by default you should have these and only these enabled:
$ dnf repolist
repo id repo name
rock-updates-znver1 OpenMandriva Rock - znver1 - Updates
rock-znver1 OpenMandriva Rock - znver1
If your install media shows any repos enabled beyond those 2 then do not use that install media. Something is really wrong. If immediately after you install OM Lx 4.1 you have any repos enabled besides those 2 something is very wrong.
Third point:
If a user does want maximum availability of software then they could able only the additional repos shown in screen shot in this post. (An exception is that gamers and some other users needing to install 3rd party software may need to also enable a few i686 repos.)
Post-edit: Yes I acknowledge that the situation with repositories in OpenMandriva is confusing to users. However it is of utmost importance that users understand what they are doing and do things in the correct way or there will be issues. Improperly configured repositories left alone for to long will lead to issues that can practically only be resolved by a fresh installation.
Apologies if the above post sounds to much like me ranting. As a QA person with OM the idea that there might be an ISO out there with all those repos enabled and worse that such an ISO might be accessible to users scares me.
