I tried the same mini.iso (16-02-2019), attempting to install beowulf on an all-intel thinkpad X200.
It gave me the kernel module error, which has been reported with previous versions and failed to discover my (plain old spinning) SATA disk, so the install failed at that point.

Other then op bug...I've continued by way,
of ascii mini iso, then chose beowulf repos, when option presented... - till beowulf mini gets rebuilt.

It gave me the kernel module error, which has been reported with previous versions and failed to discover my (plain old spinning) SATA disk, so the install failed at that point.

Edit: I used the DVD installer and not the minimal.iso...

Good to know. Thanks. Is gdisk any better?

Maybe your disk shows up in /dev/disk/by-*.  Oh, wouldn't /dev/mmcblk0 be the whole device? Shouldn't you be mounting /dev/mmcblk0p1 or something? (Maybe you just didn't type the entire name.)

On second thoughts this may actually be an issue with the Slackware fdisk/cfdisk installer. Slackware 14.2 does not recognise M.2 disks yet.

Would be interesting which kind of M2 device the OP has in his PC.

I have installed ASCII on a M2 nvme device without issues. I used a gparted live CD to pre-partition the disk. But also the installer should be able to do the job in manual mode.

Good luck, Rolf

With the exception of the 'devuan' vs 'debian' efi boot paths, Beowulf installed just fine on the nvme in my lenovo as well.

I have installed ASCII on a M2 nvme device without issues. I used a gparted live CD to pre-partition the disk. But also the installer should be able to do the job in manual mode.

Good luck, Rolf

It may involve a BIOS setting.

fsmithred wrote:

Does fdisk or lspci see the M2 disk? What's the device name? (/dev/nvme* or something else?)
Is there any useful info in /var/log/installer/syslog?

In my experience fdisk is not good with recognising SD cards - inasmuch as it doesn't see them at all. It's the same for cfdisk but no problem for a graphical installer. Attempting to mount the disk manually doesn't work [/dev/mmcblk0]. It may be a similar issue with M2 disks. I have spent hours looking round the internet for a solution but have found nothing.

Good to know. Thanks. Is gdisk any better?

Maybe your disk shows up in /dev/disk/by-*.  Oh, wouldn't /dev/mmcblk0 be the whole device? Shouldn't you be mounting /dev/mmcblk0p1 or something? (Maybe you just didn't type the entire name.)

Does fdisk or lspci see the M2 disk? What's the device name? (/dev/nvme* or something else?)
Is there any useful info in /var/log/installer/syslog?

In my experience fdisk is not good with recognising SD cards - inasmuch as it doesn't see them at all. It's the same for cfdisk but no problem for a graphical installer. Attempting to mount the disk manually doesn't work [/dev/mmcblk0]. It may be a similar issue with M2 disks. I have spent hours looking round the internet for a solution but have found nothing.

Does fdisk or lspci see the M2 disk? What's the device name? (/dev/nvme* or something else?)
Is there any useful info in /var/log/installer/syslog?

do you use the package reportbug or the package reportbug-ng?

And the mini_16-2-2019.iso is not a package. how do you report it?

You can report a bug to https://bugs.devuan.org/   I find it easiest to sent a report directly by email.  There is a link to the instructions on the index page.

I found this post

https://dev1galaxy.org/viewtopic.php?id=547

but he means jessi.

How would it be for ascii ????

do you use the package reportbug or the package reportbug-ng?

And the mini_16-2-2019.iso is not a package. how do you report it?

On the same machine on a mechanical disk the mini.iso 16-2-2019 installs without problems.

In the case of installing on a disk M2 at the end of the process of installing programs ... when you start to clean with 97% of the process freezes. The light of activity of the disk remains blocked as if the disk were being used intensively.

How are bug's reported? Who do I have to warn about this bug?

Could you name the mini.iso with the date of publication? for example mini_16-2-2019.iso

There's some confusion, I was using a mini.iso from last year.

a greeting
basati