SystemD creeping out of a new MX Linux installation
by Aeterna from LinuxQuestions.org on (#4WM5V)
I have two installations of MX Linux as virtual clients in VB.
Installation 1 is old and it was first installed as MX Linux 17 then updated up to current version of MX Linux 19.
Installation 2 is a fresh installation of MX Linux 19 from iso followed by system update.
Both installations are up to date MX Linux 19.
Should be identical? Not so much:
In both cases I use custom kernels.
MX Linux (update 17 to 19) works well so I used exactly the came kernel config file to update freshly installed MX Linux 19
.. and I see the following error after issuing:
Quote:
Quote:
after reboot, system just hangs on initramfs and that is all. Yes, I can select previous kernel and system boots, but I wonder why using the same kernel config file old MX Linux 19 boots without any issues while the new fresh install complains about systemd and PID1?
note:
antix also works with the same custom kernel config so the issue of systemd/PID1 is related only to the fresh installation of MX Linux 19
Installation 1 is old and it was first installed as MX Linux 17 then updated up to current version of MX Linux 19.
Installation 2 is a fresh installation of MX Linux 19 from iso followed by system update.
Both installations are up to date MX Linux 19.
Should be identical? Not so much:
In both cases I use custom kernels.
MX Linux (update 17 to 19) works well so I used exactly the came kernel config file to update freshly installed MX Linux 19
.. and I see the following error after issuing:
Quote:
| sudo dpkg -i /usr/src/*.deb |
| Selecting previously unselected package linux-headers-5.4.3-betelgeuse. (Reading database ... 277387 files and directories currently installed.) Preparing to unpack .../linux-headers-5.4.3-betelgeuse_5.4.3-1_amd64.deb ... Unpacking linux-headers-5.4.3-betelgeuse (5.4.3-1) ... Selecting previously unselected package linux-image-5.4.3-betelgeuse. Preparing to unpack .../linux-image-5.4.3-betelgeuse_5.4.3-1_amd64.deb ... Unpacking linux-image-5.4.3-betelgeuse (5.4.3-1) ... Preparing to unpack .../linux-libc-dev_5.4.3-1_amd64.deb ... Unpacking linux-libc-dev:amd64 (5.4.3-1) over (5.4.3-1) ... Setting up linux-headers-5.4.3-betelgeuse (5.4.3-1) ... Setting up linux-image-5.4.3-betelgeuse (5.4.3-1) ... System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down Warning: Unable to find an initial ram disk that I know how to handle. Will not try to make an initrd. System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down Error! Bad return status for module build on kernel: 5.4.3-betelgeuse (x86_64) Consult /var/lib/dkms/virtualbox-guest/6.0.12/build/make.log for more information. update-initramfs: Generating /boot/initrd.img-5.4.3-betelgeuse cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. I: The initramfs will attempt to resume from /dev/sda3 I: (UUID=11cb99ee-7c02-4ad3-b5c0-4d1a84bf9978) I: Set the RESUME variable to override this. VirtualBox Guest Additions: Building the modules for kernel 5.4.3-betelgeuse. update-initramfs: deferring update (hook will be called later) Generating grub configuration file ... Found theme: /boot/grub/themes/linen/theme.txt Found linux image: /boot/vmlinuz-5.4.3-betelgeuse Found initrd image: /boot/initrd.img-5.4.3-betelgeuse Found linux image: /boot/vmlinuz-4.19.0-6-amd64 Found initrd image: /boot/initrd.img-4.19.0-6-amd64 Found memtest86+ image: /boot/memtest86+.bin done Setting up linux-libc-dev:amd64 (5.4.3-1) |
note:
antix also works with the same custom kernel config so the issue of systemd/PID1 is related only to the fresh installation of MX Linux 19