[fedora-arm] Re: Test of Fedora-Server-37-20220831.n.0.aarch64 image
Am 02.09.2022 um 09:24 schrieb Peter Robinson
<pbrobinson(a)gmail.com>:
Hi Peter,
> I just tested the image on my rock pi 4a and it failed to boot. The last messages on
screen are
>
> | [OK] Found device dev-mapper-fe_ice - /dev/mapper/fedora-root.
> | [OK] Reached target ignited-root_e.target - Initrd Root Device
>
> And then nothing happened any more.
We'll need more info, that doesn't tell us much.
What information should I (try to) provide?
> My old raspi3 dir does boot, but showed
>
> | Booting ‚Fedora Linux (5.19.3-300.fc37.aarch64) …
> | [ 11.976909] dracut-pre-udev[394]: sh: line 1:/sbin/sysctl: No such file or
directory
>
> But continues to boot without problems.
Google gave me this: https://bugzilla.redhat.com/show_bug.cgi?id=2102903
Which was duped to this: https://bugzilla.redhat.com/show_bug.cgi?id=2100668
It's apparently fixed, but a quirk of the generic initrd, it will go
with the first kernel update.
Oh, thanks. I hadn't thought about it being an older bug.