You are not logged in.
What kind of shares are they? NFS, Samba, local partitions or something else?
What's in /etc/fstab?
Also please post the output of blkid and maybe lsblk. Maybe other stuff, too after we narrow it down.
In chimaera and daedalus, the nvidia firmware is in firmware-misc-nonfree. The version of firmware-nvidia-graphics in daedalus-backports probably has support for newer hardware and is meant to be used with the backports kernel.
My old GT218 works without the firmware, but as Altoid mentioned, there are a lot of complaints about missing firmware. I don't recall if I could see any difference when I finally installed the firmware.
Note: you can have two monitors with nouveau. The monitor settings in xfce, lxde and lxqt will let you configure two monitors. (maybe more - I never tried three).
Your description of the debian installer's network setup is what I see when I use the devuan installer on a laptop. I don't know how you got to the screen you described. I do know that near the beginning of the devuan install there's a screen that asks you to supply firmware on a separate usb stick, and in most cases you should ignore that and continue. But that comes before the screen that lets you choose the interface to set up.
No, it's not in -security. Note the "devuan" in the version string. It's a forked package and hasn't been updated yet. I don't know if the maintainer is working on it. Maybe a bug report for tomcat9 in devuan would help. (email method is easy)
https://bugs.devuan.org/Reporting.html
I don't see scripts on that page, just deb packages. And they aren't the same ones that are in debian/devuan. The versions of guile don't match the current versions in bookworm/daedalus. You're probably better off installing the packages from the repo.
apt policy shepherd
shepherd:
Installed: (none)
Candidate: 1.0.3-1
Version table:
1.0.6-2 10
10 http://deb.devuan.org/merged ceres/main amd64 Packages
1.0.3-1 500
500 http://deb.devuan.org/merged excalibur/main amd64 Packages
I'm curious to see what glxgears tells you. Added xlibre to a refracta-excalibur (xfce) VM and tested in qemu and hardware against the same system with xorg.
In qemu...
xlibre: 18FPS
xorg: 800FPS
live-usb on hardware (Thinkpad T450s)...
xlibre: 60FPS
xorg: 60FPS
I don't know enough to make any intelligent comments about that. I do notice that xlibre is slow in qemu.
Thanks for all the testing and thanks to all for helping with this. I'll keep this arrangement, and I already made a minimal-live iso with mdadm included but not installed. That one and future desktop isos won't have "noraid" in the name, but that's what they will be.
I think I found a simple solution. This iso does not have mdadm installed or have the config files for it. It does have the mdadm package sitting in the root of the filesystem, and it can easily be installed with sudo dpkg -i /mdadm*.deb. You don't need a network connection for this to work.
https://files.devuan.org/devuan_excalib … p-live.iso
Tested in vbox with a RAID1 with two virtual hard disks. I booted the iso with the drives attached, installed mdadm and was able to run mdadm commands. There was no active array until I assembled /dev/md0. Please confirm.
I don't recall exactly what the problem was, but some packages had to be left out of debootstrap builds of excalibur early on. Search forum for 'rsyslog logrotate cron' and you'll find a few posts about it. The live iso build is patched to add logrotate and rsyslog later in the build. The installer isos are going to get a fix (maybe already did) for that.
Yeah, I ran into that "module is in use" warning. I managed to screw up my builds yesterday so that the desktop wouldn't start, and I finally found my error this morning. Right now I'm leaning toward removing all the mdadm stuff from the live and letting people rely on the rescue functions in the netinstall iso. I think I'll make a no-raid iso for the main site and any other test isos can be uploaded to a different location.
I'm assuming that the netinstall gives you more control over assembling raid arrays, but I've only used it a couple of times and never looked into the code.
I'm still a little frazzled from yesterday. New iso(s) coming later today (probably).
Thanks for persevering.
- I mounted the file "devuan_excalibur_6.0-preview-2025-08-25_0923_amd64_desktop-live.iso" to the local file system, copied ./live/initrd.img to a temp directory and extracted it using the same 3* cpio + zstdcat|cpio, and examined ./etc/mdadm/mdadm.conf. The contents look like a default file. No "AUTO -all" or dummy "ARRAY <ignore>" lines.
I think you nailed it. The build script copies the kernel and initramfs to the /live directory from the chroot system that's being built. I think it's doing it too early, so it's not getting the final changes. I have to look at the code to confirm this (and correct it).
FWIW - unmkinitramfs will unpack the initrd easily with just one command.
I tried adding "blacklist md_mod" to /etc/modprobe.d/mdadm.conf and rebuilding the initramfs. Did it with and without commenting out the existing line (...ro=1) and it didn't help. All the raid modules are still being loaded.
Also noted that 'modprobe -r md_mod' fails with message that md_mod is in use. There's no raid on my test box, so I don't know who is using it. (mdadm is not running)
Another option I thought of would be to build the iso without mdadm installed but with the deb package in the iso in case someone needed it. I think that could work, but I'm not sure.
One other thought came up after booting an older kernel whose initrd was made before installing mdadm. That would be to have two initrds in the iso, one of them made without mdadm installed and one with. That's more complicated to automate.
I think part of my response belongs in the thread where I posted.
I was wondering why the first post in this thread contained a response to something that obviously came before the first post. Wasn't sure if I needed a time machine to see it. A link would suffice.
fsmithred (I compiled transcode without detailed step-by-step instructions.)
lsmod | grep raid or lsmod | grep md to see what modules are loaded.
I did that and decided that md_mod was probably the one to blacklist. When I went to /etc/modprobe.d to create a file, I saw that mdadm.conf was already there. Does anyone else have this file?
# mdadm module configuration file
# set start_ro=1 to make newly assembled arrays read-only initially,
# to prevent metadata writes. This is needed in order to allow
# resume-from-disk to work - new boot should not perform writes
# because it will be done behind the back of the system being
# resumed. See http://bugs.debian.org/415441 for details.
options md_mod start_ro=1
g4sra, thanks. Good find.
If "nodmraid" in the boot command works, then I can add that to all the boot menu entries except one and label it "with mdadm" or similar. I like that idea better.
This one has START_DAEMON=false in /etc/default/mdadm:
https://files.devuan.org/devuan_excalib … p-live.iso
Eeqmcsq, I added your edits to mdadm.conf and made a new iso. Thank you!
https://files.devuan.org/devuan_excalib … p-live.iso
stargate, this is the first such report I've seen and mdadm has been active in devuan-live for 10 years and refracta isos for a few years more than that (since 2011 I think). I don't know what other live distros include mdadm, so I can only say that thousands or maybe tens of thousands of users have booted these isos.
Edit/update: That iso somehow got the default /etc/default/mdadm with START_DAEMON=true. I'm making a new iso now.
Also, I can't seem to start mdadm when running this live-iso. Can you still use the mdadm command without the service running?
Installing cryptsetup-modified-functions might do the same thing as your edited version. I didn't need this in daedalus, but the author of the patch (devujan) did need it. I don't know if he still needs it in excalibur or if it needs to be changed.
https://dev1galaxy.org/viewtopic.php?pid=41064#p41064
https://git.devuan.org/devuan/cryptsetu … -functions
Well, it gets even weirder. I booted the the latest excalibur desktop-live iso and /home/devuan/Desktop/refractainstaller.desktop is already executable, yet when I open it, I still get the popup asking me to Launch Anyway, Mark as trusted, or cancel.
I don't know how to avoid that popup without making the .desktop file executable. I could mark it executable during the build, but I don't recall ever having to do that before. I never start it from the desktop icon, so I don't know when it started doing that.
And no, the one on the desktop is in /home/devuan/Desktop. The one in /usr/share/applications/ shows up in the apps menu. (another way to start it.)
In the running live system, open a terminal and run:
sudo refractainstaller-yad
I don't have all those dependencies installed and I don't really have yt-dlp installed, but it runs fine from my ~/bin. I have python3-requests installed, but not the other two you listed with it.
wget https://github.com/yt-dlp/yt-dlp/releases/latest/download/yt-dlp
chmod +x yt-dlp
The live-isos have wireless firmware installed. This one is new:
https://files.devuan.org/devuan_excalib … p-live.iso
sha256sum:
667f3e82469a36aa95bcbe11db67fbd96ea59ec41c66f96407d1334033db2658 devuan_excalibur_6.0-preview-2025-08-13_0014_amd64_desktop-live.iso
Almost forgot to mention:
That early screen that asks you to insert a usb with firmware can often be ignored, and the firmware package will be installed later in the installation process (unless you select expert install and tell it not to install the firmware).
Nobody has changed that config setting because Devuan is Debian-based, so we're all still waiting for it to be rolled out.
I don't see 'bpo' in the kernel version. It looks like it's the excalibur kernel. Please post your /etc/apt/sources.list and any other sources apt is using.
I just booted excalibur with that kernel and firmware-iwlwifi is working correctly. (version 20250410-2)