I had to reinstall my windows system which is fine it takes care of itself. But, I have to install my entire fedora system from scratch. Is there a way to simply reinstall the boot loader code without having to install from scratch with a UEFI system? I'm sure there is but I don't know about it. There's also a command called "efibootmgr" is this what I am looking for? AFAIK fedora doesn't install more partitions but just code in the /boot/efi partition. How can I reinstall or repair boot loader code without touching the system? Without having to reinstalling from scratch?
Bill
On Sep 19, 2023, at 20:41, Bill Cunningham bill.cu1234@gmail.com wrote:
I had to reinstall my windows system which is fine it takes care of itself. But, I have to install my entire fedora system from scratch. Is there a way to simply reinstall the boot loader code without having to install from scratch with a UEFI system? I'm sure there is but I don't know about it. There's also a command called "efibootmgr" is this what I am looking for? AFAIK fedora doesn't install more partitions but just code in the /boot/efi partition. How can I reinstall or repair boot loader code without touching the system? Without having to reinstalling from scratch?
It’s possible to use efibootmgr to re-add the firmware entry for Fedora, even from a rescue disk.
It might be easier, however, if your BIOS has a way to choose a new boot entry and to select the Fedora grub2 EFI executable, so you can just boot directly into Fedora and run efibootmgr from there.
You certainly don’t need to reinstall the whole OS. It’s just a couple bytes in the hardware’s firmware.
On 9/19/2023 9:21 PM, Jonathan Billings wrote:
On Sep 19, 2023, at 20:41, Bill Cunningham bill.cu1234@gmail.com wrote:
I had to reinstall my windows system which is fine it takes care of itself. But, I have to install my entire fedora system from scratch. Is there a way to simply reinstall the boot loader code without having to install from scratch with a UEFI system? I'm sure there is but I don't know about it. There's also a command called "efibootmgr" is this what I am looking for? AFAIK fedora doesn't install more partitions but just code in the /boot/efi partition. How can I reinstall or repair boot loader code without touching the system? Without having to reinstalling from scratch?
It’s possible to use efibootmgr to re-add the firmware entry for Fedora, even from a rescue disk.
It might be easier, however, if your BIOS has a way to choose a new boot entry and to select the Fedora grub2 EFI executable, so you can just boot directly into Fedora and run efibootmgr from there.
You certainly don’t need to reinstall the whole OS. It’s just a couple bytes in the hardware’s firmware.
The uefi bios is a pain in the behind. I'm always having to go in there and change boot orders. I'm starting to get the hang of that though. It should be as simple as deleting a directory in /boot/efi and removing boot code using efibootmgr or something similar. Does this uefi have 512 (or so) bytes at the beginning of a drive? I know nothing about it.
B
On Tue, 2023-09-19 at 20:40 -0400, Bill Cunningham wrote:
I had to reinstall my windows system which is fine it takes care of itself. But, I have to install my entire fedora system from scratch. Is there a way to simply reinstall the boot loader code without having to install from scratch with a UEFI system? I'm sure there is but I don't know about it. There's also a command called "efibootmgr" is this what I am looking for? AFAIK fedora doesn't install more partitions but just code in the /boot/efi partition. How can I reinstall or repair boot loader code without touching the system? Without having to reinstalling from scratch?
If Fedora has fully installed, it ought to do this for you. But nonetheless, it probably has installed everything, just hasn't set an entry in the bootlist for itself, or something else boots first without any timeout period for you to choose otherwise. The efibootmgr should let you set one.
You can run the command as an ordinary user, and it'll show you a list of boot options. On this PC, mine shows this:
[tim@rocky ~]$ efibootmgr BootCurrent: 0000 Timeout: 1 seconds BootOrder: 0000,0003,0005,0004 Boot0000* CentOS Boot0003* CD/DVD Drive Boot0004 Hard Drive Boot0005* USB
I don't recall why mine skips 0001 and 0002, I probably removed some stupid or duplicate options that I found in there.
As a root user (e.g. via sudo), you can also change the order, and add and remove entries. Essentially it's editing some data in the non- volatile RAM.
If Fedora is in there somewhere it can be a boot option in the firmware as your PC boots up, no having to delve into it and change settings. If you have a decent UEFI, you can get a list of clickable things to boot from.
I'd suggest look at its man file, show us your details, and grill us about what you can't work out.
Alternatively, Windows should have a similar equivalent editing function. You could see if it lists Fedora, and if it gives you any obvious ways to change the settings to your liking.
On 20 Sep 2023, at 01:41, Bill Cunningham bill.cu1234@gmail.com wrote:
I had to reinstall my windows system which is fine it takes care of itself. But, I have to install my entire fedora system from scratch. Is there a way to simply reinstall the boot loader code without having to install from scratch with a UEFI system? I'm sure there is but I don't know about it. There's also a command called "efibootmgr" is this what I am looking for? AFAIK fedora doesn't install more partitions but just code in the /boot/efi partition. How can I reinstall or repair boot loader code without touching the system? Without having to reinstalling from scratch?
In my notes I saved this command for fixing fedora booting on one of my systems. (I had a system that would fill its EFI variable space and need a full reset)
efibootmgr --create --disk /dev/md126 --part 2 --loader /EFI/fedora/shim.efi --label Fedora
In this case /dev/md126 is my raided fedora disk, replace with your disk.
/dev/md126p2 - VFAT - EFI
Partition 2 is what is mounted on /boot/EFI, change the 2 as needed.
Barry
Bill
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Wed, Sep 20, 2023 at 09:02:42AM +0100, Barry wrote:
On 20 Sep 2023, at 01:41, Bill Cunningham bill.cu1234@gmail.com wrote:
I had to reinstall my windows system which is fine it takes care of itself. But, I have to install my entire fedora system from scratch. Is there a way to simply reinstall the boot loader code without having to install from scratch with a UEFI system? I'm sure there is but I don't know about it. There's also a command called "efibootmgr" is this what I am looking for? AFAIK fedora doesn't install more partitions but just code in the /boot/efi partition. How can I reinstall or repair boot loader code without touching the system? Without having to reinstalling from scratch?
In my notes I saved this command for fixing fedora booting on one of my systems. (I had a system that would fill its EFI variable space and need a full reset)
efibootmgr --create --disk /dev/md126 --part 2 --loader /EFI/fedora/shim.efi --label Fedora
In this case /dev/md126 is my raided fedora disk, replace with your disk.
/dev/md126p2 - VFAT - EFI
Partition 2 is what is mounted on /boot/EFI, change the 2 as needed.
From my notes :) .. :
----- add a boot entry: efibootmgr -c -d /dev/sdb -p 1 -w -L Debian -l "\EFI\debian\grubx64.efi" -----
If I recall correctly: This command above was done a machine where /dev/sdb was a disk where Debian was already installed. The 'man' page should explain the rest of the options. see: https://wiki.debian.org/UEFI#efibootmgr_example_3_-_add_a_new_boot_entry
At the end of "man efibootmgr" you should find an example for a Fedora install - it says "The default OS Loader is \EFI\fedora\grub.efi" But that looks wrong to me. My guess would be that this should say for a nowadays Fedora install probably: "\EFI\fedora\shim.efi"
The latter at least was what I saw with a quick Internet search and the output from entering "efibootmgr" on my own Fedora install here. Excerpt:
[ ....] Boot0002* Fedora HD(1,GPT,[..])/File(\EFI\fedora\shim.efi) [ .... ]
See the "\EFI\fedora\shim.efi" section above..
I'd simply take some Live system on a thumb, boot it, and then have a look at the output of
# efibootmgr
and proceed with that info ...
Good luck! Wolfgang
On 9/21/2023 5:53 PM, Wolfgang Pfeiffer wrote:
On Wed, Sep 20, 2023 at 09:02:42AM +0100, Barry wrote:
On 20 Sep 2023, at 01:41, Bill Cunningham bill.cu1234@gmail.com wrote:
I had to reinstall my windows system which is fine it takes care of itself. But, I have to install my entire fedora system from scratch. Is there a way to simply reinstall the boot loader code without having to install from scratch with a UEFI system? I'm sure there is but I don't know about it. There's also a command called "efibootmgr" is this what I am looking for? AFAIK fedora doesn't install more partitions but just code in the /boot/efi partition. How can I reinstall or repair boot loader code without touching the system? Without having to reinstalling from scratch?
In my notes I saved this command for fixing fedora booting on one of my systems. (I had a system that would fill its EFI variable space and need a full reset)
efibootmgr --create --disk /dev/md126 --part 2 --loader /EFI/fedora/shim.efi --label Fedora
In this case /dev/md126 is my raided fedora disk, replace with your disk.
/dev/md126p2 - VFAT - EFI
Partition 2 is what is mounted on /boot/EFI, change the 2 as needed.
From my notes :) .. :
add a boot entry: efibootmgr -c -d /dev/sdb -p 1 -w -L Debian -l "\EFI\debian\grubx64.efi"
If I recall correctly: This command above was done a machine where /dev/sdb was a disk where Debian was already installed. The 'man' page should explain the rest of the options. see: https://wiki.debian.org/UEFI#efibootmgr_example_3_-_add_a_new_boot_entry
At the end of "man efibootmgr" you should find an example for a Fedora install - it says "The default OS Loader is \EFI\fedora\grub.efi" But that looks wrong to me. My guess would be that this should say for a nowadays Fedora install probably: "\EFI\fedora\shim.efi"
The latter at least was what I saw with a quick Internet search and the output from entering "efibootmgr" on my own Fedora install here. Excerpt:
[ ....] Boot0002* Fedora HD(1,GPT,[..])/File(\EFI\fedora\shim.efi) [ .... ]
See the "\EFI\fedora\shim.efi" section above..
I'd simply take some Live system on a thumb, boot it, and then have a look at the output of
# efibootmgr
and proceed with that info ...
Good luck! Wolfgang
What I would like to do for example, is if I removed a Windows OS, for example, the partition data (for fedora) would need to be reset. Say I reinstalled the system (windows). I believe that windows could take care of itself but I am going to have an unbootable fedora there.
Am I going to need to remove some data and let the system create a new UUID? That's exactly what I am running into. Needing to re enter boot code to rescue a fedora system. That would be done with a thumb drive. And efibootmgr would be an option in fixing boot loading. Simply removing the "fedora" directory in 'Boot/efi' might clean things but something is going to be re-written.
I will look into all this. TO be clear rescuing a fedora system is what I want to do.
B
On 09/21/2023 04:24 PM, Bill Cunningham wrote:
What I would like to do for example, is if I removed a Windows OS, for example, the partition data (for fedora) would need to be reset. Say I reinstalled the system (windows). I believe that windows could take care of itself but I am going to have an unbootable fedora there.
Before you go all heavy handed here, give us an idea of what's wrong so we have an idea what you'll need to do. Are you planning on reinstalling Windows? Does your Fedora system currently boot, and if not, what happens if you try? If your Fedora partitions are OK, and can be read when you're using a LiveUSB, there's no reason in the world that giving it a new UUID would make sense.
On 9/21/2023 6:35 PM, Joe Zeff wrote:
On 09/21/2023 04:24 PM, Bill Cunningham wrote:
What I would like to do for example, is if I removed a Windows OS, for example, the partition data (for fedora) would need to be reset. Say I reinstalled the system (windows). I believe that windows could take care of itself but I am going to have an unbootable fedora there.
Before you go all heavy handed here, give us an idea of what's wrong so we have an idea what you'll need to do. Are you planning on reinstalling Windows? Does your Fedora system currently boot, and if not, what happens if you try? If your Fedora partitions are OK, and can be read when you're using a LiveUSB, there's no reason in the world that giving it a new UUID would make sense.
From time to time I will reinstall my windows fresh. All is fine now. Since Windows clutters everything. When the windows is reinstalled fresh its bootloader will be default. I will need to boot into the fedora rescue mode. This is where grub will need to be put. With mbr boot, I used this-
grub2-install /dev/sda
grub2-mkconfig;
Then set the default. All is fine. Now, things are a little more complicated. For me anyway.
reinstalling a fedora bootloader and using that is what I need to do, everything is fine now at the moment.
B
On 9/21/23 15:43, Bill Cunningham wrote:
On 9/21/2023 6:35 PM, Joe Zeff wrote:
On 09/21/2023 04:24 PM, Bill Cunningham wrote:
What I would like to do for example, is if I removed a Windows OS, for example, the partition data (for fedora) would need to be reset. Say I reinstalled the system (windows). I believe that windows could take care of itself but I am going to have an unbootable fedora there.
Before you go all heavy handed here, give us an idea of what's wrong so we have an idea what you'll need to do. Are you planning on reinstalling Windows? Does your Fedora system currently boot, and if not, what happens if you try? If your Fedora partitions are OK, and can be read when you're using a LiveUSB, there's no reason in the world that giving it a new UUID would make sense.
From time to time I will reinstall my windows fresh. All is fine now. Since Windows clutters everything. When the windows is reinstalled fresh its bootloader will be default. I will need to boot into the fedora rescue mode. This is where grub will need to be put. With mbr boot, I used this-
grub2-install /dev/sda
Don't do this with EFI. That would be bad.
grub2-mkconfig;
Not necessary.
Then set the default. All is fine. Now, things are a little more complicated. For me anyway.
reinstalling a fedora bootloader and using that is what I need to do, everything is fine now at the moment.
If you're using EFI, you don't need to do anything. Windows and Fedora have separate, independent bootloaders. The only thing you might have to do is tell your BIOS that you want Fedora as the default boot option. (Unless windows does something stupid like reformatting the EFI partition, but it really shouldn't do that and I doubt it would.)
On Thu, Sep 21, 2023 at 03:59:23PM -0700, Samuel Sieb wrote:
If you're using EFI, you don't need to do anything. Windows and Fedora have separate, independent bootloaders. The only thing you might have to do is tell your BIOS that you want Fedora as the default boot option. (Unless windows does something stupid like reformatting the EFI partition, but it really shouldn't do that and I doubt it would.)
Your last sentence is actually the question.
So: Bill Cunningham: do you still see your Fedora installation in the BIOS/UEFI boot menu?
If yes: Either tell your BIOS - that is, if it provides this option - that Fedora should be booted by default - or, if that's not possible, efibootmgr might be the option to rewrite the BIOS boot sequence.
In that latter case - if you still can start Fedora via your BIOS/UEFI - you might boot right into Fedora and run efibootmgr from there, without the need for a Live Linux USB thumb procedure ...
Again: good luck! Wolfgang
Bill Cunningham composed on 2023-09-21 18:43 (UTC-0400):
its bootloader will be default. I will need to boot into the fedora rescue mode. This is where grub will need to be put. With mbr boot, I used this-
grub2-install /dev/sda
grub2-mkconfig;
Then set the default. All is fine. Now, things are a little more complicated. For me anyway.
They shouldn't be. Once booted to rescue media, all you *should* need is to reorder the UEFI boot priority:
# efibootmgr BootCurrent: 0005 Timeout: 1 seconds BootOrder: 0004,0000,0001,0002,0003,0005 Boot0000* fedora HD(... Boot0001* UEFI OS HD(... Boot0002* Hard Drive BBS(HD... Boot0003* CD/DVD Drive BBS(CD... Boot0004* Windows ... Boot0005* UEFI: USB DISK... Boot0006* USB BBS(HD... # efibootmgr -o 0,4,1,2,3 BootCurrent: 0005 Timeout: 1 seconds BootOrder: 0000,0004,0001,0002,0003,0005 Boot0000* fedora HD(... Boot0001* UEFI OS HD(... Boot0002* Hard Drive BBS(HD... Boot0003* CD/DVD Drive BBS(CD... Boot0004* Windows ... Boot0005* UEFI: USB DISK... Boot0006* USB BBS(HD... # systemctl reboot
One command to ID the state. One command to change the state. Another to reboot normally.
(Assuming your UEFI BIOS works as it should. Mine all do.)
On 9/21/2023 7:23 PM, Felix Miata wrote:
Bill Cunningham composed on 2023-09-21 18:43 (UTC-0400):
its bootloader will be default. I will need to boot into the fedora rescue mode. This is where grub will need to be put. With mbr boot, I used this- grub2-install /dev/sda grub2-mkconfig; Then set the default. All is fine. Now, things are a little more complicated. For me anyway.
They shouldn't be. Once booted to rescue media, all you *should* need is to reorder the UEFI boot priority:
# efibootmgr BootCurrent: 0005 Timeout: 1 seconds BootOrder: 0004,0000,0001,0002,0003,0005 Boot0000* fedora HD(... Boot0001* UEFI OS HD(... Boot0002* Hard Drive BBS(HD... Boot0003* CD/DVD Drive BBS(CD... Boot0004* Windows ... Boot0005* UEFI: USB DISK... Boot0006* USB BBS(HD... # efibootmgr -o 0,4,1,2,3 BootCurrent: 0005 Timeout: 1 seconds BootOrder: 0000,0004,0001,0002,0003,0005 Boot0000* fedora HD(... Boot0001* UEFI OS HD(... Boot0002* Hard Drive BBS(HD... Boot0003* CD/DVD Drive BBS(CD... Boot0004* Windows ... Boot0005* UEFI: USB DISK... Boot0006* USB BBS(HD... # systemctl reboot
One command to ID the state. One command to change the state. Another to reboot normally.
(Assuming your UEFI BIOS works as it should. Mine all do.)
I see. I would have ordered it usb stick, dvd,fedora,windows myself :)
Bill Cunningham composed on 2023-09-21 19:52 (UTC-0400):
Felix Miata wrote:
# efibootmgr -o 0,4,1,2,3 BootCurrent: 0005 Timeout: 1 seconds BootOrder: 0000,0004,0001,0002,0003,0005 Boot0000* fedora HD(... Boot0001* UEFI OS HD(... Boot0002* Hard Drive BBS(HD... Boot0003* CD/DVD Drive BBS(CD... Boot0004* Windows ... Boot0005* UEFI: USB DISK... Boot0006* USB BBS(HD... # systemctl reboot
One command to ID the state. One command to change the state. Another to reboot normally.
(Assuming your UEFI BIOS works as it should. Mine all do.)
I see. I would have ordered it usb stick, dvd,fedora,windows myself :)
Since UEFI, most USB sticks for installation and/or rescue are configured to boot in either legacy or EFI mode. When the UEFI BIOS has CSM (legacy) booting enabled, such USB sticks will show two entries per USB stick, one for each mode, which is why you see above both 0005 and 0006 entries.
Also with UEFI, it's preferred to have the HDD/SSD's preferred OS as top priority, and to use the BBS hotkey whenever an alternative boot device is desired instead.
On 9/21/2023 8:11 PM, Felix Miata wrote:
Bill Cunningham composed on 2023-09-21 19:52 (UTC-0400):
Felix Miata wrote:
# efibootmgr -o 0,4,1,2,3 BootCurrent: 0005 Timeout: 1 seconds BootOrder: 0000,0004,0001,0002,0003,0005 Boot0000* fedora HD(... Boot0001* UEFI OS HD(... Boot0002* Hard Drive BBS(HD... Boot0003* CD/DVD Drive BBS(CD... Boot0004* Windows ... Boot0005* UEFI: USB DISK... Boot0006* USB BBS(HD... # systemctl reboot One command to ID the state. One command to change the state. Another to reboot normally. (Assuming your UEFI BIOS works as it should. Mine all do.)
I see. I would have ordered it usb stick, dvd,fedora,windows myself :)
Since UEFI, most USB sticks for installation and/or rescue are configured to boot in either legacy or EFI mode. When the UEFI BIOS has CSM (legacy) booting enabled, such USB sticks will show two entries per USB stick, one for each mode, which is why you see above both 0005 and 0006 entries.
Also with UEFI, it's preferred to have the HDD/SSD's preferred OS as top priority, and to use the BBS hotkey whenever an alternative boot device is desired instead.
Does that mean you use a F key to boot from a USB stick? My UEFI is always putting the OS before the USB stick. I have to change it to boot from a USB stick. How do you use this "BBS Hotkey?
On 9/21/23 17:23, Bill Cunningham wrote:
On 9/21/2023 8:11 PM, Felix Miata wrote:
Also with UEFI, it's preferred to have the HDD/SSD's preferred OS as top priority, and to use the BBS hotkey whenever an alternative boot device is desired instead.
Does that mean you use a F key to boot from a USB stick? My UEFI is always putting the OS before the USB stick. I have to change it to boot from a USB stick. How do you use this "BBS Hotkey?
There's usually a function key that you can press right as the BIOS is initializing (the same point you would press a key to enter the BIOS configuration) that brings up a menu of boot options you can select from. Which key it is depends on the brand of BIOS and sometimes it needs to be enabled first.
On Thu, Sep 21, 2023 at 08:23:44PM -0400, Bill Cunningham wrote:
Does that mean you use a F key to boot from a USB stick? My UEFI is always putting the OS before the USB stick. I have to change it to boot from a USB stick. How do you use this "BBS Hotkey?
You have to find out what your "F" key is to enter your BIOS/UEFI boot menu - on my machine (Dell/Alienware) the key for that menu is F12 - you have to be very quick to press that key after powering on your computer - see your hardware manual - on- or offline - which F-Key you need ...
Wolfgang
On Fri, 2023-09-22 at 02:48 +0200, Wolfgang Pfeiffer wrote:
You have to find out what your "F" key is to enter your BIOS/UEFI boot menu - on my machine (Dell/Alienware) the key for that menu is F12 - you have to be very quick to press that key after powering on your computer - see your hardware manual - on- or offline - which F-Key you need ...
My UEFI configuration options allow me to set a timeout. It'll show a boot menu for so-many seconds before automatically carrying on booting the default choice. This is a "what to do now" choice, as opposed to making a permanent setting.
Bill, this is the configuration controls built into the motherboard, what people used to call BIOS settings, but often with a fancier interface. You get to choose your defaults, and which choices will appear, and a timeout period. You may even be able to put in more useful names, such as Fedora rather than drive 0, etc.
This is all before GRUB gets involved. When the motherboard's firmware boots Fedora (as opposed to any other choice), that's when it hands over to GRUB and the GRUB menu.
It's a bit of a pass-the-baton relay race.
Bill Cunningham composed on 2023-09-21 20:23 (UTC-0400):
Felix Miata wrote:
...
Since UEFI, most USB sticks for installation and/or rescue are configured to boot in either legacy or EFI mode. When the UEFI BIOS has CSM (legacy) booting enabled, such USB sticks will show two entries per USB stick, one for each mode, which is why you see above both 0005 and 0006 entries.
Also with UEFI, it's preferred to have the HDD/SSD's preferred OS as top priority, and to use the BBS hotkey whenever an alternative boot device is desired instead.
Does that mean you use a F key to boot from a USB stick? My UEFI is always putting the OS before the USB stick. I have to change it to boot from a USB stick. How do you use this "BBS Hotkey?
Exactly the same as you use a BIOS setup key (typically DEL or F2) specific to the various brands and their BIOS:
BBS Boot Keys
[*]ASRock F11 [*]Asus F8 [*]Biostar F9 [*]Dell F12 [*]eCS F12 or F10 [*]eMachines F10 [*]EVGA F7 [*]Gigabyte F12 [*]HP F9 or ESC or ESC,F9 [*]Intel F10 [*]Lenovo F12 or F8 or F10 [*]MSI F11 [*]Toshiba F12
What does BBS mean in BIOS? Short for BIOS boot specification, BBS is a BIOS (basic input/output system) feature that creates, maintains, and prioritizes all the IPL (initial program load) devices. While the computer is booting, each IPL device is checked to see if it's bootable. https://www.computerhope.com/jargon/b/bbs.htm
On 9/21/2023 8:58 PM, Felix Miata wrote:
Bill Cunningham composed on 2023-09-21 20:23 (UTC-0400):
Felix Miata wrote:
...
Since UEFI, most USB sticks for installation and/or rescue are configured to boot in either legacy or EFI mode. When the UEFI BIOS has CSM (legacy) booting enabled, such USB sticks will show two entries per USB stick, one for each mode, which is why you see above both 0005 and 0006 entries. Also with UEFI, it's preferred to have the HDD/SSD's preferred OS as top priority, and to use the BBS hotkey whenever an alternative boot device is desired instead.
Does that mean you use a F key to boot from a USB stick? My UEFI is always putting the OS before the USB stick. I have to change it to boot from a USB stick. How do you use this "BBS Hotkey?
Exactly the same as you use a BIOS setup key (typically DEL or F2) specific to the various brands and their BIOS:
BBS Boot Keys
[*]ASRock F11 [*]Asus F8 [*]Biostar F9 [*]Dell F12 [*]eCS F12 or F10 [*]eMachines F10 [*]EVGA F7 [*]Gigabyte F12 [*]HP F9 or ESC or ESC,F9 [*]Intel F10 [*]Lenovo F12 or F8 or F10 [*]MSI F11 [*]Toshiba F12
What does BBS mean in BIOS? Short for BIOS boot specification, BBS is a BIOS (basic input/output system) feature that creates, maintains, and prioritizes all the IPL (initial program load) devices. While the computer is booting, each IPL device is checked to see if it's bootable. https://www.computerhope.com/jargon/b/bbs.htm
OK I see well mine is HP. The Boot order key is F9 and I guess setup is F10.
To me BBS brings memories of early internet or pre internet BBS systems, with Sysops :)
On 9/21/2023 5:53 PM, Wolfgang Pfeiffer wrote:
On Wed, Sep 20, 2023 at 09:02:42AM +0100, Barry wrote:
On 20 Sep 2023, at 01:41, Bill Cunningham bill.cu1234@gmail.com wrote:
I had to reinstall my windows system which is fine it takes care of itself. But, I have to install my entire fedora system from scratch. Is there a way to simply reinstall the boot loader code without having to install from scratch with a UEFI system? I'm sure there is but I don't know about it. There's also a command called "efibootmgr" is this what I am looking for? AFAIK fedora doesn't install more partitions but just code in the /boot/efi partition. How can I reinstall or repair boot loader code without touching the system? Without having to reinstalling from scratch?
In my notes I saved this command for fixing fedora booting on one of my systems. (I had a system that would fill its EFI variable space and need a full reset)
efibootmgr --create --disk /dev/md126 --part 2 --loader /EFI/fedora/shim.efi --label Fedora
In this case /dev/md126 is my raided fedora disk, replace with your disk.
/dev/md126p2 - VFAT - EFI
Partition 2 is what is mounted on /boot/EFI, change the 2 as needed.
From my notes :) .. :
add a boot entry: efibootmgr -c -d /dev/sdb -p 1 -w -L Debian -l "\EFI\debian\grubx64.efi"
If I recall correctly: This command above was done a machine where /dev/sdb was a disk where Debian was already installed. The 'man' page should explain the rest of the options. see: https://wiki.debian.org/UEFI#efibootmgr_example_3_-_add_a_new_boot_entry
At the end of "man efibootmgr" you should find an example for a Fedora install - it says "The default OS Loader is \EFI\fedora\grub.efi" But that looks wrong to me. My guess would be that this should say for a nowadays Fedora install probably: "\EFI\fedora\shim.efi"
The latter at least was what I saw with a quick Internet search and the output from entering "efibootmgr" on my own Fedora install here. Excerpt:
[ ....] Boot0002* Fedora HD(1,GPT,[..])/File(\EFI\fedora\shim.efi) [ .... ]
See the "\EFI\fedora\shim.efi" section above..
I'd simply take some Live system on a thumb, boot it, and then have a look at the output of
# efibootmgr
and proceed with that info ...
Good luck! Wolfgang
Would it be that entering the simple grub2-install (like with a mbr boot) would work? That's the important thing, to rescue a fedora system and get it running. The other things about uefi I could learn in time.
B
On Thu, 21 Sep 2023, Bill Cunningham wrote:
On 9/21/2023 5:53 PM, Wolfgang Pfeiffer wrote:
On Wed, Sep 20, 2023 at 09:02:42AM +0100, Barry wrote:
On 20 Sep 2023, at 01:41, Bill Cunningham bill.cu1234@gmail.com wrote:
I had to reinstall my windows system which is fine it takes care of itself. But, I have to install my entire fedora system from scratch. Is there a way to simply reinstall the boot loader code without having to install from scratch with a UEFI system? I'm sure there is but I don't know about it. There's also a command called "efibootmgr" is this what I am looking for? AFAIK fedora doesn't install more partitions but just code in the /boot/efi partition. How can I reinstall or repair boot loader code without touching the system? Without having to reinstalling from scratch?
In my notes I saved this command for fixing fedora booting on one of my systems. (I had a system that would fill its EFI variable space and need a full reset)
efibootmgr --create --disk /dev/md126 --part 2 --loader /EFI/fedora/shim.efi --label Fedora
In this case /dev/md126 is my raided fedora disk, replace with your disk.
/dev/md126p2 - VFAT - EFI
Partition 2 is what is mounted on /boot/EFI, change the 2 as needed.
From my notes :) .. :
add a boot entry: efibootmgr -c -d /dev/sdb -p 1 -w -L Debian -l "\EFI\debian\grubx64.efi"
If I recall correctly: This command above was done a machine where /dev/sdb was a disk where Debian was already installed. The 'man' page should explain the rest of the options. see: https://wiki.debian.org/UEFI#efibootmgr_example_3_-_add_a_new_boot_entry
At the end of "man efibootmgr" you should find an example for a Fedora install - it says "The default OS Loader is \EFI\fedora\grub.efi" But that looks wrong to me. My guess would be that this should say for a nowadays Fedora install probably: "\EFI\fedora\shim.efi"
The latter at least was what I saw with a quick Internet search and the output from entering "efibootmgr" on my own Fedora install here. Excerpt:
[ ....] Boot0002* Fedora HD(1,GPT,[..])/File(\EFI\fedora\shim.efi) [ .... ]
See the "\EFI\fedora\shim.efi" section above..
I'd simply take some Live system on a thumb, boot it, and then have a look at the output of
# efibootmgr
and proceed with that info ...
Good luck! Wolfgang
Would it be that entering the simple grub2-install (like with a mbr boot) would work? That's the important thing, to rescue a fedora system and get it running. The other things about uefi I could learn in time.
B
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
That sure was a lot of quoteage for just a B.
On 9/22/23 17:30, Michael Hennebry wrote:
On Thu, 21 Sep 2023, Bill Cunningham wrote:
Would it be that entering the simple grub2-install (like with a mbr boot) would work? That's the important thing, to rescue a fedora system and get it running. The other things about uefi I could learn in time.
B
That sure was a lot of quoteage for just a B.
His quoting is often broken for some reason. That whole section was actually added by him.
On Fri, 2023-09-22 at 23:01 -0700, Samuel Sieb wrote:
His quoting is often broken for some reason. That whole section was actually added by him.
Probably needs to add one more blank line between quotes and replies.
Some email editors are terrible at mis-joining sections. And confusing because they do something more to it as you're sending it than appeared while you were writing it.
I've gotten used to Evolutions foibles, over time. I've never liked the way Thunderbird worked.
On 9/23/23 01:41, Tim via users wrote:
On Fri, 2023-09-22 at 23:01 -0700, Samuel Sieb wrote:
His quoting is often broken for some reason. That whole section was actually added by him.
Probably needs to add one more blank line between quotes and replies.
Some email editors are terrible at mis-joining sections. And confusing because they do something more to it as you're sending it than appeared while you were writing it.
Yes, I always make sure now that there's a blank line after the part I'm quoting.
On 9/23/2023 2:42 PM, Samuel Sieb wrote:
On 9/23/23 01:41, Tim via users wrote:
On Fri, 2023-09-22 at 23:01 -0700, Samuel Sieb wrote:
His quoting is often broken for some reason. That whole section was actually added by him.
Probably needs to add one more blank line between quotes and replies.
Some email editors are terrible at mis-joining sections. And confusing because they do something more to it as you're sending it than appeared while you were writing it.
Yes, I always make sure now that there's a blank line after the part I'm quoting.
I have only trimmed the signature here. Does this look right? Normally that's all I trim is the signature.
B
On 9/23/23 12:07, Bill Cunningham wrote:
On 9/23/2023 2:42 PM, Samuel Sieb wrote:
On 9/23/23 01:41, Tim via users wrote:
On Fri, 2023-09-22 at 23:01 -0700, Samuel Sieb wrote:
His quoting is often broken for some reason. That whole section was actually added by him.
Probably needs to add one more blank line between quotes and replies.
Some email editors are terrible at mis-joining sections. And confusing because they do something more to it as you're sending it than appeared while you were writing it.
Yes, I always make sure now that there's a blank line after the part I'm quoting.
I have only trimmed the signature here. Does this look right? Normally that's all I trim is the signature.
Yes, that was good. Just make sure to leave a blank line between the part you're quoting and the new text you're adding.
untrimmed messages be really unnerving ... I mean, it seems to be a known fact that lots of people, especially in the computer world, can't seem to think and write "in complete thoughts with context" (Nick Holland), thus being unable to understand a trimmed message - but please, everyone: trim, if possible: there are still a few of us out there who are not complete morons ...
-- Wolfgang
On Sun, 2023-09-24 at 00:48 +0200, Wolfgang Pfeiffer wrote:
untrimmed messages be really unnerving ... I mean, it seems to be a known fact that lots of people, especially in the computer world, can't seem to think and write "in complete thoughts with context" (Nick Holland), thus being unable to understand a trimmed message - but please, everyone: trim, if possible: there are still a few of us out there who are not complete morons ...
But do quote at least some of the message for context.
poc
On Sun, Sep 24, 2023 at 11:31:47AM +0100, Patrick O'Callaghan wrote:
On Sun, 2023-09-24 at 00:48 +0200, Wolfgang Pfeiffer wrote:
untrimmed messages be really unnerving ... I mean, it seems to be a known fact that lots of people, especially in the computer world, can't seem to think and write "in complete thoughts with context" (Nick Holland), thus being unable to understand a trimmed message - but please, everyone: trim, if possible: there are still a few of us out there who are not complete morons ...
But do quote at least some of the message for context.
It wasn't directed specifically at anyone here in this thread, but simply a reply to the new topic.
Every now and then, not just here on the Fedora list, extensive quotings simply are too often unnecessary to understand the answer, and then become a bit annoying ..
And sadly, admittedly: sometimes I'm even not much better in that regard .. ;)
-- Wolfgang
On Sun, 2023-09-24 at 16:32 +0200, Wolfgang Pfeiffer wrote:
On Sun, Sep 24, 2023 at 11:31:47AM +0100, Patrick O'Callaghan wrote:
On Sun, 2023-09-24 at 00:48 +0200, Wolfgang Pfeiffer wrote:
untrimmed messages be really unnerving ... I mean, it seems to be a known fact that lots of people, especially in the computer world, can't seem to think and write "in complete thoughts with context" (Nick Holland), thus being unable to understand a trimmed message
but please, everyone: trim, if possible: there are still a few of us out there who are not complete morons ...
But do quote at least some of the message for context.
It wasn't directed specifically at anyone here in this thread, but simply a reply to the new topic.
Every now and then, not just here on the Fedora list, extensive quotings simply are too often unnecessary to understand the answer, and then become a bit annoying ..
Agreed.
And sadly, admittedly: sometimes I'm even not much better in that regard .. ;)
In fact the new topic should really have been a separate thread, but it's a bit late for that now.
poc