Also, the destkop installer iso does copy correctly to the first (fat32) partition if you use the ISO_1 option, because it unpacks the iso file and no single file is bigger than 4GB. But you still have to mount it manually.

I have never been able to get [Sane] to work.
Maybe something related to the [sane-backends] file?
A complicated configuration process?
No idea.

The latest version can be downloaded from the [fossies.org] website.
See: https://fossies.org/linux/sane-backends … -scanner.c
Be aware that it is not a [*.deb] file, you have to compile it (?).

In any case, [sane] has proven to be too complex for me and [Document Scanner] served my simple needs:
- scan documents/objects to max definition with my Umax S-6E SCSI scanner.
- save as [*pdf] or graphic formats.

It worked out-of-the-box when I first installed it on [ascii] years ago, no issues ever.
[sane] needs to be installed for [Document Scanner]* to work.
* listed as [simple-scan] in the repositories.

Best,

A.

1. does ZFSbootmenu work well with Devuan?

i can't answer that, but i have been using ZFS for non-root storage without issue
for years. i have ZFS pools on spinning rust, SATA SSD and NVME SSD and
they're working well. the NVME set-up is an experiment, but it is working. i have
4x1TB NVME in RAID-0 (live fast, die young!) for storing QEMU qcow2 images
and it has not fallen over yet.

yeah, i am a fan of ZFS

due to licensing conflict, CDDL v. GPL, ZFS has to be bolted-on after the fact.
this is done via kernel modules that are built using linux kernel dkms system.

i prefer to use backports for ZFS to better stay up-to-date. so, for me, this is
what i did:

sudo apt install dkms
sudo apt install -t daedalus-backports zfs-dkms
sudo apt install -t daedalus-backports zfsutils-linux
sudo apt install -t daedalus-backports zfs-zed

the only ZFS-on-root how-to i could find on here is an old one (2020)
https://dev1galaxy.org/viewtopic.php?id=3794

there is another thread (2022) talking about using ZFS (somewhat). not
sure if it will be helpful to you, but just in case
https://dev1galaxy.org/viewtopic.php?id=5285

once installed, ZFS puts a bunch of scripts in /etc/init.d:
   zfs-import
   zfs-load-key
   zfs-mount
   zfs-share
   zfs-zed

the ZFS configuration file is /etc/modprobe.d/zfs.conf

and the trim+scrub cron jobs are in file /etc/cron/d/zfsutils-linux

hope this helps

Also used the chat bots to create this https://github.com/rations/NAMp/releases You can load multiple nam captures and change through them by turning the dial. It's supposed to be more like using a real amp. So if you capture the gain from 1 to 10, turning the dial is like turning the dial on a real amp. Or you can just load a folder of all different captures (up to 64).

There's a VST3 version for linux and windows but linux also gets a standalone version that is a VST3 and LV2 host.

i get no wired-connection (disconnected) , maybe did something wrong

Upgrade snetaid again

psmouse should be loaded by vdev-modprobe.sh early on during boot, as it scans the input and serial subsystems, amongst others. I haven’t experienced any problems with the touchpad on my laptops. Perhaps that particular machine requires a 2nd vdev-modprobe.sh pass later on. I’ll add a 2nd run in the next vdev build.

https://soundcloud.com/upliftah/love

Using refracta2usb instead of ventoy.

This is how I always do a netinstall.

Isn't it the kernel itself (perhaps the GPU driver) that should detect keyboard activity and turn on the signal to the monitor to make the text console visible?  Or, is there a userspace process involved with that?

Motherboard is an Asus Pro WS X570-ACE.  CPU is an AMD Ryzen 7 5800X 8-core.  GPU chipset is Navi 14 [Radeon RS 5500/5500M / Pro 5500M].  One physical monitor is on an HDMI port via a Kopul HDMI switcher.  The other physical monitor is on DisplayPort.  Current kernel is 6.12.101+deb13-amd64, but symptoms happened with 1 or 2 earlier Excalibur kernels.

The system serves as a droid control ship for VNC sessions with diskless zero/thin-client display heads that boot via PXE.

Normally overnight, I push the power-off buttons on the physical monitors to save energy.  At least with earlier Devuan releases, if the monitors are left on and the system tries to blank and power down the monitors, the monitors will unblank and turn on later during the night.  I use "setterm --blank 0 --powerdown 0" to keep the system from trying to blank and power down the monitors.

The problematic sequence is

1. The physical monitors are powered off to save energy.

2. Someone starts one of the diskless machines and launches a VNC session.

3. I push the power buttons on the physical monitors.  After showing the manufacturer's logo for several seconds, the monitors report no signal and go into standby state.

4. I tap on the keyboard to try to wake up the monitors (or keep them awake).  At this point, Num Lock, Scroll Lock, and Caps Lock turn on/off the respective LEDs.  As an experiment, I once logged in blindly, and the monitors did not display anything at that time.

5. Immediately after the VNC session is terminated, the monitors come out of standby state and show the results of the blind login and a couple of commands that had been done blindly.

Any suggestions for getting the GPU to send signal to the physical monitors so they will power up and display stuff?

Thanks!