You are not logged in.
Is this a re-emergence in the new kernel of this reported bug in Debian Buster, which has never seemed to be an issue in Beowulf?
5.1.5. Daemons fail to start or system appears to hang during boot
Due to systemd needing entropy during boot and the kernel treating such calls as blocking when available entropy is low, the system may hang for minutes to hours until the randomness subsystem is sufficiently initialized (random: crng init done). For amd64 systems supporting the RDRAND instruction this issue is avoided by the Debian kernel using this instruction by default (CONFIG_RANDOM_TRUST_CPU).Non-amd64 systems and some types of virtual machines need to provide a different source of entropy to continue fast booting. haveged has been chosen for this within the Debian Installer project and may be a valid option if hardware entropy is not available on the system. On virtual machines consider forwarding entropy from the host to the VMs via virtio_rng.
If you read this after upgrading a remote system to buster, ping the system on the network continuously as this adds entropy to the randomness pool and the system will eventually be reachable by ssh again.
See the wiki https://wiki.debian.org/BoottimeEntropyStarvation and DLange's overview of the issue https://daniel-lange.com/archives/152-hello-buster.html for other options.
source: https://www.debian.org/releases/buster/ … starvation
OK, so not dissimilar to mine: your is Celeron 6 gen 4 core vs the 5 gen 2 core on mine so it's not as if it has recent/high spec. hardware that could be causing problems.
Your'e operating under EFI, I'm not. However I'm assuming your previous ascii install was EFI too?
I using sysVinit. There have been problems reported on Beowulf with shutdown with OpenRC.
Are you certain your Beowulf install iso (btw which one did you use?) hasn't become corrupted. Have you checked it?
Looks like it's been this week's DistroWatch Weekly review.
to save seaching for it, it's here:
I also have a NUC running Beowulf without issue, albeit it's my mailserver, running headless and rarely rebooted: the last time was was for a kernel image upgrade to 4.19.0.9 (which was unproblematic).
Mine's a very basic NUC5CPYH 85254, 4GB, 120 GB SSD, mbr, LVM apart from /boot and I run it in legacy bios mode, not EFI.
I had this problem with nvidia-persistenced back in April when I upgraded to Beowulf-Beta.
It's caused by an error in etc/init.d/nvidia-persistenced that happens when it is started and there is already another copy running.
nvidia-persistenced is not really needed unless you use CUDA.
If you's rather keep it you can patch it so that it doesn't misbehave (with the patch it checks if there is already a copy running and just exits if there is).
See https://dev1galaxy.org/search.php?actio … w_as=posts for details.
My patched version is in post #3, also shown below:
#!/bin/sh -e
#
# NVIDIA Persistence Daemon Init Script
#
# Copyright (c) 2013 NVIDIA Corporation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
# FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
# DEALINGS IN THE SOFTWARE.
#
# This is a sample System V init script, designed to show how the NVIDIA
# Persistence Daemon can be started.
#
# This sample does not rely on any init system functions, to ensure the
# widest portability possible.
#
# chkconfig: 2345 99 01
# description: Starts and stops the NVIDIA Persistence Daemon
# processname: nvidia-persistenced
#
### BEGIN INIT INFO
# Provides: nvidia-persistenced
# Required-Start: $local_fs
# Required-Stop: $local_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Starts and stops the NVIDIA Persistence Daemon
# Description: Starts and stops the NVIDIA Persistence Daemon
### END INIT INFO
NVPD=nvidia-persistenced
NVPD_BIN=/usr/bin/${NVPD}
NVPD_RUNTIME=/var/run/${NVPD}
NVPD_PIDFILE=${NVPD_RUNTIME}/${NVPD}.pid
NVPD_USER=nvpd
NVPD_ACTION=${1}
# Gracefully exit if the package has been removed.
test -x $NVPD_BIN || exit 0
# Get the value of the PID
if [ -f ${NVPD_PIDFILE} ]; then
read -r NVPD_PID < "${NVPD_PIDFILE}"
# Is the daemon already running?
if [ "${NVPD_PID}" ] ;then
if [ -d /proc/${NVPD_PID} ]
# Daemon is running, so stop it then start a new instance
then
case "${1}" in
start)
echo "NVIDIA Persistence Daemon already running"
NVPD_ACTION=restart
;;
*)
;;
esac
# Daemon not running, but there is a stale PID
else
echo "NVIDIA Persistence Daemon, stale PID removed"
unset NVPD_PID
rm -rf "${NVPD_RUNTIME}"
fi
fi
fi
case "${NVPD_ACTION}" in
start)
echo "Starting NVIDIA Persistence Daemon"
# Execute the daemon as the intended user
${NVPD_BIN} --user ${NVPD_USER}
;;
stop)
echo "Stopping NVIDIA Persistence Daemon"
# Stop the daemon - its PID should have been read in
[ ! -z "${NVPD_PID}" ] && kill ${NVPD_PID} &> /dev/null
;;
restart)
$0 stop
sleep 2
$0 start
;;
*) echo "usage: $0 {start|stop|restart}"
;;
esac
exit 0Looks like my Cinnamon applet is based on wmctrl.
This is the sorted output (stripping Col 1) of wmctrl. The applet formats this, though in a different order within workspace (and pulls in an app icon). Workspace -1 is my Desktop (shown on all the others too), Workspace 3 and 4 are unused.
$ sudo wmctrl -l | cut -b 11- | sort -n
-1 grendel Desktop
0 grendel Inbox (3 unread) — Evolution
0 grendel John Martyn - Outside In (Paused)
0 grendel /var/log/syslog.1
1 grendel BBC iPlayer - Mozilla Firefox
1 grendel BiPAC 8900X R2 - Mozilla Firefox
1 grendel Calculator
1 grendel desktop / workspaces / Off-topic / Dev1 Galaxy Forum - Mozilla Firefox
1 grendel e-post.meeble.net/rspamd/ - Rspamd Web Interface - Mozilla Firefox
1 grendel How to create an AppArmor Profile | Ubuntu - Mozilla Firefox
1 grendel How to enable hibernate option in Ubuntu 20.04? - Ask Ubuntu - Mozilla Firefox
1 grendel marjorie@grendel: ~
1 grendel marjorie@grendel: ~
1 grendel marjorie@grendel: /etc/apparmor.d
1 grendel Newest 'nftables' Questions - Server Fault - Mozilla Firefox
1 grendel Online Challenges & Races - British Rowing - Mozilla Firefox
1 grendel Redis configuration – Redis - Mozilla Firefox
1 grendel Sound
1 grendel /var/log/syslog
1 grendel Your account | PremierPlayer.tv - Mozilla FirefoxThe "Windows Quick List" applet in Cinnamon shows this information (list of names and an icon, by Workspace).
I've never found any source code for these applets though.
Not so quick there - it's still 16 June here in the UK.
There is an /etc/cron.daily program 'popularity contest' that logs and reports weekly which packages you have/use.
It is optional (you can turn it off) and anonymous in intent.
Firefox can be configured to provide telemetry (but you can turn it off) and it can check for updates to add-ons you have installed (also optional). You can install other browsers that promise more.
To can install programs or configure your browser to encrypt DNS queries, so you only share them with your chosen DNS provider (but you still have to trust them not to log, etc). I use dnscrypt-proxy.
Maybe working again?
On my mail-server unattended-upgrades (beowulf-security updates only) downloaded an intel-microcode package at 03:45 BST.
Unattended upgrade result: All upgrades installed
Packages that were upgraded:
intel-microcode
Package installation log:
Log started: 2020-06-14 03:45:13
apt-listchanges: Reading changelogs...
Preparing to unpack .../intel-microcode_3.20200609.2~deb10u1_amd64.deb ...
Unpacking intel-microcode (3.20200609.2~deb10u1) over (3.20191115.2~deb10u1) ...
Setting up intel-microcode (3.20200609.2~deb10u1) ...
update-initramfs: deferring update (trigger activated)
intel-microcode: microcode will be updated at next boot
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64
Log ended: 2020-06-14 03:45:24
Unattended-upgrades log:
Enabled logging to syslog via daemon facility
Initial blacklist :
Initial whitelist:
Starting unattended upgrades script
Allowed origins are: o=Devuan,n=beowulf-security
Packages that will be upgraded: intel-microcode
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
All upgrades installedWorks for me, but I had to install the wmctrl package as it's not there by default.
user@hostname
-------------------------------------
os: Devuan GNU/Linux 3 (beowulf)
kernel: 4.19.0-9-amd64
uptime: 22 hours, 44 minutes
pkgs: 2102
memory: 3.1Gi / 7.8Gi
wm: Mutter
shell: /bin/bash
editor: /usr/bin/geditJust to add, there are quite a large number of additional profiles that come in the apparmor-profiles package that aren't installed by default. They are put in /usr/share/apparmor/extra-profiles instead. These include basic stuff like postfix, evolution and firefox profiles. However they do warn you that they may not work as intended, and need to be tested in complain mode against your particular installation, and perhaps modified. So I would have to agree that apparmor as currently available, if not a joke, is still quite immature.
Update: Having looked at some of these extra-profiles, they do seem very out of date: e.g. in the firefox profile I see references to the latest version - Firefox 4 b8 (2010-11); the location of the evolution files changed long ago from that in the profiles (local evolution moved from ~./evolution to ~./local/share/evolution); most of the last modified dates in the other profiles are no later than 2005-2014. Clearly they have not been maintained.
Apparmor profiles are only provided for processes that are recognized as potentially dangerous and Apparmor confinement is provided to make your computer safer.
If you do a default Beowulf install you get at default set of profiles that are known to work, or they may be provided with additional packages/programs you install. I've installed LibreOffice from backports and the Firejail package, that is explicitly provided to create a jail for Firefox. These profiles are the one you see in my previous Apparmor status reports.
Profiles that are more experimental that are not guaranteed to work are provided set to complain mode so they don't break anything but you can still use/test them and see what apparmor complains about in the logs.
The Debian package apparmor-profiles provides various experimental Apparmor profiles. It says do not expect them to work out-of-the-box. The package description says "These profiles are not mature enough to be shipped in enforce mode by default on Debian (and hence Devuan). They are shipped in complain mode so that users can test them, choose which are desired, and help improve them upstream if needed". Some even more experimental profiles are included in apparmor-profiles-extras.
Having now installed these optional profile packages the number applied in enforce or complain does not change because they are not being used. Some relate to programs I don't use on my PC (e.g pidgin), some are simply not being used at the moment (e.g. ping, avahi-daemon).
Not every program/process has an Apparmor profile. There is one for Thunderbird (as i don't use this I've moved it to /etc/apparmor.d/disable) but there isn't (to my knowledge) one for Evolution, a program I do use and is running at the moment. Also some programs (such as ping) may only run momentarily so you won't be able to see it enforced/complaining in a status report without opening a second xterm and timing it right.
Here's my apparmor status report with the two experimental profile packages installed:
$ sudo service apparmor status
[sudo] password for marjorie:
apparmor module is loaded.
46 profiles are loaded.
28 profiles are in enforce mode.
/usr/bin/evince
/usr/bin/evince-previewer
/usr/bin/evince-previewer//sanitized_helper
/usr/bin/evince-thumbnailer
/usr/bin/evince//sanitized_helper
/usr/bin/man
/usr/bin/pidgin
/usr/bin/pidgin//sanitized_helper
/usr/bin/totem
/usr/bin/totem-audio-preview
/usr/bin/totem-video-thumbnailer
/usr/bin/totem//sanitized_helper
/usr/lib/cups/backend/cups-pdf
/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session
/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session//chromium
/usr/sbin/apt-cacher-ng
/usr/sbin/cups-browsed
/usr/sbin/cupsd
/usr/sbin/cupsd//third_party
/usr/sbin/tcpdump
firejail-default
libreoffice-senddoc
libreoffice-soffice//gpg
libreoffice-xpdfimport
man_filter
man_groff
nvidia_modprobe
nvidia_modprobe//kmod
18 profiles are in complain mode.
/usr/bin/irssi
/usr/sbin/dnsmasq
/usr/sbin/dnsmasq//libvirt_leaseshelper
avahi-daemon
identd
klogd
libreoffice-oopslash
libreoffice-soffice
mdnsd
nmbd
nscd
ping
smbd
smbldap-useradd
smbldap-useradd///etc/init.d/nscd
syslog-ng
syslogd
traceroute
5 processes have profiles defined.
5 processes are in enforce mode.
/usr/sbin/cups-browsed (2141)
/usr/sbin/cupsd (2109)
/usr/lib/cups/notifier/dbus (2110) /usr/sbin/cupsd
/usr/lib/cups/notifier/dbus (2111) /usr/sbin/cupsd
/usr/lib/cups/notifier/dbus (3262) /usr/sbin/cupsd
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.I think you haven't understood that profiles are only activated ('defined') for running processes.
If I start up Document Viewer (evince) as process /usr/bin/evince with PID 5440 then apparmor defines another process and in this case puts it in enforce mode. Only running programs that have profiles have defined/enforced/complain processes which are then shown with their PID.
Compare this status result with my previous one:
$ sudo service apparmor status
apparmor module is loaded.
23 profiles are loaded.
21 profiles are in enforce mode.
/usr/bin/evince
/usr/bin/evince-previewer
/usr/bin/evince-previewer//sanitized_helper
/usr/bin/evince-thumbnailer
/usr/bin/evince//sanitized_helper
/usr/bin/man
/usr/lib/cups/backend/cups-pdf
/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session
/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session//chromium
/usr/sbin/cups-browsed
/usr/sbin/cupsd
/usr/sbin/cupsd//third_party
/usr/sbin/tcpdump
firejail-default
libreoffice-senddoc
libreoffice-soffice//gpg
libreoffice-xpdfimport
man_filter
man_groff
nvidia_modprobe
nvidia_modprobe//kmod
2 profiles are in complain mode.
libreoffice-oopslash
libreoffice-soffice
5 processes have profiles defined.
5 processes are in enforce mode.
/usr/bin/evince (5440)
/usr/sbin/cups-browsed (2102)
/usr/sbin/cupsd (5368)
/usr/lib/cups/notifier/dbus (5371) /usr/sbin/cupsd
/usr/lib/cups/notifier/dbus (5372) /usr/sbin/cupsd
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.Note: I've shutdown/restarted overnight which is why the PIDs have all changed. If I close Evince and open LibreOffice Calc I get:
6 processes have profiles defined.
4 processes are in enforce mode.
/usr/sbin/cups-browsed (2102)
/usr/sbin/cupsd (5368)
/usr/lib/cups/notifier/dbus (5371) /usr/sbin/cupsd
/usr/lib/cups/notifier/dbus (5372) /usr/sbin/cupsd
2 processes are in complain mode.
/usr/lib/libreoffice/program/oosplash (7583) libreoffice-oopslash
/usr/lib/libreoffice/program/soffice.bin (7631) libreoffice-soffice
0 processes are unconfined but have a profile defined.Beowulf is now 'stable', and Ascii 'oldstable' so you might well find that upgrading is a good idea.
Not sure what the effect of upgrading an only partially working apparmor will be on apparmor. I did a clean install and then restored my /home directory.
Anyway this is my status report in Beowulf. It says there are no processes unconfined that have a profile defined.
$ sudo service apparmor status
apparmor module is loaded.
23 profiles are loaded.
21 profiles are in enforce mode.
/usr/bin/evince
/usr/bin/evince-previewer
/usr/bin/evince-previewer//sanitized_helper
/usr/bin/evince-thumbnailer
/usr/bin/evince//sanitized_helper
/usr/bin/man
/usr/lib/cups/backend/cups-pdf
/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session
/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session//chromium
/usr/sbin/cups-browsed
/usr/sbin/cupsd
/usr/sbin/cupsd//third_party
/usr/sbin/tcpdump
firejail-default
libreoffice-senddoc
libreoffice-soffice//gpg
libreoffice-xpdfimport
man_filter
man_groff
nvidia_modprobe
nvidia_modprobe//kmod
2 profiles are in complain mode.
libreoffice-oopslash
libreoffice-soffice
3 processes have profiles defined.
3 processes are in enforce mode.
/usr/sbin/cups-browsed (2095)
/usr/sbin/cupsd (2065)
/usr/lib/cups/notifier/dbus (3187) /usr/sbin/cupsd
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.I never bothered with apparmor in Ascii but it 'works out of the box' in Beowulf (well almost I had to add a a line to/etc/apparmor/ usr.sbin.cupsd for /etc/dnscrypt-proxy/resolv.conf when I symlinked /etc/resolv.conf to it as then started to complain).
However I can confirm that in Beowulf /etc/rcS.d/S12apparmor does start before /etc/rcS.d/S13networking as one can can see by looking at /var/log/boot. I doubt if moving it any earlier (before file systems are mounted) would help.
I can't see any way of doing this in synaptic, however
from an answer on the DNG list you can do it using apt:
$ sudo apt update
and, when asked, answer 'yes' for each source.
$ sudo apt update
[sudo] password for marjorie:
Hit:1 https://updates.signal.org/desktop/apt xenial InRelease
Get:2 https://mirror.ungleich.ch/mirror/packages/devuan/merged beowulf InRelease [25.6 kB]
Get:3 https://mirror.ungleich.ch/mirror/packages/devuan/merged beowulf-security InRelease [25.6 kB]
Get:4 https://mirror.ungleich.ch/mirror/packages/devuan/merged beowulf-updates InRelease [25.6 kB]
Get:5 https://mirror.ungleich.ch/mirror/packages/devuan/merged beowulf-backports InRelease [25.6 kB]
E: Repository 'https://mirror.ungleich.ch/mirror/packages/devuan/merged beowulf InRelease' changed its 'Suite' value from 'testing' to 'stable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
E: Repository 'https://mirror.ungleich.ch/mirror/packages/devuan/merged beowulf-security InRelease' changed its 'Suite' value from 'testing-security' to 'stable-security'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
E: Repository 'https://mirror.ungleich.ch/mirror/packages/devuan/merged beowulf-updates InRelease' changed its 'Suite' value from 'testing-updates' to 'stable-updates'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
E: Repository 'https://mirror.ungleich.ch/mirror/packages/devuan/merged beowulf-backports InRelease' changed its 'Suite' value from 'testing-backports' to 'stable-backports'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
Get:6 https://mirror.ungleich.ch/mirror/packages/devuan/merged beowulf-backports/main Sources [243 kB]
Get:7 https://mirror.ungleich.ch/mirror/packages/devuan/merged beowulf-backports/main amd64 Packages [297 kB]
Fetched 591 kB in 26s (22.8 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
42 packages can be upgraded. Run 'apt list --upgradable' to see them.Can someone tell me how I go about updating my sources information, which are already set to Beowulf, now that Beowulf's Suite has moved from testing to stable?
If I try and update my package indices in Synaptic I get the message:
"Repository 'https://mirror.ungleich.ch/mirror/packages/devuan/merged beowulf InRelease' changed its 'Suite' value from 'testing' to 'stable' This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details."
This is repeated for the other sources.
I've read man apt-secure and it tells me how to update my repository if I'm a repository owner but not what I need to do as a simple user.
Sorry to hear of all your difficulties - this shouldn't be happening.
From your latest report you now seem to be getting stuck at an earlier stage than you did before. Previously it seemed to be a problem with the Nouveau video driver, which LarsH is now reported wont work with your new NVIDIA GPU and has suggested a fix to get you to a console.
FWIW I've now installed Beowulf on two different AMD-64 PCs, one Intel and the other AMD (with NVIDIA graphics) and did not have the particular problems you are now reporting, though to be fair my components are not cutting edge like yours. One of these was an entirely new install and the other was alongside an existing ascii installation.
1) I've always gone for legacy bios. Worked both times. My older motherboard has EFI but not UEFI. With the newer one I had choice in the the BIOS.
2) I've never actually installed from the live ISO, just used to check that I could boot into Beowulf (and get the WiFi working). The live install (if that is what you are using) is designed to be straightforward and therefore pretty unbreakable for a straightforward one-disk install but I'm not aware of exactly what choices it makes for you.
3) if you are using one of the other installers they can get more complicated and there is greater scope to be confused.
However:
3) You don't have to install /boot on a separate partition. It may be a bit more robust to do so if you have more than OS installed or your disk config is complex. On one of of mine I choose to keep it separate/simple because my root and /home partition are mounted as RAID1, on the other because they are LVM.
4) The boot partition doesn't have to be formatted DOS or even EXT2. Both mine are EXT4.
5) The installers themselves haven't changed between ASCII and Beowulf. I note that other users have been finding some bugs in the isos, particularly if burnt to optical CD/DVD, rather than USB, which the developers are fixing, but these are mostly pretty minor.
6) As you're getting inconsistent results it may be worth confirming (if you haven't already done so) that you isos have not got corrupted.
I would be interested to know how many of us still use optical CD/DVD as installation media.
I've got one, but you can tell from the fact that is PATA that it's old. Solid drive, but my only use for it these days is to rip audio CDs.
Although I suspect we typically write ISOs to USBs (I also have the live iso loop mounted on hard disk) the nomenclature on the installers doesn't seem to have caught up with this (as a possibility let alone as a default) and the sources.list still points to a useless CD mount point, which has causes problems when you install, wireless and ethernet aren't working, but there are wireless drivers on your usb (this has happened to me, and to others on the forum).
FWIW. I've never had any media problems with the installation iso written to usb. I've used the live iso (just to check for compatibility) and then the full 'DVD' iso to do an expert install. Used both for ASCII (stable) and Beowulf (Beta 1).
The problems I have had relate to the expert partitioner (I got confused as to the sequence of steps required when installing on RAID1), with installing the NVIDIA drivers subsequent to initially installing OK with the default Nouveau drivers.
I also could never get it to work installing over ASCII (got into dependency hell) so did a new install and then merged a copy of my ASCII /home directory back in.
As a comment on what's on the lave iso, for me it would be useful to have fsarchiver included, as with it the live iso is quite useful as a rescue disk (I hadlbacked up snapshots of the root and /home directories as .fsa archives and could reversibly swap them in and out. As it is I had to keep re-installing fsarchiver every time I booted the iso.
OK, so you're installing on a different machine than you installed Devuan ASCII on. It could be helpful to tell us what the hardware is:
Processor, UEFI/Legacy BIOS, 32 or 64 bit, Memory, Disk(s) type, Graphics card/adapter, Wireless card.
If you had used the same machine then it is unlikely that the hardware (that worked with ASCII) wouldn't work with Beowulf. Not saying you shouldn't install on a fresh machine.
As you have installed on a different machine then booting up the live CD/usb will allow you to see whether the standard-case Beowulf installation software is compatible with the hardware (graphics, wireless card, etc.) you have on it. You should be able to boot to a graphical screen and (attempt to) configure your wifi
.
It's up to you then, if it works, whether you install from the live CD/usb. If the wireless doesn't work, once configured i.e. you still need additional drivers, and you can't use ethernet then the live CD/usb is not a good idea (nor the netinstall iso).
Also the live CD/usb is limited to a simple, whole disk install and it starts up in XFCE, which may differ from what you want/have been trying to install.
You haven't said which Beowulf iso you have been trying to use:
Beowulf is still Beta. There are now several generation of Beta, the latest is 3, which fixes some of the problems in the earlier versions.
There are also different ISO. The Live iso, the Netinstall iso, the basic (CD1+some of CD2-4) desktop isos and the full (DVD) desktop iso. https://beta.devuan.org/os/documentatio … all-devuan.
Sorry to go back a bit from the useful suggestions about opening Beowulf in a console.
Can you please clarify:
Which Beowulf .iso you are using?
Have you tried to boot up the live Beowulf CD/usb? If so, does that work apart from the wireless (you indicate that there is a problem with the atheros driver)?
Are you doing a full disk on-metal install, a VM install or are you adding Beowulf on an existing system in new partitions(s) with e.g. your ascii install also bootable?
What configuration are you trying to install (partitions/display manager/desktop).
Are you getting any console output before it fails to a blank screen? Usually there is quite a lot of output before it tries to load your chosen graphical interface.
Great - we have progress.
You haven't said what your setup is. On mine I could get suspend (pm-suspend) working on both ASCII and Beowulf but, by default, hibernate (pm-hibernate) didn't work on Beowulf.
There is a 'hibernate' option on my standard logout, which I think uses upower, however it doesn't work on Beowulf. It did work and didn't interfere on my ASCII installation.
Anyway on Beowulf I fixed pm-hibernate by installing the uspsusp package, which provides user space rather than kernel hibernation and then configured pm-utils to use it.
Have a look in your /etc/pm/config.d/defaults file. Mine looks like this:
##########################################################
# DO NOT EDIT THE FILE in /usr/lib/pm-utils/ #
# #
# Edit this in /etc/pm/config.d/ instead! #
##########################################################
# Default method to power down the system when hibernating.
# If commented out, the system will use the kernel default as a
# default value.
#
# Check /sys/power/disk for valid values. The default value
# will be surrounded by [square brackets].
HIBERNATE_MODE="platform"
# Whether we need to post the video card when resuming from
# hibernate. You should not normally need to set this.
# In the future pm-utils will get this setting from HAL.
#
# Valid values are "no" and "yes"
# HIBERNATE_RESUME_POST_VIDEO="no"
# The default sleep/wake system to use. Valid values are:
# kernel The built-in kernel suspend/resume support.
# Use this if nothing else is supported on your system.
# uswsusp If your system has support for the userspace
# suspend programs (s2ram/s2disk/s2both), then use this.
# tuxonice If your system has support for tuxonice, use this.
#
# The system defaults to "kernel" if this is commented out.
SLEEP_MODULE="uswsusp"
# These variables will be handled specially when we load files in
# /etc/pm/config.d.
# Multiple declarations of these environment variables will result in
# their contents being concatenated instead of being overwritten.
# If you need to unload any modules to suspend/resume, add them here.
SUSPEND_MODULES="ath9k ath9k_common ath9k_hw ath"
# If you want to keep hooks from running, add their names here.
# HOOK_BLACKLIST=""
# If you want to unconditionally add parameters to the commandline,
# add them here.
# ADD_PARAMETERS=""
# If you want to ignore commandline parameters, add them here.
# DROP_PARAMETERS=""
# If you need to synchronize the system clock across a suspend/resume or
# hibernate/thaw cycle, set this variable.
# NEED_CLOCK_SYNC="true"In line 30 I've uncommented SLEEP_MODULE="uswsusp", which means that it now uses uwsusp rather than the kernel. I've left everything else as is, apart from lower down, where I unload my atheros wifi drivers as they refuse to power down when asked: however this is not needed to make hibernate work, even on my setup. Elsewhere I've also added a call to load a login screesaver, which does increase security a bit on resume. If you get hibernate working I'll tell you how to do this.
Lets see if that works better.
If not you may want to look at alternatives to HIBERNATE_MODE="platform" and/or install and try tuxonice as an alternative to uspsusp.
Thanks, Head-on-a-stick, that works.
Note for anyone else searching on this topic, having edited the default run level values in /etc/init.d/nftables you have to remove any existing rc.d symlinks before you reset them, so:
$ sudo update-rc.d nftables remove
$ sudo update-rc.d nftables defaultsIf you don't do that it wont just overwrite the existing symlinks (you do get a warning).
Also
$ sudo service nftables start
$ sudo service nftables status don't provide any output. However I did check that the firewall was working as intended using nmap from a different pc on the network:
$ sudo nmap --top-ports 500 mail
Starting Nmap 7.70 ( https://nmap.org ) at 2020-04-22 15:17 BST
Nmap scan report for mail (192.168.1.xx)
Host is up (0.0054s latency).
Not shown: 493 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http
143/tcp open imap
443/tcp open https
587/tcp open submission
993/tcp open imaps
MAC Address: 2D:70:6B:23:64:91which are just the ports I had configured to be open.
Sorry I previously mentioned pm-tools package. Of course that is pm-utils, but I guess you found that anyway.
I presume pm-suspend is also not working for you?
You should check /var/log/pm-suspend.log to see if it tells you anything about why it's not running (the log is common to both suspend and to hibernate). If its not there then something is very amiss.