Sometimes an installer can’t do it. The windows one can’t, another reason not to use that os
I was going to write a procedure in my phone, but i found this.
The funniest and strangest thing that I don’t have explanation.
Finally installed, rebooted to the installed system.
Updated yay -Syu. Worked on it for a while. Everything running perfect.
Rebooted. Back to square one!
I have never ever seen such thing!
How can it boot only once!???
That is extremely strange, the only thing I can think of is goofy hardware. Or a goofy UEFI implementation. Or a Windows-biased UEFI implementation, which was common back then.
That flash disk you have, is that MBR or GPT? It might only work with UEFI boot mode, and you might need a BIOS/MBR mode flash drive to install from.
Every day I see something new.
It is a Fujitsu laptop i5, 4 years old
It had windoze 10 installed and running
I believe it is one of two things
- the disk partitioning
- Grub?! (But online install should have no problem I think.
.
What is really challenging me how come it actually install, boot to what I installed only one time.
I’ll keep trying.
It is absolutely NOT four years old. The BIOS version is from four years ago but the Lifebook AH531 was released 10 years ago:
Sorry. My bad.
I thought the bios date is what specifies the manufacturing date.
The good point here this is the second 10 years old laptop I am installing EndeavourOS.
Compare that with instaling Windoze 11 on a 3 or 4 years old laptop. It would not install. I tried. Windoze always require the latest hardware.
This is another pro for Linux in general.
Oh I agree. But something that old, if I see boot problems, my first thought is bad/buggy UEFI implementation, and I’d try BIOS. You got another flash stick you can use to make a BIOS/MBR style Endeavour boot rather than a UEFI one?
1 Like
Yes… I have… but I do not know how to… even do not know… Sorry for being so illiterate!
This sounds logical after all these attempts.
How’d you create your current Endeavour boot device? Just so I know what way to point you here.
1 Like
I used dd if= of=
I really appreciate your patience and willingness to help! This is the beauty of EndeavourOS. 
OK…two options then,. I’m not comfortable giving you fdisk commands here, I don’t know what your device shows up as and something could break. So you could load up gparted and use it to initialize your flash drive as MBR. Or you could install Ventoy and use it to set yourself up an MBR device. I recommend at least checking out Ventoy, it’s a pretty cool utility though it might be more than you need right now.
1 Like
That is msdos? Format it fat32?
Just installed ventoy by the way.
Clicked install. Got it formated. (Ventoy has been successfully installed…)
MBR = MSDOS = BIOS
Fat32 is just a filesystem, that’s seperate, though you generally want your Ventoy to be fat32 either way (it’s handy, you just put one or more ISOs on the USB stick after installing Ventoy to it, and when you boot to it, it gives you a menu to choose them from).
Just copy the ISO(s) and boot from the flash disk? no need to dd? (They say so on their website. I will give it a shot!)
What about installation? Live install KDE Plasma as usual?
Yeah, just copy the ISO over, no need to DD, and you can keep multiple ISOs on there, just in case.
I have a 64 GB Ventoy that I keep Endeavour, Rocky Linux, Windows 2022, 10, and 11, PartED Magic, RescueZilla, Hirens BoodCD, and VMWare ESXi on, so I don’t have to carry a ton of USB sticks around with me. End brag. 
And do your install same as always.
1 Like
Wow. I wonder where has Ventoy been hiding from me all this time.
It is amazing.
Gosh! Life is much easier than we thought!
OK. I will report back to you once done.
Thank you very much.
1 Like
OK.Tried on this old machine. It did not boot.
I tried the same flash disk on another machine I saw two entries of the two ISOs I copied!
It seems to me that this old machine has got more than enough time and effort from you and me while it is too old to be useful.
I will take out the disks and use them as external USB disks.
So I count it sorted out.
Thank you very much for your support and patience @npaladin2000
Thank you.
1 Like
Hi @npaladin2000
Again this laptop is driving me crazy! I tried to install again… went fine to the end.
Rebooted. Nothing.
So, I thought to try install something else.
Connected an external DVD, power on to start installing…
I swear I do not know how did Grub appear and booted.
Maybe I should change to systemd-boot to be sure it will boot!
I know there is a tutorial @dalto made [Tutorial] Convert to systemd-boot
and I successfully used it and changed to systemd-boot.
But as this laptop is quite old, (maybe BIOS not UEFI, I saw something in BIOS saying Legacy and it is on) so I do not want to go and do instructions given by @dalto blindly.
It notified me there are updates but I didn’t update anything!
So, what should I do now to be sure I will be always booting (I have a gut feeling that systemd-boot should be better in my specific case. Or just leave Grub as is?)
Your valuable help is highly appreciated as usual.
Thank you.
Ok, first of all, if it’s booting in legacy mode, you can’t use the other options, systemd-boot is a UEFI bootloader. So it has to stay in UEFI mode.
What’s the boot order in there?