Since there has been discussion about supporting Fedora on the Pi4, I decided to try a few rawhide images on a Pi4B with 2 GB of RAM. Most of the experiments below used uSD cards.
The results are very strange. To begin, I connected Ethernet, a mouse, keyboard, and an HDMI monitor, along with a serial port on pins 8 and 10 of the 40-pin connector.
Fedora-Minimal-Rawhide-20220717.n.0.aarch64.raw.xz fails with the following on the serial port:
U-Boot 2022.07-rc6 (Jul 04 2022 - 00:00:00 +0000)
DRAM: 2 GiB
RPI 4 Model B (0xb03115)
Core: 211 devices, 17 uclasses, devicetree: board
MMC: mmcnr@7e300000: 1, mmc@7e340000: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
In: serial
Out: vidconsole
Err: vidconsole
Net: eth0: ethernet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00
scanning bus xhci_pci for devices... Unexpected XHCI event TRB, skipping... (3db5f620 00000004 01000000 01008401)
BUG at drivers/usb/host/xhci-ring.c:530/abort_td()!
BUG!
resetting ...
I tried disconnecting the mouse, keyboard, and Ethernet, but I got the same failure.
I then tried just disconnecting the HDMI monitor, while leaving everything else connected. In that case I am able to get further, but then I start getting timeout messages from dracut:
[ OK ] Started plymouth-start.ser…e - Show Plymouth Boot Screen.
[ OK ] Started systemd-ask-passwo…uests to Plymouth Directory Watch.
[ OK ] Reached target cryptsetup.…get - Local Encrypted Volumes.
[ OK ] Reached target paths.target - Path Units.
[ OK ] Finished systemd-udev-sett…To Complete Device Initialization.
Starting multipathd.servic…per Multipath Device Controller...
[ OK ] Started multipathd.service…apper Multipath Device Controller.
[ OK ] Reached target local-fs-pr…reparation for Local File Systems.
[ OK ] Reached target local-fs.target - Local File Systems.
Starting systemd-tmpfiles-… Volatile Files and Directories...
[ OK ] Finished systemd-tmpfiles-…te Volatile Files and Directories.
[ OK ] Reached target sysinit.target - System Initialization.
[ OK ] Reached target basic.target - Basic System.
[ 368.423014] dracut-initqueue[441]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[ 368.471849] dracut-initqueue[441]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2f6c12ffc9-6ea9-457c-9acf-7a886798e99c.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 368.472914] dracut-initqueue[441]: [ -e "/dev/disk/by-uuid/6c12ffc9-6ea9-457c-9acf-7a886798e99c" ]
[ 368.473753] dracut-initqueue[441]: fi"
[ 368.545042] dracut-initqueue[441]: Warning: dracut-initqueue: starting timeout scripts
[ 370.304891] dracut-initqueue[441]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[ 370.353412] dracut-initqueue[441]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2f6c12ffc9-6ea9-457c-9acf-7a886798e99c.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 370.354565] dracut-initqueue[441]: [ -e "/dev/disk/by-uuid/6c12ffc9-6ea9-457c-9acf-7a886798e99c" ]
[ 370.355428] dracut-initqueue[441]: fi"
[ 370.426159] dracut-initqueue[441]: Warning: dracut-initqueue: starting timeout scripts
[ 371.795792] dracut-initqueue[441]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[ 371.845592] dracut-initqueue[441]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2f6c12ffc9-6ea9-457c-9acf-7a886798e99c.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 371.846757] dracut-initqueue[441]: [ -e "/dev/disk/by-uuid/6c12ffc9-6ea9-457c-9acf-7a886798e99c" ]
[ 371.847604] dracut-initqueue[441]: fi"
[ 371.922589] dracut-initqueue[441]: Warning: dracut-initqueue: starting timeout scripts
Next, I tried Fedora-KDE-Rawhide-20220717.n.0.aarch64.raw.xz and Fedora-Workstation-Rawhide-20220717.n.0.aarch64.raw.xz. Amazingly, they are able to get past the XHCI error even with the HDMI monitor connected. However, they still fail later in the startup process with the same dracut messages that I showed above.
I then tried Fedora-Server-Rawhide-20220717.n.0.aarch64.raw.xz. It booted with everything connected. It got to the initial configuration menu, let me set the root password, and booted to a login prompt, which worked perfectly.
As a final test, I tried the Fedora-Minimal-Rawhide-20220717.n.0.aarch64.raw.xz and Fedora-KDE-Rawhide-20220717.n.0.aarch64.raw.xz images on a USB flash stick instead of on a uSD card. Both worked perfectly.
So, there is something bizarre happening with uSD cards with most of the images I tested. The only image that works for me on a uSD card is the Server image. Note that I tried several different uSD cards - Samsung, SanDisk, and a "no name" card, and got consistent results, so I don't think the uSD cards are at fault.
I tried two different USB flash sticks, a SanDisk and a Transcend - both worked perfectly.
Steve
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/arm@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
