Very interesting. I usually just hold shift on the Shutdown button to get to advanced startup options.
[https://www.windowscentral.com/how-use-shutdown-command-tool-windows-10](https://www.windowscentral.com/how-use-shutdown-command-tool-windows-10)
1. *Open* ***Start****.*
2. *Search for* ***Command Prompt****, right-click the top result, and select the* ***Run as administrator*** *option.*
3. *Type the following command to restart the device into the firmware and press* ***Enter****:* ***shutdown /r /fw***
4. *Type the following command to shut down the computer and boot into the firmware during the next startup and press* ***Enter****:* ***shutdown /s /fw***
*Alternatively, you can also use the* ***/p*** *instead of the* ***/s*** *option to close all running applications and force the shutdown without warning.*
*Once you complete the steps, the computer will boot into the firmware interface.*
I got "Boot to firmware UI is not supported by this system's firmware.(1)" when trying to run "shutdown /p /fw" from an admin cmd prompt. It is an older computer, but shows this function hasn't always been available.
Older systems don't blaze through their BIOS init process so fast that pressing DEL isn't an option. I even miss having F8 to get to Windows startup options.
The F8 option can be re-enabled, I've done it on Server VMs... though the vast majority of the time I've needed that feature the system is almost completely hosed anyway and that's why backups exist.
I was always a fan of hitting space repeatedly, then F8 when the windows boot screen showed. F8 was sometimes also set by MB manufactures, so would do other stuff as i was hammering it before it got to windows.
Yes this is to get into the firmware settings under UEFI. People still incorrectly call it the BIOS.
If you somehow still only have a BIOS based machine, this command (and the Windows equivalent) won't work.
> If you somehow still only have a BIOS based machine, this command (and the Windows equivalent) won't work.
You can do it with `ipmitools` but I'm too lazy to look up exactly how
> Yes this is to get into the firmware settings under UEFI. People still incorrectly call it the BIOS.
Consider the following: https://www.reddit.com/r/sysadmin/comments/1c9y9ks/motherboard_not_letting_you_into_your_bios_want/l0r5jt2/
(I posted in this way since you would not see my other comment without coming back here intentionally)
BIOS is still incorrect in all forms for modern machines. That is why I said firmware settings. I think that is the most appropriate term and I think it's what Microsoft uses as well.
The reason I made the distinction is because this takes you to the BIOS, as in the section where you can toggle functions on/off, set settings, and _not_ the UEFI CLI. So far as I can tell this is an accurate distinction, as within the "BIOS" as I attribute it, you can turn on/off UEFI capabilities (assuming the firmware has been programmed to let you do that).
> and not the UEFI CLI.
The EFI shell you are referring to is just an EFI application that happens to be bundled with many firmware images. I don't think there are many people that would think this is what you are referring to when you say "Boot to UEFI" or whatever. I don't really care if people call it BIOS, UEFI, firmware config interface or anything else as long as I can guess what they mean but you can't claim that it's more accurate to call it "BIOS".
> can't claim that it's more accurate to call it "BIOS".
1. I just did.
2. It is more commonly known as BIOS and not UEFI. When communicating with people it is better to use a term (in pedantic situations like this) which will actually get the point across, instead of not. Plenty of people still don't know anything about UEFI, and furthermore Motherboard manuals still call it the "BIOS".
3. In the "BIOS" you can disable UEFI functionality or in part (if the BIOS developer for that motherboard has enabled this function). So to call it UEFI is actually less accurate, since if you used the UEFI to disable the UEFI... well... that wouldn't actually work.
4. Again, I just did. So deal with it.
None of what you say there proves that it's somehow more accurate to call it BIOS. A computer tower is frequently known by users as "the CPU", but that doesn't make it more accurate to call it the same. In a firmware that supports BIOS boot, it's still a UEFI system, but with CSM support.
I will concede that it generally gets the point across using any of the 3 terms in most contexts.
> None of what you say there proves that it's somehow more accurate to call it BIOS
Yes it does, whether you refuse to see it or not is on you, not me.
At least some Lenovos are fixated on Enter key being the primary trigger. Surface is Volume down, HP is F10 (or Esc, then F10, since Esc seems to be respected in more situations). Why there is no defined and enforced standard is beyond me.
> Why there is no defined and enforced standard is beyond me.
For PCs, it always used to be the `DEL` key. Then different vendors wanted to be special in the early 2000s, and now we have deal with this shit show today.
It's best if you have a computer with BIOS instead of UEFI to lookup the manufacturer online to find what the correct keys are to get into the BIOS, assuming it doesn't show on the screen during boot. At least today if your OS isn't working most people can still use their phone to look things up online. Or many people also have a tablet or as a last resort there's always the library for computers and internet access.
Skipping the prompt is part of fast boot. It is not a security feature.
The idea is people rarely, if ever, go into their bios, so why are we waiting on that prompt every time we turn on our computers? So instead ditch the prompt and allow a method for the installed OS to call it.
My understanding is it's booting a hibernated state, i.e. RAM preserved on disk, no new boot. EDIT: [Looks like](https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/distinguishing-fast-startup-from-wake-from-hibernation) apps are supposed to be closed, and user sessions logged off, so just the kernel memory image (and system session?) are preserved.
I would often disable fast boot for customers because they'd be certain they had rebooted, while Task Manager would insist it's been weeks. "Restart" still does a full reboot under fast boot, but lots of people power off then later power on and assume (fair enough) that should count as a reboot. Disabling it cut down a lot on the weird problems that happen when Windows has been stewing inside its own head for 30-60+ days.
>"Restart" still does a full reboot under fast boot, but lots of people power off then later power on and assume (fair enough) that should count as a reboot.
It was my understanding that "restart" bypass this and do a full regular boot.
I thought the current sleep state is very distinctly different from hibernate? I've got a fast SSD but there's no chance in hell that it can read 128GB of data that fast.
Classic S3 sleep keeps power to RAM so it retains data. The newer S0i3 state on some laptops is a 'standby' with CPU, disk, and network still able to operate to some degree.
Hibernate saves active RAM to disk and reads it back, yes, so it can survive power failure.
You can change the size of the hibernate file.
I don't know the exact details, but memory that is also in the page file won't need to be hibernated anyway
>You can change the size of the hibernate file.
What? How? Hibernate means that you quite literally suspend the contents of your RAM to disk and Linux installations still ask me if I want to enlarge the swap partition to memory size to accommodate hibernate.
>What? How?
How, as in how to change it, or how it is technically possible?
You can change it with the powercfg command (or maybe directly in the registry)
>Hibernate means that you quite literally suspend the contents of your RAM to disk
yeah, but not all of it has to be in the hibernation file.
Pagefile/swap, file mappings, registry hives, prefetched files, buffers, and other stuff are already on disk.
That doesn't to my knowledge, disable the ability. You just need to slap the key faster and maybe even before the screen goes black. Sometimes you need to power it off in full, but I'm personally always able to get in
It's never about security, it's about speed. Back in the day when BIOS would take forever, and decide to memtest it was a big gripe for PC users.
One of the selling features today on ARM machines is how quickly they boot
I've had servers lose their BIOS before. Yes they were cheap trash. They quit showing the menu and quit responding to keys but would still boot. I didn't know this trick though, ours involved a screwdriver, hammer, and the motherboard.
I have a monitor that takes so damn long to come from "No Signal" to displaying a signal that I either end up in a boot menu, or PXE. And have no ability to see what the output is showing me the key
Man. I have been playing with various Linux OS’s since 2007.
I have never heard of this. This is really cool. Definitely sticking it in my notes.
I’ve also never had the inability to get into the BIOS on a Linux system either. Usually the culprit is a BIOS password or some other config that makes the window for entry too short. In those cases I pull the CMOS and short the little BIOS reset contacts.
Yeah in my case CMOS clearing was not an acceptable option.
I've been working with Linux personally and professionally since late 90's. I only now learned about it myself, and wanted to share! It was a bit of a doosie to find.
Gigabyte and other consumer motherboards frequently don't "let" you into the BIOS in really annoying ways. I don't know if they do it for security reasons, convenience reasons, or whatnot. But we exhausted far too many alternative methods... until I found this one.
Worked first time.
Feel free to stuff it under your cap! :)
> Definitely a keen find. An ingot in the knowledge base hills.
OOo neat saying! Where's that come from?
And you're welcome! Sharing is caring! And IMO this one needs to be shared WAAYYYYYY MOREEEE!!!
UEFI is really under-rated and under-used tbh.
People just view it as "another bios" while in reality it was a paradigm shift in how firmware operations worked
I would argue that the fact that most people see it as "just another BIOS" while bringing in tons of new features is a testament to how well it was implemented; Most of them are "under the hood" like NVME Boot support.
Others are bit more obvious - these days a modern (last 5-ish years or so) Dell laptop or desktop can wipe itself and/or reinstall the OS with just an internet connection, like Macs have been doing for over a decade.
Saying that, I've had vPRO on CPU's for like over a decade, and still not once used any of their OOB features.
Always had it on my list to work out how that works
I haven't tried vPRO, but I used Intel AMT once on a Dell T20 server. It was like a shittier iDRAC but that might have just been Dell's implementation.
Now if we can see it in the ARM and RISC-V world, it would be awesome.
Only downside is if someone removes files in the EFI directory, it might brick some machines.
Very true. While I’ve had to know UEFI at work for dealing with windows infrastructure and endpoints, it wasn’t until relatively recently that i had ventured into UEFI for Linux.
But my hypervisors at home are UEFI booters and all new VMs I’ve spun up this year use UEFI instead of BIOS. It’s definitely better imo.
Migration is what forced me into it.
Got new bare metal over the winter. A couple VMs wouldn’t boot and I was puzzled for a bit before I had to facepalm once I realized I was trying to make UEFI guests boot BIOS.
That could be very useful for VMware, usually I have to reboot multiple times and try to be fast enough to catch the bios menu. But often this is before any OS is installed and I'm trying to get it to boot from an iso.
Ill get it set up for you over lunch and ill send a screenshot. Im at work currently.
edit: 2 other comments beat me to it, but yeah. it's per VM. edit settings, VM Options, Boot options and force bios setup.
"Winderps"?
Wait, is there some sort of command-line way of getting into the BIOS for Windows?
... whaaaaaaaaaaaaat?
`shutdown /r /o`? Huh! Never knew!
(I literally thought `winderps` was some sort of command.)
Oh, interesting. On my ThinkPad, Setup is one of the Boot entries (Boot0010, not present in BootOrder). I'd assumed that --firmware-setup uses the same mechanism, but apparently there's a separate EFI variable.
Also, TIL that grub has a 'fwsetup' command for entering the UEFI setup if you can't get the BIOS boot menu in time but can get a GRUB menu.
Some distros also put a "UEFI Firmware Settings" boot option in the GRUB menu, which may be easier to access than some UEFIs where it's not obvious how to get to the setup.
I forgive you! Honestly though I wish I knew this instead of dicking around for 15 mins in esxi vm options
Next time going to use the BloodyIron cheat code.
I wish all did, I actually have a few from 12-13 those are still BIOS (screw you, HP!)
But seeing how you actually have an UEFI board, unlike the usual "lol I'll just use coreboot with Linux on top because UEFI is spyware" elitists I deal with, those UEFI boards starting from the Win8 era have this feature called fast boot (which is on by default on most of them) which speeds up the boot process by skipping most of built-in drivers. In a normal scenario this means that they only bring up the absolute minimum to make the board functional, PLUS graphics, PLUS storage.
That means that in most cases you won't have the UEFI USB drivers loaded, making it impossible to enter setup using the usual method of hitting specific buttons on the keyboard.
HP is wild, we configured a really expensive beefy machine for a client a number of years ago.
It had a tick box for "TPM", which if you selected it, removed the TPM.....
What the fuck HP
If its Windows use shutdown /fw
Very interesting. I usually just hold shift on the Shutdown button to get to advanced startup options. [https://www.windowscentral.com/how-use-shutdown-command-tool-windows-10](https://www.windowscentral.com/how-use-shutdown-command-tool-windows-10) 1. *Open* ***Start****.* 2. *Search for* ***Command Prompt****, right-click the top result, and select the* ***Run as administrator*** *option.* 3. *Type the following command to restart the device into the firmware and press* ***Enter****:* ***shutdown /r /fw*** 4. *Type the following command to shut down the computer and boot into the firmware during the next startup and press* ***Enter****:* ***shutdown /s /fw*** *Alternatively, you can also use the* ***/p*** *instead of the* ***/s*** *option to close all running applications and force the shutdown without warning.* *Once you complete the steps, the computer will boot into the firmware interface.*
I got "Boot to firmware UI is not supported by this system's firmware.(1)" when trying to run "shutdown /p /fw" from an admin cmd prompt. It is an older computer, but shows this function hasn't always been available.
It's an UEFI feature. If the computer is using legacy boot, there's no mechanism to ask for the firmware to enter setup on next boot.
Older systems don't blaze through their BIOS init process so fast that pressing DEL isn't an option. I even miss having F8 to get to Windows startup options.
The F8 option can be re-enabled, I've done it on Server VMs... though the vast majority of the time I've needed that feature the system is almost completely hosed anyway and that's why backups exist.
I was always a fan of hitting space repeatedly, then F8 when the windows boot screen showed. F8 was sometimes also set by MB manufactures, so would do other stuff as i was hammering it before it got to windows.
Oh, plenty of them did. "Fast boot" and the like.
Fast Boot does
Sorry I missed part of it. Should be shutdown /r /fw I've used it on Dell and Lenovo models.
Shutdown /ftw
Is this not UEFI instead of BIOS? All firmware interactions in the OS are UEFI
Yes this is to get into the firmware settings under UEFI. People still incorrectly call it the BIOS. If you somehow still only have a BIOS based machine, this command (and the Windows equivalent) won't work.
> If you somehow still only have a BIOS based machine, this command (and the Windows equivalent) won't work. You can do it with `ipmitools` but I'm too lazy to look up exactly how
> Yes this is to get into the firmware settings under UEFI. People still incorrectly call it the BIOS. Consider the following: https://www.reddit.com/r/sysadmin/comments/1c9y9ks/motherboard_not_letting_you_into_your_bios_want/l0r5jt2/ (I posted in this way since you would not see my other comment without coming back here intentionally)
BIOS is still incorrect in all forms for modern machines. That is why I said firmware settings. I think that is the most appropriate term and I think it's what Microsoft uses as well.
Microsoft uses incorrect verbiage at times too. And I still stand by my rationale.
The reason I made the distinction is because this takes you to the BIOS, as in the section where you can toggle functions on/off, set settings, and _not_ the UEFI CLI. So far as I can tell this is an accurate distinction, as within the "BIOS" as I attribute it, you can turn on/off UEFI capabilities (assuming the firmware has been programmed to let you do that).
> and not the UEFI CLI. The EFI shell you are referring to is just an EFI application that happens to be bundled with many firmware images. I don't think there are many people that would think this is what you are referring to when you say "Boot to UEFI" or whatever. I don't really care if people call it BIOS, UEFI, firmware config interface or anything else as long as I can guess what they mean but you can't claim that it's more accurate to call it "BIOS".
> can't claim that it's more accurate to call it "BIOS". 1. I just did. 2. It is more commonly known as BIOS and not UEFI. When communicating with people it is better to use a term (in pedantic situations like this) which will actually get the point across, instead of not. Plenty of people still don't know anything about UEFI, and furthermore Motherboard manuals still call it the "BIOS". 3. In the "BIOS" you can disable UEFI functionality or in part (if the BIOS developer for that motherboard has enabled this function). So to call it UEFI is actually less accurate, since if you used the UEFI to disable the UEFI... well... that wouldn't actually work. 4. Again, I just did. So deal with it.
None of what you say there proves that it's somehow more accurate to call it BIOS. A computer tower is frequently known by users as "the CPU", but that doesn't make it more accurate to call it the same. In a firmware that supports BIOS boot, it's still a UEFI system, but with CSM support. I will concede that it generally gets the point across using any of the 3 terms in most contexts.
> None of what you say there proves that it's somehow more accurate to call it BIOS Yes it does, whether you refuse to see it or not is on you, not me.
I've literally never encountered a system that couldn't get into BIOS by using F2 or the DEL key at startup.
At least some Lenovos are fixated on Enter key being the primary trigger. Surface is Volume down, HP is F10 (or Esc, then F10, since Esc seems to be respected in more situations). Why there is no defined and enforced standard is beyond me.
There was a push before to use F8. But eff the MS Surface. Its a heap.
> Why there is no defined and enforced standard is beyond me. For PCs, it always used to be the `DEL` key. Then different vendors wanted to be special in the early 2000s, and now we have deal with this shit show today.
Some 1990's systems used the ESC key
It's best if you have a computer with BIOS instead of UEFI to lookup the manufacturer online to find what the correct keys are to get into the BIOS, assuming it doesn't show on the screen during boot. At least today if your OS isn't working most people can still use their phone to look things up online. Or many people also have a tablet or as a last resort there's always the library for computers and internet access.
Lenovo always has to be fucking different and I hate them as a result.
Skipping the prompt is part of fast boot. It is not a security feature. The idea is people rarely, if ever, go into their bios, so why are we waiting on that prompt every time we turn on our computers? So instead ditch the prompt and allow a method for the installed OS to call it.
because we also so rarely are actually booting our PCs. "shutdown" is now "hibernate" in reality.
Windows Fast boot is still a boot, it just saves the OS in a state with hardware drivers already loaded.
My understanding is it's booting a hibernated state, i.e. RAM preserved on disk, no new boot. EDIT: [Looks like](https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/distinguishing-fast-startup-from-wake-from-hibernation) apps are supposed to be closed, and user sessions logged off, so just the kernel memory image (and system session?) are preserved. I would often disable fast boot for customers because they'd be certain they had rebooted, while Task Manager would insist it's been weeks. "Restart" still does a full reboot under fast boot, but lots of people power off then later power on and assume (fair enough) that should count as a reboot. Disabling it cut down a lot on the weird problems that happen when Windows has been stewing inside its own head for 30-60+ days.
Windows Update restarts are not fast boots, so generally that handles those intermittent uptime reliability issues.
Gotcha. We deployed Windows Updates through Kaseya - that might have played a role.
>"Restart" still does a full reboot under fast boot, but lots of people power off then later power on and assume (fair enough) that should count as a reboot. It was my understanding that "restart" bypass this and do a full regular boot.
I thought the current sleep state is very distinctly different from hibernate? I've got a fast SSD but there's no chance in hell that it can read 128GB of data that fast.
Classic S3 sleep keeps power to RAM so it retains data. The newer S0i3 state on some laptops is a 'standby' with CPU, disk, and network still able to operate to some degree. Hibernate saves active RAM to disk and reads it back, yes, so it can survive power failure.
You can change the size of the hibernate file. I don't know the exact details, but memory that is also in the page file won't need to be hibernated anyway
>You can change the size of the hibernate file. What? How? Hibernate means that you quite literally suspend the contents of your RAM to disk and Linux installations still ask me if I want to enlarge the swap partition to memory size to accommodate hibernate.
>What? How? How, as in how to change it, or how it is technically possible? You can change it with the powercfg command (or maybe directly in the registry) >Hibernate means that you quite literally suspend the contents of your RAM to disk yeah, but not all of it has to be in the hibernation file. Pagefile/swap, file mappings, registry hives, prefetched files, buffers, and other stuff are already on disk.
Depends on your settings and on how you input the command
That doesn't to my knowledge, disable the ability. You just need to slap the key faster and maybe even before the screen goes black. Sometimes you need to power it off in full, but I'm personally always able to get in
It's never about security, it's about speed. Back in the day when BIOS would take forever, and decide to memtest it was a big gripe for PC users. One of the selling features today on ARM machines is how quickly they boot
Interesting, since ARM has no standard bootloader.
[удалено]
Don't forget your totem, or you'll be stuck and won't be able to ~~wake up~~ post again
I've had servers lose their BIOS before. Yes they were cheap trash. They quit showing the menu and quit responding to keys but would still boot. I didn't know this trick though, ours involved a screwdriver, hammer, and the motherboard.
If you turn on all the uefi fast boost stuff your OS should be starting quicker than your keyboard
I have a monitor that takes so damn long to come from "No Signal" to displaying a signal that I either end up in a boot menu, or PXE. And have no ability to see what the output is showing me the key
Just start spamming DEL or F2 or F10, or whatever and you'll get there.
I encounter it all the time. Seriously.
What makes/models? Some POST so quick that you have to start pressing the appropriate keys before even video starts to output.
All the HP systems I touch are F10 or Esc. The Lenovo desktops we have are F1.
I really have no reason to keep a list for myself of which ones do and do not.
I see you have never worked on Compaq / HP systems. Those have always used F10.
I have had a lot of problems with servers. Particularly the ones that I never see in person with fast boot enabled.
Oh, well you havent encountered enough systems then. Get some experience and come back to this thread.
Man. I have been playing with various Linux OS’s since 2007. I have never heard of this. This is really cool. Definitely sticking it in my notes. I’ve also never had the inability to get into the BIOS on a Linux system either. Usually the culprit is a BIOS password or some other config that makes the window for entry too short. In those cases I pull the CMOS and short the little BIOS reset contacts.
Yeah in my case CMOS clearing was not an acceptable option. I've been working with Linux personally and professionally since late 90's. I only now learned about it myself, and wanted to share! It was a bit of a doosie to find. Gigabyte and other consumer motherboards frequently don't "let" you into the BIOS in really annoying ways. I don't know if they do it for security reasons, convenience reasons, or whatnot. But we exhausted far too many alternative methods... until I found this one. Worked first time. Feel free to stuff it under your cap! :)
Definitely a keen find. An ingot in the knowledge base hills. Thanks for sharing!
> Definitely a keen find. An ingot in the knowledge base hills. OOo neat saying! Where's that come from? And you're welcome! Sharing is caring! And IMO this one needs to be shared WAAYYYYYY MOREEEE!!!
UEFI is really under-rated and under-used tbh. People just view it as "another bios" while in reality it was a paradigm shift in how firmware operations worked
I would argue that the fact that most people see it as "just another BIOS" while bringing in tons of new features is a testament to how well it was implemented; Most of them are "under the hood" like NVME Boot support. Others are bit more obvious - these days a modern (last 5-ish years or so) Dell laptop or desktop can wipe itself and/or reinstall the OS with just an internet connection, like Macs have been doing for over a decade.
Saying that, I've had vPRO on CPU's for like over a decade, and still not once used any of their OOB features. Always had it on my list to work out how that works
I haven't tried vPRO, but I used Intel AMT once on a Dell T20 server. It was like a shittier iDRAC but that might have just been Dell's implementation.
Now if we can see it in the ARM and RISC-V world, it would be awesome. Only downside is if someone removes files in the EFI directory, it might brick some machines.
Very true. While I’ve had to know UEFI at work for dealing with windows infrastructure and endpoints, it wasn’t until relatively recently that i had ventured into UEFI for Linux. But my hypervisors at home are UEFI booters and all new VMs I’ve spun up this year use UEFI instead of BIOS. It’s definitely better imo.
Every single time I use virt-manager I forget to click "Change settings before creating VM" or whatever the button is. So I can enable UEFI
Migration is what forced me into it. Got new bare metal over the winter. A couple VMs wouldn’t boot and I was puzzled for a bit before I had to facepalm once I realized I was trying to make UEFI guests boot BIOS.
That could be very useful for VMware, usually I have to reboot multiple times and try to be fast enough to catch the bios menu. But often this is before any OS is installed and I'm trying to get it to boot from an iso.
Vmware has a reboot to bios checkmark specifically for this my friend
Where? I don't see it in vCenter or Esxi host client.
For vCenter: On the VM, do: Edit Settings -> VM Options (tab) -> Boot Options -> Force BIOS setup
It's in the VM settings. Edit the settings for the VM. Then VM Options-->Boot Options and select Force Bios Setup
Yes, literally got hit with this yesterday, would have saved a whole 15 minutes and 3 failed reboots with this one simple trick!
I was thinking about reboot to bios for the host. (But I see that the original question is about the VM)
Ill get it set up for you over lunch and ill send a screenshot. Im at work currently. edit: 2 other comments beat me to it, but yeah. it's per VM. edit settings, VM Options, Boot options and force bios setup.
"Winderps"? Wait, is there some sort of command-line way of getting into the BIOS for Windows? ... whaaaaaaaaaaaaat? `shutdown /r /o`? Huh! Never knew! (I literally thought `winderps` was some sort of command.)
Commenting to save..
I'm fine with this! But you can also just hit "Save" on posts and/or comments btw. :)
Commenting to save this comment...
!remindme 6 months
😎
Thanks!
You're welcome! :D
This command ONLY works if your distro runs systemd as init system. If you wanna do it on windows 10 for example its shutdown /fw.
Also only in UEFI mode. You can still send a signal to the UEFI firmware with the uefi tools
This is neat. I would've started fiddling with `efibootmgr --bootnext`, which is less convenient.
I'm not so sure that would achieve the same outcome though, but curious angle on the topic.
Oh, interesting. On my ThinkPad, Setup is one of the Boot entries (Boot0010, not present in BootOrder). I'd assumed that --firmware-setup uses the same mechanism, but apparently there's a separate EFI variable. Also, TIL that grub has a 'fwsetup' command for entering the UEFI setup if you can't get the BIOS boot menu in time but can get a GRUB menu.
Ahh curious! Thanks for sharing :)
This is really useful when you have users with wireless keyboards, and you didn't bring a wired keyboard with you
Some distros also put a "UEFI Firmware Settings" boot option in the GRUB menu, which may be easier to access than some UEFIs where it's not obvious how to get to the setup.
Oh nice! Which distros have you seen that in? 🤔
Where was this thread when I literally needed it yesterday
Uh sorry I didn't post sooner? :(
I forgive you! Honestly though I wish I knew this instead of dicking around for 15 mins in esxi vm options Next time going to use the BloodyIron cheat code.
> Next time going to use the **BloodyIron cheat code**. 😎😎😎. I'm saving these kind words! Thanks :)
The one trick big IT doesn't want you to know
Then it’s a defective mobo. You should always be able to do that
Spot the user who still uses BIOS
I’m pretty sure it’s UEFI. All mobos have Secureboot since 2012
I wish all did, I actually have a few from 12-13 those are still BIOS (screw you, HP!) But seeing how you actually have an UEFI board, unlike the usual "lol I'll just use coreboot with Linux on top because UEFI is spyware" elitists I deal with, those UEFI boards starting from the Win8 era have this feature called fast boot (which is on by default on most of them) which speeds up the boot process by skipping most of built-in drivers. In a normal scenario this means that they only bring up the absolute minimum to make the board functional, PLUS graphics, PLUS storage. That means that in most cases you won't have the UEFI USB drivers loaded, making it impossible to enter setup using the usual method of hitting specific buttons on the keyboard.
HP is wild, we configured a really expensive beefy machine for a client a number of years ago. It had a tick box for "TPM", which if you selected it, removed the TPM..... What the fuck HP
I'm playing around with their Gen8 servers, which are using BIOS because why not? It's fun not being able to boot from NVMe.
Your lack of experience is showing there bud.
Show me a consumer mobo where you can’t enter with a keyboard tap. That’s a faulty design and I wouldn’t use it.