Arm-dev May 2020

arm-dev@lists.centos.org

8 participants
12 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

Re: [Arm-dev] wireless on rpi3
by Phil Leschina 03 Jun '20

03 Jun '20

Hi, I’m new to list. I was able to connect to WiFi from 3b+ from centos 7 and 8 using: nmcli d wifi nmcli d wifi connect networkname password networkpassword

4 15

bluetooth on CentOS Linux release 7.6.1810
by R C 31 May '20

31 May '20

Hello, I am going to use a raspberry PI for browsing on a TV, so I want to connect with a wireless keyboard, bluetooth. It looks like bluetooth is "not running"; [rocr@centos-rpi3 ~]$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:bluetoothd(8) I don't have any bluetooth devices connected yet. but the service should be up, right? Is there a write-up, guide, to get bluetooth configured? thanks, Ron

2 4

Re: [Arm-dev] Add Marvell Armada7k8k NIC (mvpp2) support patches
by Marcin Wojtas 26 May '20

26 May '20

Hi Jim, It's been a while, since I sent the patch. Any objections about merging? Is v4.11 kernel still a valid baseline or for the next releases or we should use v4.14? When is that transition and next release supposed to happen? Best regards, Marcinsob., 23 cze 2018 o 08:18 Marcin Wojtas <mw(a)semihalf.com> napisał(a): > > Hi, > > I'm sending a patch that is applicable on top of the kernel > sig-altarch7-aarch64 branch. It enables ACPI support for the Marvell > Armada7k8k NIC - this required backporting very big amount of patches > (all merged upstream), hence I decided to attach the single commit, > instead of issueing 'git send-email' of it. > > Despite many attempts I wasn't able to build entire rpm package with > the mock build utility, however I managed to test the clean kernel > v4.11 with applied all patches and built with updated .config. Please > let know if this patch is sufficient and can be merged. > > Thanks, > Marcin

5 21

orange pi pc2
by sam＠samuels.id.au 19 May '20

19 May '20

hi i couldnt find a search tool for the mailing list, so apologies if it has been already discussed but i cannot find a howtofor the orange pi pc2. i see it as a supported device but not sure what i need to do to get it to boot. i used rufus and install OS and tried: CentOS-Userland-7-aarch64-generic-Minimal-2003-sda.raw.xz CentOS-Userland-7-armv7hl-generic-Minimal-2003-sda.raw.xz CentOS-Userland-7-armv7hl-RootFS-Minimal-2003-sda.raw.xz and none of them boot. I am assuming i am to load the specific uboot for the said device but not sure how?

2 2

CentOS-arm on v5 Odroids?
by Robert Moskowitz 04 May '20

04 May '20

I have been off writing IETF standards (mostly for UA comm) for the past many months. But I just got some funding for an arm Centos project but it has to be a 5v (meaning armv7) system. Quite some time ago (a year ago, wow!) I worked on Odroid HC1. Has anyone worked with any Odroids recently? Or any other similar boards? thanks

1 0

Re: [Arm-dev] wlan0 link is not ready.
by R C 02 May '20

02 May '20

>> >> in a network script, I was wondering if 'it' was waiting for a ipv6 >> address or so > You may need to disable it in the kernel module, (ipv6.disable=1 or > smething like that) I never had to do that. I replace some networking stuff (router/switch) every seemed to have survived the transition, except 3 RPIs (it should just get an IP with dhcp/wireless, but somehow it started complaining about wlan0 >> >> >>>> >>>> >>>> (I tried to create a new centos image on an SD, but somehow >>>> thatdoesn't work. where is the latest working version of it?) >>> Which image doesn't work? All the latest versions are in >>> http://mirror.centos.org/altarch/7/isos/armhfp/ >> >> That is the one for RPI3, right? Does that work on the RPI4 too? > Those are for both, that is why I asked. In fact, in the link there > are 3 images that could boot in rpi3 (the generic one, with a normal > kernel, the rpi-minimal, with kernel from rpi foundation, and the > rpi-minimal-4 which also works on the raspberrypi4) good to know, I wondered what the differences are >> >> >>>> >>>> >>>> is there a way to fix this wlan0 error ? >>> That depends on how ipv6 is disabled, but even so, that looks more >>> like a warning than an actual error. >> >> >> That's what I thought, just wondering if it actually is. > Since you're not actually using ipv6, you can ignore it right, on "regular machines" when configuring network stuff, I disable it thanks, Ron

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev May 2020