fedora-iot

#29 Raspberry Pi 4, first time boot errors
Closed: not supported by pbrobinson. Opened by barn.

Closed: not supported
Reopen Issue

Issue:
Unable to login to Raspberry Pi 4 after initial boot. There is a boot loop error regarding networking device:
"ifcfg-rh: dbus: couldn’t initialize system bus: Count not connect: no such file or directory"

System will continue to attempt to start networking devices indefinitely. Unable to access linux console.

Additionally, the OSTree boot menu is not interactive while I am using a USB-wired-keyboard, i am not not able to add arg to the boot process.

Steps to reproduce:
Created sd card using arm-image-installer. Used following command:

$ sudo arm-image-installer --image=Fedora-IoT-32-20200603.0.aarch64.raw.xz --target=rpi4 --media=/dev/sdb --resizefs -y

Full output from command:

=====================================================
= Selected Image:                                 
= Fedora-IoT-32-20200603.0.aarch64.raw.xz
= Selected Media : /dev/sdb
= U-Boot Target : rpi4
= Root partition will be resized
=====================================================
*****************************************************
*****************************************************
******** WARNING! ALL DATA WILL BE DESTROYED ********
*****************************************************
*****************************************************
= Writing: 
= Fedora-IoT-32-20200603.0.aarch64.raw.xz 
= To: /dev/sdb ....
4282138624 bytes (4.3 GB, 4.0 GiB) copied, 105 s, 40.8 MB/s
0+451473 records in
0+451473 records out
4294967296 bytes (4.3 GB, 4.0 GiB) copied, 233.712 s, 18.4 MB/s
= Writing image complete!
= Resizing /dev/sdb ....
Checking that no-one is using this disk right now ... FAILED
This disk is currently in use - repartitioning is probably a bad idea.
Umount all file systems, and swapoff all swap partitions on this disk.
Use the --no-reread flag to suppress this check.
sfdisk: Use the --force flag to overrule all checks.
Checking that no-one is using this disk right now ... OK
Disk /dev/sdb: 29.45 GiB, 31609323520 bytes, 61736960 sectors
Disk model: SD Card Reader  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5d66bafe
Old situation:
Device     Boot   Start     End Sectors  Size Id Type
/dev/sdb1  *       2048 1028095 1026048  501M  6 FAT16
/dev/sdb2       1028096 3125247 2097152    1G 83 Linux
/dev/sdb3       3125248 8386559 5261312  2.5G 83 Linux
/dev/sdb3: 
New situation:
Disklabel type: dos
Disk identifier: 0x5d66bafe
Device     Boot   Start      End  Sectors  Size Id Type
/dev/sdb1  *       2048  1028095  1026048  501M  6 FAT16
/dev/sdb2       1028096  3125247  2097152    1G 83 Linux
/dev/sdb3       3125248 61736959 58611712   28G 83 Linux
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
e2fsck 1.45.5 (07-Jan-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb3: 30023/164640 files (0.9% non-contiguous), 381131/657664 blocks
resize2fs 1.45.5 (07-Jan-2020)
Resizing the filesystem on /dev/sdb3 to 7326464 (4k) blocks.
The filesystem on /dev/sdb3 is now 7326464 (4k) blocks long.
= No U-Boot files found for rpi4.
= Installation Complete! Insert into the rpi4 and boot.

After inserting SD and continuing with the first time boot, I see this output on pi:
Image1:
<!!image>
Image2, again, I am unable to interact with my keyboard to change boot args or System Setup:
<!!image>
Image3:
<!!image>

I have tried recreating the USB a couple times, but get the same result. I have changed some parameters using SD card creation.

Here are the images...

Image 1:
signal-2020-06-19-144207_002.jpeg

Image2, again, I am unable to interact with my keyboard to change boot args or System Setup:
signal-2020-06-19-144207_001.jpeg

Image 3, this is the error / issue I am seeing:
signal-2020-06-19-140340.jpeg

We don't currently support the RPi4. There's issues with the upstream firmware and we're waiting for the RPi Foundation to fix it.

Metadata Update from @pbrobinson:
- Issue close_status updated to: not supported
- Issue status updated to: Closed (was: Open)

Ok, thank you for that. Can you share the link/ticket where that effort is being tracked?

I had incorrectly assumed it was supported because rpi4 in the supported list for arm-image-installer and I assumed that was applicable for all fedora images.

Ok, thank you for that. Can you share the link/ticket where that effort is being tracked?

No public ticket currently. RPi4 support is when I personally get time, I have not had much spare time.

I had incorrectly assumed it was supported because rpi4 in the supported list for arm-image-installer and I assumed that was applicable for all fedora images.

Fedora IoT uses EBBR which requires the vendor to provide the DT, the RPi vendor DT is lacking. There's also other issues with newer firmware. Basically there's a lot of issues to deal with and debug and I don't have the time (and currently the enthusiasm or interest TBH) to debug and get all the info required. Basically it will happen when it happens unless someone with the required expertise steps up and assists.

This context is helpful, thanks
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.