Okay, so, my holiday hobby project is setting up Fedora IoT as a home gateway
device. Gonna control some Z-wave devices and Ecobee thermostats and
I have a Rock960 device as suggested by
And I'm following
... where I immediately ran into two problems.
First, there's no link to where to download the image. I know there's
website in (slow) development, but in the meantime, shouldn't we link to
Second, despite being listed as a reference platform, there's no "rocks960".
I discovered that the arm-image-installer program actually works *without*
target, but that's not at all clear from the docs.
Fedora Project Leader
We've discussed my packaging of gateway  in our weekly IOT
meetings. The decision was made to have it bundle all the
dependencies, and that's what I've been trying to do. It looks like
there are over 1100 node modules required for this. (Nope, that isn't
packages. Several of them are binary. So that means I need to
download the modules to bundle them, and then build them in koji. By
using yarn, instead of npm install, I've been able to do that, because
yarn has an --offline mode.
Then there is/was the problem with babel-core. During the bundling we
kept ending up with 6.25.0 I believe due to the package.json wanting
7.0.0-beta.49. When it came to building in koji, yarn would freek out
because it wanted to download a newer babel-core, but it was in
offline mode. (Even if it did download the new package, it would
still end up with 6.25.0). So in the end, I hacked package.json so
that it wants 7.2.2 of babel-core.
Ya ... so now it builds on x86_64 in koji.
But ... it now *only* builds on x86_64 in koji 
I'm putting this up in this email so others can join in the fun if they want.
Here is the source rpm I have, the one that build the scratch build.
Here is the script I use to make the bundled tarball.
You need to have nodejs-yarn installed to run the tarball bundling script.
I'm going to give this another shot, but any help is appreciated.
 - https://github.com/mozilla-iot/gateway/
 - https://koji.fedoraproject.org/koji/taskinfo?taskID=31522050
 - https://tdawson.fedorapeople.org/gateway/gateway-0.6.1-1.fc29.src.rpm
 - https://tdawson.fedorapeople.org/gateway/gateway-tarball.sh
I've just upgraded to RC2 on Pi 3B+ from an earlier nightly, so used
the rebase instructions (had to manually add the GPG key, but otherwise was fine)
Now I don't have wifi at all - 'ip a' just lists eth0 an lo, nmcli can't see a wifi
Most searches then go on to iwconfig/lsusb but these aren't in the base image
Are there any debugging instructions? Didn't see a smoking gun in dmesg/journalctl,
but not sure what to look for.
Good morning folks,
Many of you may have already noticed that RC2 is available for download
If you are already using RC1 you can upgrade by running:
If you are using one of the earlier nightlies you can upgrade by running:
sed -i 's|RPM-GPG-KEY-fedora-29-primary|RPM-GPG-KEY-fedora-iot-2019|g' /etc/ostree/remotes.d/fedora-iot.conf
rpm-ostree rebase -b fedora/stable/$ARCH/iot
The RC2 fixes some issues identified in RC1:
1) tpm2-tools and clevis not in the initramfs. This appears to be fixed but
additional testing welcome.
2) Installations from ISO still use the old GPG key. Fixed in RC2.
3) console=tty0 included on the kargs on aarch64 disk images. Unfortunately
this still affects RC2. After the system is booted it can be removed by
rpm-ostree kargs --delete=console=tty0
It would be greatly appreciated if people could test this as much as possible
and let us know if they see any other issues.