On 29/04/2020 11:50, Gabor Szabo wrote:
Thanks for the quick reply, at least I don't feel totally alone in this!

Alone?


At work, we've had Asus laptops that we installed with Linux that started only agreeing to boot once every 4 to 100 tries. We've had a co-worker literally sit for one hour just trying to start his computer.


We returned one of them, and the store kept it for 10 months (!!!!) until Asus released a BIOS upgrade that solved the problem. And then the store owner had the gall to try and bring us back the (almost brand new when it was returned) laptop.


All further laptops we bought were Dell.


The BIOS does not even have an option to boot into Windows any more.
That's a completely different problem. Something deleted the Windows UEFI entry from the BIOS. I'm not sure how to restore it (probably boot a Windows recovery disk).

Linux gets to the   grub>   prompt and I don't know how to proceed from there.
It does not show a grub menu.
Yes, that is strange, but of all problems you describe, probably the least strange. I wouldn't start with this issue. If pushed, try to see if secure boot is enabled. If Linux was originally installed without placing signing keys in the BIOS (or those keys were deleted by the upgrade), weird things are _expected_ to happen.
 

What I don't understand is why your Windows would stop booting. At the very least, it should start the boot process and BSoD when the disk drivers have changed for it.


My understanding stop at the point why would the bios flashing make the Windows entry disappear from the list of boot options.
UEFI boot sequence starts at the BIOS. Unlike the legacy sequence, where the BIOS would unconditionally load the boot loader, and any boot selection you want to do is done after the BIOS has finished, UEFI needs the

Gabor
_______________________________________________
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il

Reply via email to