.. and you might want to fit in an unsort (from the unsort package) on the filename list to avoid the play order rigidity.

@tux perhaps you could describe briefly what the various snd-hda-intel options do for you?

Perhaps you can capture /var/log/syslog from the installer and show here.

For instance use ctrl-alt-f2 to enter a shell at vt2, then set up a receiver

nc -l -p 10000 > capture.log

on another machine, say 10.0.0.5, and copy over with

nc -w 2 10.0.0.5 10000 < /var/log/syslog

from the installer shell to the receiver on that other machine.

The ISO is a s.c hybrid ISO that presents itself both as a CDROM and as a disk image with 2 partitions where the first is a CDROM and the second is a FAT filesystem (for UEFI boot). The partition block ranges overlap of course, as the FAT filesystem is in fact an image file within the CDROM, but the bios is not clever enough to worry about that.

In any case, the log file should give some lead to why the installer cannot find the CDROM.

Perhaps / is mounted read-only due to filesystem errors?

If so, you probably need to boot up with another root filesystem so as to fsck the root partition first.

Or you might try to remount / read-write.

Another option is to mount a tmpfs onto /tmp. Though that might not be enough as it won't allow log files or authority files to be written.

Well, "gnome-keyring" is a program, not a collection of keys.

No worries. I didn't think I took offense, but hmm maybe I did. But it is true that I do need to retire off Devuan and that new and more people need to step up and in; not necessarily you of course.

The installer ISOs are built using https://git.devuan.org/devuan/installer-iso.git which has been streamlined into an almost push-button state by now. But, whenever an ISO is built, it relies on the state of the repository at that particular time and it's always possible for some update inconsistency to slip in. It is therefore I think the installer ISOs typically need a broader testing than a single person running through it once.

At https://ido.rrq.id.au/download there is an initial collection of trial installer ISOs that need to be tested in a range of settings.

Everyone here who doesn't devalue themselves with the label "just a Devuan user" should grab at least one of them and run it through a number of variations, and then report on it, maybe as an email to me. Refer to usecases.html for the primary use case division. VM trials as well as bare-metal trials are good.

EDIT: my alternate email is rrq at rrq dot id dot au

@Ogis1975: So what's your purpose with that kind of post?

Yes, it would be an excellent contribution to the Devuan project to refresh any of the various installer ISOs for this.

Note that the full hands-on may also require that the old local InRelease file for the distribution is removed manually, so the sequence of command would thus be (eg for chimaera):

• # rm /var/lib/apt/lists/deb.devuan.org_merged_dists_chimaera_InRelease

• # apt-get update --allow-unauthenticated --allow-insecure-repositories

• # apt-get install devuan-keyring --allow-unauthenticated

Alternatively: Anyone uncomfortable with those command line options should rather download the new keyring directly, eg

• # wget http://deb.devuan.org/devuan/pool/main/ … 04_all.deb

• # sha256sum devuan-keyring_2022.09.04_all.deb 96c4a206e8dfdc21138ec619687ef9acf36e1524dd39190c040164f37cc3468d

• # dpkg -i devuan-keyring_2022.09.04_all.deb

Alternatively: if you have your own method that works, then that is fine too.

Isn't the #PV just a counter?

If there is a difference between Devuan/Debian and those other OS types, it might be a difference in the lvm.conf files. Perhaps you can diff those between systems?

You might have forgotten to activate the volume group?