Very likely these aren't exactly related - as in, the 'hardware configuration' (the system BIOS) is not provided by the host OS, its the board's firmware. Likely you've got some 'quick boot' or similar enabled, coupled with UEFI boot, and that's causing the machine to POST more quickly than you can hit the delete key (or whatever it likes). You can try grabbing the BIOS configuration menu via a reboot command issued through systemctl:
Code:
systemctl reboot --firmware-setup
(more here:
https://www.freedesktop.org/software...firmware-setup - as it notes some systems won't be able to do this, and I have encountered a few in the wild so that warning is worth noting)
If your system won't/can't work with that command, or you need into the BIOS to fix an issue and can't get into the OS to run that reboot (e.g. something goes wrong with Fedora or hardware), the easiest, but probably crudest, solution I can think of is to just remove the bootable drive(s) connection to the motherboard and then boot up - most newer motherboards will default into their BIOS setup if no bootable media is detected, but otherwise you'll just get the "No Boot disk Found Reboot" error, give it the three-finger salute, and mash delete (usually 'holding it down' causes issues in my experience - so just channel your inner arcader and button-mash it) or whatever the key is for your specific system (some systems want an F-key instead) and it should be good to go. This is inelegant, but the way things have gone with 'boot time' becoming a 'performance metric' somewhat inevitable: folks buy systems based on how rapidly they can 'start up' which removes all of the time for user intervention at startup (modern problems...as they say).