Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
BootCurrent: 0005
Timeout: 2 seconds
BootOrder: 0000,0005,0003,0002,0001
Boot0000* Windows Boot Manager HD(2,1f4800,82000,88e50bfb-f30c-4915-9628-1712260476df)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...l................
Boot0001* Windows Boot Manager Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
Boot0002* UEFI: IPV6 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(c03fd5e6c930,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000..BO
Boot0003* UEFI: IPV4 Realtek PCIe GBE Family Controller ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(c03fd5e6c930,0)IPv4(0.0.0.0:0<->0.0.0.0:0,0, 0..BO
Boot0005* Slackware HD(2,1f4800,82000,88e50bfb-f30c-4915-9628-1712260476df)File(\EFI\Slackware\elilo.efi)
The two Windows entries are obsolete and I will delete them eventually, but I don't want to modify anything until I understand the setup better. Note that there is no CD option here.
If I boot from a CD and run the same command, I get:
UEFI BIOS may seem mixed up more easily or often than we like, but they aren't stupid. When there is bootable removable media during POST, they would normally include it among boot selections, unless some option in BIOS setup directs it be ignored or disabled.
What surprised me was that there isn't a permanent entry for the cdrom drive. After all, the UEFI chip must be able to detect that there is a second SATA drive in the machine. Having an entry for the empty drive surely wouldn't do any more harm than those empty Windows entries. As far as I can see, UEFIs treat non-functioning boot entries the same way that BIOS's do: just try the next one on the list!
BIOS differ. My newest are two Kaby Lakes. The Asus' BIOS doesn't remember as much as my Gigabyte's does, which includes hard disks (2), NVME (1) devices, and labels of unattached OM and USB sticks. How many it's capable of I can't say. There are 7 total ATM (4 removables).
Everyone has to monitor their systems if they have one that never seems to stop adding entries. I have one that will get up to 400 or so before I have to do a mass delete.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.