that’s when you gotta walk away until tomorrow. you have a good install stick.
if this is your day in/day out computer then it’s a mystery–I didn’t see every word of this thread.
But this behavior (loads but doesn’t open) also exactly occurs when the system is desperately seeking a bootloader and it can’t find a flagged one and it also exactly occurs in the install Fail intersection of efi/fat/bios/grub boot partition trainwreck if not thought-out well during install. it’s very common.I did this twice tonight before I learned my ‘bios’ needed uefi gutted and ‘csm’ install enabled. It got weirder but I digress.
I finally got the etcher boot to work after burning it for the 4th time… kept hanging either on the boot itself or trying to open the installer. I don’t know why it’s been so finicky but i sincerely appreciate everyone’s help.
The things I do know might need attention are Ventoy with Neo, and Galileo not updating without corrupt updating (only mattered because I didn’t think etcher would work so i opted for what did load on Ventoy).
I have a suggestion after looking at the hardware. One is the UEFI Bios. Maybe check if there is an update since it is some what dated. UEFI: Dell v: 1.14.0 date: 07/23/2021
Yes, I finally got the installer app to work on the live iso. The install went off without a hitch afterwards. I just got this laptop so I’ll update the bios asap, it was on the back of my mind that it may be what’s causing me to chase my tail. If I get ventoy to work later on I’ll report back!
There may or may not be a UEFI Bios update but you could check. I’m not saying this has anything to do with the issues you had but I am a firm believer in updating the UEFI Firmware (Bios)
I’m also not a fan of ventoy myself. But, that’s just my personal preference. Ive used etcher lots of times and have no issue with it. When you say it took 4x to finally get it to work it may be an issue with the usb drive itself. Sometimes it’s the partition/file system that’s been written to it that causes this. Ventoy isn’t the only culprit.
the lone usb stick is better than ventoy for endeavour but how fussy could it be? well–you are correct—I personally am a complete weirdo. I NEVER let a distro install the way it wants to install itself. I prefer the hand the installer a GPT partition I formatted and if I’m feeling insane I will make the partitions myself–]
–likewise before Ethcher I will erase and Fat32 the stick in gnome-disks or gparted before giving it etcher.
We all have our rituals that work…
wow. like a permanent legacy state for the usb? that would certainly result in different behavior, I think. I mean even seemingly stupid stuff like having to choose grub or uefi just to load an OS from Ventoy…
…some distros need for you make that decision right away and will only launch with one…some launch with either you select and it makes no difference.
as time passes I realize you are dealing with too many variables (ventoy, stick health since USBs were not meant for heavy lifting, the hdd that is actually mounting ventoy, burning software, etc, and a cast of thousands).
My two-lager epiphany: Linux is that guy juggling knives on the tightrope. Can get messy some nights, but I will never go back to MS.
ventoy -h
**********************************************
Ventoy: 1.0.99 x86_64
longpanda admin@ventoy.net
https://www.ventoy.net
**********************************************
Usage: Ventoy2Disk.sh CMD [ OPTION ] /dev/sdX
CMD:
-i install Ventoy to sdX (fails if disk already installed with Ventoy)
-I force install Ventoy to sdX (no matter if installed or not)
-u update Ventoy in sdX
-l list Ventoy information in sdX
OPTION: (optional)
-r SIZE_MB preserve some space at the bottom of the disk (only for install)
-s/-S enable/disable secure boot support (default is enabled)
-g use GPT partition style, default is MBR (only for install)
-L Label of the 1st exfat partition (default is Ventoy)
-n try non-destructive installation (only for install)
@hwmpunk
This right here I think is most peoples issue with ventoy after taking a look at my alias for ventoy i realized i had this flag included so ventoy is making my USB drives with secure boot off.
I just checked and ran Neo just fine from it. I didn’t do and install but the live environment booted just fine.
Just to clarify, I’m not specifically criticizing Ventoy or how they developed their software—the issue is with the BIOS firmware. In my experience, 9 times out of 10, when an OS fails to boot from a perfectly functioning USB drive, it’s usually due to a limitation in the BIOS or the need for a firmware update.
This was often the case with Intel boards for me, but as soon as I switched to ASUS, the problem was resolved.
Just like you’ll never return to MS, I’ll never go back to using an inferior Intel motherboard.
Can you start a new thread if you are having issues?
I have been messing with ventoy and don’t have and issue. in fact i just used it to check the latest(unreleased version)
I can launch and have fun with all distros in Ventoy but only a handful of distros are resistant to bare metal install so…
…conventional wisdom, almost unanimously, says failing USB and there’s a lot of truth to this. As an experiment I moved all my ISOs to a new-ish (old one was old-ish) 32GB USB and voila! I could bare metal more stuff (before I stop install)…but not that rascal Endeavour
just for reference I create a ventoy from command line using the below command sudo ventoy -i -g -S
(i) installs to chosen device
(g) sets partition as gpt
(-S) Secure boot off.
currently doing a bare metal install with this and everything is working as expected.
