Arm-dev September 2019

arm-dev@lists.centos.org

11 participants
13 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

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

CentOS - AltArch ; ARM
by Douglas E. Hopley Jr. 26 Sep '19

26 Sep '19

Greetings. How can I provide any help? Is there something specific needed or best for a new participant to work on or for? What is best to do to get started? Thanks in advance for your time.

2 7

FW: Centos specific patch for uboot images
by Mark Verlinde 20 Sep '19

20 Sep '19

If we can agree in principle of this: https://github.com/markVnl/rpms-uboot-tools/compare/master...centosisms If will see what I can do. Grtz Mark (Sorry Pablo, accidentally answered to you instead to the list) > -----Oorspronkelijk bericht----- > Afzender: Pablo Sebastián Greco<pablo(a)fliagreco.com.ar> > Verstuurd: Vrijdag 20 September 2019 15:14 > Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org>; Mark Verlinde <mark(a)havak.nl> > Onderwerp: Re: [Arm-dev] Centos specific patch for uboot images > > Mark, > you're absolutely right, and I have a local copy of that same > idea. > > WRT your patches, I have some nitpicks. I think the generated > srpm should be the same in both CentOS and Fedora, which could > be solved by including "the other one" as a source > > If you'd like take on the task of getting this upstreamed to > Fedora, you'd be helping me "a lot", if not, just know that it > is in my to-do list :-) > > Pablo. > > El 20/9/19 a las 09:46, Mark Verlinde > escribió: > > First of all congratulations and thanks for the latest 7.7 release; updated several systems without issues! > > As mentioned in an other conversation it is the logical continuation of 7.6-updates nevertheless found some nice surprises in the armhfp and especially aarch64 extras repository's including updated u-boot images > > This being said it saddens me to see in the source file of the uboot-tools-2019.07-3 they still carry a Fedora specific patch. While it is not a difficult fix the get centosisms in. Especially since the upstream maintainer (intentionally?) reverted the order of first two distro specific patches. (This makes a clean patch possible without patching the patch.) > > I know it is not a encouraged to boot aarch64 on our SBC's, nor is it my objective to promote this. > But an easy route I use for over an year is though uboot-uefi boot > grub2. > And have to say I like it a lot, with an (serial)monitor attracted you can choose the kernel in grub2; > or partion you want to boot (if you happen to feel to be inclined to have a multiboot-environment) > > after re-basing to uboot-tools-2019.07-3 > ( https://github.com/markVnl/rpms-uboot-tools/compare/centos...el7 <https://github.com/markVnl/rpms-uboot-tools/compare/centos...el7> ) > these two patches do the job for me: > > >From 98a2c15275a5fe154cf80344b7538d72ecb00645 Mon Sep 17 00:00:00 2001 > From: Mark Verlinde <mark(a)havak.nl> <mailto:mark@havak.nl> > Date: Fri, 20 Sep 2019 13:29:10 +0200 > Subject: [PATCH 1/2] uefi use Centos specific path name > > --- > uefi-use-Centos-specific-path-name.patch | 50 ++++++++++++++++++++++++++++++++ > 1 file changed, 50 insertions(+) > create mode 100644 uefi-use-Centos-specific-path-name.patch > > diff --git a/uefi-use-Centos-specific-path-name.patch b/uefi-use-Centos-specific-path-name.patch > new file mode 100644 > index 0000000..14abac1 > --- /dev/null > +++ b/uefi-use-Centos-specific-path-name.patch > @@ -0,0 +1,50 @@ > +From dd6a7a9726e5d79bb053d3ab0a8b0ae273140bce Mon Sep 17 00:00:00 2001 > +From: Mark Verlinde <mark(a)havak.nl> <mailto:mark@havak.nl> > +Date: Tue, 25 Dec 2018 15:28:56 +0100 > +Subject: [PATCH 1/1] uefi use Centos specific path name > + > +Signed-off-by: Mark Verlinde <mark(a)havak.nl> <mailto:mark@havak.nl> > +--- > + include/config_distro_bootcmd.h | 10 +++++----- > + 1 file changed, 5 insertions(+), 5 deletions(-) > + > +diff --git a/include/config_distro_bootcmd.h b/include/config_distro_bootcmd.h > +index 47e98e14ac..aa4b24d4de 100644 > +--- a/include/config_distro_bootcmd.h > ++++ b/include/config_distro_bootcmd.h > +@@ -92,9 +92,9 @@ > + > + #ifdef CONFIG_EFI_LOADER > + #if defined(CONFIG_ARM64) > +-#define BOOTEFI_NAME "bootaa64.efi" > ++#define BOOTEFI_NAME "grubaa64.efi" > + #elif defined(CONFIG_ARM) > +-#define BOOTEFI_NAME "bootarm.efi" > ++#define BOOTEFI_NAME "grubarm.efi" > + #elif defined(CONFIG_X86_RUN_32BIT) > + #define BOOTEFI_NAME "bootia32.efi" > + #elif defined(CONFIG_X86_RUN_64BIT) > +@@ -130,7 +130,7 @@ > + "bootefi bootmgr ${fdtcontroladdr};" \ > + "fi;" \ > + "load ${devtype} ${devnum}:${distro_bootpart} " \ > +- "${kernel_addr_r} efi/boot/"BOOTEFI_NAME"; " \ > ++ "${kernel_addr_r} efi/centos/"BOOTEFI_NAME"; " \ > + "if fdt addr ${fdt_addr_r}; then " \ > + "bootefi ${kernel_addr_r} ${fdt_addr_r};" \ > + "else " \ > +@@ -165,9 +165,9 @@ > + "run boot_efi_binary\0" \ > + "scan_dev_for_efi=" \ > + "if test -e ${devtype} ${devnum}:${distro_bootpart} " \ > +- "efi/boot/"BOOTEFI_NAME"; then " \ > ++ "efi/centos/"BOOTEFI_NAME"; then "\ > + "echo Found EFI removable media binary " \ > +- "efi/boot/"BOOTEFI_NAME"; " \ > ++ "efi/centos/"BOOTEFI_NAME"; " \ > + "run scan_dev_for_dtb; " \ > + "echo EFI LOAD FAILED: continuing...; " \ > + "fi; " \ > +-- > +2.16.5 > + > >

2 1

Centos specific patch for uboot images
by Mark Verlinde 20 Sep '19

20 Sep '19

First of all congratulations and thanks for the latest 7.7 release; updated several systems without issues! As mentioned in an other conversation it is the logical continuation of 7.6-updates nevertheless found some nice surprises in the armhfp and especially aarch64 extras repository's including updated u-boot images This being said it saddens me to see in the source file of the uboot-tools-2019.07-3 they still carry a Fedora specific patch. While it is not a difficult fix the get centosisms in. Especially since the upstream maintainer (intentionally?) reverted the order of first two distro specific patches. (This makes a clean patch possible without patching the patch.) I know it is not a encouraged to boot aarch64 on our SBC's, nor is it my objective to promote this. But an easy route I use for over an year is though uboot-uefi boot > grub2. And have to say I like it a lot, with an (serial)monitor attracted you can choose the kernel in grub2; or partion you want to boot (if you happen to feel to be inclined to have a multiboot-environment) after re-basing to uboot-tools-2019.07-3 ( https://github.com/markVnl/rpms-uboot-tools/compare/centos...el7 ) these two patches do the job for me: >From 98a2c15275a5fe154cf80344b7538d72ecb00645 Mon Sep 17 00:00:00 2001 From: Mark Verlinde <mark(a)havak.nl> Date: Fri, 20 Sep 2019 13:29:10 +0200 Subject: [PATCH 1/2] uefi use Centos specific path name --- uefi-use-Centos-specific-path-name.patch | 50 ++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 uefi-use-Centos-specific-path-name.patch diff --git a/uefi-use-Centos-specific-path-name.patch b/uefi-use-Centos-specific-path-name.patch new file mode 100644 index 0000000..14abac1 --- /dev/null +++ b/uefi-use-Centos-specific-path-name.patch @@ -0,0 +1,50 @@ +From dd6a7a9726e5d79bb053d3ab0a8b0ae273140bce Mon Sep 17 00:00:00 2001 +From: Mark Verlinde <mark(a)havak.nl> +Date: Tue, 25 Dec 2018 15:28:56 +0100 +Subject: [PATCH 1/1] uefi use Centos specific path name + +Signed-off-by: Mark Verlinde <mark(a)havak.nl> +--- + include/config_distro_bootcmd.h | 10 +++++----- + 1 file changed, 5 insertions(+), 5 deletions(-) + +diff --git a/include/config_distro_bootcmd.h b/include/config_distro_bootcmd.h +index 47e98e14ac..aa4b24d4de 100644 +--- a/include/config_distro_bootcmd.h ++++ b/include/config_distro_bootcmd.h +@@ -92,9 +92,9 @@ + + #ifdef CONFIG_EFI_LOADER + #if defined(CONFIG_ARM64) +-#define BOOTEFI_NAME "bootaa64.efi" ++#define BOOTEFI_NAME "grubaa64.efi" + #elif defined(CONFIG_ARM) +-#define BOOTEFI_NAME "bootarm.efi" ++#define BOOTEFI_NAME "grubarm.efi" + #elif defined(CONFIG_X86_RUN_32BIT) + #define BOOTEFI_NAME "bootia32.efi" + #elif defined(CONFIG_X86_RUN_64BIT) +@@ -130,7 +130,7 @@ + "bootefi bootmgr ${fdtcontroladdr};" \ + "fi;" \ + "load ${devtype} ${devnum}:${distro_bootpart} " \ +- "${kernel_addr_r} efi/boot/"BOOTEFI_NAME"; " \ ++ "${kernel_addr_r} efi/centos/"BOOTEFI_NAME"; " \ + "if fdt addr ${fdt_addr_r}; then " \ + "bootefi ${kernel_addr_r} ${fdt_addr_r};" \ + "else " \ +@@ -165,9 +165,9 @@ + "run boot_efi_binary\0" \ + "scan_dev_for_efi=" \ + "if test -e ${devtype} ${devnum}:${distro_bootpart} " \ +- "efi/boot/"BOOTEFI_NAME"; then " \ ++ "efi/centos/"BOOTEFI_NAME"; then "\ + "echo Found EFI removable media binary " \ +- "efi/boot/"BOOTEFI_NAME"; " \ ++ "efi/centos/"BOOTEFI_NAME"; " \ + "run scan_dev_for_dtb; " \ + "echo EFI LOAD FAILED: continuing...; " \ + "fi; " \ +-- +2.16.5 + -- 1.8.3.1 >From a4ac56bf5b7baa15eca75870a8fdca6defc5e8ff Mon Sep 17 00:00:00 2001 From: Mark Verlinde <mark(a)havak.nl> Date: Fri, 20 Sep 2019 13:44:43 +0200 Subject: [PATCH 2/2] Add Centosisms --- uboot-tools.spec | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/uboot-tools.spec b/uboot-tools.spec index 226bbb6..91b3faf 100644 --- a/uboot-tools.spec +++ b/uboot-tools.spec @@ -2,7 +2,7 @@ Name: uboot-tools Version: 2019.07 -Release: 3%{?candidate:.%{candidate}}%{?dist} +Release: 4%{?candidate:.%{candidate}}%{?dist} Summary: U-Boot utilities License: GPLv2+ BSD LGPL-2.1+ LGPL-2.0+ URL: http://www.denx.de/wiki/U-Boot @@ -14,11 +14,18 @@ Source3: aarch64-boards Source4: aarch64-chromebooks Source5: 10-devicetree.install -# Fedoraisms patches +# Fedora/CentOS-isms patches # Needed to find DT on boot partition that's not the first partition Patch1: uefi-distro-load-FDT-from-any-partition-on-boot-device.patch + # Needed due to issues with shim -Patch2: uefi-use-Fedora-specific-path-name.patch +%if 0%{?centos} +# CentOSisms +Patch2: uefi-use-Centos-specific-path-name.patch +%else +# Fedoraisms +Patch3: uefi-use-Fedora-specific-path-name.patch +%endif # Board fixes and enablement Patch5: usb-kbd-fixes.patch @@ -265,6 +272,9 @@ cp -p board/warp7/README builds/docs/README.warp7 %endif %changelog +* Thu Aug 29 2019 Mark Verlinde <mark.verlinde(a)gmail.com> 2019.07-4 +- Add conditional CentOS specific EFI location + * Sun Aug 4 2019 Peter Robinson <pbrobinson(a)fedoraproject.org> 2019.07-3 - Fixes for Rock960 - Iniital Raspberry Pi 4 support -- 1.8.3.1

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev September 2019