Devuan runit system pauses during first boot at net connect manager.

devuan_dk_fan · 2024-12-30 15:43:32

Devuan system new KDE Plasma install with runit init:
First boot pauses at “Starting network connection manager: NetworkManager.” Refuses to continue. From what I have read, Devuan's runit implementation is a hybrid form of some runit bits, while most startup items continue to use SystemV. I am not really sure how to address the above problem to successfully get a first boot. Any ideas? I know that a PeppermintOS based Devuan install with XFCE and runit work without problems, so my working hypothesis is that NetworkManager isn't getting loaded. While I assume that NetworkManager is still SysV, I have no idea how to solve this on a hybrid runit system.

Help?

devuan_dk_fan · 2024-12-30 20:38:28

I have since the last post tried installing Devuan with LXQT, as well as another KDE Plasma directory configuration at install - both with runit init. The LXQT install could not complete a first system boot, pausing at "bluetooth". The KDE install paused at the same place. In both cases, pressing the return key returned a cli prompt to log in. Both installs appear to be malformed, as there are no directories in user /home. Likewise, an ls in /root returns nothing, however I was able to get into /usr and complete an ls of the directories inside. commands such as # poweroff, halt -h now, halt -r now, etc. did not work, despite a verification that they were there when doing an # ls in /sbin.

This is starting to look more and more like an issue of malformed installs...

devuan_dk_fan · 2024-12-31 10:45:53

OK, I now have a working runit system, but I had to do some serious thinking outside of the box:

Comment out CD in /etc/apt/sources.list

If directories are lacking:
$ xdg-user-dirs-update

$ wget q4os.org/downloads/q4os-setup.sh
$ su (or sudo -s)
# sh q4os-setup.sh

Run the following after reboot to confirm running init system:
$ cat /proc/1/comm

The fundamental problem appears to have been that I could not get any desktop. Nouveau (if installed) didn't give me a GUI, and installing nvidia-driver ended with a dpkg error #1. Likewise, a guided disk formatting with a separate /home partition gave me a system with a home directory without any sub-directories (both sysv and runit). After having run the q4os script and rebooted, I now have a functioning system (KDE Plasma) using runit - confirmed by $ cat /proc/1/comm

Current status is that while I have a running system, /var/log/boot contains the following error message:
"Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon failed!"
which could be why Discovery doesn't appear to be able to access a wired internet connection. Synaptic works fine.

I as of yet have not installed the Nvidia drivers as I am trying to avoid the dpkg error again. It will be interesting to see how long I can do that... The computer has an NVIDIA TU116 [GeForce GTX 1660 SUPER] gpu.

Last edited by devuan_dk_fan (2024-12-31 11:04:15)

stargate-sg1-cheyenne-mtn · 2024-12-31 11:38:42

according to this, q4os-setup.sh puts a q4os system "on_top_of" whatever _debian_distro_ is "under" it?

https://www.q4os.org/dqa017.html

distrowatch says q4os expects?/uses? systemd?

https://distrowatch.com/table.php?distribution=q4os

hmmm...

devuan_dk_fan · 2024-12-31 14:32:38

Here is a more in depth look at the result of running the q4os script on a Devuan KDE runit install:

$ ps ax | grep run
    1 ?        Ss     0:00 runit
 1542 ?        Ss     0:00 runsvdir -P /etc/service log: .....................................................................................................................................................................................................................................................................................................................................check: 3: socklog-check: not found check: 3: socklog-check: not found 
 1593 ?        S      0:00 /usr/sbin/smartd --pidfile /var/run/smartd.pid
 1685 ?        Ss     0:00 runsv getty-tty4
 1686 ?        Ss     0:00 runsv cups
 1687 ?        Ss     0:00 runsv getty-ttyS0
 1688 ?        Ss     0:00 runsv dbus
 1689 ?        Ss     0:00 runsv dhclient
 1690 ?        Ss     0:00 runsv getty-tty3
 1691 ?        Ss     0:00 runsv anacron
 1692 ?        Ss     0:00 runsv cron
 1693 ?        Ss     0:00 runsv sddm
 1694 ?        Ss     0:00 runsv acpid
 1695 ?        Ss     0:00 runsv elogind
 1696 ?        Ss     0:00 runsv getty-tty6
 1697 ?        Ss     0:00 runsv getty-tty5
 1698 ?        Ss     0:00 runsv rsyslog
 1699 ?        Ss     0:00 runsv dbus.dep-fixer
 1700 ?        Ss     0:00 runsv getty-tty2
 1701 ?        Ss     0:00 runsv default-syslog
 1702 ?        Ss     0:00 runsv getty-tty1
 1706 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/dbus
 1709 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/sddm
 1712 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/dhclient
 1716 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/anacron
 1719 ?        S      0:00 svlogd -tt /var/log/runit/acpid
 1919 ?        S      0:00 avahi-daemon: running [host_computer.local]
 1924 tty7     Ssl+   0:00 /usr/lib/xorg/Xorg -nolisten tcp -auth /var/run/sddm/{5bc3cb32-6e3c-4fe0-ae1b-8f42736e3c47} -background none -noreset -displayfd 17 -seat seat0 vt7
 1980 ?        S      0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
 2112 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sddm/sddm-helper --socket /tmp/sddm-auth5d07c714-2378-448c-b18f-637ebc26e64d --id 1 --start /usr/lib/x86_64-linux-gnu/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland --user brian
 2117 tty8     Ss+    0:00 dbus-run-session /usr/bin/startplasma-wayland
 2142 tty8     Sl+    0:03 /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_AViBbU --xwayland
 2163 tty8     Sl+    0:00 /usr/bin/Xwayland :1 -auth /run/user/1000/xauth_AViBbU -listenfd 49 -listenfd 50 -displayfd 41 -rootless -wm 44
 2328 tty8     S+     0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/1000/at-spi/bus_1
 2644 tty8     Sl+    0:00 /usr/lib/x86_64-linux-gnu/libexec/baloorunner
 2782 ?        Ss     0:00 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /run/user/1000/doc
 3993 pts/1    S+     0:00 grep run

/etc/runit$ ls -1F runsvdir
current@
default/
default.run/
single/
solo/
svmanaged/

/etc/runit$ ls -1F runsvdir/default
acpid@
anacron@
cron@
cups@
dbus@
dbus.dep-fixer@
default-syslog@
dhclient@
elogind@
getty-tty1@
getty-tty2@
getty-tty3@
getty-tty4@
getty-tty5@
getty-tty6@
getty-ttyS0@
rsyslog@
sddm@

$ ls -F /etc/init.d
acpid*                   cups-browsed*           mountkernfs.sh*               saned*
alsa-utils*              dbus*                   mountnfs-bootclean.sh*        sddm*
anacron*                 elogind*                mountnfs.sh*                  seatd*
apparmor*                eudev*                  networking*                   sendsigs*
avahi-daemon*            gdomap*                 network-manager*              single*
bluetooth*               halt*                   openntpd                      smartmontools*
bootlogd*                hostname.sh*            procps*                       speech-dispatcher
bootlogs*                hwclock.sh*             pulseaudio-enable-autospawn*  stop-bootlogd*
bootmisc.sh*             keyboard-setup.sh*      rc@                           stop-bootlogd-single*
brightness*              killprocs*              rc.local*                     sudo*
checkfs.sh*              kmod*                   rcS@                          umountfs*
checkroot-bootclean.sh*  lm-sensors*             README@                       umountnfs.sh*
checkroot.sh*            mountall-bootclean.sh*  reboot*                       umountroot*
console-setup.sh*        mountall.sh*            rmnologin*                    unattended-upgrades*
cron*                    mount-configfs*         rsync*                        urandom*
cups*                    mountdevsubfs.sh*       rsyslog*                      x11-common*

fsmithred · 2024-12-31 19:32:50

I did a minimal install of daedalus with runit in qemu and then added xorg and kde-standard without recommends. I can confirm that on reboot into the installed system I don't get a login prompt until I press ENTER. After installing sddm, it boots to a graphical login screen.

User's subdirectories get created on first login to the graphical desktop. I got them.

devuan_dk_fan · 2025-01-07 09:24:08

So far, so good. I followed your lead and installed a minimal system before adding xorg and kde-standard, with no recommendations. (I personally view this as counterintuitive, when I am using an “expert install”, but ok.)

Everything seems to have worked so far, but the system isn’t booting into sddm at start. Since this is a runit init install, I assume something needs to be done manually, but I am unsure if sddm is launched by runit or by one of the remaining sysv init scripts 🤔

—-

sddm appears in a list when I run the following:

# cd /etc
# ls sv

This would suggest that sddm should be started by runit. Running the following command would suggest that sddm does get started:

$ ps ax | grep run

returns “runsv sddm” and “runsv elogind”

I should mention that I continue to need to press the return key after boot is finished, to get a command line login.

Last edited by devuan_dk_fan (2025-01-07 09:55:16)

fsmithred · 2025-01-07 11:29:15

I didn't have to do anything special to get sddm to work. It is being handled by runit. Here are the relevant commands I used to install kde.

apt install xorg xinit xterm
apt install kde-standard  xserver-xorg-video-all xserver-xorg-input-all --no-install-recommends
reboot
apt install sddm --no-install-recommends
reboot

I don't have any good ideas for why sddm is running but you don't see it. Is there anything in the sddm log file? (/var/log/sddm.log)

I'd say check the sddm config file, but there doesn't seem to be a simple sddm.conf. Another option might be to replace sddm with lightdm or some other display manager that has a normal config file instead of unintelligible stuff in /etc/pam.d.

RedGreen925 · 2025-01-07 13:31:41

First boot pauses at “Starting network connection manager: NetworkManager.”
so my working hypothesis is that NetworkManager isn't getting loaded. While I assume that NetworkManager is still SysV, I have no idea how to solve this on a hybrid runit system.

With the networking being setup using the /etc/network/interfaces file in Devuan you need to tell
NetworkManager to manage the network using that method, it expects the systemd garbage.

From my install notes.

root@9600k:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The first card in the system added for devuan method of networking

auto eth0
    allow-hotplug eth0
    iface eth0 inet dhcp
zeus@9600k:~# nmcli dev status
DEVICE  TYPE      STATE                   CONNECTION
lo      loopback  connected (externally)  lo
eth0    ethernet  unmanaged               --
root@9600k:~# cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

root@9600k:~# nano /etc/NetworkManager/NetworkManager.conf
root@9600k:~# cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=true

root@9600k:~# service network-manager restart
Stopping network connection manager: NetworkManager.
Starting network connection manager: NetworkManager.
root@8400:~# nmcli dev status
DEVICE  TYPE      STATE                   CONNECTION
eth0    ethernet  connected (externally)  eth0
lo      loopback  connected (externally)  lo

devuan_dk_fan · 2025-01-07 17:15:05

I followed the instructions exactly, but after having tried two more installs to get sddm working, I installed lightdm instead. Lightdm starts into a kde plasma gui that has a number of issues:

Unable to resize windows.

The kde application launcher kicked up some errors as well:

Errors:
file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Kickoff.qml:157:34: Type FullRepresentation unavailable

file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/FullRepresentation.qml:80:22: Type NormalPage unavailable

file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/NormalPage.qml:43:13: Type Footer unavailable

file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/Footer.qml:155:5: Type LeaveButtons unavailable

file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/LeaveButtons.qml:14:1: module "org.kde.kitemmodels" is not installed

My wired ethernet connection functions, but there is no NetworkManager directory, and no .conf file:

# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

# cd /etc/NetworkManager
bash: cd: /etc/NetworkManager: No such file or directory

RedGreen925 · 2025-01-07 17:25:53

My wired ethernet connection functions, but there is no NetworkManager directory, and no .conf file

Yes it will function if something like dhcpcd is installed to bring up the connection. Just that the network manager in KDE will show you nothing about the connection without it doing the management of it. For the other problems I would say the runit is more trouble to get going, the sysvinit works perfectly.

devuan_dk_fan · 2025-01-08 08:22:42

The Q4OS script solution, unfortunately still looks like the only way to get a fully functioning KDE Plasma install on a runit init base. I would have preferred a fully Devuan install, but it looks like the Q4OS script or a Peppermint OS runit install are the only options for getting a fully working runit Devuan based system, the later with XFCE not KDE…

devuan_dk_fan · 2025-01-08 16:24:33

I just tried two more installs. What works best (relative term) on bare metal is the following:

# apt install xorg xinit xterm

# apt install kde-standard

# reboot

There are a few extra apps installed that I am not interested in, however for the most part, the system behaves as I expect it to. The exceptions are as follows:

SDDM is installed, but doesn't appear at boot. This is probably due to the second exception. Interestingly, SDDM appears when I choose one of the commands from the application menu (logout, restart, shutdown).

An ethernet connection is available and working, but not with NetworkManager, which is also likely the reason that Discover doesn't detect an internet connection.

~~Cups doesn't appear to be working either.~~

I can live without SDDM and ~~Discover~~ not working properly, but it would be nice if they did...

---

Not sure how, but Discover looks like it is working now. Only lacking SDDM...

Last edited by devuan_dk_fan (2025-01-08 18:26:06)

The officially official Devuan Forum!

#1 2024-12-30 15:43:32

Devuan runit system pauses during first boot at net connect manager.

#2 2024-12-30 20:38:28

Re: Devuan runit system pauses during first boot at net connect manager.

#3 2024-12-31 10:45:53

Re: Devuan runit system pauses during first boot at net connect manager.

#4 2024-12-31 11:38:42

Re: Devuan runit system pauses during first boot at net connect manager.

#5 2024-12-31 14:32:38

Re: Devuan runit system pauses during first boot at net connect manager.

#6 2024-12-31 19:32:50

Re: Devuan runit system pauses during first boot at net connect manager.

#7 2025-01-07 09:24:08

Re: Devuan runit system pauses during first boot at net connect manager.

#8 2025-01-07 11:29:15

Re: Devuan runit system pauses during first boot at net connect manager.

#9 2025-01-07 13:31:41

Re: Devuan runit system pauses during first boot at net connect manager.

#10 2025-01-07 17:15:05

Re: Devuan runit system pauses during first boot at net connect manager.

#11 2025-01-07 17:25:53

Re: Devuan runit system pauses during first boot at net connect manager.

#12 2025-01-08 08:22:42

Re: Devuan runit system pauses during first boot at net connect manager.

#13 2025-01-08 16:24:33

Re: Devuan runit system pauses during first boot at net connect manager.

Board footer