I used the one on this page, but I think it's the same one.
http://pkgmaster.devuan.org/devuan/dist … s/netboot/

The kernel in my beowulf is dated July 19. The mini.iso is dated June 27.

Did an UEFI install with the June 27 ISO end of last week and ran into same problem as OP.

Issue was fixed here by getting the system booting manually through the grub CLI (set root and all that stuff) and then noticed that /boot/efi/EFI didn't contain the usual "debian" or "devuan" directory so ran

grub-install --bootloader-id=devuan

. It's been a few days now and I've definitely slept since then so YMMV.

If needed, I can go boot that system up again and review what was done; hoping I saved my history....

The kernel in my beowulf is dated July 19. The mini.iso is dated June 27. It might not work now. Normally when that happens, you can get part way through the installation and then get a message about kernel modules being wrong. You didn't get that.

for the Jun 27 amd64 mini.iso I get the following. Check yours to see if it was a bad download.

$ sha256sum mini.iso 
85a227cb9bdf79352851195ed7e8c78c3e649dbc4b5f59a8d6232da62ef2fed9  mini.iso

I install it and in the reboot it jumps the console of grub.

I have tried it to install with the safe mode of the uefi and without it. In both cases the same problem.

I have to read but the grub console does not accept me device names that I initially recognize with a ls.

Someone has installed using the mini.iso ?????? this version:

https://pkgmaster.devuan.org/devuan/dis … t/mini.iso

I think it's very strange what's happening to me, the grub is badly installed.

Greetings