Re: Call for testing: UEFI boot of current Rawhide images written to USB with dd
On Tue, 2022-08-02 at 23:06 -0300, Geraldo Simião Kutz wrote: > Adam, I tested with this same iso you linked here on two different > computers (acer aspire native UEFI and HP-G42 BIOS) pendrive (Sandisk > cruzer blade 16GB) using dd (dd > if="./Fedora-Everything-netinst-x86_64-Rawhide-20220802.n.0.iso" > of="/dev/sdb" status="progress" conv="fsync"). > Both booted fine to the installer, no problems here. > Hope this helps. Thanks a lot for the data Geraldo! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Call for testing: UEFI boot of current Rawhide images written to USB with dd
Adam, I tested with this same iso you linked here on two different computers (acer aspire native UEFI and HP-G42 BIOS) pendrive (Sandisk cruzer blade 16GB) using dd (dd if="./Fedora-Everything-netinst-x86_64-Rawhide-20220802.n.0.iso" of="/dev/sdb" status="progress" conv="fsync"). Both booted fine to the installer, no problems here. Hope this helps. Geraldo @geraldosimiao:matrix.org Em ter., 2 de ago. de 2022 às 20:44, Adam Williamson < adamw...@fedoraproject.org> escreveu: > Hey folks! > > As part of testing the switch to using grub2 for BIOS boot of live and > installer images, I tried writing a recent image to USB with dd and > booting it in native UEFI mode on my test box. It didn't work. > > However, Brian Lane says it's fine for him, and I haven't seen anyone > else mention this issue. So maybe it's something odd with my test stick > or system. > > Can anyone else try writing a recent Rawhide image - I used Fedora- > Everything-netinst-x86_64-Rawhide-20220704.n.0.iso at the time, so a > current equivalent would be > > https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220802.n.0/compose/Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-Rawhide-20220802.n.0.iso > - to USB with dd then booting it in native UEFI mode on some system, > and see if it works? It'd be good to know if there's a general issue or > I just have some cranky hardware. Thanks! > -- > Adam Williamson > Fedora QA > IRC: adamw | Twitter: adamw_ha > https://www.happyassassin.net > > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-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/test@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Call for testing: UEFI boot of current Rawhide images written to USB with dd
On Tue, Aug 2, 2022, at 7:44 PM, Adam Williamson wrote: > Hey folks! > > As part of testing the switch to using grub2 for BIOS boot of live and > installer images, I tried writing a recent image to USB with dd and > booting it in native UEFI mode on my test box. It didn't work. > > However, Brian Lane says it's fine for him, and I haven't seen anyone > else mention this issue. So maybe it's something odd with my test stick > or system. > > Can anyone else try writing a recent Rawhide image - I used Fedora- > Everything-netinst-x86_64-Rawhide-20220704.n.0.iso at the time, so a > current equivalent would be > https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220802.n.0/compose/Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-Rawhide-20220802.n.0.iso > - to USB with dd then booting it in native UEFI mode on some system, > and see if it works? It'd be good to know if there's a general issue or > I just have some cranky hardware. Thanks! Run this on the stick that's been dd'd sudo parted /dev/sdb u s p Is there a pmbr_boot disk flag? I forget how to remove it using parted, but maybe parted /dev/sdb disk_set pmbr_boot off Now see if the stick boots the cranky hardware. -- Chris Murphy ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Call for testing: UEFI boot of current Rawhide images written to USB with dd
Hey folks! As part of testing the switch to using grub2 for BIOS boot of live and installer images, I tried writing a recent image to USB with dd and booting it in native UEFI mode on my test box. It didn't work. However, Brian Lane says it's fine for him, and I haven't seen anyone else mention this issue. So maybe it's something odd with my test stick or system. Can anyone else try writing a recent Rawhide image - I used Fedora- Everything-netinst-x86_64-Rawhide-20220704.n.0.iso at the time, so a current equivalent would be https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220802.n.0/compose/Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-Rawhide-20220802.n.0.iso - to USB with dd then booting it in native UEFI mode on some system, and see if it works? It'd be good to know if there's a general issue or I just have some cranky hardware. Thanks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: rpm -ivh kernel installation put no vmlinuz* in /boot/
Adam Williamson composed on 2022-08-02 14:10 (UTC-0700): > On Tue, 2022-08-02 at 15:20 -0400, Felix Miata wrote: >> Adam Williamson composed on 2022-08-02 11:23 (UTC-0700): >>> On Mon, 2022-08-01 at 11:02 -0400, Felix Miata wrote: Is this normal procedure now in rawhide? I copied vmlinuz directly from the rpm to /boot/ and renamed it vmlinuz-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64, though I could have symlinked its location in the /lib/modules tree. It works. >>> kernel is a metapackage that doesn't contain any files, the actual main >>> parts of the kernel are in kernel-core. Is that what you meant? >> I haven't installed "kernel" in over a year. I haven't been able to >> determine any purpose it serves that is actually needed. What I ran was: >> time rpm -ivh >> kernel-core-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64 >> kernel-modules-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64 > OK. Well, it should have wound up putting the file in place, I think. I > think it's not directly installed, but put in place by the %posttrans > script, which does this (from the current package): > rm -f /var/lib/rpm-state/kernel/installing_core_5.19.0-65.fc37.x86_64 > /bin/kernel-install add 5.19.0-65.fc37.x86_64 > /lib/modules/5.19.0-65.fc37.x86_64/vmlinuz || exit $? > did you get any scriptlet failures or anything? I don't remember seeing anything to indicate failure at the time. String vmlinuz does not appear in /var/log/messages from yesterday, or in last 6 iterations of journal. :p -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: kernels failing to boot in rawhide for a few weeks now.
On Tue, 02 Aug 2022 14:07:24 -0700 Adam Williamson wrote: > Not sure what's going on in your case, but FWIW, I'm on current > Rawhide and not seeing any such problem... Thanks for the confirmation. I was assuming this was the case, as it seemed too major for it not to be widely reported if it was common. There were hundreds of updates in the time frame that whatever is causing this occurred. And, since the mass rebuild, they have rolled off. Maybe it is some arcane system setting I have enabled or disabled, but I don't recall changing anything that could cause this. I'll just keep plugging away. I'll probably focus on trying to boot without an initramfs, as that seems pretty straightforward, and would conclusively point or not point at dracut as the issue. That early boot process is difficult to debug because it is so minimal. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: rpm -ivh kernel installation put no vmlinuz* in /boot/
On Tue, 2022-08-02 at 15:20 -0400, Felix Miata wrote: > Adam Williamson composed on 2022-08-02 11:23 (UTC-0700): > > > On Mon, 2022-08-01 at 11:02 -0400, Felix Miata wrote: > > > > Is this normal procedure now in rawhide? > > > > I copied vmlinuz directly from the rpm to /boot/ and renamed it > > > vmlinuz-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64, > > > though I could have symlinked its location in the /lib/modules tree. It > > > works. > > > kernel is a metapackage that doesn't contain any files, the actual main > > parts of the kernel are in kernel-core. Is that what you meant? > > I haven't installed "kernel" in over a year. I haven't been able do determine > any purpose it serves that is actually needed. What I ran was: > time rpm -ivh kernel-core-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64 > kernel-modules-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64 OK. Well, it should have wound up putting the file in place, I think. I think it's not directly installed, but put in place by the %posttrans script, which does this (from the current package): rm -f /var/lib/rpm-state/kernel/installing_core_5.19.0-65.fc37.x86_64 /bin/kernel-install add 5.19.0-65.fc37.x86_64 /lib/modules/5.19.0-65.fc37.x86_64/vmlinuz || exit $? did you get any scriptlet failures or anything? -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: kernels failing to boot in rawhide for a few weeks now.
On Tue, 2022-08-02 at 13:46 -0700, stan via test wrote: > Just a data point, that I have been unable to run locally built or > stock Fedora kernels for a couple of weeks now. I have opened a > bugzilla against dracut for this, but I'm not sure that it really is > dracut at fault. It is all documented in > > https://bugzilla.redhat.com/show_bug.cgi?id=2109194 > > I can't think what is causing this on my system, since a Fedora kernel > I built and installed from a src.rpm on 20220703 is running fine. And > rawhide is up to date with the latest packages. > > How can a stock Fedora kernel not boot on a Fedora system? Really > puzzling. Not sure what's going on in your case, but FWIW, I'm on current Rawhide and not seeing any such problem... -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
kernels failing to boot in rawhide for a few weeks now.
Just a data point, that I have been unable to run locally built or stock Fedora kernels for a couple of weeks now. I have opened a bugzilla against dracut for this, but I'm not sure that it really is dracut at fault. It is all documented in https://bugzilla.redhat.com/show_bug.cgi?id=2109194 I can't think what is causing this on my system, since a Fedora kernel I built and installed from a src.rpm on 20220703 is running fine. And rawhide is up to date with the latest packages. How can a stock Fedora kernel not boot on a Fedora system? Really puzzling. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: rpm -ivh kernel installation put no vmlinuz* in /boot/
Adam Williamson composed on 2022-08-02 11:23 (UTC-0700): > On Mon, 2022-08-01 at 11:02 -0400, Felix Miata wrote: >> Is this normal procedure now in rawhide? >> I copied vmlinuz directly from the rpm to /boot/ and renamed it >> vmlinuz-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64, >> though I could have symlinked its location in the /lib/modules tree. It >> works. > kernel is a metapackage that doesn't contain any files, the actual main > parts of the kernel are in kernel-core. Is that what you meant? I haven't installed "kernel" in over a year. I haven't been able do determine any purpose it serves that is actually needed. What I ran was: time rpm -ivh kernel-core-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64 kernel-modules-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64 -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: rpm -ivh kernel installation put no vmlinuz* in /boot/
On Mon, 2022-08-01 at 11:02 -0400, Felix Miata wrote: > Is this normal procedure now in rawhide? > > I copied vmlinuz directly from the rpm to /boot/ and renamed it > vmlinuz-5.19.0-0.rc8.20220729git6e2c0490769e.62.fc37.x86_64, > though I could have symlinked its location in the /lib/modules tree. It works. kernel is a metapackage that doesn't contain any files, the actual main parts of the kernel are in kernel-core. Is that what you meant? -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
