grep: /init: no such file or directory INIT NOT FOUND
/ventoy/busybox/sh: can’t access tty; job control turned off
/ # _
So I loaded Galileo, and selected to delete the drive and install a fresh instance. As its installing, at the very end before its at 100% it says “Installation Failed, EndeavourOS Galileo has not been installed on your computer. The error message was: Package Manager Error.”
Any thoughts on why Ventoy can’t load Neo, and why Galileo online install seems broken?
Update: Offline Galileo install worked fine. So long as it updates without issues, this thread is more of a heads up about those issues trying to install EOS.
I updated to Ventoy version 1.99, and now instead of getting the error when loading Neo, it shows a black screen with an underscore then goes back to the Ventoy boot menu. Galileo still boots fine.
Do you get the same error? Is updating from Galileo as stable as installing a fresh copy of Neo?
instead of choosing normal boot choose grub boot and it should work. I had a similar issue with ventoy even after updating however doing it this way works so maybe the next update or two will resolve the issue.
Using the live iso for a fresh partition install. I cannot get Neo to load on Ventoy and Galileo only works on offline install. I’m worried about all the updating whether it ends up as clean as installing a fresh copy of Neo.
The option to boot in grub2 mode just immediately brings it back to the Ventoy boot menu. Seems both normal and grub do not work with Ventoy. I tried on both a Linux and Windows installed Ventoy drive. Galileo and Casini do boot just fine. Hopefully the next EOS update fixes it!
There’s popular opinion and then there’s my experience:
Endeavour is one of a handful of Distros I could NEVER install from Ventoy.
Dust off Etcher and make it it’s own USB stick. Success rate for this method: 4 installs, 100%/
Ventoy: 4 failures, 100%
I’m not sure how you’d want me to enter that command, if you could please clarify?
I formatted the USB and did a fresh Ventoy install of the latest version. I tried both on Linux then on windows to make sure it wasn’t a compatibility issue.
The update from Galileo seemed to go alright, with multiple individual failures along the way but I assume it’s all part of the process. Kdelibs4support did not install, not sure if it’s a big deal though.
I actually ran into an issue updating. It finished with some errors along the way and I restarted. Seems to be up to date and on Wayland, however when I type the password to log into the session, with the rocket taking off in the background, the screen goes black with a blinking underscore, then goes back to the password login screen. I can’t seem to get past it. this happens the fallback boot option too.
It does work on x11 instead of Wayland. Do you know what the issue could be and if there’s a way to resolve it? I’ve been on Wayland since it came out on 6 but since this issue fresh installing Galileo to update it just starting doing it.
I made a Neo USB boot on etcher and this time, it shows the boot manager. I select the standard eos and then it gets hung up on this screen… The fallback boot option hangs on the same screen. I can’t seem to clean install Neo despite having spent all day trying to make it work!
I was able to get Neo iso to boot on a new flash drive via etcher and it loads the desktop and all apps work except the install system app… It acts like it loads but doesn’t open. Today just isn’t my day…
