Re: Beta TC4 karma requests
On Sun, 2013-05-12 at 16:24 -0600, Chris Murphy wrote: > > On May 12, 2013, at 4:18 PM, "T.C. Hollingsworth" > wrote: > > > > Found Windows Boot Manager on Microsoft/Boot/bootmgfw.efi > > Windows Boot Manager is not yet supported by grub-mkconfig. > > done > > > > Is this supposed to work with grub2-mkconfig also, or only from anaconda? > > It's sorta messy to use GRUB2-EFI as a boot manager. Ideally the > firmware manufacturer would supply a decent GUI boot manager so you > can choose the OS, rather than rely on GRUB acting as a boot manager. That is not really happening in practice, though. TC4 was definitely intended to add Windows to the grub2 bootloader. See https://admin.fedoraproject.org/updates/F19/FEDORA-2013-7487 , https://bugzilla.redhat.com/show_bug.cgi?id=873207 . > The better alternative right now on UEFI computers, is rEFInd or > gummiboot as the substitute boot manager, which then points to the > native boot manager for Windows and Linux (on Linux that's EFI STUB > which is built into the kernel). This totally obviates GRUB2, and I > understand that I'm not actually answering your question. ...and it's much more manual effort to set up, as things stand. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Beta TC4 karma requests
On May 12, 2013, at 5:19 PM, Chris Murphy wrote: > There's a debug line you can add to the grub.cfg, and possibly you'll get > more information after the error but before the hang. Helps to read the whole bug first. I see the debug info. I can't reproduce this on Apple EFI hardware. T.C. Hollingsworth wrote: > Is this supposed to work with grub2-mkconfig also, or only from anaconda? anaconda calls grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg on UEFI, and it calls grub2-mkconfig -o /boot/grub2/grub.cfg on BIOS. I don't know why it goes on the ESP on UEFI systems. If grub2-install is invoked, replacing the Fedora supplied (and signed) grubx64.efi file, it expects to find grub.cfg at /boot/grub2 not on the ESP. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Beta TC4 karma requests
On May 12, 2013, at 4:40 PM, T.C. Hollingsworth wrote: > > I already use gummiboot, since GRUB2 can't boot Fedora on my system. > [1] My main reason for trying this out was to see if GRUB2 could boot > Windows, as that might be an interesting datapoint to add to that bug. Not really, it's totally unrelated as the Windows portion is apparently a limitation of the grub-mkconfig script, so I'd say it needs to be posted to one of the grub lists, either help or devel. Probably help. Maybe support is in upstream but not in the Fedora package. Is this Windows 8? > > -T.C. > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=951761 I think that bug and screen shot need to go upstream for sure. I'd file it in the savannha.gnu.org bug reporter, and then cite the bug in help or devel grub lists. What's weird about this is that you're getting a boot failure after successful installation, which necessarily uses GRUB2 to boot UEFI hardware, and it's the same GRUB2 used to boot the installation. There's a debug line you can add to the grub.cfg, and possibly you'll get more information after the error but before the hang. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Beta TC4 karma requests
On Sun, May 12, 2013 at 3:24 PM, Chris Murphy wrote: > It's sorta messy to use GRUB2-EFI as a boot manager. Ideally the firmware > manufacturer would supply a decent GUI boot manager so you can choose the OS, > rather than rely on GRUB acting as a boot manager. > > The better alternative right now on UEFI computers, is rEFInd or gummiboot as > the substitute boot manager, which then points to the native boot manager for > Windows and Linux (on Linux that's EFI STUB which is built into the kernel). > This totally obviates GRUB2, and I understand that I'm not actually answering > your question. I already use gummiboot, since GRUB2 can't boot Fedora on my system. [1] My main reason for trying this out was to see if GRUB2 could boot Windows, as that might be an interesting datapoint to add to that bug. -T.C. [1] https://bugzilla.redhat.com/show_bug.cgi?id=951761 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Beta TC4 karma requests
On May 12, 2013, at 4:18 PM, "T.C. Hollingsworth" wrote: > > Found Windows Boot Manager on Microsoft/Boot/bootmgfw.efi > Windows Boot Manager is not yet supported by grub-mkconfig. > done > > Is this supposed to work with grub2-mkconfig also, or only from anaconda? It's sorta messy to use GRUB2-EFI as a boot manager. Ideally the firmware manufacturer would supply a decent GUI boot manager so you can choose the OS, rather than rely on GRUB acting as a boot manager. The better alternative right now on UEFI computers, is rEFInd or gummiboot as the substitute boot manager, which then points to the native boot manager for Windows and Linux (on Linux that's EFI STUB which is built into the kernel). This totally obviates GRUB2, and I understand that I'm not actually answering your question. Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Beta TC4 karma requests
On Fri, May 10, 2013 at 4:14 PM, Adam Williamson wrote: > If anyone has a UEFI install of Windows and can test installing F19 Beta > TC4 alongside it, please do - the os-prober update should mean that the > Windows install will now be present in Fedora's grub menu (before it was > not). I haven't got a chance to try installing TC4, but this doesn't seem to work as intended on a fully up-to-date existing F19 install: % rpm -q grub2 os-prober grub2-2.00-16.fc19.x86_64 os-prober-1.58-1.fc19.x86_64 # grub2-mkconfig -o /boot/EFI/fedora/grub.cfg Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.9.1-301.fc19.x86_64 Found initrd image: /boot/initramfs-3.9.1-301.fc19.x86_64.img Found linux image: /boot/vmlinuz-3.9.0-301.fc19.x86_64 Found initrd image: /boot/initramfs-3.9.0-301.fc19.x86_64.img Found linux image: /boot/vmlinuz-3.9.0-0.rc8.git0.2.fc19.x86_64 Found initrd image: /boot/initramfs-3.9.0-0.rc8.git0.2.fc19.x86_64.img Found linux image: /boot/vmlinuz-0-rescue-9388a5eb453d59f4fd98567b37061720 Found initrd image: /boot/initramfs-0-rescue-9388a5eb453d59f4fd98567b37061720.img Found linux image: /boot/vmlinuz-3.9.1-301.fc19.x86_64 Found initrd image: /boot/initramfs-3.9.1-301.fc19.x86_64.img Found linux image: /boot/vmlinuz-3.9.0-301.fc19.x86_64 Found initrd image: /boot/initramfs-3.9.0-301.fc19.x86_64.img Found linux image: /boot/vmlinuz-3.9.0-0.rc8.git0.2.fc19.x86_64 Found initrd image: /boot/initramfs-3.9.0-0.rc8.git0.2.fc19.x86_64.img Found Windows Boot Manager on Microsoft/Boot/bootmgfw.efi Windows Boot Manager is not yet supported by grub-mkconfig. done Is this supposed to work with grub2-mkconfig also, or only from anaconda? -T.C. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Beta TC4 karma requests
Hey folks! Here are the updates from TC4 that require karma: https://admin.fedoraproject.org/updates/FEDORA-2013-7635/gnome-shell-3.8.1-4.fc19 https://admin.fedoraproject.org/updates/FEDORA-2013-7320/gnome-initial-setup-0.9-2.fc19 https://admin.fedoraproject.org/updates/FEDORA-2013-/gnome-settings-daemon-3.8.1-2.fc19 https://admin.fedoraproject.org/updates/F19/FEDORA-2013-7487/os-prober-1.58-1.fc19 https://admin.fedoraproject.org/updates/python-blivet-0.13-1.fc19,pykickstart-1.99.30-1.fc19,anaconda-19.25-1.fc19 It should be pretty obvious how to test most of them. If Shell works, +1 it. (The update also adds more prominent Fedora branding on the login screen). If initial-setup works, +1 it. If GNOME works, +1 settings-daemon (it should also *hopefully* set up IMEs correctly for CJK users). If install works, +1 the anaconda etc. update. If you do an install alongside some other OS and that works okay, +1 os-prober. If anyone has a UEFI install of Windows and can test installing F19 Beta TC4 alongside it, please do - the os-prober update should mean that the Windows install will now be present in Fedora's grub menu (before it was not). Thanks folks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
