two distros won't load from ventoy

[FrostKnight]

Official FAQ

• [x] I have checked the official FAQ.

Ventoy Version

1.1.05

What about latest release

Now. I did try the latest release.

Try alternative boot mode

Yes. I have tried them, but the bug still exist.

BIOS Mode

Legacy Mode (Secure Boot disabled) Although, not sure how to ventoy to boot my distros from legacy and not uefi

Partition Style

MBR

Disk Capacity

1TB

Disk Manufacturer

Sabrent

Image file checksum (if applicable)

None

Image file download link (if applicable)

Devuan daedalus and Hyperbola Milky way 0.4.4

These are the links:

https://mirror.leaseweb.com/devuan/devuan_daedalus/installer-iso/devuan_daedalus_5.0.1_amd64_netinstall.iso https://repo.hyperbola.info:50000/other/live_images/gnu-plus-linux-libre/hyperbola-milky-way-latest/hyperbola-milky-way-v0.4.4-dual.iso

What happened?

They refused to boot and also, I don't know the file checksum and I don't completely know how to change it to boot from legacy mode.

I tried to do so by disabling secure boot in ventoy menu, but I am not sure it worked.

[FrostKnight]

I just checked and it seems you fixed this... my bad

EDIT:

I seem to be still having a problem even with the latest version. It keeps expecting my distro to be compatible with UEFI. But it isn't.

Can someone tell me how to tell me how to boot from legacy not UEFI with my distros via Ventoy

[ventoy]

It's the BIOS that decide to boot Ventoy in Legacy BIOS mode or UEFI mode.
Ventoy can not change the boot mode.

[FrostKnight]

It's the BIOS that decide to boot Ventoy in Legacy BIOS mode or UEFI mode. Ventoy can not change the boot mode.

Yeah... uh it doesn't choose to boot in bios mode for some reason. Even if I disable secure boot.

Also, isos are not detected in certain bioses, like coreboot and libreboot even if the isos/imgs are there.

Would it be possible to make it possible to change the bios option arbitrarily in options? like, to legacy as well as UEFI.

Btw, I am using an AMD Ryzen 5 processor in this computer.

[TRONGNGUYEN2022]

vmware, virtualBox, QEMU.....

[FrostKnight]

vmware, virtualBox, QEMU.....

Actually, I tried live images and I tried qemu qcow2 images that have devuan daedalus and hyperbola 0.4.4 installed on them.

Oddly enough, I cannot seem to get them to boot by legacy method. No matter what happens, my distros are forcibly loaded by UEFI, even though... that will never, ever work.

I need to be able to force legacy mode in order to get those images to boot.

It seems, that ventoy is erroneously detecting uefi even though I disabled secure boot.

I will have to check most recent ventoy I guess again? nvm still same one.

Btw, updated original post to add these links:

https://mirror.leaseweb.com/devuan/devuan_daedalus/installer-iso/devuan_daedalus_5.0.1_amd64_netinstall.iso https://repo.hyperbola.info:50000/other/live_images/gnu-plus-linux-libre/hyperbola-milky-way-latest/hyperbola-milky-way-v0.4.4-dual.iso

[TRONGNGUYEN2022]

You should use Vmware or VirtualBox

Vào Th 5, 6 thg 3, 2025 vào lúc 13:20 FrostKnight < @.***> đã viết:

vmware, virtualBox, QEMU.....

Actually, I tried live images and I tried qemu qcow2 images that have devuan daedalus and hyperbola 0.4.4 installed on them.

Oddly enough, I cannot seem to get them to boot by legacy method. No matter what happens, my distros are forcibly loaded by UEFI, even though... that will never, ever work.

I need to be able to force legacy mode in order to get those images to boot.

— Reply to this email directly, view it on GitHub https://github.com/ventoy/Ventoy/issues/3151#issuecomment-2702917763, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3JK2KIYOD2N2DFUWS3CRB32S7SJ5AVCNFSM6AAAAABYFW4HHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBSHEYTONZWGM . You are receiving this because you commented.Message ID: @.***> [image: FrostKnight]FrostKnight left a comment (ventoy/Ventoy#3151) https://github.com/ventoy/Ventoy/issues/3151#issuecomment-2702917763

vmware, virtualBox, QEMU.....

Actually, I tried live images and I tried qemu qcow2 images that have devuan daedalus and hyperbola 0.4.4 installed on them.

Oddly enough, I cannot seem to get them to boot by legacy method. No matter what happens, my distros are forcibly loaded by UEFI, even though... that will never, ever work.

I need to be able to force legacy mode in order to get those images to boot.

— Reply to this email directly, view it on GitHub https://github.com/ventoy/Ventoy/issues/3151#issuecomment-2702917763, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3JK2KIYOD2N2DFUWS3CRB32S7SJ5AVCNFSM6AAAAABYFW4HHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBSHEYTONZWGM . You are receiving this because you commented.Message ID: @.***>

[FrostKnight]

You should use Vmware or VirtualBox

Vào Th 5, 6 thg 3, 2025 vào lúc 13:20 FrostKnight < @.***> đã viết: …

What does that have to do with anything? Also, I prefer qemu or virt-manager.

[FrostKnight]

Can anyone tell me if they have tested 0.4.4 version of hyperbola to boot from iso in ventoy?

Same with devuan.

Although, it might be wise to have an option to boot off legacy even if it detects uefi, for some distros.

I wonder if I should make this a separate issue, the option to boot legacy even if it detects uefi

[FrostKnight]

I still haven't gotten an answer to my last posts...

Can you guys tell me?

0.3.1 is a very old Hyperbola release and getting that working is largely irrelevant

[0xlne]

Devuan 6 (Excalibur) from the latest 6.0.0 rc1 is also failing to load, both in normal & grub2 modes. It gets stuck when looking for the boot medium with a label of DEVUAN600. The same image boots successfully in VMs.

[FrostKnight]

Devuan 6 (Excalibur) from the latest 6.0.0 rc1 is also failing to load, both in normal & grub2 modes. It gets stuck when looking for the boot medium with a label of DEVUAN600. The same image boots successfully in VMs.

Not to mentiom, hyperbola 0.4.4 is also not working either.

for some reason they tested 0.3.1 which is meaningless, its very old/outdated.