Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/
Count your blessings?zoli62 wrote: Sun Nov 21, 2021 4:33 pmI recently upgraded from MX Linux 19.4 to MX Linux 21. When I boot the system with systemd, I get to the emergency shell every time. With Sysvinit, everything works perfectly. I am using multiple boot with an EFI partition with Kubuntu Grub. I reinstalled the systemd systemd-shim packages, but to no avail. What could be the possible causes?
manyroads wrote: Mon Nov 22, 2021 11:10 am No systems specs... no help.
Please follow the instructions on how-to obtain help. You'll be happier with your results.
Code: Select all
System: Host: <filter> Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel, plank wm: xfwm4
dm: LightDM 1.26.0 Distro: MX-21_x64 Wildflower October 21 2019
base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: LENOVO product: 20AT0030UK v: ThinkPad L440 serial: <filter>
Chassis: type: 10 serial: <filter>
Mobo: LENOVO model: 20AT0030UK v: 0B98401 Pro serial: <filter> UEFI: LENOVO
v: J4ET81WW(1.81) date: 08/14/2015
Battery: ID-1: BAT0 charge: 7.5 Wh condition: 70.8/71.3 Wh (99%) volts: 11.7/10.8
model: SMP 45N1149 type: Li-ion serial: <filter> status: Charging
CPU: Topology: Dual Core model: Intel Core i5-4200M bits: 64 type: MT MCP arch: Haswell
family: 6 model-id: 3C (60) stepping: 3 microcode: 28 L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19953
Speed: 947 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 992 2: 867 3: 972 4: 911
Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Lenovo
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0416
Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.3.5
compat-v: 3.0 direct render: Yes
Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0c0c
Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Intel Ethernet I217-V vendor: Lenovo driver: e1000e v: 3.2.6-k port: 5080
bus ID: 00:19.0 chip ID: 8086:153b
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: efa0 bus ID: 02:00.0
chip ID: 8086:08b2
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 447.13 GiB used: 9.82 GiB (2.2%)
ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: B1C2 scheme: GPT
Partition: ID-1: / raw size: 27.77 GiB size: 27.09 GiB (97.52%) used: 9.82 GiB (36.3%) fs: ext4
dev: /dev/sda5
ID-2: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sda6
Sensors: System Temperatures: cpu: 41.0 C mobo: 24.0 C
Fan Speeds (RPM): cpu: 0
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/microsoft-edge-dev.list
1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://quantum-mirror.hu/mirrors/pub/mx-linux/packages/mx/repo/ bullseye main non-free
2: deb https://quantum-mirror.hu/mirrors/pub/mx-linux/packages/mx/testrepo/ bullseye test
Active apt repos in: /etc/apt/sources.list.d/opera-developer.list
1: deb https://deb.opera.com/opera-developer/ stable non-free #Opera Browser (final releases)
Active apt repos in: /etc/apt/sources.list.d/opera-stable.list
1: deb https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases)
No active apt repos in: /etc/apt/sources.list.d/various.list
Active apt repos in: /etc/apt/sources.list.d/vivaldi-snapshot.list
1: deb [arch=amd64] https://repo.vivaldi.com/snapshot/deb/ stable main
Info: Processes: 216 Uptime: N/A Memory: 7.69 GiB used: 603.7 MiB (7.7%) Init: SysVinit
v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36 Selecting boot from hard disk from the MX Linux live cd boot menu does not change the situation.figueroa wrote: Mon Nov 22, 2021 1:39 pmCount your blessings?zoli62 wrote: Sun Nov 21, 2021 4:33 pmI recently upgraded from MX Linux 19.4 to MX Linux 21. When I boot the system with systemd, I get to the emergency shell every time. With Sysvinit, everything works perfectly. I am using multiple boot with an EFI partition with Kubuntu Grub. I reinstalled the systemd systemd-shim packages, but to no avail. What could be the possible causes?
Try letting MX-21 manage GRUB.
You may be right, but a simple manual upgrade can cover the system so much? I remember that the update process was never interrupted on the fly, but there was a package dependency error that needed to be fixed manually and the update could continue after that. I don’t have multiple free partitions for this purpose, and I use multiple boot with several different distributions, so I can’t do a clean install. I will look at the error messages in the logs, if I have more time, the sysvinit will work well. I probably can’t get away with this anymore without reinstalling.figueroa wrote: Tue Nov 23, 2021 12:17 am @zoli62
I'm guessing that some changes you've made to MX-21 has compromised your ability to boot with systemd. Can you try a clean install of MX-21 on another partition/drive? On a freshly installed MX-21, systemd boots without issue here.
Does it really read "emergency shell?" What actually prints to the screen? What does the end of dmesg show immediately after failing?
Have you searched through /var/log/boot.log, kern.log, syslog, messages, Xorg.0.log for points of failure.
Well done. Looks like a dmesg equivalent. It doesn't look good, but I don't speak "systemd." I expect someone else may be able to help.zoli62 wrote: Wed Nov 24, 2021 11:06 pm Here is output of journalctl -bx https://pastebin.com/raw/JfC1X6Ns