Problems booting into LiveCD

Hello, I am attempting to boot into Endeavour Neo (2024.9.22) to save a laptop from Manjaro hell, though no matter what I do I can’t seem to boot into the LiveCD

I’m using Ventoy on my boot USB, and I had this same issue when first installing Endeavour on my desktop, though I got around it by ensuring the USB and essentials were the only thing connected, and moved the USB drive to a different port, then it worked fine.

Below are the different errors I get from different boot options (as images, sorry for any inconvenience)

Booting via “normal” mode in Ventoy:

Booting via Grub2 in Ventoy:

Additionally, the BIOS on this laptop is extremely minimal and offers like no control, especially nothing relating to USB.

I’ve tried changing the USB port (there’s only 2 USB A ports and 1 USB C port) and there are no other external devices connected.

Only thing i can suggest is make sure you’re using an up to date Ventoy installation.
Good luck.

I have installed EOS 4 times and Ventoy launched 0 times.
Always had to install it on a dedicated USB.

Burn it to a USB.

Your experience and my identical experience shows we are the tiny minority. But many Ventoy users deny that could ever happen. But it happens. USB health could be a tiny part of it.

According to you, ports may have been a reason so you can’t take hardware off the table.

I also speculate you may not have your bios in uefi/legacy sync with the Ventoy.

The new stick and the double check of usb settings will cost you little time. There’s more that one way to skin a cat here.

“Hello, I am attempting to boot into Endeavour Neo (2024.9.22) to save a laptop from Manjaro hell, though no matter what I do I can’t seem to boot into the LiveCD”

EDIT: I re-read. Ventoy boots. All your distros are there. You choose Endeaovour, press enter, and the pictures are your subsequent output. I stand by by two options: dedicated stick or something simple in bios.

I must admit, that between the few posts here about Ventoy issues, and several on Reddit… It makes me wonder, why use it? Just honest curiosity on my part.

To me it’s been 95% perfect if you like to test drive .isos, just never for EOS and a couple other distros.

edit: @dbarronoss I agree with you and edited to 95

I agree, I would push it to 95%, though when I get a busybox error or it can’t find it’s own drives with both hands, I will burn it to usb directly.
That’s far less of a problem than it used to be, and EOS typically works all the time on Ventoy for me.

You can try DD but be careful as it can overwrite your SSD/HDD.

use sudo fdisk -l to find out the name of your USB.

then

sudo dd bs=4M if=path/to/the/archlinux.iso of=/dev/sdx

replace sdx with the name of your USB

1 Like

I hear ya. I’ve just never had any issues using more traditional ISO USB options. KDE ISO Image Writer, balenaEtcher, openSUSE Imagewriter… none of those have ever failed me over the years.

you only need to mix up the if= and the of= once to have an awful weekend.:slight_smile: But I do like dd.

2 Likes

the selling point of Ventoy is you can have 15 distros on the stick which means you don’t have to burn 15 sticks thus increasing your goof off time exponentially which is really cool :slight_smile:

2 Likes

Your correct but I grew up on DD ( Data Destroyer ) and love it.

2 Likes

I will try updating first, been a long while since I’ve done so.

And I use Ventoy because I have a lot of different ISOs in my toolkit, not only just Linux but different Windows versions as well, and it’s much more convenient to have one USB stick on my keychain compared to having a drawer full of them, and I can just add more to it whenever, and it’s nice.

Though the 5% of times it doesn’t work is really inconvenient, and I’ll admit the latest Endeavour Neo release is the first time I’ve come into any issues.

Will report back once I try that out, AUR is taking a while to build it so it may be a moment.

Never had an issue with ventoy, it is just convenient. But yeh, dd is the way forward. Just about to try the shiny new iso as am snowed in :smiley:

1 Like

You certainly need to ensure that Ventoy’s soft is up to date, because often because of this very thing, systems don’t boot. In addition, you may need to run EOS in GRUB2 mode. The second option at startup.

1 Like

This is a majority of the issues I have seen with people using ventoy. It does need updating unlike a disk burned by a dd or even an image writer. The difference is in the efi.

Ventoy needs to keep up with the latest efi.

For best practices its always suggested to run a update on ventoy before trying to install.

4 Likes

This :point_up_2: i allways check Ventoy for any update before trying to use/install with my Ventoy USB and never had any issues!

1 Like

Still using CD to boot? :thinking: … I don’t care for ventoy the same as i don’t care for installing a bunch of linux distros on the same disc. :wink: … It can be problematic but there are many that do use it so it is an option. Just have to make sure it’s up to date. I don’t use it but I have in the past a couple of times. I prefer writing the ISO directly to usb with other methods.

Sorry for not updating for so long, updating Ventoy worked fine, will make sure to check for updates every now and then in the future!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.