[opensuse] Grub2 --> Grub2-EFI ???
![](https://seccdn.libravatar.org/avatar/7cd8f94c4852691e6be83aff3a1a5322.jpg?s=120&d=mm&r=g)
Hello list, I installed opensuse 13.2 64bit on a UEFI machine (HP Compaq 6200 Pro SFF PC). Installation went fine but I obviously missed something, because now I can boot only if I choose F9 menu (boot order) and then go for "legacy boot options" (boot from SATA0). If I try to boot automaticaly it hangs at grub rescue prompt, after reporting an error about unknown filesystem. There is no option to permanently change the boot priority from efi to legacy in BIOS (EFI) setup on this machine. So I'm stuck to make manual choice of legacy boot on every (re)boot -- F9 menu etc. Not nice. My previous installation (opensuse 12.3) on this computer worked without any problems. Actualy it was so smooth that I even did not notice the fact that comp had UEFI instead of BIOS. Now I am considering to try boot loader module in Yast2. I see there is an option to install "Grub2-EFI" (Now it's "Grub2" in there). Would you recommend me to do so? Is it safe? If not what could be the best option? Best regards, Radule
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 10/12/2014 12:05, Radule Soskic a écrit :
If I try to boot automaticaly it hangs at grub rescue prompt, after reporting an error about unknown filesystem.
I think I had this very same error on, hp machine recently and solved it with the help of a friend, but I don't remember how. I will ask him jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/efef591f3cf498b944051e2c2ffc3056.jpg?s=120&d=mm&r=g)
On Wed, 10 Dec 2014 11:05:38 +0000
Radule Soskic
Now I am considering to try boot loader module in Yast2. I see there is an option to install "Grub2-EFI" (Now it's "Grub2" in there).
Would you recommend me to do so? Is it safe?
Yes, I recommend doing that. But it won't work. To do that, you will need your EFI system partition mounted as "/boot/efi". And you should add a line to "/etc/fstab" to make that permanent. When you switch to grub2-efi, it should mostly work. But you will get an error message. The problem is that information has to be written to NVRAM. And the attempt to do that will fail unless you booted in EFI mode. If your firmware gives you an efi shell, you might be able to do a final fixup from there. Otherwise, you can boot the install media to EFI mode, and then use the "efibootmgr" command to add the needed NVRAM entry. The man pages for "efibootmgr" are reasonably good, and a web search will give examples of what you need. You might also find reports of problems with UEFI booting of linux on HP systems. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/7cd8f94c4852691e6be83aff3a1a5322.jpg?s=120&d=mm&r=g)
On 12/10/2014 05:50 PM, Neil Rickert wrote:
On Wed, 10 Dec 2014 11:05:38 +0000 Radule Soskic
wrote: Now I am considering to try boot loader module in Yast2. I see there is an option to install "Grub2-EFI" (Now it's "Grub2" in there).
Would you recommend me to do so? Is it safe?
Yes, I recommend doing that. But it won't work.
To do that, you will need your EFI system partition mounted as "/boot/efi". And you should add a line to "/etc/fstab" to make that permanent.
When you switch to grub2-efi, it should mostly work. But you will get an error message. The problem is that information has to be written to NVRAM. And the attempt to do that will fail unless you booted in EFI mode.
If your firmware gives you an efi shell, you might be able to do a final fixup from there. Otherwise, you can boot the install media to EFI mode, and then use the "efibootmgr" command to add the needed NVRAM entry. The man pages for "efibootmgr" are reasonably good, and a web search will give examples of what you need.
You might also find reports of problems with UEFI booting of linux on HP systems.
I followed your recommendation, thank you. You were right - it didn't work. Installation went OK and now I have gru2-EFI installed, but machine still boots in legacy mode. Regarding NVRAM write, I booted from installation DVD in efi mode and tried efibootmgr. The problem is that boot menu entries shown by efibootmgr are not the same as the list of efi boot options that are shown in F9 boot menu. The diferrence between the two is quite strange -- while F9 menu conatins more than 60hex entries (!?), all named "opensuse", the efibootmgr shows just a few of such entries (can't remember exactly, but no more than 5-6). These two lists clearly are read from diferrent sources. Further, changes that I make through efibootmgr apparently have no effect on F9 menu behavior. Now I ask again - what are my options?. I would like to get 13.2 function in the same way as old 12.3 did. Any suggestions? TIA and best regards, Radule
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 12/12/2014 12:45, Radule Soskic a écrit :
Now I ask again - what are my options?. I would like to get 13.2 function in the same way as old 12.3 did. Any suggestions?
do you really need uefi boot? why not keep legacy? did you try to rename the EFI entries as I proposed? jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/7cd8f94c4852691e6be83aff3a1a5322.jpg?s=120&d=mm&r=g)
On 12/12/2014 12:49 PM, jdd wrote:
Le 12/12/2014 12:45, Radule Soskic a écrit :
Now I ask again - what are my options?. I would like to get 13.2 function in the same way as old 12.3 did. Any suggestions?
do you really need uefi boot? why not keep legacy?
did you try to rename the EFI entries as I proposed?
jdd
I think your suggestion would fit fine in case I wanted to install grub2 and boot in legacy mode. But my case was diferrent - I already had grub2 legacy, but my computer booted only after I intervene manualy during boot (pressing F9 - boot menu and choosing legacy boot device sata0). In unattended, it goes uefi mode and hangs with an error. My primary problem was that booting wasn't possible unattended. So, it's not that I needed uefi boot -- but, knowing that this problem didn't exist in opensuse 12.3 (when my comp booted in uefi mode and everything was fine), I thought it would be ok if I install grub2-efi and revert to uefi mode. So I followed Neil's suggestion and tried to enable uefi boot mode. In the process I learned that there is something very weird with my uefi boot option list (see my previous post). I am still waiting for new ideas, if any. Best regards, Radule
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 15/12/2014 11:03, Radule Soskic a écrit :
On 12/12/2014 12:49 PM, jdd wrote:
Le 12/12/2014 12:45, Radule Soskic a écrit :
Now I ask again - what are my options?. I would like to get 13.2 function in the same way as old 12.3 did. Any suggestions?
do you really need uefi boot? why not keep legacy?
did you try to rename the EFI entries as I proposed?
jdd
I think your suggestion would fit fine in case I wanted to install grub2 and boot in legacy mode.
But my case was diferrent - I already had grub2 legacy, but my computer booted only after I intervene manualy during boot (pressing F9 - boot menu and choosing legacy boot device sata0). In unattended, it goes uefi mode and hangs with an error.
My primary problem was that booting wasn't possible unattended.
this is why I proposed to change the names in EFI folder, this prevent boot in EFI mode... and so should prevent the error
So, it's not that I needed uefi boot -- but, knowing that this problem didn't exist in opensuse 12.3 (when my comp booted in uefi mode and everything was fine), I thought it would be ok if I install grub2-efi and revert to uefi mode.
So I followed Neil's suggestion and tried to enable uefi boot mode. In the process I learned that there is something very weird with my uefi boot option list (see my previous post).
I am still waiting for new ideas, if any.
Best regards,
Radule
N�����r��y隊Z)z{.�ﮞ˛���m�)z{.��+�:�{Zr�az�'z��j)h���Ǿ� ޮ�^�ˬz�
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/7cd8f94c4852691e6be83aff3a1a5322.jpg?s=120&d=mm&r=g)
On 12/15/2014 11:37 AM, jdd wrote:
this is why I proposed to change the names in EFI folder, this prevent boot in EFI mode... and so should prevent the error
I found another solution to my primary problem -- resetting bios options to defaults happened to help. Now, the legacy options are included in the boot order, so when uefi fails system skips to legacy automatically. My concern now is to understand what's wrong with my uefi. As I've mentioned, my boot options list has more than 80 entries named "opensuse". The list seems to get larger with every reboot. And efibootmgr doesn't see them, so I can't delete any. My EFI folder has only one entry named "opensuse". I'll experiment with your idea of renaming it. I'll see how it effects my boot menu entries and/or boot behavior. Radule
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 15/12/2014 12:09, Radule Soskic a écrit :
My EFI folder has only one entry named "opensuse". I'll experiment with
be warned that I mean the EFI folder in the boot fat partition (sdx1 or sdx2 usually, easy to know: FAT and small I'm not sure how/if it's mounted, specially on non EFI boot (that is if you boot legacy) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/7cd8f94c4852691e6be83aff3a1a5322.jpg?s=120&d=mm&r=g)
On 12/15/2014 01:10 PM, jdd wrote:
Le 15/12/2014 12:09, Radule Soskic a écrit :
My EFI folder has only one entry named "opensuse". I'll experiment with
be warned that I mean the EFI folder in the boot fat partition (sdx1 or sdx2 usually, easy to know: FAT and small
I'm not sure how/if it's mounted, specially on non EFI boot (that is if you boot legacy)
jdd
Yes, I know that, thank you. Since I went through grub2-efi install I made efi partition permanently mounted in the proper place, so that part is not a problem. I'll play with this later this evening. RaduleN�����r��y隊Z)z{.�ﮞ˛���m�)z{.��+�:�{Zr�az�'z��j)h���Ǿ� ޮ�^�ˬz��
![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 10/12/2014 12:05, Radule Soskic a écrit :
If not what could be the best option?
my friend rembered me what I did last meeting. On this machine windows was installed and insisted to boot alone, but a mint was installed but not usable what we did: boot any system (rescue if no other), find the EFI partition (usually one of the first, small fat32 one). in it you have a tree EFI -Microsoft -opensuse -whatever rename these sub folder to any tother name (easy to remember), for example Microsoft-ori to prevent the other systems to find then after that the computer sould boot legacy bios emulation and you should be able to install openSUSE with grub2 (non uefi) if it don't work, it's easy to revert jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
jdd
-
Neil Rickert
-
Radule Soskic