Arm-dev May 2021

arm-dev@lists.centos.org

5 participants
7 discussions

AArch64 Pi4 and CentOS 8
by Brent Kolasinski 31 Oct '25

31 Oct '25

Hi everyone, I've been looking into things I can do to help with getting CentOS 8 AArch64 to run on the Pi4. It appears that the upstream kernel now has the proper stuff merged in to support the NIC and eMMC controller. So far 2 approaches are being made: The U-Boot mechanism (looks like this is what Ubuntu 20.04 is doing) and the SBBR (ACPI + UEFI) way. It looks like a few folks may be loading the SBBR firmware with luck on the standard CentOS 8 aarch64 image. Could one potentially recompile the SRPM for kernel 5.6 from elrepo and drop it in? I found the CentOS8 pi4 aarch64 userland image here: https://people.centos.org/pgreco. Has anyone tried getting the SBBR firmware to load the stock aarch64 CentOS 8 image without support for the eMMC / NIC, to basically bootstrap and compile the SRPM for the 5.6 kernel? And finally does anyone know if CentOS will be backporting the Pi4 changes to 4.18, or will they be releasing a custom kernel? Could I help out with that?

5 5

rng-tools missing and /dev/hwrng without driver
by SW＠EU 31 Oct '25

31 Oct '25

Hi, today I will report a problem that is released to ipa-server. This server contains a certificate authority and such service need many entropy. The default on CentOS 7 on a Banana PI is not enough, i.e. $(cat /proc/sys/kernel/random/entropy_avail) is less than 1000. I have solved this in meantime by installing and enabling of haveged from the EPEL repository. Normally it would be done by installing the rng-tools. But there are two problems: 1. The rng-tools was not in the repositories, so I have downloaded rng-tools-5-8.fc24.armv7hl.rpm because this are the same version which is included in CentOS 7.3 for x86_64. 2. This rng-tools are usable but the daemon starts and stops immediately with the following error message: # rngd -v /dev/hwrng: No such device /dev/tpm0: No such file or directory No entropy sources found, exiting This is not the problem of this binary it is a problem of the Kernel. /dev/hwrng exists and if I remove it then it reappears after reboot, but # ls -l /dev/hwrng crw-------. 1 root root 10, 183 1. Jan 1970 /dev/hwrng # udevadm info -a -n /dev/hwrng Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/virtual/misc/hw_random': KERNEL=="hw_random" SUBSYSTEM=="misc" DRIVER=="" ATTR{rng_current}=="none" ATTR{rng_available}=="" there is no driver for this device. I have searched and found this link http://forum.lemaker.org/thread-23618-1-1.html which includes a link to the full story. If I read all right then on bananian /dev/hwrng appears only if the adapted or a more actual sun4i-ss.ko module is loaded (there is written: "module author has indicated this will be going into the mainline kernel shortly“). This module is also loaded on a Banana PI with current CentOS 7. So does the kernel of CentOS 7.3 for ARM32 include this patch and if yes why it does not work or otherwise why this device appears but has no driver? TIA, Silvio Sent with [ProtonMail](https://protonmail.com) Secure Email.

4 5

EPEL repo not available?
by Boyd Ako 31 Oct '25

31 Oct '25

Can anybody verify that the EPEL repo for ARMHFP isn’t available? I keep getting an error saying the REPOMD file isn’t there when running yum. It works if I use —disablerepo=epel\* when using yum. But, there might be some stuff in the EPEL that I’m looking for. Running it on a Raspberry Pi 3 and trying to get Nagios installed for home use. Domo, Boyd H. Ako boyd.hanalei.ako(a)gmail.com (424) 244-9653 https://www.boydhanaleiako.me “Coming together is a beginning. Keeping together is progress. Working together is success.” -Henry Ford PGP/GPG Public Key: https://sks-keyservers.net/pks/lookup?op=get&search=0xC58073B21618F134

5 4

Gigabyte MP30-AR0
by Gordan Bobic 31 Oct '25

31 Oct '25

Hi, I am toying with the idea of getting a Gigabyte MP30-AR0 board (despite the insanely exorbitant price tag). Has anyone got the aarch64 CentOS working on one of those? Any special instructions? Also, if I get the ISO, is it bootable on aarch64? Does the installer work? Or does the image have to be used like on 32-bit ARM? Thanks. Gordan

18 208

Re: [Arm-dev] Consider updating uboot-tools
by mark 21 May '21

21 May '21

-----Original message----- > From: Pablo Sebastián Greco <pablo(a)fliagreco.com.ar> > Sent: Friday May 21st, 2021 13:20 > To: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org>; mark <mark(a)havak.nl> > Subject: Re: [Arm-dev] Consider updating uboot-tools > > > On 20/5/21 14:29, mark wrote: > > Hello list (maintainer of uboot-tools), > > > > I'd like to bring a nice enhancement of u-boot to you attention; > > looks like with commit (1) u-boot will call the efi boot manager before > falling back to the default removable-media location: > > EFI/BOOT on the (fat32) efi partition > > > > If I understand correctly this would take care of the fedora-path patch > issue still carried in CentOS u-boot. > > As a matter of fact fedora dropped the uefi-use-Fedora-specific-path-name.patch > (2) > > > > As per subject: IMHO this is a extra incentive to update the fairly old > uboot-tools :) > > > > > > (1) > > https://github.com/u-boot/u-boot/commit/f3866909e35074ea6f50226d40487a180de… > > > > (2) > > https://src.fedoraproject.org/rpms/uboot-tools/c/6209cab21ad85061b66d6be412… > > Hello Mark, > > Updating uboot has been in my to-do list for a while and it keeps being > delayed due to lack of time. My main problem is that I try to build it > for 7 and 8, armhfp/aarch64 and there are some tools that I need to > backport from Fedora to correctly do that. el8 aarch64 is a bit problematic, the now quite popular aarch64(Rockchip) rk3399 needs a arm 32bit cross compiler, until now used a hack to pull it from epel-7 as it is not present in epel-8. Recently rebuild the cross-toolchian from FC29 (cross-gcc-8.1.1-3) as this fits the major versioning of binutils 2.30.x . Also the device tree compiler in el8 does not ship the python3 wrappers needed to build uboot-tools, Hence did rebuild dtc with the python3 wrapper packaged. Again, as far as I know the above only applies to el8. > I have some PoC tools from a few months ago that I'll try to revive, > we'll see how that goes. Let me know if I can be of some help here! > > Thanks. > Pablo. > >

1 0

Consider updating uboot-tools
by mark 21 May '21

21 May '21

Hello list (maintainer of uboot-tools), I'd like to bring a nice enhancement of u-boot to you attention; looks like with commit (1) u-boot will call the efi boot manager before falling back to the default removable-media location: EFI/BOOT on the (fat32) efi partition If I understand correctly this would take care of the fedora-path patch issue still carried in CentOS u-boot. As a matter of fact fedora dropped the uefi-use-Fedora-specific-path-name.patch (2) As per subject: IMHO this is a extra incentive to update the fairly old uboot-tools :) (1) https://github.com/u-boot/u-boot/commit/f3866909e35074ea6f50226d40487a180de… (2) https://src.fedoraproject.org/rpms/uboot-tools/c/6209cab21ad85061b66d6be412…

2 1

Centos 7.9 weird firewall/application issue
by R C 10 May '21

10 May '21

Hello, I have a weird issue with the firewall running (Centos 7.9) wit an application. The application pulls data from an Ad-converter card, via USB, and sends the data to a db server using curl. (via a wireless device that is plugged into USB. When the firewall is running I get all kinds of weird errors (in that application), usb-port related BUT when the firewall is not running, it works just fine. (I wonder if it is a memory issue?) any ideas here? thanks, Ron

3 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev May 2021