So I think we're almost there. I believe all the no device specific
issues are now fixed, or at least worked around in a statifactory and
1) initial-setup hangs during boot after IoT installation
2) ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0))
3) The 35network-legacy is still used even if network-scripts isn't
installed in Fedora 29
These two only appear on the RPi and not in a manner than I've been
able to consistently reproduce. The issue with not being able to
consistently reproduce is that it's almost impossible to currently fix
them. They appear to be at least partially affected by environment,
types of storage and pwoer supply could play a factor here, and the
way ostree applies updates also appears to interact with the HW
differnently to a standard Fedora ARM install. We could literally
block the release on them for the rest of time, given the plan is to
do a release every 4-6 weeks I don't believe we should, or even can,
block on these:
4) rpm-ostree will not reliably install packages in fedora-iot
5) WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()!
The other thing to note is I've adjusted the references, they are now
stable instead of 29. If you're using rpm-ostree to upgrade you'll
need to rebase to get onto the new branch:
First update the key to RPM-GPG-KEY-fedora-iot-2019 in
Then run "rpm-ostree rebase -b fedora/stable/ARCH/iot"
New installs use the right one by default.
The RC is at: https://dl.fedoraproject.org/pub/alt/iot/29/IoT/
There's been a few other fixes incorporated too, please review and
I have a machine that boots to 29.20181113.0
Running `rpm-ostree update`
'perf; interrupt took too long(5943 > 5767), lowering
kernel.perf_event_max_sample_rate to 33000'
Seems the process gets to 99% (4612/4616)
and hangs. I will plan to let it go for ~1hour then 'poweroff'
What details can I provide beyond the above? What is next?
I just pulled down Fedora-IoT-29-20181120.0.aarch64.raw.xz
booting my RPi3B+ has a repeating error:
~ 'NG at drivers/mmc/bcm2835_sdchost.c:408/bcm_2835_send_command()!
There have been some mention about SD cards as a potential factor. Is
How is that making an impact? Is it speed, quality?
As a note, the SD card I used for this test is a Kingsington 8GB HC 4
Let me know if I need to provide more details, OK?
What can I test / try / attempt next?
Thanks for your time.
How long does it take upstream fixes to make it into fedora-iot, or can I deploy rawhide packages to f-iot images ? - I’d guess not.
I’ve just found that the latest version of podman enables me to run systemd inside a container, which the current version in f29 does not. I’m hoping this capability will make it easier to port a bunch of existing systemd services.