[Test-Announce] Fedora 22 Rawhide 20150203 nightly compose nominated for testing

[Adam Williamson]

Announcing the creation of a new nightly release validation test event
for Fedora 22 Rawhide 20150203. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
pykickstart - 20150124: 1.99.65-1, 20150203: 1.99.66-1
anaconda - 20150124: 22.16-1, 20150203: 22.17-1

Test coverage information for the current release can be seen at:
https://www.happyassassin.net/testcase_stats/22

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Su...

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_In...
https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Se...
https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_De...
https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Se...

Thank you for testing!
-- 
Mail generated by relval: https://www.happyassassin.net/wikitcms/
On behalf of: adamwill
_______________________________________________
test-announce mailing list
test-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[Adam Williamson]

On Tue, 2015-02-03 at 04:48 -0800, adamwill(a)fedoraproject.org wrote:
>  Announcing the creation of a new nightly release validation test 
>  event for Fedora 22 Rawhide 20150203. Please help run some tests for 
>  this nightly compose if you have time. For more information on 
>  nightly release validation testing, see:
>  https://fedoraproject.org/wiki/QA:Release_validation_test_plan
>  
>  Notable package version changes:
>  pykickstart - 20150124: 1.99.65-1, 20150203: 1.99.66-1
>  anaconda - 20150124: 22.16-1, 20150203: 22.17-1
>  
>  Test coverage information for the current release can be seen at: 
>  https://www.happyassassin.net/testcase_stats/22
>  
>  You can see all results, find testing instructions and image 
>  download locations, and enter results on the Summary page:
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Su...
>  
>  
>  The individual test result pages are:
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_In...
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Base
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Se...
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Cloud
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_De...
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Se...
>   
With my current lil' development project, I can tell you we have only 
LXDE, MATE, Xfce and SoaS lives for 2015-02-03, and where to get 'em:

https://kojipkgs.fedoraproject.org/work/tasks/5891/8805891/Fedora-Live-LX...
https://kojipkgs.fedoraproject.org/work/tasks/5889/8805889/Fedora-Live-LX...
https://kojipkgs.fedoraproject.org/work/tasks/5893/8805893/Fedora-Live-MA...
https://kojipkgs.fedoraproject.org/work/tasks/5895/8805895/Fedora-Live-MA...
https://kojipkgs.fedoraproject.org/work/tasks/5909/8805909/Fedora-Live-Xf...
https://kojipkgs.fedoraproject.org/work/tasks/5907/8805907/Fedora-Live-Xf...
https://kojipkgs.fedoraproject.org/work/tasks/5904/8805904/Fedora-Live-So...
https://kojipkgs.fedoraproject.org/work/tasks/5902/8805902/Fedora-Live-So...
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Joerg Lechner]

Hi,
silly question:
I would like to test now F22-Rawhide i.e. LXDE. My system ist a fast laptop with Win 8.1
and Fedora on an external disk. I don't want to test in a sandbox.
Is in this stage of development of F22-Rawhide danger that Fedora could damage the windows
installation? F22-Rawhide will be on a seperate spare external disk connected via USB to
the Windows laptop.
Kind Regards

 

 

 

-----Ursprüngliche Mitteilung----- 
Von: Adam Williamson <adamwill(a)fedoraproject.org&gt;
An: test <test(a)lists.fedoraproject.org&gt;
Verschickt: Di, 3 Feb 2015 9:09 pm
Betreff: Re: [Test-Announce] Fedora 22 Rawhide 20150203 nightly compose nominated for
testing


On Tue, 2015-02-03 at 04:48 -0800, adamwill(a)fedoraproject.org wrote:
>  Announcing the creation of a new nightly release validation test 
>  event for Fedora 22 Rawhide 20150203. Please help run some tests for 
>  this nightly compose if you have time. For more information on 
>  nightly release validation testing, see:
>  https://fedoraproject.org/wiki/QA:Release_validation_test_plan
>  
>  Notable package version changes:
>  pykickstart - 20150124: 1.99.65-1, 20150203: 1.99.66-1
>  anaconda - 20150124: 22.16-1, 20150203: 22.17-1
>  
>  Test coverage information for the current release can be seen at: 
>  https://www.happyassassin.net/testcase_stats/22
>  
>  You can see all results, find testing instructions and image 
>  download locations, and enter results on the Summary page:
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Su...
>  
>  
>  The individual test result pages are:
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_In...
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Base
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Se...
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Cloud
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_De...
>  
>  https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20150203_Se...
>   
With my current lil' development project, I can tell you we have only 
LXDE, MATE, Xfce and SoaS lives for 2015-02-03, and where to get 'em:

https://kojipkgs.fedoraproject.org/work/tasks/5891/8805891/Fedora-Live-LX...
https://kojipkgs.fedoraproject.org/work/tasks/5889/8805889/Fedora-Live-LX...
https://kojipkgs.fedoraproject.org/work/tasks/5893/8805893/Fedora-Live-MA...
https://kojipkgs.fedoraproject.org/work/tasks/5895/8805895/Fedora-Live-MA...
https://kojipkgs.fedoraproject.org/work/tasks/5909/8805909/Fedora-Live-Xf...
https://kojipkgs.fedoraproject.org/work/tasks/5907/8805907/Fedora-Live-Xf...
https://kojipkgs.fedoraproject.org/work/tasks/5904/8805904/Fedora-Live-So...
https://kojipkgs.fedoraproject.org/work/tasks/5902/8805902/Fedora-Live-So...
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

-- 
test mailing list
test(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[Adam Williamson]

On Tue, 2015-02-03 at 18:27 -0500, Joerg Lechner wrote:
>  Hi,
>  silly question:
>  I would like to test now F22-Rawhide i.e. LXDE. My system ist a fast 
>  laptop with Win 8.1 and Fedora on an external disk. I don't want to 
>  test in a sandbox.
>  Is in this stage of development of F22-Rawhide danger that Fedora 
>  could damage the windows installation? F22-Rawhide will be on a 
>  seperate spare external disk connected via USB to the Windows laptop.
>  Kind Regards 
Nothing's 100% guaranteed, but if you don't select the internal drive 
as a target disk during installation, it's very unlikely that 
installing F22 to the external drive will affect your existing Windows 
install in any way.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Dan Mossor]

On 02/03/2015 06:13 PM, Adam Williamson wrote:
>  On Tue, 2015-02-03 at 18:27 -0500, Joerg Lechner wrote:
> > Hi,
> > silly question:
> > I would like to test now F22-Rawhide i.e. LXDE. My system ist a fast
> > laptop with Win 8.1 and Fedora on an external disk. I don't want to
> > test in a sandbox.
> > Is in this stage of development of F22-Rawhide danger that Fedora
> > could damage the windows installation? F22-Rawhide will be on a
> > seperate spare external disk connected via USB to the Windows laptop.
> > Kind Regards
>
>  Nothing's 100% guaranteed, but if you don't select the internal drive
>  as a target disk during installation, it's very unlikely that
>  installing F22 to the external drive will affect your existing Windows
>  install in any way.
>  
However, Fedora has been known to modify UEFI boot settings in such a 
way that the system will not boot at all without that external drive 
attached. [1]


1- https://fedoraproject.org/wiki/User:Dmossor/uefi-recovery

-- 
Dan Mossor
Systems Engineer at Large
Fedora KDE WG | Fedora QA Team | Fedora Server SIG
Fedora Infrastructure Apprentice
FAS: dmossor IRC: danofsatx
San Antonio, Texas, USA

[Adam Williamson]

On Tue, 2015-02-03 at 18:54 -0600, Dan Mossor wrote:
>  On 02/03/2015 06:13 PM, Adam Williamson wrote:
>  > On Tue, 2015-02-03 at 18:27 -0500, Joerg Lechner wrote:
>  > > Hi,
>  > > silly question:
>  > > I would like to test now F22-Rawhide i.e. LXDE. My system ist a 
>  > > fast laptop with Win 8.1 and Fedora on an external disk. I don't 
>  > > want to test in a sandbox.
>  > > Is in this stage of development of F22-Rawhide danger that 
>  > > Fedora could damage the windows installation? F22-Rawhide will 
>  > > be on a seperate spare external disk connected via USB to the 
>  > > Windows laptop. Kind Regards
>  > 
>  > Nothing's 100% guaranteed, but if you don't select the internal 
>  > drive as a target disk during installation, it's very unlikely that
>  > installing F22 to the external drive will affect your existing 
>  > Windows install in any way.
>  > 
>  However, Fedora has been known to modify UEFI boot settings in such a
>  way that the system will not boot at all without that external drive 
>  attached. [1] 
So, that genre of problem is *there*, but I don't think it's quite as 
you describe it. I'm not sure you're entirely clear on what happened 
in your case.

When you do a UEFI install of Fedora, it deletes any existing UEFI 
boot manager entry named 'Fedora' and creates a new one, pointing to 
the bootloader of the Fedora install you just did. It then makes this 
entry the first one in the UEFI boot manager order.

It doesn't delete any *other* boot entries. Unless your firmware is 
really, really terrible, if the Fedora entry fails, it should fall 
back through the rest of the entries in the BootOrder - in your page, 
it looks like it should then try a UEFI-native boot from 'KingstonDT 
101 G2 PMAP', then BIOS compatibility boot from 'Hard Drive', then 
BIOS compatibility boot from 'CD/DVD Drive'. I don't *think* it's 
correct to say that "What this effectively does is cripple the 
system". The worst effect it can really have is to render previous 
Fedora installations unbootable in certain cases (when the new Fedora 
install's bootloader can't boot the old Fedora install).

Say you have Fedora 21 installed to an internal disk, then you decide 
to try installing Fedora 22 to an external disk; it'll delete the UEFI 
boot manager entry for the Fedora 21 install and create a new one for 
the Fedora 22 install. If you put the Fedora 22 install's EFI system 
partition on the external disk, the 'Fedora' UEFI boot manager entry 
is only going to work when that external disk is plugged in. So you'll 
only be able to boot the Fedora 22 install *or* the Fedora 21 install 
(the Fedora 22 bootloader should have entries for booting the Fedora 
21 install) when the external disk is connected.

A similar case might affect Joerg. I'm not entirely clear from his 
description, though. But say he has Windows 8.1 on the internal disk, 
Fedora 21 (including its ESP) on one external disk, and he wants to 
try installing Rawhide on a *second* external disk. The Fedora 22 
install will delete the UEFI boot manager 'Fedora' entry that points 
to the Fedora 21 external disk and create a new one pointing to the 
Fedora 22 external disk. If the F21 external disk is connected when he 
installs F22, the F22 bootloader may get menu entries to boot the F21 
install, but it'll only work with both disks connected. With only the 
F21 disk connected, he won't be able to boot either Fedora.

I can't see a case where he wouldn't be able to boot Windows, though, 
except for a completely broken firmware which refuses to fall back from 
a UEFI boot manager entry which fails to work. Windows' UEFI boot 
manager entry will not get deleted, and nothing will touch its ESP, 
which is presumably on the internal disk.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Joerg Lechner]

Hi Adam,
for me it's the case that I unplug the external F21 disk and try to install F22 from a
Flash Media to another external disk, instead the one which has installed F21. Sorry for
my English, it's not my native language. Regarding the UEFI entries, I have tried
different ones, which are offered if i connect an external i.e. F21 disk. There a name
"xyzDisk", "Fedora-yxz", and "Fedora", I gave them different
names, which are then displayed in the boot menue and could connect different F21 disks,
via whitelisting - but I don't know if this corresponds to Your discussion about
Fedora and UEFI.
Kind Regards

 

 

 

-----Ursprüngliche Mitteilung----- 
Von: Adam Williamson <adamwill(a)fedoraproject.org&gt;
An: dmossor <dmossor(a)fedoraproject.org>; For testing and quality assurance of Fedora
releases <test(a)lists.fedoraproject.org&gt;
Verschickt: Mi, 4 Feb 2015 1:19 pm
Betreff: Re: [Test-Announce] Fedora 22 Rawhide 20150203 nightly compose nominated for
testing


On Tue, 2015-02-03 at 18:54 -0600, Dan Mossor wrote:
>  On 02/03/2015 06:13 PM, Adam Williamson wrote:
>  > On Tue, 2015-02-03 at 18:27 -0500, Joerg Lechner wrote:
>  > > Hi,
>  > > silly question:
>  > > I would like to test now F22-Rawhide i.e. LXDE. My system ist a 
>  > > fast laptop with Win 8.1 and Fedora on an external disk. I don't 
>  > > want to test in a sandbox.
>  > > Is in this stage of development of F22-Rawhide danger that 
>  > > Fedora could damage the windows installation? F22-Rawhide will 
>  > > be on a seperate spare external disk connected via USB to the 
>  > > Windows laptop. Kind Regards
>  > 
>  > Nothing's 100% guaranteed, but if you don't select the internal 
>  > drive as a target disk during installation, it's very unlikely that
>  > installing F22 to the external drive will affect your existing 
>  > Windows install in any way.
>  > 
>  However, Fedora has been known to modify UEFI boot settings in such a
>  way that the system will not boot at all without that external drive 
>  attached. [1] 
So, that genre of problem is *there*, but I don't think it's quite as 
you describe it. I'm not sure you're entirely clear on what happened 
in your case.

When you do a UEFI install of Fedora, it deletes any existing UEFI 
boot manager entry named 'Fedora' and creates a new one, pointing to 
the bootloader of the Fedora install you just did. It then makes this 
entry the first one in the UEFI boot manager order.

It doesn't delete any *other* boot entries. Unless your firmware is 
really, really terrible, if the Fedora entry fails, it should fall 
back through the rest of the entries in the BootOrder - in your page, 
it looks like it should then try a UEFI-native boot from 'KingstonDT 
101 G2 PMAP', then BIOS compatibility boot from 'Hard Drive', then 
BIOS compatibility boot from 'CD/DVD Drive'. I don't *think* it's 
correct to say that "What this effectively does is cripple the 
system". The worst effect it can really have is to render previous 
Fedora installations unbootable in certain cases (when the new Fedora 
install's bootloader can't boot the old Fedora install).

Say you have Fedora 21 installed to an internal disk, then you decide 
to try installing Fedora 22 to an external disk; it'll delete the UEFI 
boot manager entry for the Fedora 21 install and create a new one for 
the Fedora 22 install. If you put the Fedora 22 install's EFI system 
partition on the external disk, the 'Fedora' UEFI boot manager entry 
is only going to work when that external disk is plugged in. So you'll 
only be able to boot the Fedora 22 install *or* the Fedora 21 install 
(the Fedora 22 bootloader should have entries for booting the Fedora 
21 install) when the external disk is connected.

A similar case might affect Joerg. I'm not entirely clear from his 
description, though. But say he has Windows 8.1 on the internal disk, 
Fedora 21 (including its ESP) on one external disk, and he wants to 
try installing Rawhide on a *second* external disk. The Fedora 22 
install will delete the UEFI boot manager 'Fedora' entry that points 
to the Fedora 21 external disk and create a new one pointing to the 
Fedora 22 external disk. If the F21 external disk is connected when he 
installs F22, the F22 bootloader may get menu entries to boot the F21 
install, but it'll only work with both disks connected. With only the 
F21 disk connected, he won't be able to boot either Fedora.

I can't see a case where he wouldn't be able to boot Windows, though, 
except for a completely broken firmware which refuses to fall back from 
a UEFI boot manager entry which fails to work. Windows' UEFI boot 
manager entry will not get deleted, and nothing will touch its ESP, 
which is presumably on the internal disk.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

-- 
test mailing list
test(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

[Adam Williamson]

On Tue, 2015-02-03 at 18:54 -0600, Dan Mossor wrote:

>  1- https://fedoraproject.org/wiki/User:Dmossor/uefi-recovery 
Oh, on this point:

"It is possible to rename your boot entry to something other than 
"Fedora", but efibootmgr appears to be incapable of this - or at least 
my knowledge of it is."

AIUI renaming UEFI boot manager entries isn't exactly _possible_ so 
far as the actual design of the UEFI variable store is concerned, 
though a tool like efibootmgr could choose to hide the details if it 
wanted to and offer a 'rename' operation, I guess. To 'rename' one you 
actually just delete it and re-create it with a different name (or, if 
you want to be safer, create a dupe with a different name *then* 
delete the original...). You can use 'efibootmgr -v' to see all the 
values for an entry, then delete it and create it again with the same 
values but a different name.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Chris Murphy]

On Tue, Feb 3, 2015 at 5:54 PM, Dan Mossor <danofsatx(a)gmail.com&gt; wrote:
>  On 02/03/2015 06:13 PM, Adam Williamson wrote:
> >
> > On Tue, 2015-02-03 at 18:27 -0500, Joerg Lechner wrote:
> >>
> >> Hi,
> >> silly question:
> >> I would like to test now F22-Rawhide i.e. LXDE. My system ist a fast
> >> laptop with Win 8.1 and Fedora on an external disk. I don't want to
> >> test in a sandbox.
> >> Is in this stage of development of F22-Rawhide danger that Fedora
> >> could damage the windows installation? F22-Rawhide will be on a
> >> seperate spare external disk connected via USB to the Windows laptop.
> >> Kind Regards
> >
> >
> > Nothing's 100% guaranteed, but if you don't select the internal drive
> > as a target disk during installation, it's very unlikely that
> > installing F22 to the external drive will affect your existing Windows
> > install in any way.
> >
>  However, Fedora has been known to modify UEFI boot settings in such a way
>  that the system will not boot at all without that external drive attached.
>  [1]
>
>
>  1- https://fedoraproject.org/wiki/User:Dmossor/uefi-recovery 
Oops. This is a problem. What you describe could be a firmware bug.
Thing is, the BootOrder is reported identically before and after
anaconda ran efibootmgr. Possibly something is getting corrupted
behind the scenes.

There's a problem with the advice to run grub2-install, however. This
obliterates the signed grubx64.efi that's installed by the grub2-efi
package. The grubx64.efi binary that pops out of grub2-install isn't
signed, so it can't boot a UEFI Secure Boot system until, at minimum,
a hash for it is registered via mokmanager. There's no reason to do
this unless you're e.g. experimenting with upstream GRUB and secure
boot, or you just don't want to have to disable secure boot in between
booting Fedora and Windows 8.

gru2-install also writes an entry in NVRAM, and this additional write
might be kicking the firmware in the pants and getting it to
cooperate. Anyway, this kinda needs more testing and refinement. In
the meantime I suggest modifying the advice so that people are aware
that as written, Fedora will not boot with secure boot enabled. If
grub2-efi package is reinstalled again, however, this would restore
the Fedora signed grubx64.efi.

-- 
Chris Murphy

[Joerg Lechner]

Hi,
in my case I have to whitelist to be able to boot Fedora 21. The Acer ( I run an Acer
Aspire E15 E5-571G Laptop) support says there is no other way to have UEFI and Linux
booting on this laptop together in my case (external disk is an old PATA spare disk, this
can be the reason). My install for F22 will be via Fedora USB Creator -> USB
"Stick" -> external disk.
I would like to start F22 tests on this laptop, as early as the risk of a damage of
Windows 8.1 by F22 (internal disk of the laptop) is minimal.
Kind Regards

 

 

 

-----Ursprüngliche Mitteilung----- 
Von: Chris Murphy <lists(a)colorremedies.com&gt;
An: dmossor <dmossor(a)fedoraproject.org>; For testing and quality assurance of Fedora
releases <test(a)lists.fedoraproject.org&gt;
Verschickt: Mi, 4 Feb 2015 7:39 am
Betreff: Re: [Test-Announce] Fedora 22 Rawhide 20150203 nightly compose nominated for
testing


On Tue, Feb 3, 2015 at 5:54 PM, Dan Mossor <danofsatx(a)gmail.com&gt; wrote:
>  On 02/03/2015 06:13 PM, Adam Williamson wrote:
> >
> > On Tue, 2015-02-03 at 18:27 -0500, Joerg Lechner wrote:
> >>
> >> Hi,
> >> silly question:
> >> I would like to test now F22-Rawhide i.e. LXDE. My system ist a fast
> >> laptop with Win 8.1 and Fedora on an external disk. I don't want to
> >> test in a sandbox.
> >> Is in this stage of development of F22-Rawhide danger that Fedora
> >> could damage the windows installation? F22-Rawhide will be on a
> >> seperate spare external disk connected via USB to the Windows laptop.
> >> Kind Regards
> >
> >
> > Nothing's 100% guaranteed, but if you don't select the internal drive
> > as a target disk during installation, it's very unlikely that
> > installing F22 to the external drive will affect your existing Windows
> > install in any way.
> >
>  However, Fedora has been known to modify UEFI boot settings in such a way
>  that the system will not boot at all without that external drive attached.
>  [1]
>
>
>  1- https://fedoraproject.org/wiki/User:Dmossor/uefi-recovery 
Oops. This is a problem. What you describe could be a firmware bug.
Thing is, the BootOrder is reported identically before and after
anaconda ran efibootmgr. Possibly something is getting corrupted
behind the scenes.

There's a problem with the advice to run grub2-install, however. This
obliterates the signed grubx64.efi that's installed by the grub2-efi
package. The grubx64.efi binary that pops out of grub2-install isn't
signed, so it can't boot a UEFI Secure Boot system until, at minimum,
a hash for it is registered via mokmanager. There's no reason to do
this unless you're e.g. experimenting with upstream GRUB and secure
boot, or you just don't want to have to disable secure boot in between
booting Fedora and Windows 8.

gru2-install also writes an entry in NVRAM, and this additional write
might be kicking the firmware in the pants and getting it to
cooperate. Anyway, this kinda needs more testing and refinement. In
the meantime I suggest modifying the advice so that people are aware
that as written, Fedora will not boot with secure boot enabled. If
grub2-efi package is reinstalled again, however, this would restore
the Fedora signed grubx64.efi.

-- 
Chris Murphy
-- 
test mailing list
test(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test