Hi all :-)

I wanted to try to run Devuan on a Raspberry Pi Zero 2 W. From what's listed in https://arm-files.devuan.org/README.txt, I couldn't really figure out what image to use, and I also didn't find anything about Devuan and this model. After some trial and error, I decided to create an image using the Raspberry Pi Imager to see if it would boot at all (the specs say this thing had a 64 bit processor, but neither the Raspberry Pi 1, nor the more recent arm64 images, nor the "0" image would work). For the Raspberry Pi Zero 2 W, it suggests to use the legacy 2024-03-12-raspios-bullseye-armhf image. The SD card flashed with it did work and it did boot.

So I looked for an "armhf" image. There's only one: devuan_chimaera_4.0.0_armhf_rpi2.img (why are those images packed with zip btw and not with something more effective?!).

I dd'ed the image to my SD card and took all the dtb files from the "Raspberry Pi OS" image's boot partition, including bcm2710-rpi-zero-2-w.dtb, and put it in it's boot partition.

The image then worked and I could boot Devuan. Also, I could configure the WLAN through /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf – worked out of the box.

So, after all, I simply wanted to share this. Maybe I simply didn't find the official Devuan image for the Raspberry Pi Zero 2 W. If there's actually none, maybe somebody wants to add one, or instructions how to get it running. However, Devuan works fine on this board :-)

Cheers, Tobias

Hi all :-)

I have Devuan on a quite old notebook (still x86, but I don't know if that matters). I updated it yesterday and noticed it would not shut down correctly anymore, just hangs and nothing happens.

I played around a bit and found that network-manager would refuse to stop, and later on, "Deconfigurating network interfaces" (or such) would finally block the shutdown, so that one can only push the power button so long the machine is finally killed.

This only happens using kernel 6.1.0-15. When booting 6.1.0-13, the machine shuts down normally.

I'm quite new to Devuan (and to the whole Debian world, I'm normally on Gentoo or Artix), so: Where would I report such an issue or search for anybody else having done so? And what's the proper way to tell my system it should boot 6.1.0-13 for now, and keep the kernel? On Gentoo, we normally build a kernel ourselves, and the package manager would only touch the sources when cleaning up, not the compiled kernel.

Thanks for all (newbie) help :-)

Hi all :-)

I have LxQt running.

As soon as the energy management turns off the monitor, a lot of "lxqt-config-monitor -l" processes are started. Maybe, the process keeps crashing and is started over and over again. At the time I saw it, the system was up several weeks, and I had > 200 such processes:

 $ ps -ef | grep lxqt-config-monitor
...
serverh+ 19102  3339  0 16:30 ?        00:00:00 /usr/bin/lxqt-config-monitor -l
serverh+ 19112  3339  0 16:30 ?        00:00:00 /usr/bin/lxqt-config-monitor -l
serverh+ 19122  3339  0 16:30 ?        00:00:00 /usr/bin/lxqt-config-monitor -l
serverh+ 19132  3339  0 16:30 ?        00:00:00 /usr/bin/lxqt-config-monitor -l
serverh+ 19143  3339  0 16:30 ?        00:00:00 /usr/bin/lxqt-config-monitor -l
serverh+ 19153  3339  0 16:30 ?        00:00:00 /usr/bin/lxqt-config-monitor -l
serverh+ 19163  3339  0 16:31 ?        00:00:00 /usr/bin/lxqt-config-monitor -l
serverh+ 19173  3339  0 16:31 ?        00:00:00 /usr/bin/lxqt-config-monitor -l
serverh+ 19183  3339  0 16:31 ?        00:00:00 /usr/bin/lxqt-config-monitor -l
serverh+ 19193  3339  0 16:31 ?        00:00:00 /usr/bin/lxqt-config-monitor -l
...

Playing around a bit, I saw that at the exact moment the energy management turns off the monitor, a few such processes appear.

I also played around with the xscreensaver settings. This seems to change nothing. Also, I never changed any screen setting. Running "lxqt-config-monitor -l" manually doesn't crash and returns normally.

As soon as the monitor is turned off, the following appears over and over again in ~/.xsession-errors (it was > 300 MB big at the time I noticed this):

lxqt-session: "Session 'session': display device '/dev/dri/card0'"
[load.applyBestSettings()] Finished
qt.qpa.xcb: QXcbConnection: XCB error: 148 (Unknown), sequence: 190, resource id: 0, major code: 140 (Unknown), minor code: 20
lxqt-session: "Session 'session': display device '/dev/dri/card0'"
[load.applyBestSettings()] Finished
lxqt-config-monitor: Applying current settings...
Output:  "DP-1"
Output:  "HDMI-1"
Output:  "DP-2"
Output:  "HDMI-2"
lxqt-config-monitor: Settings applied.

What may cause this? And how can I prevent it other than turning off the energy management?

Thanks for all help!

Hi all :-)

I wrote a Python daemon to control PV surplus charging with an go-e Charger (cf. https://gitlab.com/l3u/go-e-pvsd if this may be of interest for anybody). The daemon is well-behaved, backgrounds itself and creates a pidfile.

I also wrote a quite simple OpenRC init script to start it:

#!/sbin/openrc-run

depend() {
    need net
    use logger
}

command="/usr/bin/go-e-pvsd"
pidfile="/run/${RC_SVCNAME}.pid"
command_args="-s"
command_args_background="-d -p $pidfile"

Both on my Gentoo/OpenRC machine and my Artix/OpenRC machine, the script does what it should, starts and stops the daemon:

# ./go-e-pvsd start
 * Starting go-e-pvsd ...                                                [ ok ]
# ./go-e-pvsd stop
 * Stopping go-e-pvsd ...                                                [ ok ]
#

But if I use it on the Devuan server (where it should run later), I can start the daemon, but not stop it:

# ./go-e-pvsd start
 * Starting go-e-pvsd ...                                                [ ok ]
# ./go-e-pvsd stop
 * Stopping go-e-pvsd ...
No /usr/bin/go-e-pvsd found running; none killed.
 * Failed to stop go-e-pvsd                                              [ !! ]
 * ERROR: go-e-pvsd failed to stop
#

However, the pidfile is created as it should be:

cat /run/go-e-pvsd.pid 
21411

the daemon runs and actually does have this pid:

# ps -ef | grep /usr/bin/go-e-pvsd
root     21411     1  1 09:47 ?        00:00:00 python3 /usr/bin/go-e-pvsd -d -p /run/go-e-pvsd.pid -vs
root     21454 21389  0 09:48 pts/0    00:00:00 grep --color=auto /usr/bin/go-e-pvsd

and I can also manually tell it to stop by sending a SIGTERM:

# kill -s SIGTERM 21411
# ps -ef | grep /usr/bin/go-e-pvsd
root   21980 21976  0 10:21 pts/0    00:00:00 grep /usr/bin/go-e-pvsd

Starting and stopping the daemon using a sysvinit init script like this works as expected:

#!/bin/sh
### BEGIN INIT INFO
# Provides:          go-e-pvsd
# Required-Start:    $local_fs $remote_fs $network $syslog
# Required-Stop:     $local_fs $remote_fs $network $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start the go-e PV surplus daemon
# Description:       Daemon for PV surplus charging
#                    with an go-e Charger
### END INIT INFO

PATH=/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/bin/go-e-pvsd
NAME=go-e-pvsd
DESC="pv surplus charging daemon"
PIDFILE=/run/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME

DAEMON_OPTS="-d -p $PIDFILE -s"

test -x $DAEMON || exit 0

set -e

. /lib/lsb/init-functions

case "$1" in
    start)
        status="0"
        pidofproc -p $PIDFILE $DAEMON >/dev/null || status="$?"
        if [ "$status" = 0 ]; then
            log_daemon_msg "$NAME is already running" $NAME
            log_end_msg 0
            exit 0
        fi
        log_daemon_msg "Starting $DESC" $NAME
        if ! start-stop-daemon --start --pidfile $PIDFILE \
                 --exec $DAEMON -- $DAEMON_OPTS
        then
            log_end_msg 1
        else
            log_end_msg 0
        fi
        ;;
    stop)
        log_daemon_msg "Stopping $DESC" $NAME
        if start-stop-daemon --stop --pidfile $PIDFILE
        then
            rm -f $PIDFILE
            log_end_msg 0
        else
            log_end_msg 1
        fi
        ;;
    restart)
        $0 stop
        $0 start
        ;;
    status)
        status_of_proc -p "$PIDFILE" "$DAEMON" go-e-pvsd && exit 0 || exit $?
        ;;
    *)
        echo "Usage: $SCRIPTNAME {start|stop|status}" >&2
        exit 1
        ;;
esac

exit 0

So … what's wrong with OpenRC? Why can't it stop the daemon, although both the process name and the pidfile provide the correct information?

Thanks for all help!