IoT February 2021

iot@lists.fedoraproject.org

7 participants
13 discussions

Swapping to compressed memory by default
by Peter Oliver 09 Mar '21

09 Mar '21

I just installed Fedora IoT edition for the first time, version 33, and was surprised that by default there was no swap to compressed memory. I understand that other Fedora editions have been enabling this, and it seems like something that would be of particular benefit to small devices with slow storage. It was straightforward to enable this myself (rpm-ostree install zram-generator-defaults), but I wondered if it was an oversight that this is not installed by default?

2 3

Fedora IoT Working Group Meeting Minutes 2021-02-24
by Paul Whalen 24 Feb '21

24 Feb '21

================================================= #fedora-meeting: Fedora IoT Working Group Meeting ================================================= Meeting started by pwhalen at 15:00:22 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2021-02-24/fedora_iot_work… . Meeting summary --------------- * roll call (pwhalen, 15:00:23) * 1) ==== Working Group process and admin ==== (pwhalen, 15:05:33) * LINK: https://docs.fedoraproject.org/en-US/iot/ (pwhalen, 15:05:33) * LINK: https://docs.fedoraproject.org/en-US/iot/ (pwhalen, 15:07:21) * 2) ==== Fedora 33 status ==== (pwhalen, 15:08:05) * Latest - Fedora-IoT-33-20210224.0 (pwhalen, 15:08:18) * LINK: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=33&bu… (pwhalen, 15:08:18) * Yellow results are AVC's, pwhalen to follow up and file some bugs. (pwhalen, 15:08:36) * 3) ==== Fedora 34 status ==== (pwhalen, 15:11:54) * Latest compose Fedora-IoT-34-20210222 (pwhalen, 15:12:10) * LINK: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=34&bu… (pwhalen, 15:12:10) * ARMv7 looking good. No issues with layered packages, podman on the RPi3. Wider testing appreciated. (pwhalen, 15:14:12) * 4) ==== Fedora 35 (Rawhide) status ==== (pwhalen, 15:19:09) * Latest compose Fedora-IoT-35-20210224.0 (pwhalen, 15:19:19) * LINK: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&bu… (pwhalen, 15:19:19) * 5) ==== Open Floor ==== (pwhalen, 15:21:51) Meeting ended at 15:24:02 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (42) * coremodule (10) * zodbot (6) * bcotton (0) * pbrobinson (0) * tdawson (0) * puiterwijk (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting
by pwhalen＠fedoraproject.org 23 Feb '21

23 Feb '21

Dear all, You are kindly invited to the meeting: IoT Working Group weekly meeting on 2021-02-24 from 15:00:00 to 16:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Fedora IoT weekly status meeting. More information available at: [https://pagure.io/fedora-iot/](https://pagure.io/fedora-iot/) Source: https://apps.fedoraproject.org/calendar/meeting/9244/

1 0

Several Fedora IoT development/deployment questions
by Paul Graham 20 Feb '21

20 Feb '21

I apologize if these are clearly answered elsewhere, but I had several questions about developing using Fedora IoT and deploying Fedora IoT. Before asking the questions, though, I do have to say "thank you" for the work on this. The ideas and approaches look innovative and it is nice to have this sort of development in a community project. First, if I wanted to try out Fedora IoT on a piece of hardware with a custom kernel, what would be the right method to try out the custom kernel? In the past when using Fedora ARM, I could control the kernel that U-Boot loaded directly. With Fedora IoT, though, it isn't clear to me how to try this out without breaking the boot process. Likewise, how would I try out some custom boot loaders and device trees? I am assuming that the process of trying these out with Fedora IoT might be similar to using a custom kernel. I am looking at a few different aarch64 devices and boards with special built-in security features that could be used at boot time for validating firmware and software (without a TPM). Further, there will likely be a need to support some custom I2C and SPI devices on these boards, which would require (based on past experience with arm7hl boards) custom device trees. I have read through the libostree documentation (https://ostreedev.github.io/ostree/) and it gave me a few ideas on how individual files are managed, but I am still coming up to speed on libostree systems. One additional question is how would I set up a repository mirror for Fedora IoT so that I could feed updates to IoT devices that are on a private network (i.e., don't have direct access to the usual Fedora IoT repositories)? I am assuming that I would also have to also update the repository information somehow on the IoT devices themselves. Guidance on how to do that would also be greatly appreciated. Along these lines, I would like to control the particular updates that roll into the update repository so that only those updates/snapshots that are tested and work well on the target hardware make it into the local mirrored update repository. Is there a simple way to manage this? Finally, how does Fedora IoT handle transitions in the base Fedora distribution. Does it simply move forward (for example, from Fedora 33 to Fedora 34) on Fedora IoT devices without additional intervention or does the person managing the Fedora IoT device have to explicitly do something to transition from a Fedora IoT 33 base to a Fedora IoT 34 base, for example? I apologize for all of the questions and if I missed it in the documentation. Thanks! Paul

2 1

Pine64 Rockpro64
by Aaron Siegel 20 Feb '21

20 Feb '21

Hello I am stuck, I cannot install Fedora on a rockpro64. I have tried arm-image- installer and with U-Boot installed on the SPI using the iso installer. The arm-image-installer does not boot, I receive the error as described in this blog: https://marcin.juszkiewicz.com.pl/2020/06/22/installing-fedora-on-rockpro64/ When I mount the SD cards efi partition on a desktop I receive an I/O error message and cannot read the EFI directory. I have also load U-Boot on the SPI using the instruction below. I am able to boot the Fedora IOT 20210214 iso and complete most of the installation but at the end I receive error: "The following error occurred while installing the boot loader. The system will not be bootable. Would you like to ignore this and continue with installation? Failed to set new EFI boot target this is most likely a kernel or firmware bug." Has anyone had successfully installed Fedora IOT on a Rockpro64? The message when trying to boot with U-Boot loaded into the SPI U-Boot 2020.07-rc4-00056-g0ce4047820 (Jun 17 2020 - 16:46:23 +0200) SoC: Rockchip rk3399 Reset cause: POR Model: Pine64 RockPro64 v2.1 DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from SPI Flash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial Out: vidconsole Err: vidconsole Model: Pine64 RockPro64 v2.1 Net: eth0: ethernet@fe300000 starting USB... Bus usb@fe380000: USB EHCI 1.00 Bus usb@fe3a0000: USB OHCI 1.0 Bus usb@fe3c0000: USB EHCI 1.00 Bus usb@fe3e0000: USB OHCI 1.0 Bus dwc3: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 Bus dwc3: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe380000 for devices... 1 USB Device(s) found scanning bus usb@fe3a0000 for devices... 2 USB Device(s) found scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found scanning bus usb@fe3e0000 for devices... 2 USB Device(s) found scanning bus dwc3 for devices... 1 USB Device(s) found scanning bus dwc3 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found EFI removable media binary efi/boot/bootaa64.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Card did not respond to voltage select! Scanning disk mmc(a)fe310000.blk... Disk mmc(a)fe310000.blk not ready Card did not respond to voltage select! Scanning disk mmc(a)fe320000.blk... Disk mmc(a)fe320000.blk not ready Scanning disk sdhci(a)fe330000.blk... ** Unrecognized filesystem type ** Found 4 disks BootOrder not defined EFI boot manager: Cannot load any image 858216 bytes read in 108 ms (7.6 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC System BootOrder not found. Initializing defaults. Could not read \EFI\: Invalid Parameter Error: could not find boot options: Invalid Parameter start_image() returned Invalid Parameter ## Application terminated, r = 2 EFI LOAD FAILED: continuing... Card did not respond to voltage select! PCIe link training gen1 timeout! Device 0: unknown device Device 0: unknown device failed to find ep-gpios property Thank you Aaron

2 1

Fedora IoT Working Group Meeting Minutes - 2021-02-17
by Paul Whalen 17 Feb '21

17 Feb '21

================================================= #fedora-meeting: Fedora IoT Working Group Meeting ================================================= Meeting started by pwhalen at 15:00:42 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2021-02-17/fedora_iot_work… . Meeting summary --------------- * roll call (pwhalen, 15:00:42) * 1) ==== Working Group process and admin ==== (pwhalen, 15:04:09) * LINK: https://docs.fedoraproject.org/en-US/iot/ (pwhalen, 15:04:09) * No changes. (pwhalen, 15:05:59) * 2) ==== Fedora 33 status ==== (pwhalen, 15:06:06) * Latest - Fedora-IoT-33-20210214.0 (pwhalen, 15:06:15) * LINK: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=33&bu… (pwhalen, 15:06:15) * No new issues reported. (pwhalen, 15:08:12) * 3) ==== Fedora 34 status ==== (pwhalen, 15:08:43) * Latest compose Fedora-IoT-34-20210215 (pwhalen, 15:08:51) * LINK: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=34&bu… (pwhalen, 15:08:52) * Parsec fixes in progress, waiting for a new parsec daemon to fix the last bits. (pwhalen, 15:12:08) * 4) ==== Fedora 35 (Rawhide) status ==== (pwhalen, 15:19:43) * LINK: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=35&bu… (pwhalen, 15:22:05) * 5) ==== Open Floor ==== (pwhalen, 15:23:31) Meeting ended at 15:40:48 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (52) * pbrobinson (32) * coremodule (29) * zodbot (9) * jsmith (7) * tdawson (3) * bcotton (2) * puiterwijk (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting
by pwhalen＠fedoraproject.org 16 Feb '21

16 Feb '21

Dear all, You are kindly invited to the meeting: IoT Working Group weekly meeting on 2021-02-17 from 15:00:00 to 16:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Fedora IoT weekly status meeting. More information available at: [https://pagure.io/fedora-iot/](https://pagure.io/fedora-iot/) Source: https://apps.fedoraproject.org/calendar/meeting/9244/

1 0

HEADS UP: Fedora 34 branched off from rawhide
by Peter Robinson 15 Feb '21

15 Feb '21

Hey All, Just a heads up that the rawhide branch is what will now become Fedora 35. Fedora 34 content can be found on the devel branch. Details for rebasing can be found in: https://docs.fedoraproject.org/en-US/iot/rebasing/ Let me know of any issues you may find. Peter

1 0

Fedora IoT Working Group Meeting Minutes 2021-02-10-15
by Paul Whalen 10 Feb '21

10 Feb '21

================================================= #fedora-meeting: Fedora IoT Working Group Meeting ================================================= Meeting started by pwhalen at 15:01:14 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2021-02-10/fedora_iot_work… . Meeting summary --------------- * roll call (pwhalen, 15:01:14) * 1) ==== Working Group process and admin ==== (pwhalen, 15:02:35) * 2) ==== Fedora 33 status ==== (pwhalen, 15:04:12) * Latest - Fedora-IoT-33-20210128.0 (pwhalen, 15:04:58) * LINK: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=33&bu… (pwhalen, 15:04:58) * Upgrade removes all overrides - https://bugzilla.redhat.com/show_bug.cgi?id=1925717 (pwhalen, 15:09:30) * 3) ==== Fedora 34 (Rawhide) status ==== (pwhalen, 15:11:22) * Fedora 34 IoT Edition branching to be completed today. (pwhalen, 15:12:18) * Latest compose Fedora-IoT-34-20210208.0 (pwhalen, 15:12:48) * LINK: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=34&bu… (pwhalen, 15:12:48) * Podman failure fixed with kernel-5.11.0-0.rc7.149.fc34 (pwhalen, 15:13:06) * 4) ==== Open Floor ==== (pwhalen, 15:25:10) Meeting ended at 15:40:00 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (45) * coremodule (20) * pbrobinson (13) * zodbot (7) * jsmith (4) * bcotton (1) * tdawson (0) * puiterwijk (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[Fedocal] Reminder meeting : IoT Working Group weekly meeting
by pwhalen＠fedoraproject.org 09 Feb '21

09 Feb '21

Dear all, You are kindly invited to the meeting: IoT Working Group weekly meeting on 2021-02-10 from 15:00:00 to 16:00:00 UTC At fedora-meeting(a)irc.freenode.net The meeting will be about: Fedora IoT weekly status meeting. More information available at: [https://pagure.io/fedora-iot/](https://pagure.io/fedora-iot/) Source: https://apps.fedoraproject.org/calendar/meeting/9244/

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

IoT February 2021