You are not logged in.
Does the netinstall iso have firmware-mediatek on it?
Yes, there's firmware-mediatek_20260810-1_all.deb
However, I found in firmware/Contents-firmware:
/usr/lib/firmware/mediatek/mt7925/BT_RAM_CODE_MT7925_1_1_hdr.bin firmware-mediatek_20260622-1_all.deb non-free-firmware
/usr/lib/firmware/mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin firmware-mediatek_20260622-1_all.deb non-free-firmware
/usr/lib/firmware/mediatek/mt7925/WIFI_RAM_CODE_MT7925_1_1.bin firmware-mediatek_20260622-1_all.deb non-free-firmwareSo it appears I need to update the Contents-firmware file to the correct version on the disc image.
Hopefully it will all be good in the next iso (check mirrors in a while)
Please, when you have an opportunity, test the new devuan_freia_7.0-202609031921_amd64_netinstall.iso - it should be on the mirrors by now. And if you don't mind, report back whether that fixes the issue.
Thanks for reporting this. I'll update the freia installer soon... it still was using the excalibur Contents-firmware file which I believe is the source of your issue.
syslog-ng will replace rsyslog as default logging in the future ?
I don't know, haven't taken a poll or anything. So far it's just a test on the netinstall. Have you had any issues with it?
The reason for the change: https://www.rsyslog.com/clarifying-ai-f … r-rsyslog/
Of course, you're free to remove syslog-ng and replace it with rsyslog after the installation is complete. And I may change the default back later, if that's what most users want.
Another option...
With qemu, use -nic user option, and set up networking as follows
ip address add 10.0.2.15/24 dev eth0
ip link set dev eth0 up
ip route add 10.0.2.0/24 dev eth0
ip route add default via 10.0.2.2 dev eth0Also, your /etc/resolv.conf should contain
nameserver 10.0.2.3From there, you should be able to apt install dhcpcd-base or whatever package(s) you want.
With virtualbox, you could change the network to bridged, and set up static networking as though it were a physical device on your LAN. For example, if your LAN uses 192.168.1.0/24 with a gateway of 192.168.1.1 (I think this is a common default setup), you could do something like this
ip address add 192.168.1.20/24 dev eth0
ip link set dev eth0 up
ip route add 192.168.1.0/24 dev eth0
ip route add default via 192.168.1.1 dev eth0Obviously, you'd want to use an address not in use by another device. That was just an example.
Whatever is going on, it's blocking gnlug.org just like the other mirrors. All I get are "could not resolve" errors for both the original and these repositories.
That's odd. Is your nameserver accessible? What's in /etc/resolv.conf?
from what I'm seeing on daedalus, nvidia-driver and nvidia-kernel-dkms are at version 535.261.03-1 (daedalus), 535.309.01-0+deb12u1 (daedalus-security), and oddly 535.216.03-2-bpo12+1 (daedalus-backports).
maybe this would work?
apt install nvidia-driver/daedalus-security nvidia-kernel-dkms/daedalus-securityOf course, you'll need to have apt working properly first.
I would also point out, according to what you wrote,
the --write-link, --write-url-link, and --write-desktop-link options can write .url or .desktop shortcut files ...
If you don't use those options (--write-link, --write-url-link, or --write-desktop-link), this particular issue won't affect you. If you do use them, and don't want to check the output files, then by all means, update to a newer version (which is probably necessary anyway for it to work with youtube)
OK. For now it seems like you need to manually run
sh /lib/debian-installer-startup.d/S21ventoy-loop to get your iso loop device set up properly.
Could you run the "expert install" and find out on which step does it freeze? Are you able to change to tty4 at that point and read any debugging text?
OK, your S21ventoy-loop file looks good.
What does this return?
losetup -aIf it returns nothing, try this
sh /lib/debian-installer-startup.d/S21ventoy-loop ; losetup -aIf there's this line: /dev/loop0: 0 /mnt/devuan_excalibur_6.1.1_amd64_netinstall.iso - then try this:
mkdir -p /cdrom ; mount -t iso9660 /dev/loop0 /cdromIf it mounts correctly, then see if installation will continue.
If there are any errors/info displayed, please report back.
6) re-write the excalibur netinstall iso to usb stick using a different writing program (or: burn to cd/dvd media)
There's probably a 7), 8), 9), and 10) that I haven't thought of yet, also.
You seem to have a few options at this point. It's up to you which to choose (in no particular order):
1) try an experiemental excalibur netinstall iso at https://files.devuan.org/user/tempforever/
2) try excalibur desktop-live iso
3) try freia netinstall iso (freia is in "testing" but it should mostly work)
4) continue trying the released excalibur netinstall iso
(FYI, I've been unable to get #1 and #3 to boot properly from ventoy, at least in efi mode. But you're welcome to test, of course.)
If you choose #4 above, it would be helpful to know the debugging output text on tty4 after it fails to detect installation media.
For reference, the output on my test system (with ventoy) says:
cdrom-detect: Searching for Debian installation media...
cdrom-detect: Devices: '/dev/sr0'
cdrom-detect: CD-ROM mount succeeded: device=/dev/sr0 fstype=iso9660
cdrom-detect: Detected CD 'Devuan GNU/Linux 6.1.1 excalibur amd64 - netinstall 20260425'
kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
kernel: ISO 9660 Extensions: RRIP_1991A
cdrom-detect: Detected CD with 'stable' (excalibur) distribution
anna-install: Queueing udeb eject-udeb for later installationWhat happens if you try to run, in tty2:
mkdir -p /cdrom ; mount -t iso9660 /dev/sr0 /cdromAlso the output of this might be helpful:
ls /sys/class/block(you can press alt + left-or-right arrow to switch between tty windows)
My first suspicion would be to verify the download (check the sha256sum). Secondly, verify that it was written to your boot media without any errors. Is this a cd, usb stick, virtual machine install, something else ? Also, which ISO file are you using?
The installer iso should allow you to press alt-F4 to view the latest ouput, there may be some debugging text there that will let you know what it's locked up on, or waiting for, or at least what succeeded last. alt-F2 and alt-F3 will activate terminals in which you can issue commands, and alt-F1 will go back to the installer.
Another option is to do the "expert install" which will help narrow down on which point it is stuck.
Scrollbars that jump many pages when you click the wrong place
GTK themes can contain general GTK settings. Devuan Excalibur's theme contains a settings.ini containing the line
gtk-primary-button-warps-slider = falseThis makes the scrollbar only scroll by one page if you left-click it somewhere other than the handle.
If you want this behavior all the time and not just when you're using Excalibur's default theme, simply create ~/.config/gtk-3.0/settings.ini and add the same line to it.
Thanks for posting this! The same setting works on Daedalus also. Note that if you're creating a settings.ini file, that code should be in a "[Settings]" group, like so:
[Settings]
gtk-primary-button-warps-slider = falseOtherwise you'll get a gtk warning, failed to parse settings.ini: Key file does not start with a group.
There's this page, if you like trying to reproduce/fix bugs... https://bugs.devuan.org/db/ix/full.html
chromium 150 appears to be working okay on a new installation (that is, I did not previously have 149).
does 'chromium --temp-profile' work?
For the installer ISOs, 6.1.0 -> 6.1.1 changes are listed here: https://git.devuan.org/devuan/installer … a1ca9fb841
Perhaps someone else with a raid setup can assist you with /dev/md124 problem.
I hadn't tested a 2-optical drive system with the installer in the 2nd drive, and was unaware of the issue.
Very nice.
I know it's simple and maybe you want to keep it that way.
One feature request would be, after searching, to double-click an item in the list would either (1) view that page, or (2) put it in the "view page" text box.
Another feature request would be for the new window it opens to remember its last size and position - or at least make it as wide as the text that it's displaying, to prevent the word-wrap.
I installed the iso and got a boot menu. The system would not boot. I gave it 15 minutes to boot.
Could you explain what does happen? What's on the screen?
I use overlay-boot on several servers now. A couple different configurations -- mainly using overlayfs, one is using a loop image file with drbd. In fact just this last weekend I updated my installation of overlay-boot -- it was a bit outdated. There's now a SHARE option that will bind-mount, which I've also found helpful for my use case. In my overlay-boot configuration, the subhost's LOWER directory is a higher version of devuan than the hosting system (I created it with debootstrap --minbase and added things as needed). For example, on a chimaera host I run daedalus subhosts; on a daedalus host, I run excalibur subhosts. It's taken a bit of trial-and-error getting things set up, but for the most part it's been working well.
Did you have any particular question about overlay-boot?
No github is required to report bugs - that's what reportbug is for. I think you'll want to use -B debian since udisks2 is not a forked package.
I can confirm that the issue is not with labels, at least not that alone. Perhaps it's a combination of label and apfs, or even just an issue with apfs.
I did a file-based loopback device, with vfat and ext and swap partitions. None of them have lables, but udisksctl worked properly on them all (except swap which won't mount).
The vfat partition:
udisksctl info --block-device /dev/loop0p1
/org/freedesktop/UDisks2/block_devices/loop0p1:
...
org.freedesktop.UDisks2.Filesystem:
MountPoints: /media/tempo/D5A1-A960
Size: 0
...One of the ext4 partitions:
udisksctl info --block-device /dev/loop0p2
/org/freedesktop/UDisks2/block_devices/loop0p2:
...
org.freedesktop.UDisks2.Filesystem:
MountPoints: /media/tempo/fa4de3c0-b3c5-4352-81c6-f3447ad475c6
Size: 5626658816
...In all of these cases, udisksctl unmount worked.
What's the filename of the ISO you're using?
From your description, I'm pretty sure you're using one of the installer ISOs, not the live ISO, but just want confirmation of that.
You mentioned you're using USB for the installer. How did you copy the ISO image to the USB drive? The preferred method is to write the ISO directly to the USB block device (for example, using dd). Multiboot schemes may cause issues with the installer, such as booting it in legacy mode instead of EFI mode.
Setting the hostname is the 3rd screen of the installer as documented here https://www.devuan.org/os/documentation … installing
You can set it to whatever you want.
It would probably be helpful to see the actual lines you added to /etc/fstab.