arm January 2022

arm@lists.fedoraproject.org

14 participants
19 discussions

Kernel update -> 5.15.13-200.fc35.aarch64
by David W. Legg 15 Jan '22

15 Jan '22

Enthused by my success with getting Fedora 35 going on mu rpi4, I thought I would try an update :) Starting from Fedora-Minimal-35-1.2.aarch64.raw.xz, I tried to upgrade the kernel from 5.14.10-300.fc35.aarch64 to 5.15.13-200.fc35.aarch64. So, I did a(n) rpi-uboot-update then dnf update kernel -y init 0 Power off/on Connect HDMI monitor, and *nothing* after the grub spiel. Just sayin', in case it helps anyone :(

2 2

Moving headless install from 2GB rpi4 to 4GB rpi4
by David W. Legg 14 Jan '22

14 Jan '22

Just wondering why my attempt to move a working headless Fedora 34 build from a 2 GB rpi4 to a 4 GB rpi4 fails even to boot. In fact, it never even puts out the steady red LED. I copied the micro SD card (from the 2 GB pi) directly over USB and wrote the build to another SD card using dd using a set of commands that has always been reliable in the past. Any thoughts, please?

7 10

How to install Fedora and MicroShift on the NVIDIA Jetson AGX Xavier
by John Walicki 13 Jan '22

13 Jan '22

Great article detailing how to install NVIDIA using the new UEFI/ACPI Experimental Firmware 1.1.2 for Jetson AGX Xavier and Jetson Xavier NX. https://egallen.com/nvidia-jetson-agx-xavier-fedora-arm-microshift/

1 0

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

12 Jan '22

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2022-01-11 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/

2 1

Re: Moving headless install from 2GB rpi4 to 4GB rpi4
by David W. Legg 10 Jan '22

10 Jan '22

(parted) p free Model: Generic Mass-Storage (scsi) Disk /dev/sdf: 31.9GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1024B 1049kB 1048kB Free Space 1 1049kB 630MB 629MB primary fat32 boot 2 630MB 1704MB 1074MB primary ext4 3 1704MB 8514MB 6811MB primary ext4 8514MB 31.9GB 23.4GB Free Space On 09/01/2022 16:44, Dennis Gilmore wrote: > Subject: > Re: [fedora-arm] Re: Moving headless install from 2GB rpi4 to 4GB rpi4 > From: > Dennis Gilmore <dennis(a)ausil.us> > Date: > 09/01/2022, 16:44 > > To: > David Legg <dwlegg(a)gmail.com> > > > I would then use parted to check that if it thinks the disk is valid. > In cases like this, I always copy the whole disk. > > Dennis > > On Sun, Jan 9, 2022 at 8:07 AM David Legg<dwlegg(a)gmail.com> wrote: >> The count is to avoid copying the whole card. I use 9000 going both ways so that it can't go wrong, i.e. get chopped >> Good thought, though. Thanks. >> >> On Sun, 9 Jan 2022, 13:35 Dennis Gilmore,<dennis(a)ausil.us> wrote: >>> Adding count probably cut the image short, it is not necessary, I generally always us bs=4MiB >>> >>> Dennis >>> >>> On Sun, Jan 9, 2022, 03:54 David W. Legg<dwlegg(a)gmail.com> wrote: >>>> Well, I copied the card from the 2GB rpi4 using: >>>> >>>> dd if=/dev/sdf of=card.img bs=1M count=9000 status=progress >>>> >>>> and wrote another card using the reverse command: >>>> >>>> dd if=card.img of=/dev/sdf bs=1M count=9000 status=progress >>>> >>>> So, I expected it just to*work* when I put the card into a brand new >>>> 4GB rpi4. >>>> >>>> Alas, all I get is the steady red LED and a handful of flashes from the >>>> yellow ACT LED. The 2 Ethernet LEDs come on steadily too. >>>> >>>> That's why I was asking whether you experts would know about going from >>>> a 2GB to 4GB machine would normally just*work* or not. >>>> >>>> Thanks in advance for any insights. >>>> >>>> :D >>>> >>>> On 08/01/2022 21:59, Nathan Giovannini wrote: >>>>> Subject: >>>>> Re: [fedora-arm] Re: Moving headless install from 2GB rpi4 to 4GB rpi4 >>>>> From: >>>>> Nathan Giovannini<nathan95(a)live.it> >>>>> Date: >>>>> 08/01/2022, 21:59 >>>>> >>>>> To: >>>>> Peter Robinson<pbrobinson(a)gmail.com> >>>>> CC: >>>>> "dwlegg(a)gmail.com" <dwlegg(a)gmail.com>,"arm(a)lists.fedoraproject.org" >>>>> <arm(a)lists.fedoraproject.org> >>>>> >>>>> >>>>> Could you provide more details.... >>>>> >>>>> This will make it easier to help you. >>>>> >>>>>> Il giorno 8 gen 2022, alle ore 21:14, Peter Robinson<pbrobinson(a)gmail.com> ha scritto: >>>>>> >>>>>> On Sat, Jan 8, 2022 at 8:09 PM David W. Legg<dwlegg(a)gmail.com> wrote: >>>>>>> Just wondering why my attempt to move a working headless Fedora 34 build >>>>>>> from a 2 GB rpi4 to a 4 GB rpi4 fails even to boot. In fact, it never >>>>>>> even puts out the steady red LED. I copied the micro SD card (from the 2 >>>>>>> GB pi) directly over USB and wrote the build to another SD card using dd >>>>>>> using a set of commands that has always been reliable in the past. >>>>>>> >>>>>>> Any thoughts, please? >>>>>> Why not just physically move the SD card from one to the other? >>>>>> >>>>>> It's ultimately hard to know why without including the commands you >>>>>> used as what you describe is a fairly high level overview. >>>>>> _______________________________________________ >>>>>> arm mailing list --arm(a)lists.fedoraproject.org >>>>>> To unsubscribe send an emailtoarm-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/arm@lists.fedoraproj… >>>>>> Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure >>>> _______________________________________________ >>>> arm mailing list --arm(a)lists.fedoraproject.org >>>> To unsubscribe send an email toarm-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/arm@lists.fedoraproj… >>>> Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure

1 0

Grub slow at loading kernel and initrd
by Michael Whapples 10 Jan '22

10 Jan '22

Hello, I have been using fedora on my Odroid XU4 for some time (well over a year) and its generally been working well. I had been updating the install to the latest Fedora release as they came out. Recently though I decided to start with a fresh image of Fedora 35 and I noticed that it was very slow for grub to load the kernel and initrd (I haven't timed it but well over a minute). To check that it definitely was kernel and initrd loading I edited the menu item and inserted echo commands around the linux and initrd lines. Previously with the old Fedora install using the extlinux.conf boot configuration there was no such delay and the system could be fully booted in less time than it takes grub to load the kernel and initrd on the new install. Also with the new install I have tried manually starting the kernel and initrd from uboot, both the old bootz and the EFI bootefi commands, and neither of these have the delay I notice with grub. When I have searched online for a solution, I have found some reports of grub being slow to load the kernel, but no real answers as how to fix it. So my questions are: 1. Does anyone know how to solve this? Hints on how to debug grub and what is going on would also be welcome. 2. As I can still get a installation using the extlinux.conf configuration instead of grub (either by installing an old version and upgrading or by booting the Everything installer in non-EFI mode), is this likely to be supported for much longer and is this really a sensible route to take? Thanks for any help which can be given on this one. Michael Whapples

2 2

Re: Moving headless install from 2GB rpi4 to 4GB rpi4
by David W. Legg 10 Jan '22

10 Jan '22

Well, I copied the card from the 2GB rpi4 using: dd if=/dev/sdf of=card.img bs=1M count=9000 status=progress and wrote another card using the reverse command: dd if=card.img of=/dev/sdf bs=1M count=9000 status=progress So, I expected it just to *work* when I put the card into a brand new 4GB rpi4. Alas, all I get is the steady red LED and a handful of flashes from the yellow ACT LED. The 2 Ethernet LEDs come on steadily too. That's why I was asking whether you experts would know about going from a 2GB to 4GB machine would normally just *work* or not. Thanks in advance for any insights. :D On 08/01/2022 21:59, Nathan Giovannini wrote: > Subject: > Re: [fedora-arm] Re: Moving headless install from 2GB rpi4 to 4GB rpi4 > From: > Nathan Giovannini <nathan95(a)live.it> > Date: > 08/01/2022, 21:59 > > To: > Peter Robinson <pbrobinson(a)gmail.com> > CC: > "dwlegg(a)gmail.com" <dwlegg(a)gmail.com>, "arm(a)lists.fedoraproject.org" > <arm(a)lists.fedoraproject.org> > > > Could you provide more details.... > > This will make it easier to help you. > >> Il giorno 8 gen 2022, alle ore 21:14, Peter Robinson<pbrobinson(a)gmail.com> ha scritto: >> >> On Sat, Jan 8, 2022 at 8:09 PM David W. Legg<dwlegg(a)gmail.com> wrote: >>> Just wondering why my attempt to move a working headless Fedora 34 build >>> from a 2 GB rpi4 to a 4 GB rpi4 fails even to boot. In fact, it never >>> even puts out the steady red LED. I copied the micro SD card (from the 2 >>> GB pi) directly over USB and wrote the build to another SD card using dd >>> using a set of commands that has always been reliable in the past. >>> >>> Any thoughts, please? >> Why not just physically move the SD card from one to the other? >> >> It's ultimately hard to know why without including the commands you >> used as what you describe is a fairly high level overview. >> _______________________________________________ >> arm mailing list --arm(a)lists.fedoraproject.org >> To unsubscribe send an email toarm-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/arm@lists.fedoraproj… >> Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure

2 1

issue booting Fedora 35 with RPI4
by RENARD Pierre-Francois 05 Jan '22

05 Jan '22

Hello guys, I have been working on a very strange issue when booting Fedora 35 on RPI4. I have the issue on 5 different RPI 4 boards, I have tried to swap power, network cable, network port, network switch, even use a new sd card/ssd drives.... 1/ I use the arm-image-installer with target=rpi4 and the last F35 aarch64 raw image to flash a SD Card. 2/ I boot the new system and it is working fine 3/ I updated the system with dnf -y upgrade 4/ I move the system VG (fedora_fedora) on a SSD drive connected using USB-SATA converter. and then use "dracut --force" to make the system working fine. 5/ reboot is ok after that and the system is running well. I discovered after many tests that when the USB-SATA is connected on one of the 2 USB2 ports (en the left side) that the system is booting well. but if you connect on the USB3 ports (between USB2 and ethernet port) the system is not booting.... but if in this configuration you have a HDMI port connected to a monitor, then the system is booting well.... to sum up USB-SATA : USB2 => booting ok USB-SATA : USB3 => not booting USB-SATA : USB3 + HDMI : connected to monitor => booting ok I used theses systems to test ESXI arm edition and everything was working fine using USB3 ports without any HDMI port used. I found the following posts (https://forums.raspberrypi.com/viewtopic.php?t=245767, https://forums.raspberrypi.com/viewtopic.php?f=28&t=245323) and tried to append "usb_storage.quirks=174c:0825:u" using grubby --args="usb_storage.quirks=174c:0825:u" --update-kernel /boot/vmlinuz-5.15.12-200.fc35.aarch64 but it seams to have no effect ... the system is not booting When I plug back the HDMI port, from dmesg I see that [ 0.000000] Kernel command line: BOOT_IMAGE=(hd1,msdos2)/vmlinuz-5.15.12-200.fc35.aarch64 root=/dev/mapper/fedora_fedora-root r o rd.lvm.lv=fedora_fedora/root rhgb quiet console=tty0 usb_storage.quirks=174c:0825:u [ 6.677469] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd [ 6.708417] usb 2-2: New USB device found, idVendor=174c, idProduct=0825, bcdDevice= 0.20 [ 6.708445] usb 2-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 6.708456] usb 2-2: Product: X825 [ 6.708464] usb 2-2: Manufacturer: SupTronics [ 6.708472] usb 2-2: SerialNumber: 20210300005A [ 6.773292] usb 2-2: UAS is ignored for this device, using usb-storage instead [ 6.773317] usb-storage 2-2:1.0: USB Mass Storage device detected [ 6.773902] usb-storage 2-2:1.0: Quirks match for vid 174c pid 0825: 800000 [ 6.774078] scsi host0: usb-storage 2-2:1.0 Did I do something wrong, do you have any idea ? Thanks Fox

2 2

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠fedoraproject.org 03 Jan '22

03 Jan '22

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2022-01-04 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm January 2022