MX Linux boots in init not systemd

When you run into problems installing MX Linux XFCE
Message
Author
User avatar
JesusLinux
Posts: 74
Joined: Fri Aug 16, 2024 4:47 pm

MX Linux boots in init not systemd

#1 Post by JesusLinux »

Hello,
I have installed MX Linux from a snapshot from other machine.
This laptop is dual booting with Win11.



I can boot on both OSes however MX Linux is booting in init instead of systemd so I can't use sudo for upgrades and basic commands.
What is going on?
Here's the info:

Code: Select all

jesuslinux@B-970:~
$ sudo apt update && apt upgrade && flatpak upgrade
[sudo] password for jesuslinux:     
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 3787 (apt-get)
N: Be aware that removing the lock file is not a solution and may break your system.
E: Unable to lock directory /var/lib/apt/lists/
jesuslinux@B-970:~
$ sudo apt-get update && apt-get upgrade && flatpak upgrade
Hit:1 http://deb.debian.org/debian bookworm-updates InRelease                                                                                        
Hit:2 http://security.debian.org/debian-security bookworm-security InRelease                                                                         
Hit:3 http://deb.debian.org/debian bookworm InRelease                                                                           
Hit:4 https://dl.google.com/linux/chrome/deb stable InRelease                                                                  
Hit:5 https://mirrors.ocf.berkeley.edu/mx-packages/mx/repo bookworm InRelease    
Hit:6 http://repository.spotify.com stable InRelease
Reading package lists... Done
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
jesuslinux@B-970:~
$ ps -p 1 -o comm=
init
System info:

Code: Select all

Snapshot created on: 20250202_2320
System:
  Kernel: 6.1.0-30-amd64 [6.1.124-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-30-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.3_x64 Libretto August 15  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: Hewlett-Packard product: HP Pavilion g6 Notebook PC
    v: 0791100000205610000620100 serial: <superuser required> Chassis: type: 10
    serial: <superuser required>
  Mobo: Hewlett-Packard model: 1840 v: 56.32 serial: <superuser required> UEFI-[Legacy]: Insyde
    v: F.27 date: 09/07/2016
CPU:
  Info: model: Intel Pentium B970 bits: 64 type: MCP arch: Sandy Bridge level: v2 built: 2010-12
    process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x2F
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
    L2: 512 KiB desc: 2x256 KiB L3: 2 MiB desc: 1x2 MiB
  Speed (MHz): avg: 2295 min/max: 800/2300 scaling: driver: intel_cpufreq governor: ondemand
    cores: 1: 2295 2: 2295 bogomips: 9179
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: disabled; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Hewlett-Packard
    driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
    active: LVDS-1 empty: DP-1,HDMI-A-1,VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0106 class-ID: 0300
  Device-2: AMD Thames [Radeon HD 7500M/7600M Series] vendor: Hewlett-Packard driver: N/A
    alternate: radeon, amdgpu arch: TeraScale-2 code: Evergreen process: TSMC 32-40nm built: 2009-15
    pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: lanes: 16 bus-ID: 01:00.0 chip-ID: 1002:6840
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 362x204mm (14.25x8.03") s-diag: 416mm (16.36")
  Monitor-1: LVDS-1 model: LG Display 0x02f2 built: 2011 res: 1366x768 hz: 60 dpi: 101 gamma: 1.2
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 3.3 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 2000 (SNB GT1)
    direct-render: Yes
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Hewlett-Packard 7
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403
  API: ALSA v: k6.1.0-30-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Ralink vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 modules: wl pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 07:00.0 chip-ID: 1814:539a class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 08:00.0 chip-ID: 10ec:8136
    class-ID: 0200
  IF: eth0 state: down mac: <filter>
Drives:
  Local Storage: total: 689.33 GiB used: 17.14 GiB (2.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1103 scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Hitachi model: HTS545050A7E380 size: 465.76 GiB
    block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: A7A0 scheme: GPT
Partition:
  ID-1: / raw-size: 69.34 GiB size: 67.7 GiB (97.64%) used: 10.93 GiB (16.1%) fs: ext4
    dev: /dev/sda6 maj-min: 8:6
  ID-2: /boot/efi raw-size: 200 MiB size: 196.9 MiB (98.44%) used: 1 KiB (0.0%) fs: vfat
    dev: /dev/sda5 maj-min: 8:5
  ID-3: /home raw-size: 195.31 GiB size: 191.19 GiB (97.89%) used: 6.21 GiB (3.2%) fs: ext4
    dev: /dev/sdb2 maj-min: 8:18
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 8.59 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda7
    maj-min: 8:7
Sensors:
  System Temperatures: cpu: 53.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2291 pm: dpkg pkgs: 2282 libs: 1159
    tools: apt,apt-get,aptitude,gnome-software,nala,synaptic pm: rpm pkgs: 0 pm: flatpak pkgs: 9
  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 bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mirrors.ocf.berkeley.edu/mx-packages/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/spotify.list
    1: deb http://repository.spotify.com stable non-free
Info:
  Processes: 203 Uptime: 14m wakeups: 2 Memory: 7.65 GiB used: 2.11 GiB (27.6%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Already reinstalled twice!
The boot partition is ESP 200MB on SSD
/root is on SSD
/home is on HDD

Any suggestions?
Thanks

User avatar
AK-47
Developer
Posts: 1189
Joined: Sun Mar 24, 2019 7:04 pm

Re: MX Linux boots in init not systemd

#2 Post by AK-47 »

This has nothing to do with systemd vs sysvinit. It's the shell code you are using.
You are only using sudo on the first command.

Code: Select all

$ sudo apt-get update && apt-get upgrade && flatpak upgrade
That will only run apt-get update as superuser since this line breaks down as follows:

Code: Select all

sudo apt-get update
apt-get upgrade
flatpak upgrade
To do it all in one line:

Code: Select all

sudo apt-get update && sudo apt-get upgrade && sudo flatpak upgrade

User avatar
Adrian
Developer
Posts: 8855
Joined: Wed Jul 12, 2006 1:42 am

Re: MX Linux boots in init not systemd

#3 Post by Adrian »

I was writing the same thing but Ak-47 ninja'd me. Only comment is that you might not need to run flatpak with sudo (depending if you install stuff for user or for system)

User avatar
JesusLinux
Posts: 74
Joined: Fri Aug 16, 2024 4:47 pm

Re: MX Linux boots in init not systemd

#4 Post by JesusLinux »

AM I LINUX-STUPID?
Oh well...
:D

User avatar
DukeComposed
Posts: 1283
Joined: Thu Mar 16, 2023 1:57 pm

Re: MX Linux boots in init not systemd

#5 Post by DukeComposed »

JesusLinux wrote: Sun Feb 23, 2025 12:53 am AM I LINUX-STUPID?
No. This week I experimented with moving my machine from using sudo to using doas and symlinking doas to /usr/bin/sudo.

Things went well except for the fact that slock stopped working, rendering my machine entirely incapable of being locked.

That's Linux stupid.

User avatar
j2mcgreg
Global Moderator
Posts: 6534
Joined: Tue Oct 23, 2007 12:04 pm

Re: MX Linux boots in init not systemd

#6 Post by j2mcgreg »

@JesusLinux wrote:
I can boot on both OSes however MX Linux is booting in init instead of systemd so I can't use sudo for upgrades and basic commands.
What is going on?
Our Live System / installer only works with SysV init. If you want to use SystemD, you have to make the change in Grub, post install, with Boot Options in MX Tools.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
atomick
Posts: 111
Joined: Tue Jan 30, 2024 11:16 pm

Re: MX Linux boots in init not systemd

#7 Post by atomick »

Ah gee trying not to ninja - sir Adrian ' anyone simply ideas to share. much is it not already contained in the actual "Booting of MX" just as the 1st screen appears to tap the enter or down arrow key to click on "Advanced" this takes you directly to 1st item is what your default is to boot the 2nd item is to select "SystemD" for booting. Nice feature allowing these various types of "Systems Ordinance" only other I've recently seen is Devuan linux as to it has 3 boot variance with init.d as one of the 3.
Think also this is a Start Script entry in /etc/grub.d think to believe quick view is responsible by 20_linux_xen start script all functional thru the "Grub Menu"
cheers.
Snapshots should also have this set, the 2nd option for creating a snapshot " without User Accounts " (For sharing).iso to others. Is a slim form for a snapshot - account creation will be just as regular install asks of additional can easily be created via MX-User-management (MX-Tools - Maintenance)
or by cmdline "examples:"

#> sudo useradd -m -d /home/newAcctname -s /bin/bash -k /etc/skel newAcctname Or
#> sudo useradd -m -d /home/johndoe -s /bin/bash -k /etc/skel johndoe
#> sudo usermod -aG group1,grp2,grp3 johndoe
#> sudo usermod -aG sudo johndoe - results to adding johndoe to "sudo users group' change sudo to wheel in other system distro simple a different method using sudo package. for allow to disallow Note id provides you with a common list of all groups Default provides, some users can be added to other groups not on the common. "This takes only accountability to "Multi -users-" on system. My house Mom Dad Kid-A Kid-computer kid-sister dog-rover cat-kutie
#> sudo userdel -rf johndoe - results removing from the system user johndoe there are others lock him out add time stamp to passwd changes lots of info yet features only.

User avatar
Eadwine Rose
Administrator
Posts: 14416
Joined: Wed Jul 12, 2006 2:10 am

Re: MX Linux boots in init not systemd

#8 Post by Eadwine Rose »

@atomick Does this have to do with the OP's question?

If this is a different topic altogether please start your own, because then you are topic stealing, which is a no no.
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

User avatar
atomick
Posts: 111
Joined: Tue Jan 30, 2024 11:16 pm

Re: MX Linux boots in init not systemd

#9 Post by atomick »

details details all within . Covers many posts even by the 1st entry shares to show how a Snapshot is verified/tested by loading other systems. as well selecting advanced "SystemD" need somewhere to get too have this be a Re-install. Accounting is also part of the process.

Quote; "Hello,
I have installed MX Linux from a snapshot from other machine."
Cheers.

User avatar
atomick
Posts: 111
Joined: Tue Jan 30, 2024 11:16 pm

Re: MX Linux boots in init not systemd

#10 Post by atomick »

yes default does not at grub menu tapping the Down key entering the Advanced options provide booting systemD memory tests. for choice of environment. ? never use it but do still run the odd systemctl command.
ie: systemctl list-unit-files | grep 'something' - something is only the example not literal. change that to say avahi or saned. or ssh.service

Post Reply

Return to “Installation”