Arm-dev June 2020

arm-dev@lists.centos.org

9 participants
11 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?

4 4

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.

3 4

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

4 3

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

13 203

centos 7 64 bit on raspberry Pi 3
by R 23 Sep '20

23 Sep '20

Hello, I was wondering if there is a procedure for installing Centos 7 on the Raspberry Pi 3 B+ while installing Centos 7.5 on armhfp is very clear and documented given that a raw root image is provided and you just "dd" it on the memory card, it is not clear to me how to do it with aarch64. A ISO image is provided but how to install it on the raspberry ? thank you Rick

6 16

epel-release
by Robert Moskowitz 30 Jun '20

30 Jun '20

Ok, I see this epel-release in the epel1 repo that I installed via the wiki. So I decide to install it, and it created an epel.repo.rpmnew file. I swicth around the files and try a 'yum update' and get: epel/armhfp/metalink | 47 kB 00:00 Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=armhfp error was No repomd file One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: .... File /var/cache/yum/armhfp/7/epel/metalink.xml does not exist So I put everything back.

3 7

MP30-AR0/AR1 - Tianocore Firmware
by Gordan Bobic 26 Jun '20

26 Jun '20

In my ongoing quest to get my MP30-AR0 to not choke on most PCIe cards I finally (yes, I know, years late, but I stopped being able to make do without adding things into the machine), flashed the firmware on it from u-boot to AMI, thus turning it into an MP30-AR1. I was originally intending to flash it with Tianocore, but the download links for that firmware all point to dropbox, and that link is dead. Does anyone have the tianocore firmware for the MP30-AR0 that they could kindly repost? I was originally chain-loading Tianocore from u-boot, and that could have been upsetting something that made RH kernels comprehensively and consistently crash. Interestingly, my locally built mainline kernels have always worked (using 4.9.x branch) without even needing acpi=off. It looks like the Tianocore image I need for flashing to the board may not be the same as the chainloading firmware, so I wanted to make sure I have the exact right firmware image to avoid the risk of bricking it. FYI, flashing the AR1 firmware via the BMC "just works". Anyway, the AMI firmware (AR1) seems to cure some of the problems. I can now have additional PCIe cards in the machine without this causing an insta-crash as soon as the driver for the card loads (Marvell SATA and SAS controllers, Silicon Image SATA controllers, 3ware SAS controllers, it all ends the same way, with an insta-crash when the driver loads). The reason why I want to try Tianocore firmware instead are the following: 1) This looks scary at boot time: SecBoot-0, SecMode-1, DefaultProvision-0, BackDoorVendorKeyChange-0 2) AMI UEFI firmware takes about 5 minutes (no, not an exaggeration) to get from power-on to showing the grub boot menu. If it wasn't for the serial console, I would have written the board off as bricked by the firmware update. So - anyone happen to have the Tianocore firmware for the MP30-AR0 that they wouldn't mind reposting somewhere? Many thanks. Gordan

2 3

Re: [Arm-dev] Centos on rpi4
by mark 22 Jun '20

22 Jun '20

Just for the appreciation for all the work Pablo did (we make much use of it); Downloaded the image, flashed it and boot up right away.. _OT_ As for Centos 8 I'll took the liberty to copy-cat and create an aarch64 development-image for the RPI4 Note: it has no swap on disk but a zram implementation.. development image: https://github.com/markVnl/centos-sbc-tools/releases ( I run libvirt on it ot test aarch64 and armhfp packages in VM's on it and it did not let me down once...) kernel (re)build on Copr: https://copr.fedorainfracloud.org/coprs/markvnl/Raspberry_PI4/packages/ Awating a 5.x kernel with somewhat decent RPI 4 support i'v prepared aarch64 U-boot build with a <EFI/centos> patch https://copr.fedorainfracloud.org/coprs/markvnl/epel-8-aarch64_SBC-tools/pa… grtz, Mark -----Original message----- From: R C <cjvijf(a)gmail.com> Sent: Tuesday, June 2, 2020 7:48 PM To: Pablo Sebastián Greco <pablo(a)fliagreco.com.ar>; Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> Subject: Re: [Arm-dev] Centos on rpi4 On 6/2/20 11:36 AM, Pablo Sebastián Greco wrote: > > On 2/6/20 13:52, R C wrote: >> Hello, >> >> I am trying to get Centos going on an RPI4 with 4GB; >> >> >> so far I tried to use: >> >> CentOS-Userland-7-armv7hl-RaspberryPI-Minimal-4-2003-sda.raw.xz >> >> (which does seem to do much of anything at all, black screen) >> >> > This is the image I use normally for my work on my rpi4-4G without any > issues (32bit-lpae memory) Ok, I'll try that again. (I have no idea what lpae memory is, I just bought an rpi4 with 4gb) >> and: >> >> CentOS-Userland-7-armv7hl-RaspberryPI-Minimal-2003-sda.raw.xz: >> >> which seems to display the "rainbow screen", but that's about i. > That's expected not to work on rpi-4, so that's ok >> >> >> Is there a different Centos image that would work Or is there some >> setting that's needed? >> >> >> thanks, >> >> >> Ron >> >> >> _______________________________________________ >> Arm-dev mailing list >> Arm-dev(a)centos.org >> https://lists.centos.org/mailman/listinfo/arm-dev _______________________________________________ Arm-dev mailing list Arm-dev(a)centos.org https://lists.centos.org/mailman/listinfo/arm-dev

4 18

No access to HAT i2c EEPROM
by Stephan GUILLOUX 16 Jun '20

16 Jun '20

Hello all, Maybe some will be able to help a bit. I'm running 2 Raspberries 3B+, with the same old CentOS image, freshly prepared. Both run raspberrypi2-kernel 4.19.xx Both Raspberry have a hat, with a valid EEPROM. On both, the application I'm in charge of, has R/W access to /sys/class/i2c-adapter/i2c-3/3-0050/eeprom On one Raspberry, I update the kernel and only the kernel (yum update raspberrypi2-kernel) and I come to 5.4.42. After reboot, the whole content of /sys/class has changed, regarding I2C. 4.19.94: [root@Raspberry-DD7BD7 OLD ~]$ ls -al /sys/bus/i2c/devices/ total 0 drwxr-xr-x. 2 root root 0 Jan 1 1970 . drwxr-xr-x. 4 root root 0 Jan 1 1970 .. lrwxrwxrwx. 1 root root 0 Jan 1 1970 3-0050 -> ../../../devices/platform/ffffffff.i2c/i2c-3/3-0050 lrwxrwxrwx. 1 root root 0 Jan 1 1970 i2c-3 -> ../../../devices/platform/ffffffff.i2c/i2c-3 [root@Raspberry-DD7BD7 OLD ~]$ ls -al /sys/bus/i2c/devices/3-0050/eeprom 5.4.42: [root@CertifBox-8AC500 OLD ~]$ ls -al /sys/class/i2c-adapter/ total 0 drwxr-xr-x. 2 root root 0 Jan 1 1970 . drwxr-xr-x. 54 root root 0 Jan 1 1970 .. lrwxrwxrwx. 1 root root 0 Jun 15 22:53 i2c-11 -> ../../devices/platform/ffffffff.i2c/i2c-11 [root@CertifBox-8AC500 OLD ~]$ Any idea where I can find this EEPROM file ? A module option, maybe ? Regards, Stephan.

1 2

epel-release package landed in unofficial armhfp epel-pass-1 repo
by mark 07 Jun '20

07 Jun '20

Hi, For the first time iv'e located a faulty package in the unofficial armhfp epel-pass-1 repository and oddly enough it is epel-release-7-12 (1) itself. It contains yum configurations pointing to non-existing repositories. (ie https://mirrors.fedoraproject.org) I fully understand it's not a big issue and stay's under the radar as nobody actual installs epel-release on a armhfp system; It kind of disturbs the CentOS 7 based installations we are using. Because the package is actually faulty i'm inclined to share to it here and hope to hear a likely action (if any). Grtz Mark 1) https://armv7.dev.centos.org/repodir/epel-pass-1/epel-release/7-12/noarch/

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev June 2020