Installing inetutils-ping (which removed iputils-ping) did remove that warning, so that part is solved.  Thanks :-)

The change with tpm2-abrmd (adding the '-u tss' to line 17 of /etc/init.d/tpm2-abrmd) didn't help.

# service tpm2-abrmd start
Starting TPM2 Access Broker and Resource Management Daemon: tpm2-abrmdIllegal option -u
/sbin/start-stop-daemon: unable to stat //tss (No such file or directory)
 failed!

I *do* have a user "tss" listed in /etc/passwd.  I guess I'm wondering, do I need this service?
After a little bit of internet searching, I think I may not even have tpm enabled on my motherboard.  Maybe that's part of the problem.  I'll reboot and check the ol' bios.

OK, under the "Trusted Computing" section of bios setup, my motherboard informed me that no device was found.  Guess it's not built-in and I never added it.  So I'll remove the tpm2-abrmd package, not sure why it got pulled in.  Sorry for the noise

These log entries look very similar to an issue I had at the beginning of the year.

What fixed it for me was removing (actually, renaming, in case it was needed later; it wasn't) the file /var/lib/mysql/ib_logfile0

cd /var/lib/mysql
mv ib_logfile0 ib_logfile0.bad-renamed
service mariadb start

can you open the pihole web admin page? ( try http://192.168.1.3/admin ... or whatever the machine's ip address is)

Basically the same as mine, except for PIHOLE_DNS_1=127.0.0.1#5335
This might be valid, I'm not sure, but it's not how mine is set up at all.  My pihole goes out to other DNS servers for its non-piholed queries.  I also don't see IPV4_ADDRESS or IPV6_ADDRESS in your configuration.  Mine is:

PIHOLE_DNS_1=208.67.222.222
PIHOLE_DNS_2=208.67.220.220
PIHOLE_DNS_3=198.6.100.194
PIHOLE_DNS_4=9.9.9.9
IPV4_ADDRESS=192.168.1.4/24
IPV6_ADDRESS=

what happens when you run these:

root@devuan:/etc/pihole# ss -tnlp | grep 4711
LISTEN     0      5      127.0.0.1:4711                     *:*                   users:(("pihole-FTL",pid=2819,fd=10))
LISTEN     0      5          ::1:4711                    :::*                   users:(("pihole-FTL",pid=2819,fd=13))
root@devuan:/etc/pihole# telnet 127.0.0.1 4711
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
root@devuan:/etc/pihole# 

Thanks for this, I knew about Steve's repository, but wasn't aware that 32-bit was included there (I rarely use my 32-bit machine).

I don't have the *exact* same setup as you (32-bit on beowulf)... I do have amd64 running beowulf, and i686 running chimaera.  Both of them show firefox at 91.12.0esr.  my arm64 running ascii shows firefox at 91.11.0esr.  Have you run apt update recently?  Do you have anything in /etc/apt/preferences.d/ that would prevent firefox upgrade (apt pinning)?

An alternate option for this particular case (apparmor) would be to create a file, e.g. /etc/apt/preferences.d/noapparmor
Contents:

Package: apparmor*
Pin: release n=beowulf
Pin-Priority: -1

Change the release name if you're not using beowulf.

Adding to this thread, in case someone finds this useful, or needs the info at some later point.  To get the wifi (b43) working on this imac, I followed the steps at http://linuxwireless.sipsolutions.net/e … ivers/b43/ under "Other distributions" to build the driver manually.
In case that page goes down, basically it came down to this:

wget http://bues.ch/b43/fwcutter/b43-fwcutter-018.tar.bz2
wget http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
tar xjf b43-fwcutter-018.tar.bz2
cd b43-fwcutter-018
make
sudo make install
cd ..
tar xjf broadcom-wl-5.100.138.tar.bz2
sudo b43-fwcutter -w /lib/firmware broadcom-wl-5.100.138/linux/wl_apsta.o

a reboot or modprobe b43 should get the device driver loaded, and wifi available.  I also had to set the wireless interface to "wlan0" in wicd preferences., but this might be done automatically if you reboot rather than use the modprobe command.

Thank you both for the replies.

Unfortunately, I am not able to boot the amd64 debian buster netinstall cd, either.  The prompt that comes up trying to boot any amd64 disc (so far) is:
1.
2.
Select CD-ROM Boot Type :
(and all keyboard input is ignored at this point)

Also, thanks for the hint on using the desktop *live* installer disc.  I'll try that next, I think I should be able to get that to work.  Even if I can't boot it directly, I should be able to mount it and run the installer from it.

I use devuan ascii daily on my desktop, 3rd gen core i5 with 32gb ram, nvidia gtx650, dual monitor, 2tb + 250gb hdd
also on a raspberry pi 3b+  16gb microsd

devuan jessie I use twice a week on laptop, it's got some amd cpu from around 2010-2012, 8gb ram and a 250gb hdd
also devuan jessie once a week on a very old desktop (actually planning to replace it with a newer desktop soon), pentium 4 with 512mb ram and a 40gb hdd

also considering to replace debian 8 with devuan ascii on a remote server (or two) that I manage for work

To reply to my self (or is it preferred to edit the original post):
Apparently this didn't begin with the Ascii upgrade (which I did 2 weeks ago) -- /var/log/pm-suspend.log has a date of Fri Jun 29 (morning wakeup time).  There's no record of Fri Jun 29 (night sleep time) or Sat Jun 30, Sun Jul 1 in /var/log/pm-suspend.log at all.  This is likely when the suspend/resume hooks stopped running.  This seems strange to me.  I have rebooted in the meantime, which did not correct the issue.  On Jun 29 I did remove mono and a bunch of things along with it... I'll see if any of that is related.  So at this point it seems less likely a bug and more likely something I've done to my own system.

[Mon Jul 2 AM edit]
So last night I directly ran /usr/sbin/pm-suspend instead of /usr/bin/xfce4-session-logout --suspend
The result was the hooks were called on suspend/resume, /var/log/pm-suspend.log was updated, screen was not locked on resume (of course).
I suppose I could change my suspend routine to call /usr/bin/xflock4 then run /usr/sbin/pm-suspend, after granting my user account the ability to run /usr/sbin/pm-suspend .  Still unclear as to what changed with xfce4-session-logout .