arm September 2021

arm@lists.fedoraproject.org

16 participants
17 discussions

Add LUKS disk to an Raspberry Pi 4 install
by Barry Scott 18 Sep '21

18 Sep '21

I'm trying to build a RPi4 system that uses a LUKS encrypted disk. But I cannot get the volume to be unlocked when the system boots. I have install Fedora-Minimal-34-1.2.aarch64.raw.xz to with arm-image-installer --target=rpi4 and that boots. That I have added a new partition to that sdcard that I setup using this command from Fedora 34 x86_86 system. cryptsetup \ --type luks2 \ --cipher xchacha20,aes-adiantum-plain64 \ --hash sha256 \ --iter-time 5000 \ --pbkdf argon2i \ luksFormat ${DEVICE} I got these settings from a blog on setting up crypt for debian on raspberry pi. I add an entry to /etc/crypttab for the volume. When I boot the system I am not prompted for the password to unlock the volume as I was expecting. Looking in journalctl -b 0 I see these lines: Apr 06 01:01:36 clef.chelsea.private systemd[1]: dev-disk- by\x2duuid-8c2519ae\x2d78a9\x2d44b0\x2d871f\x2d0aa2422de03a.device: Job dev- disk-by\x2duuid-8c2519ae\x2d78a9\x2d44b0\x2d871f\x2d0aa2422de03a.device/start timed out. Apr 06 01:01:36 clef.chelsea.private systemd[1]: Timed out waiting for device /dev/disk/by-uuid/8c2519ae-78a9-44b0-871f-0aa2422de03a. Apr 06 01:01:36 clef.chelsea.private systemd[1]: Dependency failed for Cryptography Setup for clef-root. Apr 06 01:01:36 clef.chelsea.private systemd[1]: Dependency failed for Local Encrypted Volumes. Once I log in I can open the volume and mount it $ cryptsetup luksOpen /dev/mmcblk0p4 clef-root $ mount /dev/mapper/clef-root /mnt I have tried updating the initrd with: dracut --force. And also adding to the kernel command line: # cat /proc/cmdline BOOT_IMAGE=(hd0,msdos2)/vmlinuz-5.11.12-300.fc34.aarch64 root=UUID=67ca2085-9dab-405b-a042-ff6269816fbc ro rhgb quiet console=tty0 rd.luks.uuid=8c2519ae-78a9-44b0-871f-0aa2422de03a I have a other systems that use full disk encryption that work. But I have failed to spot the difference between the RPi config and the working systems config. Do you know what is missing or not configured? Hmm, just noticed that the kernel command says console is tty0. But when I log in on the console its tty1. Barry Just not

1 0

What if Fedora stopped building for 32-bit ARM (armv7hl) in F36+?
by Miro Hrončok 16 Sep '21

16 Sep '21

Hello, an interesting discussion is happening on the Fedora devel mailing list about possibly dropping 32-bit ARM (armv7hl) support: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… Before proceeding with the idea, I'd like to know what do the ARM people on this list think about it. Is it crazy, or is it about time? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

9 9

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠fedoraproject.org 12 Sep '21

12 Sep '21

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2021-09-14 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.libera.chat The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/9910/

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠fedoraproject.org 05 Sep '21

05 Sep '21

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2021-09-07 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.libera.chat The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/9910/

1 0

Re: The future of a Fedora LXQT Spin on Raspberry 3+?
by Joe 04 Sep '21

04 Sep '21

Sorry, I posted this to the wrong mailing list last night! On Sep 2, 2021, 10:45 PM, at 10:45 PM, information(a)josephpesco.info wrote: >I've been using LXQT on my rasp3+ since f33 and even forgot >I successfully upgraded to f34 on 03/24/21, but can't find >an f34 image. Is there an image available for f34 and will >one be made available for f35? > >Joe >_______________________________________________ >devel mailing list -- devel(a)lists.fedoraproject.org >To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org >Fedora Code of Conduct: >https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >List Archives: >https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org >Do not reply to spam on the list, report it: >https://pagure.io/fedora-infrastructure

4 3

grub2-2.06-4.fc35 is broken on 32-bit arm (armhfp)
by Paul Whalen 03 Sep '21

03 Sep '21

To those testing Fedora 35 on armhfp, The grub2 update in updates-testing (grub2-2.06-4.fc35) fixes a kernel alignment issue on AArch64, but unfortunately breaks the boot on 32-bit arm[1] and should be excluded when updating until a fixed build is available. Paul [1] - https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2000756

1 0

Dual kernels on Fedora-Server-netinst-armhpf iso
by John W. Himpel 01 Sep '21

01 Sep '21

The Fedora Server WG is working on resolving https://bugzilla.redhat.com/show_bug.cgi?id=1963007 . At today's Server WG group meeting, it was stated there are two different kernels on the armhfp iso's. A normal kernel and an LPAE kernel. I volunteered to ask this list if: 1) Are two kernels indeed being loaded onto the netinst-armhfp images 2) If the answer to #1 is yes, are both images needed? Thanks.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm September 2021