"NetworkManager is not running/Networking disabled" after update

[zoli62]

why is mxlinux 21 using sysvinit instead of systemd?

You know, you can boot with systemd ("Advanced Options" in Grub) furthermore, can make it default ( Menu => "MX Boot Options" : "Boot to" ). Shortly, MX prefers SysV for this or that reason but doesn't force anyone to use this or that :)

I remember when the introduction of systemd met with resistance from the community. Since I use multiple systems in parallel, for testing purposes, I don't use MX Linux Grub, so I can't configure it to start with systemd. :) I just find it interesting that MX Linux has migrated from systemd to Sysvinit by default.

[Huckleberry Finn]

I don't use MX Linux Grub, so I can't configure it to start with systemd.

Boot into MX, Menu => "MX Boot Options" : Add into "Kernel parameters" after others:

Code: Select all

init=/lib/systemd/systemd

Apply.

( ...Or manually in /etc/default/grub in this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash blahblah" , save.)


Reboot into "other" distro (whichever is controlling grub):

Code: Select all

sudo update-grub

[zoli62]

I don't use MX Linux Grub, so I can't configure it to start with systemd.

Boot into MX, Menu => "MX Boot Options" : Add into "Kernel parameters" after others:

Code: Select all

init=/lib/systemd/systemd

Apply.

( ...Or manually in /etc/default/grub in this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash blahblah" , save.)


Reboot into "other" distro (whichever is controlling grub):

Code: Select all

sudo update-grub

I have two questions. I guess network-manager-sysvinit-compat doesn't work under sytemd, and I think I should have remembered first not to install this csysvinit network manager if I want to use systemd? What do I lose by continuing to use sysvinit instead of systemd?

[dolphin_oracle]

I don't use MX Linux Grub, so I can't configure it to start with systemd.

Boot into MX, Menu => "MX Boot Options" : Add into "Kernel parameters" after others:

Code: Select all

init=/lib/systemd/systemd

Apply.

( ...Or manually in /etc/default/grub in this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash blahblah" , save.)


Reboot into "other" distro (whichever is controlling grub):

Code: Select all

sudo update-grub

I have two questions. I guess network-manager-sysvinit-compat doesn't work under sytemd, and I think I should have remembered first not to install this csysvinit network manager if I want to use systemd? What do I lose by continuing to use sysvinit instead of systemd?

network-manager-sysvinit-compat doens't do anything under systemd. it exits without action, because network-manager already provides a systemd service file for startup.

the live system is designed to be used under sysvinit. snapshot and the installer will still work, but certain activities like semi-automatic persistence file saving and a few other odds and ends on the live system will not. but on an installed system, you don't lose anything.

and if you leave sysvinit installed, the live snapshots will use sysvinit automatically.

[zoli62]

Boot into MX, Menu => "MX Boot Options" : Add into "Kernel parameters" after others:

Code: Select all

init=/lib/systemd/systemd

Apply.

( ...Or manually in /etc/default/grub in this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash blahblah" , save.)


Reboot into "other" distro (whichever is controlling grub):

Code: Select all

sudo update-grub

I have two questions. I guess network-manager-sysvinit-compat doesn't work under sytemd, and I think I should have remembered first not to install this csysvinit network manager if I want to use systemd? What do I lose by continuing to use sysvinit instead of systemd?

network-manager-sysvinit-compat doens't do anything under systemd. it exits without action, because network-manager already provides a systemd service file for startup.

the live system is designed to be used under sysvinit. snapshot and the installer will still work, but certain activities like semi-automatic persistence file saving and a few other odds and ends on the live system will not. but on an installed system, you don't lose anything.

and if you leave sysvinit installed, the live snapshots will use sysvinit automatically.

Thank you so it's understandable. After all, what is the reason that Mx Linux, unlike Debian, prefers sysvinit by default?

[dolphin_oracle]

Thank you so it's understandable. After all, what is the reason that Mx Linux, unlike Debian, prefers sysvinit by default?

some of us are old farts that like sysVinit.

but mostly the live-usb system works just better with sysvinit.

[zoli62]

I don't use MX Linux Grub, so I can't configure it to start with systemd.

Boot into MX, Menu => "MX Boot Options" : Add into "Kernel parameters" after others:

Code: Select all

init=/lib/systemd/systemd

Apply.

( ...Or manually in /etc/default/grub in this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash blahblah" , save.)


Reboot into "other" distro (whichever is controlling grub):

Code: Select all

sudo update-grub

After making the desired changes, I typed the string containing systemd after the existing kernel parameter, and interestingly, I got to the emergency shell after the next boot. Then, of course, I edited the grub.cfg file with nano and deleted the string containing systemd at the appropriate places in the file. I then started the other distro with my own grub (Kubuntu), logged in, issued a sudo update-grub command, rebooted, and then was able to log in to MX Linux normally. What could have caused this?

PS.
If I made the desired changes to the / etc / default / grub file and then ran a sudo update-grub command, the next boot was successful. I checked the contents of the / etc / default / grub file and the GRUB_CMDLINE_LINUX_DEFAULT line was missing the] init = / lib / systemd / systemd string I typed earlier. However, a grub.bak file was created. So it looks like the system didn't allow me to save the changes, even though I made them as root. . This is a different problem from the previous one, I just supplemented what I described earlier.

[zoli62]

Thank you so it's understandable. After all, what is the reason that Mx Linux, unlike Debian, prefers sysvinit by default?

some of us are old farts that like sysVinit.

but mostly the live-usb system works just better with sysvinit.

I agree. Nor did I applaud my joy when systemd was introduced as an old adult warrior on Debian. :)

[Huckleberry Finn]

This is a thread from Feb 19 and last reply was on 23 Aug

Also we still don't have your "Quick System Info". How can anyone "guess" what happened / how / why / why not ... ?

[zoli62]

This is a thread from Feb 19 and last reply was on 23 Aug

Also we still don't have your "Quick System Info". How can anyone "guess" what happened / how / why / why not ... ?

I manually upgraded from MX Linux 19.4 to MX Linux 21 based on an unofficial Wiki described on the MX Linux website. The system information based on inxi -M is as follows:

Code: Select all

System:    Host: mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 4.16.0 
           Distro: MX-21_x64 Wildflower October 21  2019 
Machine:   Type: Laptop System: LENOVO product: 20AT0030UK v: ThinkPad L440 
           serial: <root required> 
           Mobo: LENOVO model: 20AT0030UK v: 0B98401 Pro serial: <root required> UEFI: LENOVO 
           v: J4ET81WW(1.81) date: 08/14/2015 
Battery:   ID-1: BAT0 charge: 53.5 Wh condition: 70.8/71.3 Wh (99%) 
CPU:       Topology: Dual Core model: Intel Core i5-4200M bits: 64 type: MT MCP 
           L2 cache: 3072 KiB 
           Speed: 798 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 807 2: 864 3: 798 4: 798 
Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915 v: kernel 
           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 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel 
           Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Intel Ethernet I217-V driver: e1000e 
           IF: eth0 state: down mac: 54:ee:75:0a:e1:33 
           Device-2: Intel Wireless 7260 driver: iwlwifi 
           IF: wlan0 state: down mac: e2:42:aa:19:ed:f7 
           Device-3: ZTE WCDMA MSM ZTE Mobile Broadband type: USB driver: cdc_ether,usb-storage 
           IF: usb0 state: up speed: N/A duplex: N/A mac: f6:f6:67:f3:51:ae 
Drives:    Local Storage: total: 447.13 GiB used: 13.18 GiB (2.9%) 
           ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB 
Partition: ID-1: / size: 27.09 GiB used: 13.18 GiB (48.6%) fs: ext4 dev: /dev/sda5 
           ID-2: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda6 
Sensors:   System Temperatures: cpu: 46.0 C mobo: 35.0 C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 203 Uptime: 7m Memory: 7.69 GiB used: 676.9 MiB (8.6%) Shell: bash 
           inxi: 3.0.36