Fedora IoT Working Group Meeting Minutes 2018-11-21
by Peter Robinson
Apologies it appears I forgot to send out last week's notes
=================================================
#fedora-meeting: Fedora IoT Working Group Meeting
=================================================
Meeting started by pbrobinson at 14:01:41 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2018-11-21/fedora_iot_wo...
.
Meeting summary
---------------
* roll call (pbrobinson, 14:01:42)
* 1) ==== Fedora 29 blocker status for IoT ==== (pbrobinson, 14:08:35)
* initial-setup hangs during boot after IoT installation (pwhalen,
14:11:33)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1646568
(pwhalen, 14:11:34)
* https://bodhi.fedoraproject.org/updates/FEDORA-2018-f9bf4608fa
(pwhalen, 14:14:38)
* The 35network-legacy is still used even if network-scripts isn't
installed in Fedora 29 (pwhalen, 14:21:29)
* LINK: https://github.com/dracutdevs/dracut/issues/488 (pwhalen,
14:21:30)
* LINK:
https://docs.fedoraproject.org/en-US/Fedora/26/html/Installation_Guide/ch...
(pwhalen, 14:38:57)
* initial-setup should be fixed, needs testing
https://bugzilla.redhat.com/show_bug.cgi?id=1646568 (pbrobinson,
14:41:33)
* dracut issues on boot with no ethernet
https://github.com/dracutdevs/dracut/issues/488 (pbrobinson,
14:42:00)
* not a blocker but discussed - issues on install/upgrade with some SD
cards on RPi https://bugzilla.redhat.com/show_bug.cgi?id=1648112
(pbrobinson, 14:42:39)
* raspberry pi3 intermittent wifi issues, mtimc to file a bug
(pbrobinson, 14:46:18)
* aiming for a release early next week (pbrobinson, 14:48:28)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1648112
(pbrobinson, 14:49:00)
* 2) ==== Open Floor ==== (pbrobinson, 14:49:12)
* LINK: https://github.com/coreos/coreos-assembler (lorbus,
14:50:34)
* LINK: https://pagure.io/workstation-ostree-config/pull-request/109
(lorbus, 14:51:53)
Meeting ended at 15:00:55 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* pbrobinson (65)
* pwhalen (34)
* mtimc (25)
* lorbus (19)
* zodbot (7)
* jsmith (2)
* ipcloud (1)
* bcotton (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
5 years, 3 months
Fedora IoT 29 RC
by Peter Robinson
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
sustainable means:
1) initial-setup hangs during boot after IoT installation
https://bugzilla.redhat.com/show_bug.cgi?id=1646568
2) ttyAMA ttyAMA0: tty_open: tty->count(2) != (#fd's(1) + #kopen's(0))
https://bugzilla.redhat.com/show_bug.cgi?id=1644884
3) The 35network-legacy is still used even if network-scripts isn't
installed in Fedora 29
https://github.com/dracutdevs/dracut/issues/488
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
https://bugzilla.redhat.com/show_bug.cgi?id=1648112
5) WARNING at drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()!
https://bugzilla.redhat.com/show_bug.cgi?id=1644873
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
/etc/ostree/remotes.d/fedora-iot.conf
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
provide feedback.
Peter
5 years, 3 months
Fedora IoT - x86_64 ; rpm-ostree update 99%
by Douglas E. Hopley Jr.
I have a machine that boots to 29.20181113.0
Running `rpm-ostree update`
starts
runs
reports ...:
'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?
\
5 years, 3 months
Fedora IoT -Rasberry Pi 3B+ ; boot issue ; 20181120 ;
by Douglas E. Hopley Jr.
Greetings.
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
that correct?
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.
Best,
Doug
5 years, 3 months
timelag from upstream
by Tim Coote
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.
tc
5 years, 3 months