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

[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 at colorremedies.com>
An: dmossor <dmossor at fedoraproject.org>; For testing and quality assurance of Fedora releases <test at lists.fedoraproject.org>
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 at gmail.com> 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 at lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/test/attachments/20150204/d39548b0/attachment-0001.html>