Arm-dev February 2019

arm-dev@lists.centos.org

6 participants
14 discussions

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] 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

Different issues with "DTOVERLAY".
by Stephan Guilloux 26 Feb '19

26 Feb '19

Hello, Small issues, today, with dtoverlay gpio-shutdown/poweroff [root@mypi ~]# dtoverlay gpio-shutdown su: user pi does not exist * Failed to apply overlay '1_gpio-shutdown' (kernel) su: user pi does not exist [root@mypi ~]# dtoverlay gpio-poweroff su: user pi does not exist su: user pi does not exist [root@mypi ~]# Even if I add a fake user "PI", this does not work better. [root@mypi ~]# useradd -r pi -p pi [root@mypi ~]# [root@mypi ~]# [root@mypi ~]# dtoverlay gpio-poweroff * Failed to apply overlay '2_gpio-poweroff' (kernel) [root@mypi ~]# dtoverlay gpio-shutdown * Failed to apply overlay '2_gpio-shutdown' (kernel) [root@mypi ~]# But when I check the overlay list, I get: [root@mypi ~]# dtoverlay -l Overlays (in load order): 0: gpio-shutdown 1: gpio-poweroff [root@mypi ~]# At least, something is done :-) Last problems: [root@mypi ~]# dtoverlay -h gpio-shutdown * Help file not found [root@mypi ~]# dtoverlay -h gpio-poweroff * Help file not found [root@mypi ~]# dtoverlay -h rpi-rtc * Help file not found [root@mypi ~]# dtoverlay -h rpi-display * Help file not found [root@mypi ~]# In case ... [root@mypi ~]# cat /proc/version Linux version 4.14.65-v7.1.el7 (mockbuild(a)armhfp-03.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC)) #1 SMP Mon Aug 20 19:04:20 UTC 2018 [root@mypi ~]# [root@mypi ~]# rpm -qa 'raspberrypi-vc*' raspberrypi-vc-demo-source-20170705-502.gitaa39775.el7.noarch raspberrypi-vc-libs-20170705-502.gitaa39775.el7.armv7hl raspberrypi-vc-utils-20170705-502.gitaa39775.el7.armv7hl [root@mypi ~]# Stephan.

2 3

Re: [Arm-dev] Different issues with "DTOVERLAY".
by Stephan Guilloux 24 Feb '19

24 Feb '19

Hi Pablo, Found the cause for the Help problem. On CentOS, /boot/overlays/README is missing. It contains the help for all the dtoverlay commands... I got the file from its original distro, and I put it under /boot/overlays/README.rasp for the demo: [pi@myrpi ~]$ dtoverlay -h i2c-gpio * Help file not found [pi@myrpi ~]$ sudo mv /boot/overlays/README.rasp /boot/overlays/README [pi@myrpi ~]$ dtoverlay -h i2c-gpio Name: i2c-gpio Info: Adds support for software i2c controller on gpio pins Usage: dtoverlay=i2c-gpio,<param>=<val> Params: i2c_gpio_sda GPIO used for I2C data (default "23") i2c_gpio_scl GPIO used for I2C clock (default "24") i2c_gpio_delay_us Clock delay in microseconds (default "2" = ~100kHz) [pi@myrpi ~]$ Unfortunatelly, the files under this folder seem to belong to no package... [pi@myrpi ~]$ rpm -qf /boot/overlays/i2c-gpio.dtbo file /boot/overlays/i2c-gpio.dtbo is not owned by any package [pi@myrpi ~]$ So, I'm stuck there, for now ... Le lun. 24 sept. 2018 à 14:12, Stephan Guilloux < stephan.guilloux(a)crisalid.com> a écrit : > > > Le 24/09/2018 à 10:46, Pablo Sebastian Greco a écrit : > > > > El 24 sept 2018, a las 04:41, Stephan Guilloux < > stephan.guilloux(a)crisalid.com> escribió: > > Hello Pablo, > > Sorry for the direct mail. > > No problem. I'm on vacation this week so it is probably better > > Enjoy ;-) > > > I'll have a look, this week, but I need the sources that CentOS delivers. > I Tried to check on vault.centos.org, but no armhfp (only aarch64). > > You're right. I had touble finding it myself. It got lost when moving from > the old to the new build system. > Try here > https://armv7.dev.centos.org/repodir/c7-extras-1/raspberrypi-vc/20170705-50… > I'll update the srpm and probably github when I'm back but if you find the > problems, better. Hehe > > OK. Got it there. > Will inform you through the list, in case I find anything. > > > > Can you indicate where to find the current raspberrypi-vc-utils.src.rpm ? > > Regards, > > Stéphan. > > Thanks, Pablo > > > > Le 20/09/2018 à 13:02, Pablo Sebastián Greco a écrit : > > Stephan, sorry for the delay > El 10/9/18 a las 12:28, Stephan Guilloux escribió: > > Hello, > > Small issues, today, with dtoverlay gpio-shutdown/poweroff > > [root@mypi ~]# dtoverlay gpio-shutdown > su: user pi does not exist > * Failed to apply overlay '1_gpio-shutdown' (kernel) > su: user pi does not exist > [root@mypi ~]# dtoverlay gpio-poweroff > su: user pi does not exist > su: user pi does not exist > [root@mypi ~]# > > That seems to come from here ( > https://github.com/raspberrypi/userland/blob/master/host_applications/linux…) > If you run as root, it tries to run as the user "pi", as a normal > user(any), you shouldn't have that problem > > > Even if I add a fake user "PI", this does not work better. > > [root@mypi ~]# useradd -r pi -p pi > [root@mypi ~]# > [root@mypi ~]# > [root@mypi ~]# dtoverlay gpio-poweroff > * Failed to apply overlay '2_gpio-poweroff' (kernel) > [root@mypi ~]# dtoverlay gpio-shutdown > * Failed to apply overlay '2_gpio-shutdown' (kernel) > [root@mypi ~]# > > That bit seems to come from here ( > https://github.com/raspberrypi/userland/blob/2448644657e5fbfd82299416d21839…) > it fails to check if the overlay was actually applied > > > But when I check the overlay list, I get: > > [root@mypi ~]# dtoverlay -l > Overlays (in load order): > 0: gpio-shutdown > 1: gpio-poweroff > [root@mypi ~]# > > At least, something is done :-) > > That is a little stranger, why does it say it did something when the > command before said it failed??? > > Last problems: > [root@mypi ~]# dtoverlay -h gpio-shutdown > * Help file not found > [root@mypi ~]# dtoverlay -h gpio-poweroff > * Help file not found > [root@mypi ~]# dtoverlay -h rpi-rtc > * Help file not found > [root@mypi ~]# dtoverlay -h rpi-display > * Help file not found > [root@mypi ~]# > > > > I guess I'll have to add some debugging info and check in my rpi (as time > permits) > > In case ... > [root@mypi ~]# cat /proc/version > Linux version 4.14.65-v7.1.el7 (mockbuild(a)armhfp-03.bsys.centos.org) > (gcc version 4.8.5 20150623 (Red Hat 4.8.5-28) (GCC)) #1 SMP Mon Aug 20 > 19:04:20 UTC 2018 > [root@mypi ~]# > > [root@mypi ~]# rpm -qa 'raspberrypi-vc*' > raspberrypi-vc-demo-source-20170705-502.gitaa39775.el7.noarch > raspberrypi-vc-libs-20170705-502.gitaa39775.el7.armv7hl > raspberrypi-vc-utils-20170705-502.gitaa39775.el7.armv7hl > [root@mypi ~]# > > 2 questions > 1) has it ever worked before? > 2) which rpi exactly are you using? (don't know if it is really relevant). > > Thanks. > Pablo. > > > Stephan. > > P.S.: Today we built 4.14.71 and will be released as soon as it passes the > tests. > > > >

2 1

raspi 3b+ kernel module
by Skorpeo Skorpeo 19 Feb '19

19 Feb '19

Hi, I'm trying to use wireguard on a raspi 3b+ by compiling it. The raspi command output for uname -r shows 4.14.79-v7+, the extra "+" at the end is what I think is causing some troubles in getting it to work. It seems my best bet is to recompile the kernel so I wasn't sure where to find the right sources as it seems there's specific sources for the raspi? Any pointers appreciated!

2 2

efi for raspi 3
by Skorpeo Skorpeo 19 Feb '19

19 Feb '19

Looks like efi for raspi3 is upstream now: https://github.com/tianocore/edk2-platforms/tree/master/Platform/RaspberryP…

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev February 2019