Hi,
Due to a problem with the KDE Plasma update tool, see https://forums.opensuse.org/showthread.php/572534-Possible-Bug-in-Plasma-PackageKit-Updater
I was forced to use zypper for updates. As expected I got a lot of warnings/errors that I couldn’t understand
zypper dup --no-allow-vendor-change
[update ....OK]
[update ....OK]
...
[about 1500 packages...OK]
racut: Executing: /usr/bin/dracut --kver=5.18.15-1-default -f
dracut: dracut module 'systemd-coredump' will not be installed, because command 'coredumpctl' could not be found!
dracut: dracut module 'systemd-coredump' will not be installed, because command '/usr/lib/systemd/systemd-coredump' could not be found!
....
dracut: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found!
dracut: 35network-legacy: Could not find any command of 'dhclient wicked'!
dracut: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found!
...
dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found!
dracut: memstrack is not available
dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng
dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found!
...
dracut: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found!
dracut: 35network-legacy: Could not find any command of 'dhclient wicked'!
dracut: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found!
...
dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found!
dracut: memstrack is not available
dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng
dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found!
dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found!
dracut: *** Including module: systemd ***
...
dracut: *** Including module: dm ***
dracut: Skipping udev rule: 64-device-mapper.rules
dracut: Skipping udev rule: 60-persistent-storage-dm.rules
dracut: Skipping udev rule: 55-dm.rules
dracut: *** Including module: kernel-modules ***
...
dracut: *** Including module: lvm ***
dracut: Skipping udev rule: 64-device-mapper.rules
dracut: Skipping udev rule: 56-lvm.rules
dracut: Skipping udev rule: 60-persistent-storage-lvm.rules
dracut: *** Including module: resume ***
...
dracut: *** Including module: udev-rules ***
dracut: Skipping udev rule: 40-redhat.rules
...
dracut: Skipping udev rule: 80-drivers-modprobe.rules
dracut: *** Including module: dracut-systemd ***
...
dracut: *** Hardlinking files ***
...
dracut: Executing: /usr/bin/dracut --kver=5.18.4-1-default -f
dracut: dracut module 'systemd-coredump' will not be installed, because command 'coredumpctl' could not be found!
...
dracut: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found!
dracut: 35network-legacy: Could not find any command of 'dhclient wicked'!
dracut: dracut module 'network-wicked' will not be installed, because command 'wicked' could not be found!
dracut: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found!
...
dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found!
dracut: memstrack is not available
dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng
dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found!
...
dracut: 35network-legacy: Could not find any command of 'dhclient wicked'!
...
dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found!
...
dracut: *** Stripping files done ***
dracut: *** Creating image file '/boot/initrd-5.18.6-1-default' ***
dracut: *** Creating initramfs image file '/boot/initrd-5.18.6-1-default' done ***
Can anyone please tell me, what this means? Is it, because it is the first time I have used zypper for updates (so far I always used the KDE Plasma tool, which worked fine without any warnings)?
Or due to the option --no-allow-vendor-change? I read it is the default now, but as this is not written in /etc/zypp/zypp.conf (everything is commented out there), I thought it couldn’t harm to name the option).
In the end the update finished and asked me to reboot. After reboot I was freaked out, because
Tumbleweed would not start!
Neither any of the main systems (default, recovery (or some name like this),…) nor the old read-only snapshots. The error was always:
can‘t allocate the kernel
Luckily, after rebooting again, everything was fine and the default tumbleweed booted. This had happed once in the past with using the KDE Plasma update tool.
Does anyone understand, what is going on there? Is it normal?
Kind regards,
Flo
PS: I use a dual boot Win11 and Tumbleweed system to choose from in grub