On Tue, Mar 12, 2019 at 9:00 PM Jan Kratochvil jan.kratochvil@redhat.com wrote:
On Tue, 12 Mar 2019 20:58:43 +0100, Stuart D. Gathman wrote:
I have rPi3B, and it required a few config tweaks. The arm-image-installer package for Fedora has a script with the tweaks.
Could you be more specific, please?
I have tried both 'xz -dc' and both fedora-arm-image-installer with no change of the result: # fedora-arm-image-installer --image=arch/iso-copy/Fedora-Workstation-29-1.2.aarch64.raw.xz --media=/dev/XXXsda --norootpass --resizefs --target=rpi3
I have found as a "tweak" only --blacklistvc4 from: Blank screen after boot on Raspberry Pi https://bugzilla.redhat.com/show_bug.cgi?id=1387733 Where they talk about black screen but I do not get black screen. When I added --blacklistvc4 I got during installation: = Blacklisting the VC4 Driver for the Raspberry Pi 2/3 sed: can't read /tmp/boot/extlinux/extlinux.conf: No such file or directory But it did not change anything, it still fails during boot with:
On aarch64 we boot with grub2, not extlinux so that explains the issue there, I don't believe the vc4 driver is the issue you're actually experiencing here.
https://www.jankratochvil.net/t/rpi3fail.jpg [FAILED] Failed to start Avahi mDNS/DNS-SD Stack. ... [FAILED] Failed to start Modem Manager etc. It stays at the text failed systemd startup messages.Also /usr/share/arm-image-installer/boards.d/rpi3 contains just: echo "= Raspberry Pi 3 Uboot is already in place, no changes needed." SYSCON="ttyS1,115200" So I do not see "a script with the tweaks".
The Raspberry Pi, because of the way it boots, is setup by default, the vast majority of the boards need U-Boot dd:ed to somewhere special in the first 2Mb of the disk.