Hello,
There is bug reported about grub2-install 2240994 for a while but no solution are proposed.
grub2-install: error: This utility should not be used for EFI platforms because it does not support UEFI Secure Boot. If you really wish to proceed, invoke the --force option. Make sure Secure Boot is disabled before proceeding.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com ===========================================================================
On 6/2/24 6:00 AM, Patrick Dupre via users wrote:
There is bug reported about grub2-install 2240994 for a while but no solution are proposed.
grub2-install: error: This utility should not be used for EFI platforms because it does not support UEFI Secure Boot. If you really wish to proceed, invoke the --force option. Make sure Secure Boot is disabled before proceeding.
What are you trying to do? There's nothing to install. The grub package puts the files in the right place.
On 2/6/24 23:00, Patrick Dupre via users wrote:
Hello,
There is bug reported about grub2-install 2240994 for a while but no solution are proposed.
grub2-install: error: This utility should not be used for EFI platforms because it does not support UEFI Secure Boot. If you really wish to proceed, invoke the --force option. Make sure Secure Boot is disabled before proceeding.
That is not a defect unless you don't have a UEFI system but have a legacy boot system. For UEFI systems grub2-install is redundant, it is no longer needed. For UEFI you only need to run run grub2-mkconfig to build the config that grub will use at boot, but you only need to use grub2-mkconfig if, like me, you don't like what grubby does when a new kernel is installed.
regards, Steve
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com =========================================================================== -- _______________________________________________ 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
Thank for the feedback,
Thus, I am going to summarize the situation. I updated a fedora 38 installation to 40 (on sdc3) as I used to do. But this installation is now not visible from the grub bot menu. I run grub2-mkconfig -o /boot/grub2/grub.cfg again, and again from both installation (40 and 38 on sda4).
The output seems OK (Fedora 40 found from fedora 38, and fedora 38 found from fedora 40). os-prober OK cf /dev/sdc3:Fedora Linux 40 (Forty):Fedora1:linux (from fedora 38)
The only way to start fedora 40 is to boot from super grub2 If I understand UEFI does not see the fedora 40 installation
It looks that the information from grub2-mkconfig are never made available to the grub boot
-- _______________________________________________ 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
I wish to add that efibootmgr
does not list the sdc3 installation.
Subject: Re: grub2-install
Thank for the feedback,
Thus, I am going to summarize the situation. I updated a fedora 38 installation to 40 (on sdc3) as I used to do. But this installation is now not visible from the grub bot menu. I run grub2-mkconfig -o /boot/grub2/grub.cfg again, and again from both installation (40 and 38 on sda4).
The output seems OK (Fedora 40 found from fedora 38, and fedora 38 found from fedora 40). os-prober OK cf /dev/sdc3:Fedora Linux 40 (Forty):Fedora1:linux (from fedora 38)
The only way to start fedora 40 is to boot from super grub2 If I understand UEFI does not see the fedora 40 installation
It looks that the information from grub2-mkconfig are never made available to the grub boot
-- _______________________________________________ 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
-- _______________________________________________ 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 Mon, 2024-06-03 at 13:53 +0200, Patrick Dupre via users wrote:
I wish to add that efibootmgr does not list the sdc3 installation.
By default, it'll only show the boot options that installations have entered into it. If your install didn't do that, you can add entries, yourself.
Have a look at the man file for efibootmgr (or other documentation). If you're not sure what you have to do, post back what you think you might have to do, to consult with people here.
I can't tell from your posts in this thread whether you're trying to use a UEFI or BIOS system, or shoehorning one install type into the other system.
Hello,
With your message we lost the thread.
The Fedora 38 is installed on sda4 with /boot/efi on sda3 (fat16 EFI System Partition) The fedora 40 is installed on sdc3 I only have /boot installed on sdc2 I guess that I could run something like grub-install /dev/sda --target=x86_64-efi --efi-directory=/boot/efi/ but this provide an error as indicated in my previous message. sda1 is BIOS boot partition grub2 core.img (I cannot mount it)
efibootmgr -v BootCurrent: 0000 Timeout: 1 seconds BootOrder: 0000,0006,0004,0005,0002,0001 Boot0000* fedora HD(3,GPT,01dd38df-fda0-487b-add4-1fca3aecf167,0x2001800,0xfa000)/\EFI\FEDORA\GRUBX64.EFI Boot0006* Fedora HD(3,GPT,01dd38df-fda0-487b-add4-1fca3aecf167,0x2001800,0xfa000)/\EFI\FEDORA\SHIM.EFI0000424f
0005, 0002, 0001 are hardware
Running grub-customizer I get (from fedora 38) "Could not import accounts from legacy client configuration initializing (w/o specified bootloader type)… * reading partition info… * Loading Framebuffer resolutions (background process) * Finding out if this is a live CD sh: line 1: hwinfo: command not found *** initializing (w/ specified bootloader type)… * Checking if the config directory is clean *** loading configuration *** loading - preserveConfig: no * unsetting saved config *** loading settings *** loading grub list * loading scripts… * loading proxies… * cleaning up proxy configuration… * creating proxifiedScript links & chmodding other files… * running grub2-mkconfig Error getting object manager client: Error calling StartServiceByName for com.nextcloudgmbh.Nextcloud: Timeout was reachedError getting object manager client: Error calling StartServiceByName for com.nextcloudgmbh.Nextcloud: Timeout was reached * restoring grub configuration * removing invalid proxies from list exception '28InvalidStringFormatException' with message 'unable to parse index from ' in /builddir/build/BUILD/grub-customizer-5.2.3/src/main/../Bootstrap/../Model/Script.hpp:308 * loading completed *** grub list completely loaded *** loading saved grub list
I do not understand all the fedora 36 that I never use (no fedora 38 or fedora 40) They also show at the grub boot !
Should I do something like efibootmgr --create --disk=/dev/sdc --part=3 --label="fedora 40" --loader=/boot/efi/EFI/fedora/shimx64.efi ?
Do I need to do something from Fedora 40 (right now only bootable from supergrub2 USB key)?
On Mon, 2024-06-03 at 13:53 +0200, Patrick Dupre via users wrote:
I wish to add that efibootmgr does not list the sdc3 installation.
By default, it'll only show the boot options that installations have entered into it. If your install didn't do that, you can add entries, yourself.
Have a look at the man file for efibootmgr (or other documentation). If you're not sure what you have to do, post back what you think you might have to do, to consult with people here.
I can't tell from your posts in this thread whether you're trying to use a UEFI or BIOS system, or shoehorning one install type into the other system.
--
uname -rsvp Linux 3.10.0-1160.118.1.el7.x86_64 #1 SMP Wed Apr 24 16:01:50 UTC 2024 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list.
On Mon, 2024-06-03 at 13:53 +0200, Patrick Dupre via users wrote:
I wish to add that efibootmgr does not list the sdc3 installation.
By default, it'll only show the boot options that installations have entered into it. If your install didn't do that, you can add entries, yourself.
Have a look at the man file for efibootmgr (or other documentation). If you're not sure what you have to do, post back what you think you might have to do, to consult with people here.
I can't tell from your posts in this thread whether you're trying to use a UEFI or BIOS system, or shoehorning one install type into the other system.
--
uname -rsvp Linux 3.10.0-1160.118.1.el7.x86_64 #1 SMP Wed Apr 24 16:01:50 UTC 2024 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list.
On Mon, 2024-06-03 at 15:59 +0200, Patrick Dupre via users wrote:
With your message we lost the thread.
The thread is there. You're not supposed to keep quoting every prior reply when you respond to messages. Messages become huge and unreadable messes.
You're supposed to reply to the bits you're responding to, and cut out the rest that isn't actually needed. Unfortunately people are forgetting this and trying to get an entire thread inside each and every message.
If anyone has answers to something you've posted, they'll post them as a reply to THAT message (if they know what they're doing), not just jam them into some other message somewhere in the thread. That's what threading is, it's somewhat like a family tree.
On Tue, 2024-06-04 at 23:36 +0930, Tim via users wrote:
You're supposed to reply to the bits you're responding to, and cut out the rest that isn't actually needed. Unfortunately people are forgetting this and trying to get an entire thread inside each and every message.
If anyone has answers to something you've posted, they'll post them as a reply to THAT message (if they know what they're doing), not just jam them into some other message somewhere in the thread. That's what threading is, it's somewhat like a family tree.
+1
poc
On Mon, Jun 3, 2024 at 3:11 AM Patrick Dupre via users users@lists.fedoraproject.org wrote:
I updated a fedora 38 installation to 40 (on sdc3) as I used to do. But this installation is now not visible from the grub bot menu. I run grub2-mkconfig -o /boot/grub2/grub.cfg again, and again from both installation (40 and 38 on sda4).
The output seems OK (Fedora 40 found from fedora 38, and fedora 38 found from fedora 40). os-prober OK cf /dev/sdc3:Fedora Linux 40 (Forty):Fedora1:linux (from fedora 38)
The only way to start fedora 40 is to boot from super grub2 If I understand UEFI does not see the fedora 40 installation
It looks that the information from grub2-mkconfig are never made available to the grub boot
I ran into something similar installing Fedora 39 under KVM. To make it work I had to make sure the VM was configured for UEFI. I did not pursue trying to get to boot as BIOS.