Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 06.10.20 um 01:50 schrieb Chris Murphy: > In this case you can replace it by just copying a substitute > grubx64.efi to the proper location on the USB stick... which might be > EFI/BOOT, I'd have to poke it with a stick to find out. > > I already tried to replace it with a f31 one, it did not help at all. The difference must be something else: a block signature, blockloader, mbr whatever is used on an efi bios with secure boot disabled before that file is loaded. I did not try to boot it with secure boot enabled, maybe i should test that. Best regards, Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Mon, Oct 5, 2020 at 12:59 PM Samuel Sieb wrote: > > On 10/5/20 11:21 AM, Marius Schwarz wrote: > > Am 04.10.20 um 21:01 schrieb Samuel Sieb: > >> On 10/4/20 9:36 AM, Marius Schwarz wrote: > >>> And still,we do not know why the f33 livedisc does not boot at all when > >>> inserted early > >>> AND > >>> why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is > >>> overwriting the ssd boot setup, instead of the usbdrive bootconfig. > >> > >> You can't use "grub2-install /dev/USBDRIVE", that's for non-EFI > >> systems. And as Chris explained, you can't use "grub2-install" either > >> or it will mess things up badly. > > > > So, this is a loose-loose-situation. > > > > Still, how the heck could the system be installed in the first place, > > because it was booted with secure-boot enabled? :) > > I don't understand why you think that would be a problem. You left out > the following line. > > >>If you have the usb drive EFI partition mounted at /boot/efi, then > >> re-installing "grub2-efi" should fix the grub install on your usb drive. > > When Fedora is installed on a UEFI system, the "grub2-efi" package is > installed which puts grub on the EFI partition where it should be. If > you want to fix the grub install, then you need to reinstall that > package with the right EFI partition mounted at /boot/efi. Right and this cannot be done with a USB stick imaged using dd (or variant including Fedora Media Writer) from a Fedora produced ISO image. And that's because that image is a read-only ISO 9660 file system. Hence my advice in related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1883609#c30 In this case you can replace it by just copying a substitute grubx64.efi to the proper location on the USB stick... which might be EFI/BOOT, I'd have to poke it with a stick to find out. -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On 10/5/20 11:21 AM, Marius Schwarz wrote: Am 04.10.20 um 21:01 schrieb Samuel Sieb: On 10/4/20 9:36 AM, Marius Schwarz wrote: And still,we do not know why the f33 livedisc does not boot at all when inserted early AND why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is overwriting the ssd boot setup, instead of the usbdrive bootconfig. You can't use "grub2-install /dev/USBDRIVE", that's for non-EFI systems. And as Chris explained, you can't use "grub2-install" either or it will mess things up badly. So, this is a loose-loose-situation. Still, how the heck could the system be installed in the first place, because it was booted with secure-boot enabled? :) I don't understand why you think that would be a problem. You left out the following line. If you have the usb drive EFI partition mounted at /boot/efi, then re-installing "grub2-efi" should fix the grub install on your usb drive. When Fedora is installed on a UEFI system, the "grub2-efi" package is installed which puts grub on the EFI partition where it should be. If you want to fix the grub install, then you need to reinstall that package with the right EFI partition mounted at /boot/efi. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 04.10.20 um 21:01 schrieb Samuel Sieb: > On 10/4/20 9:36 AM, Marius Schwarz wrote: >> And still,we do not know why the f33 livedisc does not boot at all when >> inserted early >> AND >> why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is >> overwriting the ssd boot setup, instead of the usbdrive bootconfig. > > You can't use "grub2-install /dev/USBDRIVE", that's for non-EFI > systems. And as Chris explained, you can't use "grub2-install" either > or it will mess things up badly. So, this is a loose-loose-situation. Still, how the heck could the system be installed in the first place, because it was booted with secure-boot enabled? :) > If you have the usb drive EFI partition mounted at /boot/efi, then > re-installing "grub2-efi" should fix the grub install on your usb drive. > > As for why the live image isn't booting, that really seems like a BIOS > problem. hard to tell, when there is nothing to debug on. So i need to try the update to F32 (first version not to boot on usb) and see what happens :( ok, thanks to all for the affords. best regards, Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Sun, Oct 4, 2020 at 10:50 AM Marius Schwarz wrote: > > Am 03.10.20 um 22:07 schrieb Chris Murphy: > > > > No the correct invocation is "dnf reinstall grub2-efi-x64 shim-x64" > > > > Suggesting UEFI users install GRUB with grub2-install is asking for a > > support nightmare, it's untenable. > > > > Isn't a simple check "are we booted with efi" a working solution to this? No because grub comes in arch and firmware specific flavors, which are compile time options. You get one or the other. As amazing as GRUB is in terms of all the use cases it can support, it's mind numbingly complicated because of all the use cases it can support. And that's a reference to upstream. Fedora keeps over 200 patches on top of that, which have to be updated and tested every time we rebase. -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Sun, Oct 4, 2020 at 10:37 AM Marius Schwarz wrote: > > now, the efi stuff is installed, i accept a few "oh, theres efi, i do > efi" mistakes from time to time. But i don't have a clue, how the system > could boot with those symlinks before that grub-install destroyed it. The symlinks are in /etc, they aren't used for booting. The pointer to the grub.cfg is baked in the grubx64.efi itself. The Fedora built on looking on the ESP and the one created by grub-install looks in /boot/grub. > > And still,we do not know why the f33 livedisc does not boot at all when > inserted early > AND > why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is > overwriting the ssd boot setup, instead of the usbdrive bootconfig. It's either face planting on the partition scheme, shim.efi, or grubx64.efi. The shim.efi hasn't changed since 2018, libisoburn hasn't changed in 12 months, so yeah that leaves grub. -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Sun, Oct 4, 2020 at 3:01 PM Samuel Sieb wrote: > > On 10/4/20 9:36 AM, Marius Schwarz wrote: > > And still,we do not know why the f33 livedisc does not boot at all when > > inserted early > > AND > > why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is > > overwriting the ssd boot setup, instead of the usbdrive bootconfig. > > You can't use "grub2-install /dev/USBDRIVE", that's for non-EFI systems. > And as Chris explained, you can't use "grub2-install" either or it > will mess things up badly. If you have the usb drive EFI partition > mounted at /boot/efi, then re-installing "grub2-efi" should fix the grub > install on your usb drive. This is why, for elementary OS image testing or live image testing, it's often safer and faster to do it inside of a virtual system, whether you use KVM, Virtualbox, VMWare, Xen, or whatever. Manipulating your test system's grub settings is somewhat risky. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On 10/4/20 9:36 AM, Marius Schwarz wrote: And still,we do not know why the f33 livedisc does not boot at all when inserted early AND why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is overwriting the ssd boot setup, instead of the usbdrive bootconfig. You can't use "grub2-install /dev/USBDRIVE", that's for non-EFI systems. And as Chris explained, you can't use "grub2-install" either or it will mess things up badly. If you have the usb drive EFI partition mounted at /boot/efi, then re-installing "grub2-efi" should fix the grub install on your usb drive. As for why the live image isn't booting, that really seems like a BIOS problem. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 03.10.20 um 22:07 schrieb Chris Murphy: > > No the correct invocation is "dnf reinstall grub2-efi-x64 shim-x64" > > Suggesting UEFI users install GRUB with grub2-install is asking for a > support nightmare, it's untenable. > Isn't a simple check "are we booted with efi" a working solution to this? best regards, Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 03.10.20 um 22:23 schrieb Chris Murphy: > >> after investigating the problem with not finding grub.cfg in the >> proprosed bootpath /boot/ .. the solution was simple. >> >> The system died not use secure boot, as secure-boot was disabled for the >> kernel-surface kernelseries. They are not signed, so no secure boot possible. >> >> Means: bios is loading "/boot/grub2/grub.cfg" but it can't find it, because >> those are symlinks to "/boot/efi/fedora/grub.cfg" but that is not >> accessible, because the partition it's linked to, is not mounted there when >> grub starts. > A grub2-install based grubx64.efi expects to find the grub.cfg in > /boot/grub2/grub.cfg. This OSLoader is not signed. > > The grub2-efi-x64-2.04-31.fc33.x86_64 based grubx64.efi expects to > find the grub.cfg on the EFI system partition inside EFI/fedora/ and > this OSLoader is signed. > > Basically you've stepped through the Looking Glass by using > grub2-install on a UEFI computer. > I believe this due to the way the system got installed in the first place, which was via a secure booted livedisc. Later, as the usual kernel build for Fedora did not support touch on the pro4, Jake Day's 5.1 kernel was build on the system, but i needed to be started without secure boot. now, the efi stuff is installed, i accept a few "oh, theres efi, i do efi" mistakes from time to time. But i don't have a clue, how the system could boot with those symlinks before that grub-install destroyed it. And still,we do not know why the f33 livedisc does not boot at all when inserted early AND why grub-install /dev/USBDRIVE (correct devicename ofcourse ) is overwriting the ssd boot setup, instead of the usbdrive bootconfig. best regards, Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Sat, Oct 3, 2020 at 4:09 AM Marius Schwarz wrote: > > Am 03.10.20 um 11:43 schrieb Tomasz Torcz: > > If you do not state the devicename, how does grub choose the correct > > drive? I don't want to overwrite the bootloader on the ssd. > > There is only one correct ESP partition in EFI system to install > bootloader to. You can read the code finding it at > https://github.com/rhboot/grub2/blob/master/util/grub-install.c#L1029 > > > > That seems to be commented incorrectly: > > L1045: > /* > The EFI System Partition may have been given directly using > --root-directory. > */ > > there is no such option according to man and --help . > >grub-install [--modules=MODULES] [--install-modules=MODULES] > [--themes=THEMES] [--fonts=FONTS] [--locales=LOCALES] > [--compress[=no,xz,gz,lzo]] [-d | --directory=DIR] > [--grub-mkimage=FILE] [--boot-directory=DIR] > [--target=TARGET] [--grub-setup=FILE] > [--grub-mkrelpath=FILE] [--grub-probe=FILE] > [--allow-floppy] [--recheck] [--force] [--force-file-id] > [--disk-module=MODULE] [--no-nvram] [--removable] > [--bootloader-id=ID] [--efi-directory=DIR] INSTALL_DEVICE > > could --efi-directory be meant? > > ### UPDATE ### > > after investigating the problem with not finding grub.cfg in the > proprosed bootpath /boot/ .. the solution was simple. > > The system died not use secure boot, as secure-boot was disabled for the > kernel-surface kernelseries. They are not signed, so no secure boot possible. > > Means: bios is loading "/boot/grub2/grub.cfg" but it can't find it, because > those are symlinks to "/boot/efi/fedora/grub.cfg" but that is not accessible, > because the partition it's linked to, is not mounted there when grub starts. A grub2-install based grubx64.efi expects to find the grub.cfg in /boot/grub2/grub.cfg. This OSLoader is not signed. The grub2-efi-x64-2.04-31.fc33.x86_64 based grubx64.efi expects to find the grub.cfg on the EFI system partition inside EFI/fedora/ and this OSLoader is signed. Basically you've stepped through the Looking Glass by using grub2-install on a UEFI computer. -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Fri, Oct 2, 2020 at 3:12 AM Petr Pisar wrote: > > On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote: > > On 10/1/20 5:52 AM, Marius Schwarz wrote: > > > > > > > > > > > Is it possible to boot from the stick and then perform a grub-install > > > > with an old grub? > > > > > > > > > > This attempt failed too: > > > > > > # grub2-install /dev/sda > > > grub2-install: Fehler: /usr/lib/grub/x86_64-efi/modinfo.sh existiert > > > nicht. Bitte geben Sie --target oder --directory an. > > > > > > and that file seems not to be part of any package. There is only one for > > > "i386-pc". > > > > You can't (and must not!) use grub2-install on an EFI system. > > Of course you have. How else would you get GRUB EFI executable onto the boot > partition and register it into boot environments? It's in an arch specific RPM. e.g. grub2-efi-x64-2.04-31.fc34.x86_64.rpm contains grubx64.efi created and signed within the Fedora build system. The grub2-install created executable is not signed, will not work with UEFI Secure Boot enabled unless manually signed by the user, and it has different behavior from the Fedora created one: where it expects to find modules and the grub.cfg. > But the correct invocation for EFI systems is different. You just use > "grub2-install" without the disk device name. No the correct invocation is "dnf reinstall grub2-efi-x64 shim-x64" Suggesting UEFI users install GRUB with grub2-install is asking for a support nightmare, it's untenable. -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 03.10.20 um 11:43 schrieb Tomasz Torcz: > If you do not state the devicename, how does grub choose the correct >> drive? I don't want to overwrite the bootloader on the ssd. > There is only one correct ESP partition in EFI system to install > bootloader to. You can read the code finding it at > https://github.com/rhboot/grub2/blob/master/util/grub-install.c#L1029 > > That seems to be commented incorrectly: L1045: /* The EFI System Partition may have been given directly using --root-directory. */ there is no such option according to man and --help . grub-install [--modules=MODULES] [--install-modules=MODULES] [--themes=THEMES] [--fonts=FONTS] [--locales=LOCALES] [--compress[=no,xz,gz,lzo]] [-d | --directory=DIR] [--grub-mkimage=FILE] [--boot-directory=DIR] [--target=TARGET] [--grub-setup=FILE] [--grub-mkrelpath=FILE] [--grub-probe=FILE] [--allow-floppy] [--recheck] [--force] [--force-file-id] [--disk-module=MODULE] [--no-nvram] [--removable] [--bootloader-id=ID] [*--efi-directory=DIR*] INSTALL_DEVICE could --efi-directory be meant? ### UPDATE ### after investigating the problem with not finding grub.cfg in the proprosed bootpath /boot/ .. the solution was simple. The system died not use secure boot, as secure-boot was disabled for the kernel-surface kernelseries. They are not signed, so no secure boot possible. Means: bios is loading "/boot/grub2/grub.cfg" but it can't find it, because those are symlinks to "/boot/efi/fedora/grub.cfg" but that is not accessible, because the partition it's linked to, is not mounted there when grub starts. those symlinks where necessary to fix some other bugs with grubby, which has a slight different imagination where to do updates to grub.cfg, as grub itself has. In other words, one loads from efi path, one not . So symlinks were there to keep them in Sync. ( documented in a grub/grubby br @ bz ) Because it worked before the grub2-install with those symlinks (grub.cfg & grubenv) , there needs to be a different grub-install cmd needed : which could that be? (for now my system starts again) best regards, Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Sat, Oct 03, 2020 at 11:17:44AM +0200, Marius Schwarz wrote: > Am 02.10.20 um 11:12 schrieb Petr Pisar: > > On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote: > >> On 10/1/20 5:52 AM, Marius Schwarz wrote: > Is it possible to boot from the stick and then perform a grub-install > with an old grub? > > >>> This attempt failed too: > >>> > >>> # grub2-install /dev/sda > >>> grub2-install: Fehler: /usr/lib/grub/x86_64-efi/modinfo.sh existiert > >>> nicht. Bitte geben Sie --target oder --directory an. > >>> > >>> and that file seems not to be part of any package. There is only one for > >>> "i386-pc". > >> You can't (and must not!) use grub2-install on an EFI system. > > Of course you have. How else would you get GRUB EFI executable onto the boot > > partition and register it into boot environments? > > > > But the correct invocation for EFI systems is different. You just use > > "grub2-install" without the disk device name. > If you do not state the devicename, how does grub choose the correct > drive? I don't want to overwrite the bootloader on the ssd. There is only one correct ESP partition in EFI system to install bootloader to. You can read the code finding it at https://github.com/rhboot/grub2/blob/master/util/grub-install.c#L1029 -- Tomasz Torcz“Funeral in the morning, IDE hacking to...@pipebreaker.pl in the afternoon and evening.” - Alan Cox ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 03.10.20 um 11:17 schrieb Marius Schwarz: > > FYI: Not working without manual corrections > > insmod lvm > insmod xfs > set root=(hd0,gpt3) > configfile /grub2/grub.cfg > linux /vmlinuz-5.8.10 > initrd /initramfs-5.8.10 > boot > > Q: Why is configfile read, but not used if anything important is in it > i.e. the sysroot options passed to "linux" to find the decrypted luks > partition? > A: because it's not found This is working and maybe the clue, why grub2-install fails: set root=(hd0,gpt3) configfile (hd0,gpt2)/grub2/grub.cfg Any ideas? Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 02.10.20 um 11:12 schrieb Petr Pisar: > On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote: >> On 10/1/20 5:52 AM, Marius Schwarz wrote: Is it possible to boot from the stick and then perform a grub-install with an old grub? >>> This attempt failed too: >>> >>> # grub2-install /dev/sda >>> grub2-install: Fehler: /usr/lib/grub/x86_64-efi/modinfo.sh existiert >>> nicht. Bitte geben Sie --target oder --directory an. >>> >>> and that file seems not to be part of any package. There is only one for >>> "i386-pc". >> You can't (and must not!) use grub2-install on an EFI system. > Of course you have. How else would you get GRUB EFI executable onto the boot > partition and register it into boot environments? > > But the correct invocation for EFI systems is different. You just use > "grub2-install" without the disk device name. If you do not state the devicename, how does grub choose the correct drive? I don't want to overwrite the bootloader on the ssd. by entering "grub2-install /dev/sdb" where sdb was the usb drive, grub2 removed the working boot config from .. you guessed it by now.. the ssd :( The repair try, done by the docs.fp.orgbootloading-with-grub2 guide, honestly said, it wants to install i386 on a clearly x64 system. FYI: Not working without manual corrections insmod lvm insmod xfs set root=(hd0,gpt3) configfile /grub2/grub.cfg linux /vmlinuz-5.8.10 initrd /initramfs-5.8.10 boot Q: Why is configfile read, but not used if anything important is in it i.e. the sysroot options passed to "linux" to find the decrypted luks partition? AFTER this: i managed to boot the system, by manually mounting the dm-0 device to /sysroot BUT: grub2-mkconfig -o /boot/grub2/grub.cfg grub2-install --boot-directory=/boot /dev/nvm0n1 did not succeed in recreating a working boot environment, in fact, nothing changed. Still not presenting a grub menu, where grub2-mkconfig said, it created the menu. (i hate lying tools) Q: What did anaconda different on the first installation of Fedora, to make it work? --> HELP needed <-- Lesson learned: once it's on a system, don't play with grub2-install. Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Thu, Oct 01, 2020 at 11:07:28AM -0700, Samuel Sieb wrote: > On 10/1/20 5:52 AM, Marius Schwarz wrote: > > > > > > > > Is it possible to boot from the stick and then perform a grub-install > > > with an old grub? > > > > > > > This attempt failed too: > > > > # grub2-install /dev/sda > > grub2-install: Fehler: /usr/lib/grub/x86_64-efi/modinfo.sh existiert > > nicht. Bitte geben Sie --target oder --directory an. > > > > and that file seems not to be part of any package. There is only one for > > "i386-pc". > > You can't (and must not!) use grub2-install on an EFI system. Of course you have. How else would you get GRUB EFI executable onto the boot partition and register it into boot environments? But the correct invocation for EFI systems is different. You just use "grub2-install" without the disk device name. The missing file is provided by grub2-efi-x64-modules package. -- Petr signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On 10/1/20 5:52 AM, Marius Schwarz wrote: Is it possible to boot from the stick and then perform a grub-install with an old grub? This attempt failed too: # grub2-install /dev/sda grub2-install: Fehler: /usr/lib/grub/x86_64-efi/modinfo.sh existiert nicht. Bitte geben Sie --target oder --directory an. and that file seems not to be part of any package. There is only one for "i386-pc". You can't (and must not!) use grub2-install on an EFI system. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
> > Is it possible to boot from the stick and then perform a grub-install > with an old grub? > This attempt failed too: # grub2-install /dev/sda grub2-install: Fehler: /usr/lib/grub/x86_64-efi/modinfo.sh existiert nicht. Bitte geben Sie --target oder --directory an. and that file seems not to be part of any package. There is only one for "i386-pc". Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 01.10.20 um 07:22 schrieb Chris Murphy: > On Wed, Sep 30, 2020 at 4:22 PM Marius Schwarz wrote: >> Am 01.10.20 um 00:02 schrieb Chris Murphy: >> >> I made some more tests. It's a race, 1 out of 10 tries succeeds and the >> chance that it does is improoved by inserting the usb drive while being >> in the bios. >> >> The F31 grub files i exchanged do not seem to have something to do with it. >> >> The race happens with the same probability regardless of GRUB Fedora >> release version? >> >> No, F31 boots everytime under any condition. It's only for F32/33 afaict. >> >> I tested it with the same stick, to avoid a problem with the stick >> electronics itself. > OK so some kind of regression in GRUB, but also a firmware bug because > otherwise many other people would run into this. It's GRUB 2.02 in > Fedora 31 and GRUB 2.04 in Fedora 32. So it could be an upstream bug. It's M$ firmware, so be sure it has bugs. ( could tell you about one very nasty ) Until F32 i had no problem booting any livedisk, so something changed. > Where I'd start is making a livecd-iso-to-disk based USB stick, from > the Fedora 32 ISO that you already know fails, and make sure it still > fails when created this way. If it doesn't, then it's probably not > GRUB it's something else about the image. > > But assuming it fails, you now have an easily modifiable USB stick, > it's read-writable, so you can just copy each test grubx64.efi binary > onto the stick. > > You could start with this, pretty sure it'll fail too. So just extract > the grubx64.efi from grub2-efi-x64-2.04-1.fc32.x86_64.rpm and replace > the one on the USB stick. > https://koji.fedoraproject.org/koji/buildinfo?buildID=1356278 > > I replace anything besides boot and grub.cfg , and it's the same .. inserted before powerup => not working, inserted while in bios => working and this does not change if altered or unaltered. AFAIk the MBR ( or alike ) has a portion of code in it. sure it's not there and the bootloader needs to be updated to have effect? Is it possible to boot from the stick and then perform a grub-install with an old grub? best regards, Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On 9/30/20 10:28 PM, Elliott Sales de Andrade wrote: On Wed, 30 Sep 2020 at 18:27, Marius Schwarz wrote: The working/non-working procedure is: Power on ... inserting the stick OK, but why insert the USB stick after power on? Wouldn't it be less trouble to insert beforehand so that the firmware will always see it? He was saying that if he puts the stick in earlier, it's less likely to be able to boot. It's not about the firmware seeing it. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Wed, 30 Sep 2020 at 18:27, Marius Schwarz wrote: > > Am 01.10.20 um 00:19 schrieb Elliott Sales de Andrade: > > Could it be a timing issue of some kind? > > the sooner i hit the boot from usb button, after the stick got inserted, > the higher is the propability to start. > > Are you saying you insert the USB stick _after_ turning on the > machine? Otherwise I don't understand the correlation between the > insertion and pressing a boot from USB button. > > > The working/non-working procedure is: > > Power on > ... > inserting the stick OK, but why insert the USB stick after power on? Wouldn't it be less trouble to insert beforehand so that the firmware will always see it? > Marius -- Elliott ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Wed, Sep 30, 2020 at 4:22 PM Marius Schwarz wrote: > > Am 01.10.20 um 00:02 schrieb Chris Murphy: > > I made some more tests. It's a race, 1 out of 10 tries succeeds and the > chance that it does is improoved by inserting the usb drive while being > in the bios. > > The F31 grub files i exchanged do not seem to have something to do with it. > > The race happens with the same probability regardless of GRUB Fedora > release version? > > No, F31 boots everytime under any condition. It's only for F32/33 afaict. > > I tested it with the same stick, to avoid a problem with the stick > electronics itself. OK so some kind of regression in GRUB, but also a firmware bug because otherwise many other people would run into this. It's GRUB 2.02 in Fedora 31 and GRUB 2.04 in Fedora 32. So it could be an upstream bug. Where I'd start is making a livecd-iso-to-disk based USB stick, from the Fedora 32 ISO that you already know fails, and make sure it still fails when created this way. If it doesn't, then it's probably not GRUB it's something else about the image. But assuming it fails, you now have an easily modifiable USB stick, it's read-writable, so you can just copy each test grubx64.efi binary onto the stick. You could start with this, pretty sure it'll fail too. So just extract the grubx64.efi from grub2-efi-x64-2.04-1.fc32.x86_64.rpm and replace the one on the USB stick. https://koji.fedoraproject.org/koji/buildinfo?buildID=1356278 -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 01.10.20 um 00:19 schrieb Elliott Sales de Andrade: >> Could it be a timing issue of some kind? >> >> the sooner i hit the boot from usb button, after the stick got inserted, >> the higher is the propability to start. >> > Are you saying you insert the USB stick _after_ turning on the > machine? Otherwise I don't understand the correlation between the > insertion and pressing a boot from USB button. > The working procedure is: Power on entering Bios switching to boot manager page inserting the stick waiting until it gets powered on swiping the usb storage boot entry to left acknowledging the usb boot. None working procedure: Power on Inserting stick switching to bios switching to boot manager page swiping the usb storage boot entry to left acknowledging the usb boot. ... none secure boot message from bios reset. Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 01.10.20 um 00:02 schrieb Chris Murphy: >> I made some more tests. It's a race, 1 out of 10 tries succeeds and the >> chance that it does is improoved by inserting the usb drive while being >> in the bios. >> >> The F31 grub files i exchanged do not seem to have something to do with it. > The race happens with the same probability regardless of GRUB Fedora > release version? > No, F31 boots everytime under any condition. It's only for F32/33 afaict. I tested it with the same stick, to avoid a problem with the stick electronics itself. best regards, Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Wed, 30 Sep 2020 at 17:42, Marius Schwarz wrote: > > Am 30.09.20 um 23:00 schrieb Chris Murphy: > > > > > > And then these are current > > grub2-efi-x64-2.04-31.fc33.x86_64 > > grub2-efi-x64-2.04-23.fc32.x86_64 > > grub2-efi-x64-2.02-110.fc31.x86_64 > > > > I wonder if the affected hardware is adversely affected by all three > > of these versions of GRUB? > > > > I made some more tests. It's a race, 1 out of 10 tries succeeds and the > chance that it does is improoved by inserting the usb drive while being > in the bios. > > The F31 grub files i exchanged do not seem to have something to do with it. > > Could it be a timing issue of some kind? > > the sooner i hit the boot from usb button, after the stick got inserted, > the higher is the propability to start. > Are you saying you insert the USB stick _after_ turning on the machine? Otherwise I don't understand the correlation between the insertion and pressing a boot from USB button. > I think we can rule out signing here as the surface is in none secure > boot mode and it starts ( screenshot available). > > So what else could cause this? > > best regards, > Marius > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Wed, Sep 30, 2020 at 3:42 PM Marius Schwarz wrote: > > Am 30.09.20 um 23:00 schrieb Chris Murphy: > > > > > > And then these are current > > grub2-efi-x64-2.04-31.fc33.x86_64 > > grub2-efi-x64-2.04-23.fc32.x86_64 > > grub2-efi-x64-2.02-110.fc31.x86_64 > > > > I wonder if the affected hardware is adversely affected by all three > > of these versions of GRUB? > > > > I made some more tests. It's a race, 1 out of 10 tries succeeds and the > chance that it does is improoved by inserting the usb drive while being > in the bios. > > The F31 grub files i exchanged do not seem to have something to do with it. The race happens with the same probability regardless of GRUB Fedora release version? > > Could it be a timing issue of some kind? > > the sooner i hit the boot from usb button, after the stick got inserted, > the higher is the propability to start. > > I think we can rule out signing here as the surface is in none secure > boot mode and it starts ( screenshot available). > > So what else could cause this? Sounds like a firmware bug. I wonder if it's strictly USB related or if it's at all triggered by the isohybrid nature of our ISOs - maybe it's more or less likely to happen if the USB stick were created using livecd-iso-to-disk with '--format --efi' options and allow it to blow away the entire USB stick. -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 30.09.20 um 23:00 schrieb Chris Murphy: > > > And then these are current > grub2-efi-x64-2.04-31.fc33.x86_64 > grub2-efi-x64-2.04-23.fc32.x86_64 > grub2-efi-x64-2.02-110.fc31.x86_64 > > I wonder if the affected hardware is adversely affected by all three > of these versions of GRUB? > I made some more tests. It's a race, 1 out of 10 tries succeeds and the chance that it does is improoved by inserting the usb drive while being in the bios. The F31 grub files i exchanged do not seem to have something to do with it. Could it be a timing issue of some kind? the sooner i hit the boot from usb button, after the stick got inserted, the higher is the propability to start. I think we can rule out signing here as the surface is in none secure boot mode and it starts ( screenshot available). So what else could cause this? best regards, Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Wed, Sep 30, 2020 at 10:46 AM Stephen John Smoogen wrote: > > The Fedora secure boot signing keys were updated after F32 was initially released to deal with the grub2 problems found during the summer. I believe some systems have needed firmware updates from the manufacturer to work with the new key because they worked by white listing the old set, and don't know how to handle when a new key signed and authorized is presented. I don't know how the Surface Pro does its firmware updates and if one is needed. Fedora 31, 32, and 33 have: shim-x64-15-8.x86_64 koji date 2018-10-02 The signing keys haven't yet been updated in Fedora, they'd need to happen here. And then these are current grub2-efi-x64-2.04-31.fc33.x86_64 grub2-efi-x64-2.04-23.fc32.x86_64 grub2-efi-x64-2.02-110.fc31.x86_64 I wonder if the affected hardware is adversely affected by all three of these versions of GRUB? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 30.09.20 um 18:45 schrieb Stephen John Smoogen: > > The Fedora secure boot signing keys were updated after F32 was > initially released to deal with the grub2 problems found during the > summer. I believe some systems have needed firmware updates from the > manufacturer to work with the new key because they worked by white > listing the old set, and don't know how to handle when a new key > signed and authorized is presented. I don't know how the Surface Pro > does its firmware updates and if one is needed. I have replaced the files grubia32.efi and grubx64.efi in ANADCONDA:/EFI/BOOT/ with the ones from the F31 image. After 2 tries, the surface pro 4 booted like a charm. @Elmar: can you confirm this for your surface device? Sidenote: the files on the iso9660 partition are unchanged (because it mounts obviously ro ) best regards, Marius PS: I'm really excited to make an iso, that boots into a working surface kernel with touch enabled etc. . Unfortunatly, that kernel isn't fedora complient license wise :( ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 30.09.20 um 20:54 schrieb Brian C. Lane: > On Wed, Sep 30, 2020 at 12:45:40PM -0400, Stephen John Smoogen wrote: >> The Fedora secure boot signing keys were updated after F32 was initially >> released to deal with the grub2 problems found during the summer. I believe >> some systems have needed firmware updates from the manufacturer to work >> with the new key because they worked by white listing the old set, and >> don't know how to handle when a new key signed and authorized is presented. >> I don't know how the Surface Pro does its firmware updates and if one is >> needed. > This would be my guess as well. If you install with secure boot disabled > and then turn it back on after doing a full update does it boot > correctly? > > Brian > BTW.. meine SB is off , the none signed kernel made for the surface won't boot due to not being signed. But that means, it can't be a signing issue at all. I'm now puzzeld. Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 30.09.20 um 18:45 schrieb Stephen John Smoogen: > > > > The Fedora secure boot signing keys were updated after F32 was > initially released to deal with the grub2 problems found during the > summer. I believe some systems have needed firmware updates from the > manufacturer to work with the new key because they worked by white > listing the old set, and don't know how to handle when a new key > signed and authorized is presented. I don't know how the Surface Pro > does its firmware updates and if one is needed. > It you have removed windows, there is no update mechanism for a surface pro 4 ,, at least , not out of the box. I will ask in the surface kernel group, they tend to know such things. Best regards, Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
Am 30.09.20 um 17:17 schrieb Chris Murphy: > > That suggests the scary region of firmware, hybrid ISO, shim, and boot loader. > > The bug reports have the wrong component set on them, and aren't > discrete actionable bug reports. It's just saying "this doesn't work" which one do you suggest? >> An instant reset back into the bios happens if a usb boot is tried. > Sounds like both a regression and a firmware bug. Maybe we'll be lucky > and someone on the list has an idea already. But if not, someone with > the hardware will have to do the tedious work of figuring out exactly > where it's getting tripped up. I have one, just how do we do that? > > I have no idea what the LiveCD component is, but the bug report > contains so little information I also don't know what I'd reassign it > to. Asking about it on devel is probably the right thing to do for > now. > Thats because there isn't more to tell .. it resets on try :D No kernel message, not error message, only a reset. Wait, didn't you say shim... there was something a while ago, a bug with the shim loader or uefi ... "The Grub2 Fix from early august" But, as F32 doesn't boot too, i doN't think it has the shim in it's image. Best regards, Marius ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Wed, Sep 30, 2020 at 12:45:40PM -0400, Stephen John Smoogen wrote: > The Fedora secure boot signing keys were updated after F32 was initially > released to deal with the grub2 problems found during the summer. I believe > some systems have needed firmware updates from the manufacturer to work > with the new key because they worked by white listing the old set, and > don't know how to handle when a new key signed and authorized is presented. > I don't know how the Surface Pro does its firmware updates and if one is > needed. This would be my guess as well. If you install with secure boot disabled and then turn it back on after doing a full update does it boot correctly? Brian -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Wed, 30 Sep 2020 at 11:54, Erich Eickmeyer wrote: > On 9/30/2020 8:17 AM, Chris Murphy wrote: > > On Wed, Sep 30, 2020 at 2:05 AM Marius Schwarz > wrote: > >> Hi, > >> > >> the livecds from F32 and F33 are suffering from a problem not booting on > >> Microsoft device(s) > >> > >> https://bugzilla.redhat.com/show_bug.cgi?id=1879921 > >> https://bugzilla.redhat.com/show_bug.cgi?id=1883593 > >> > >> F31 is booting fine, the newer ones not. Looks like a GrubBootloader > >> issue to me, as not even grub comes up. > > That suggests the scary region of firmware, hybrid ISO, shim, and boot > loader. > > > > The bug reports have the wrong component set on them, and aren't > > discrete actionable bug reports. It's just saying "this doesn't work" > > but the people most likely to figure out what *is* happening are those > > with this specific hardware. > > > >> An instant reset back into the bios happens if a usb boot is tried. > > Sounds like both a regression and a firmware bug. Maybe we'll be lucky > > and someone on the list has an idea already. But if not, someone with > > the hardware will have to do the tedious work of figuring out exactly > > where it's getting tripped up. > > > > > >> Unfortunatly the assignee is not reacting and i would really miss my > >> linux surface after upgrading to F32 :D > > I have no idea what the LiveCD component is, but the bug report > > contains so little information I also don't know what I'd reassign it > > to. Asking about it on devel is probably the right thing to do for > > now. > > I can confirm this bug does exist. Attempting to boot on my Surface Pro > 4 requires secure boot to be momentarily shut-off. SB actually is > reporting a secure boot violation for whatever reason. I have reason to > believe that the UEFI files are missing correct signing, or that signing > needs to be updated. > > I have also seen SB failures with my Dell laptop with SB enabled, but > those are easier to work around than going nuclear on a Surface Pro and > shutting-off secure boot. > > F31 and F32 are unaffected, this appears to have started with F33. > > The Fedora secure boot signing keys were updated after F32 was initially released to deal with the grub2 problems found during the summer. I believe some systems have needed firmware updates from the manufacturer to work with the new key because they worked by white listing the old set, and don't know how to handle when a new key signed and authorized is presented. I don't know how the Surface Pro does its firmware updates and if one is needed. > -- > Erich Eickmeyer > Project Leader Ubuntu Studio > Maintainer Fedora Jam > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > -- Stephen J Smoogen. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On 9/30/2020 8:17 AM, Chris Murphy wrote: > On Wed, Sep 30, 2020 at 2:05 AM Marius Schwarz wrote: >> Hi, >> >> the livecds from F32 and F33 are suffering from a problem not booting on >> Microsoft device(s) >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1879921 >> https://bugzilla.redhat.com/show_bug.cgi?id=1883593 >> >> F31 is booting fine, the newer ones not. Looks like a GrubBootloader >> issue to me, as not even grub comes up. > That suggests the scary region of firmware, hybrid ISO, shim, and boot loader. > > The bug reports have the wrong component set on them, and aren't > discrete actionable bug reports. It's just saying "this doesn't work" > but the people most likely to figure out what *is* happening are those > with this specific hardware. > >> An instant reset back into the bios happens if a usb boot is tried. > Sounds like both a regression and a firmware bug. Maybe we'll be lucky > and someone on the list has an idea already. But if not, someone with > the hardware will have to do the tedious work of figuring out exactly > where it's getting tripped up. > > >> Unfortunatly the assignee is not reacting and i would really miss my >> linux surface after upgrading to F32 :D > I have no idea what the LiveCD component is, but the bug report > contains so little information I also don't know what I'd reassign it > to. Asking about it on devel is probably the right thing to do for > now. I can confirm this bug does exist. Attempting to boot on my Surface Pro 4 requires secure boot to be momentarily shut-off. SB actually is reporting a secure boot violation for whatever reason. I have reason to believe that the UEFI files are missing correct signing, or that signing needs to be updated. I have also seen SB failures with my Dell laptop with SB enabled, but those are easier to work around than going nuclear on a Surface Pro and shutting-off secure boot. F31 and F32 are unaffected, this appears to have started with F33. -- Erich Eickmeyer Project Leader Ubuntu Studio Maintainer Fedora Jam pEpkey.asc Description: application/pgp-keys ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32/33 livedisks do not boot on M$ system(s)
On Wed, Sep 30, 2020 at 2:05 AM Marius Schwarz wrote: > > Hi, > > the livecds from F32 and F33 are suffering from a problem not booting on > Microsoft device(s) > > https://bugzilla.redhat.com/show_bug.cgi?id=1879921 > https://bugzilla.redhat.com/show_bug.cgi?id=1883593 > > F31 is booting fine, the newer ones not. Looks like a GrubBootloader > issue to me, as not even grub comes up. That suggests the scary region of firmware, hybrid ISO, shim, and boot loader. The bug reports have the wrong component set on them, and aren't discrete actionable bug reports. It's just saying "this doesn't work" but the people most likely to figure out what *is* happening are those with this specific hardware. > An instant reset back into the bios happens if a usb boot is tried. Sounds like both a regression and a firmware bug. Maybe we'll be lucky and someone on the list has an idea already. But if not, someone with the hardware will have to do the tedious work of figuring out exactly where it's getting tripped up. > > Unfortunatly the assignee is not reacting and i would really miss my > linux surface after upgrading to F32 :D I have no idea what the LiveCD component is, but the bug report contains so little information I also don't know what I'd reassign it to. Asking about it on devel is probably the right thing to do for now. -- Chris Murphy ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 32/33 livedisks do not boot on M$ system(s)
Hi, the livecds from F32 and F33 are suffering from a problem not booting on Microsoft device(s) https://bugzilla.redhat.com/show_bug.cgi?id=1879921 https://bugzilla.redhat.com/show_bug.cgi?id=1883593 F31 is booting fine, the newer ones not. Looks like a GrubBootloader issue to me, as not even grub comes up. An instant reset back into the bios happens if a usb boot is tried. Unfortunatly the assignee is not reacting and i would really miss my linux surface after upgrading to F32 :D Best regards, Marius Schwarz ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
