Dear Folks,
I installed Fedora 19 on my son's laptop, and it worked beautifully with the already installed Windows 8. Then foolishly, I upgraded the Windows 8 to Windows 8.1. Now it boots straight to Windows 8.1 and grub does not appear.
I disabled secure boot in the firmware.
I do not even know which version of grub was booting the UEFI system before; it just worked.
Now I need to know.
Can anyone suggest:
1. What grub would the Fedora 19 installer have provided to boot it and Windows 8? (grub2, grub-efi,...) 2. Can anyone point to any documentation on how to fix this?
I am a little nervous on this, as I once attempted to upgrade an F18 UEFI stand alone system from grub-efi to grub2 with the result that I could not boot the machine, and wound up re-installing Fedora.
I have a live disk, can boot the machine with that, and have some experience with grub and non-EFI systems.
Dear Folks,
On 20/11/13 09:53 +1100, Nick Urbanik wrote:
Dear Folks,
I installed Fedora 19 on my son's laptop, and it worked beautifully with the already installed Windows 8. Then foolishly, I upgraded the Windows 8 to Windows 8.1. Now it boots straight to Windows 8.1 and grub does not appear.
I disabled secure boot in the firmware.
I do not even know which version of grub was booting the UEFI system before; it just worked.
Now I need to know.
Can anyone suggest:
- What grub would the Fedora 19 installer have provided to boot it
and Windows 8? (grub2, grub-efi,...) 2. Can anyone point to any documentation on how to fix this?
I am a little nervous on this, as I once attempted to upgrade an F18 UEFI stand alone system from grub-efi to grub2 with the result that I could not boot the machine, and wound up re-installing Fedora.
I have a live disk, can boot the machine with that, and have some experience with grub and non-EFI systems.
After much poking around, and seeing http://askubuntu.com/questions/240496/how-to-show-grub-after-install-ubuntu-... and reading documentation, I did this from a Fedora 19 Live CD; gdisk to see the partition layout, then efibootmgr to fix it:
[liveuser@localhost ~]$ sudo gdisk /dev/sda ... Command (? for help): p Disk /dev/sda: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 8EB52CEC-C6A8-4A63-8AB3-3675A2AB07DE Partition table holds up to 128 entries First usable sector is 34, last usable sector is 976773134 Partitions will be aligned on 2048-sector boundaries Total free space is 2029 sectors (1014.5 KiB)
Number Start (sector) End (sector) Size Code Name 1 2048 821247 400.0 MiB 2700 Basic data partition 2 821248 1435647 300.0 MiB EF00 EFI system partition 3 1435648 1697791 128.0 MiB 0C01 Microsoft reserved part 4 1697792 223358975 105.7 GiB 0700 Basic data partition 5 223358976 224075775 350.0 MiB 2700 6 224075776 937428991 340.2 GiB 8E00 7 937428992 976773119 18.8 GiB 2700 Basic data partition
Command (? for help): q ... [liveuser@localhost ~]$ mount |grep -i efi efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) [liveuser@localhost ~]$ sudo efibootmgr -c -p 2 -d /dev/sda -l "\EFI\fedora\grubx64.efi" -L "Fedora" ** Warning ** : Boot0002 has same label Fedora BootCurrent: 0000 Timeout: 2 seconds BootOrder: 0003,0000,0001,0002 Boot0000* ATAPI CDROM: HL-DT-ST DVDRAM GT51N Boot0001* Windows Boot Manager Boot0002* Fedora Boot0003* Fedora [liveuser@localhost ~]$
Now grub works, and both Fedora and Windows 8.1 boot.
Quoting Nick Urbanik nick.urbanik@optusnet.com.au:
Dear Folks,
On 20/11/13 09:53 +1100, Nick Urbanik wrote:
Dear Folks,
I installed Fedora 19 on my son's laptop, and it worked beautifully with the already installed Windows 8. Then foolishly, I upgraded the Windows 8 to Windows 8.1. Now it boots straight to Windows 8.1 and grub does not appear.
I disabled secure boot in the firmware.
I do not even know which version of grub was booting the UEFI system before; it just worked.
Now I need to know.
Can anyone suggest:
- What grub would the Fedora 19 installer have provided to boot it
and Windows 8? (grub2, grub-efi,...) 2. Can anyone point to any documentation on how to fix this?
I am a little nervous on this, as I once attempted to upgrade an F18 UEFI stand alone system from grub-efi to grub2 with the result that I could not boot the machine, and wound up re-installing Fedora.
I have a live disk, can boot the machine with that, and have some experience with grub and non-EFI systems.
After much poking around, and seeing http://askubuntu.com/questions/240496/how-to-show-grub-after-install-ubuntu-... and reading documentation, I did this from a Fedora 19 Live CD; gdisk to see the partition layout, then efibootmgr to fix it:
[liveuser@localhost ~]$ sudo gdisk /dev/sda ... Command (? for help): p Disk /dev/sda: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 8EB52CEC-C6A8-4A63-8AB3-3675A2AB07DE Partition table holds up to 128 entries First usable sector is 34, last usable sector is 976773134 Partitions will be aligned on 2048-sector boundaries Total free space is 2029 sectors (1014.5 KiB)
Number Start (sector) End (sector) Size Code Name 1 2048 821247 400.0 MiB 2700 Basic data partition 2 821248 1435647 300.0 MiB EF00 EFI system partition 3 1435648 1697791 128.0 MiB 0C01 Microsoft reserved part 4 1697792 223358975 105.7 GiB 0700 Basic data partition 5 223358976 224075775 350.0 MiB 2700 6 224075776 937428991 340.2 GiB 8E00 7 937428992 976773119 18.8 GiB 2700 Basic data partition
Command (? for help): q ... [liveuser@localhost ~]$ mount |grep -i efi efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) [liveuser@localhost ~]$ sudo efibootmgr -c -p 2 -d /dev/sda -l "\EFI\fedora\grubx64.efi" -L "Fedora" ** Warning ** : Boot0002 has same label Fedora BootCurrent: 0000 Timeout: 2 seconds BootOrder: 0003,0000,0001,0002 Boot0000* ATAPI CDROM: HL-DT-ST DVDRAM GT51N Boot0001* Windows Boot Manager Boot0002* Fedora Boot0003* Fedora [liveuser@localhost ~]$ Now grub works, and both Fedora and Windows 8.1 boot. -- Nick Urbanik http://nicku.org 808-71011 nick.urbanik@optusnet.com.au GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24 I disclaim, therefore I am.
And THAT, my friends, is why you have separate Windows and Linux machines. ;) (half-joking. I have three Windows machines, one a Win7, one a WinXP (going away) and a second refurbed Win7 machine as well as a home-brew Linux box.)
On Wed, Nov 20, 2013 at 12:53 AM, Nick Urbanik nick.urbanik@optusnet.com.au wrote:
Dear Folks,
I installed Fedora 19 on my son's laptop, and it worked beautifully with the already installed Windows 8. Then foolishly, I upgraded the Windows 8 to Windows 8.1. Now it boots straight to Windows 8.1 and grub does not appear.
I disabled secure boot in the firmware.
I do not even know which version of grub was booting the UEFI system before; it just worked.
Now I need to know.
Can anyone suggest:
- What grub would the Fedora 19 installer have provided to boot it and Windows 8? (grub2, grub-efi,...)
- Can anyone point to any documentation on how to fix this?
I am a little nervous on this, as I once attempted to upgrade an F18 UEFI stand alone system from grub-efi to grub2 with the result that I could not boot the machine, and wound up re-installing Fedora.
I have a live disk, can boot the machine with that, and have some experience with grub and non-EFI systems. --
Hi,
In a number of laptops @work that have Fedora + *gasp* Windows 8.1, we actually found out that grub was not damaged, instead, we simply had to point the BIOS to a different partition.
- Gilboa
On Tue, Nov 19, 2013 at 10:53 PM, Nick Urbanik nick.urbanik@optusnet.com.au wrote:
I installed Fedora 19 on my son's laptop, and it worked beautifully with the already installed Windows 8. Then foolishly, I upgraded the Windows 8 to Windows 8.1. Now it boots straight to Windows 8.1 and grub does not appear.
I disabled secure boot in the firmware.
I do not even know which version of grub was booting the UEFI system before; it just worked.
Now I need to know.
Can anyone suggest:
- What grub would the Fedora 19 installer have provided to boot it and Windows 8? (grub2, grub-efi,...)
- Can anyone point to any documentation on how to fix this?
I am a little nervous on this, as I once attempted to upgrade an F18 UEFI stand alone system from grub-efi to grub2 with the result that I could not boot the machine, and wound up re-installing Fedora.
Windows has changed the EFI boot order.
You can boot to EFI's boot manager (the key to use depends on your hardware) and choose to boot from Fedora.
Once in Fedora, you can use efibootmgr to change the boot order.
On Wed, Nov 20, 2013 at 4:11 AM, Tom H tomh0665@gmail.com wrote:
Once in Fedora, you can use efibootmgr to change the boot order.
Not all systems allow you to do this. My HP Pavilion g6 laptop will not allow you to flip Windows and Linux in the boot order. You can do it in efibootmgr, but nothing happens.
On Nov 22, 2013, at 1:40 PM, Steven Rosenberg stevenhrosenberg@gmail.com wrote:
On Wed, Nov 20, 2013 at 4:11 AM, Tom H tomh0665@gmail.com wrote: Once in Fedora, you can use efibootmgr to change the boot order.
Not all systems allow you to do this. My HP Pavilion g6 laptop will not allow you to flip Windows and Linux in the boot order. You can do it in efibootmgr, but nothing happens.
So if you use efibootmgr -v before and after the change in order with efibootmgr, does BootOrder show the change in the 2nd efibootmgr -v instance?
UEFI spec 2.4.0, page 66, paragraph 3 in particular addresses this; but the whole 3.1.1 section is less than clear to me how BootOrder is supposed to be modifiable. I have one instance of firmware that doesn't like BootOrder modified, it appears to only add options, it won't remove them. And I'm not sure if this is a firmware bug, or a lack of clarity in the spec how this is supposed to work.
Chris Murphy
On Nov 22, 2013, at 2:50 PM, Chris Murphy lists@colorremedies.com wrote:
So if you use efibootmgr -v before and after the change in order with efibootmgr, does BootOrder show the change in the 2nd efibootmgr -v instance?
That's sorta confusing. What I'm wondering is if the BootOrder change is actually getting into NVRAM and then ignored by the firmware, or if the firmware is disallowing the change in BootOrder by efibootmgr.
Chris Murphy
On Fri, Nov 22, 2013 at 1:50 PM, Chris Murphy lists@colorremedies.com wrote:
On Nov 22, 2013, at 1:40 PM, Steven Rosenberg stevenhrosenberg@gmail.com wrote:
On Wed, Nov 20, 2013 at 4:11 AM, Tom H tomh0665@gmail.com wrote:
Once in Fedora, you can use efibootmgr to change the boot order.
Not all systems allow you to do this. My HP Pavilion g6 laptop will not allow you to flip Windows and Linux in the boot order. You can do it in efibootmgr, but nothing happens.
So if you use efibootmgr -v before and after the change in order with efibootmgr, does BootOrder show the change in the 2nd efibootmgr -v instance?
The boot order changes. But once I reboot, it goes back to what it was before.
On Nov 22, 2013, at 3:21 PM, Steven Rosenberg stevenhrosenberg@gmail.com wrote:
On Fri, Nov 22, 2013 at 1:50 PM, Chris Murphy lists@colorremedies.com wrote:
On Nov 22, 2013, at 1:40 PM, Steven Rosenberg stevenhrosenberg@gmail.com wrote:
On Wed, Nov 20, 2013 at 4:11 AM, Tom H tomh0665@gmail.com wrote:
Once in Fedora, you can use efibootmgr to change the boot order.
Not all systems allow you to do this. My HP Pavilion g6 laptop will not allow you to flip Windows and Linux in the boot order. You can do it in efibootmgr, but nothing happens.
So if you use efibootmgr -v before and after the change in order with efibootmgr, does BootOrder show the change in the 2nd efibootmgr -v instance?
The boot order changes. But once I reboot, it goes back to what it was before.
So the boot order changes in NVRAM, according to efibootmgr -v, but when you reboot and then run efibootmgr -v again, it's changed the order?
Wow, that's goofy. How does it even know what the order was and that it's changed? The spec language seems to imply that BootOrder isn't what gets changed, but rather than boot entry, which just seems wrong. I must be reading the spec incorrectly, but then I read it again….
"To change boot option on an existing Boot####, only the Boot#### variable would need to be rewritten. A similar operation would be done to add, remove, or modify the driver load list."
Chris Murphy
On Fri, Nov 22, 2013 at 5:40 PM, Steven Rosenberg < stevenhrosenberg@gmail.com> wrote:
My HP Pavilion g6 laptop will not allow you to flip Windows and Linux in the boot order. You can do it in efibootmgr, but nothing happens.
Sounds like a good reason to contact HP and tell them to fix this, open an incident#. Maybe they need to fix their UEFI...
FC
On Nov 23, 2013, at 12:49 AM, Fernando Cassia fcassia@gmail.com wrote:
Sounds like a good reason to contact HP and tell them to fix this, open an incident#. Maybe they need to fix their UEFI…
Fix it how? What exactly in the spec is being violated by the current behavior? Before asking them to do something, there should be some clarity in what the problem and solution is. A lot of lee way is given in the spec to the built-in boot manager, which BTW is a huge chunk of what GRUB is rather than as a boot loader.
Chris Murphy
-
Chris Murphy -
Fernando Cassia -
Gilboa Davara -
John Aldrich -
Nick Urbanik -
Steven Rosenberg -
Tom H