Arm-dev August 2016

arm-dev@lists.centos.org

9 participants
15 discussions

Gigabyte MP30-AR0
by Gordan Bobic 12 Nov '19

12 Nov '19

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

10 197

Request for a new package: raspberrypi-vc
by Jordi Sanfeliu 13 Sep '17

13 Sep '17

Hello, Following the Fabian Arrotin recommendation, I open here the request to include the 'raspberrypi-vc' package into the CentOS 7 EPEL repository, or in the main tree. This package includes a command called 'vcgencmd' which offers a set of interesting values of the Raspberry Pi board; e.g. its temperature. Check here <http://www.elinux.org/RPI_vcgencmd_usage> for more information. I've downloaded the SRPM package from here <http://www.squeezecommunity.org/repo/fedora/24/pi/SRPMS/raspberrypi-vc-2016…>, and I realized that it was pretty easy to build on a full-updated CentOS 7 (kernel 4.4.14-v7). The following are the small modifications I made on the .spec file to accomplish it: --- raspberrypi-vc.spec 2016-07-05 23:23:13.000000000 +0200 +++ raspberrypi-vc.spec.ok 2016-07-13 12:14:39.494059817 +0200 @@ -21,12 +21,12 @@ Patch1: raspberrypi-vc-EGL-dep.patch # dtoverlay -BuildRequires: libfdt-devel >= 1.4.1-501.gitbeef80b%{?dist} +##BuildRequires: libfdt-devel >= 1.4.1-501.gitbeef80b%{?dist} Requires: libfdt >= 1.4.1-501.gitbeef80b%{?dist} BuildRequires: cmake, gcc-c++ -ExclusiveArch: armv6hl armv7hnl +ExclusiveArch: armv7hl %description Libraries, utilities and demos for the Raspberry Pi BCM2835/6 SOC GPU @@ -34,7 +34,7 @@ %package libs Summary: Libraries for accessing the Raspberry Pi GPU -Requires: %{name}-firmware >= 20150212git47bd0f0-501 +##Requires: %{name}-firmware >= 20150212git47bd0f0-501 #Provides: libEGL.so #Provides: libGLESv1_CM.so The build generated successfully the following packages: [root@rpi3 rpmbuild]# l -R RPMS/ RPMS/: total 8 drwxr-xr-x 2 root root 4096 Jul 26 15:59 armv7hl drwxr-xr-x 2 root root 4096 Jul 13 12:23 noarch RPMS/armv7hl: total 1352 -rw-r--r-- 1 root root 552156 Jul 13 12:22 raspberrypi-vc-libs-20160705-501.git0b8c195.el7.centos.armv7hl.rpm -rw-r--r-- 1 root root 340184 Jul 13 12:22 raspberrypi-vc-libs-devel-20160705-501.git0b8c195.el7.centos.armv7hl.rpm -rw-r--r-- 1 root root 244960 Jul 13 12:23 raspberrypi-vc-static-20160705-501.git0b8c195.el7.centos.armv7hl.rpm -rw-r--r-- 1 root root 241332 Jul 13 12:23 raspberrypi-vc-utils-20160705-501.git0b8c195.el7.centos.armv7hl.rpm RPMS/noarch: total 30688 -rw-r--r-- 1 root root 31420584 Jul 13 12:23 raspberrypi-vc-demo-source-20160705-501.git0b8c195.el7.centos.noarch.rpm The installation worked finely: # [root@rpi3 armv7hl]# rpm -ivh raspberrypi-vc-utils-20160705-501.git0b8c195.el7.centos.armv7hl.rpm raspberrypi-vc-libs-20160705-501.git0b8c195.el7.centos.armv7hl.rpm Preparing... ################################# [100%] Updating / installing... 1:raspberrypi-vc-libs-20160705-501.################################# [ 50%] 2:raspberrypi-vc-utils-20160705-501################################# [100%] Then a simple command to get the temperature: [root@rpi3 ~]# vcgencmd measure_temp temp=47.2'C Thanks. -- Jordi Sanfeliu FIBRANET Network Services Provider http://www.fibranet.cat

4 5

Kernel for BananaPi R1 (Lamobo R1)
by mo.ucina 12 May '17

12 May '17

Hello Guys, I have been compiling the Fedora 4.4.2-300 kernel for Centos , using the new Centos image for the Banana-pi . I have used the Fedora src rpm and then added the patch for the switch drivers specific for R1 (Lamobo R1) , then compiled it within the Centos dev arm environment I have . I ran into a couple of things : one cosmetic , the other one not so . Firstly the cosmetic one is that my packages came out looking like this : -rw-rw-r-- 1 user user 49332 Feb 26 07:27 kernel-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 87721969 Feb 26 07:27 kernel-4.4.2-300.LR1.el7.centos.src.rpm -rw-rw-r-- 1 user user 18785384 Feb 26 07:29 kernel-core-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 10452672 Feb 26 07:30 kernel-devel-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 1012496 Feb 26 07:27 kernel-headers-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 11844188 Feb 26 07:31 kernel-modules-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 925980 Feb 26 07:31 kernel-modules-extra-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 105452 Feb 26 07:27 kernel-tools-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 65356 Feb 26 07:27 kernel-tools-libs-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 52160 Feb 26 07:27 kernel-tools-libs-devel-4.4.2-300.LR1.el7.centos.armv7hl.rpm They all have "centos" as part of the name , which I did not expect . I did not get that when compiling in Fedora. How do you remove that ? Second observation , a one that is a bit of a concern is that , after installing the new kernel I am missing bits : user@bananapi /boot $ ls -l total 43611 drwxr-xr-x. 5 root root 1024 Feb 25 22:21 38f5ec9e217b471e8adee477d933f640 -rw-r--r--. 1 root root 171924 Nov 26 00:43 config-4.2.3-200.el7.armv7hl drwxr-xr-x. 2 root root 15360 Dec 3 14:37 dtb-4.2.3-200.el7.armv7hl drwxr-xr-x. 2 root root 1024 Dec 3 14:47 extlinux drwxr-xr-x. 2 root root 1024 Jan 1 1970 grub -rw-r--r--. 1 root root 34922581 Dec 3 14:46 initramfs-4.2.3-200.el7.armv7hl.img -rw-r--r--. 1 root root 592347 Dec 3 14:37 initrd-plymouth.img drwxr-xr-x. 3 root root 1024 Dec 3 14:44 loader drwx------. 2 root root 12288 Dec 3 14:31 lost+found -rw-------. 1 root root 2879429 Nov 26 00:43 System.map-4.2.3-200.el7.armv7hl -rwxr-xr-x. 1 root root 5866104 Nov 26 00:43 vmlinuz-4.2.3-200.el7.armv7hl I expected that I would be missing 'initramfs' as the install prog is still work-in-progress. And I was prepared to create it with dracut . However I did not expect not to be missing all the other bits such as : config , dtb, system.map, vmlinuz . I did find my new kernel it was in that dir with a hex name : user@bananapi /boot $ ls -l 38f5ec9e217b471e8adee477d933f640/* 38f5ec9e217b471e8adee477d933f640/0-rescue: total 40652 -rw-r--r--. 1 root root 35427302 Dec 3 14:43 initrd -rwxr-xr-x. 1 root root 6033128 Feb 25 22:26 linux 38f5ec9e217b471e8adee477d933f640/4.2.3-200.el7.armv7hl: total 39995 -rw-r--r--. 1 root root 34923169 Dec 3 14:40 initrd -rw-r--r--. 1 root root 5866104 Dec 3 14:44 linux 38f5ec9e217b471e8adee477d933f640/4.4.2-300.LR1.el7.centos.armv7hl: total 41061 -rw-r--r--. 1 root root 35844934 Feb 25 22:24 initrd -rw-r--r--. 1 root root 6033128 Feb 25 22:36 linux So my question is how do I go from these 2 files above , to the situation where I can boot into the new kernel 4.4.2-300.LR1.el7.centos.armv7hl . Best Regards Milorad PS Once I have verified that the switch driver works , I will post it here .

5 13

I2C in Centos 7
by cjvijf＠gmail.com 29 Jan '17

29 Jan '17

Hello, I am running Centos on a raspberry pi 2b. (I downloaded the image from: http://people.centos.org/hughesjr/armv7hl/rpi2/images/ rpi2-centos-image.img.xz ) and installed the i2c libraries and modules for i2c. [root@rpi2-2 ~]# lsmod | grep i2c i2c_bcm2708 5006 0 i2c_dev 6027 0 From what I read that should be correct device file is there too: crw------- 1 root root 89, 1 Dec 31 1969 i2c-1 kernel: Linux rpi2-2 3.18.14-v7+ #794 SMP PREEMPT Sun Jun 7 12:50:51 BST 2015 armv7l armv7l armv7l GNU/Linux However, when I scan the i2c bus with 'i2cdetect -y 1' I don't see any devices (and I tried 2 that I know work). is the I2C stuff in this kernel working? (or is there a newer kernel version?) thanks, Ron P.S. I know this is an arm-dev list, but figured the I2C topic would fit better here than in a general Centos list

2 1

kernel rebase for rpi2/rpi3 : call for feedback !
by Fabian Arrotin 27 Sep '16

27 Sep '16

Hi, I just rebased the raspberry pi 2/3 kernel to 4.4.14, with a specific patch to cover also selinux/auditd support. I'd like to have some additional testers (tested on my rpi2 and rpi3 boards). Create (for example) the /etc/yum.repos.d/kernel.repo file with the following content : [kernel] name=rpi kernel baseurl=http://armv7.dev.centos.org/repodir/arm-kernels/rpi2-4.4.14/ gpgcheck=0 enabled=1 Then a traditional "yum update ; systemctl reboot" If you want to have selinux working, feel free to follow https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32?highlight=%28arm… , except that for rpi2/rpi3, there is no /boot/exlinux/extlinux.conf, but rather edit /boot/cmdline.txt Thanks for the feedback, and then we'll be able to sign/push those to mirrors (and also include those in newer images for rpi2/rpi3) -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

4 12

Re: [Arm-dev] [rdo-list] next steps for altarch with ceph and openstack
by Jim Perrin 20 Sep '16

20 Sep '16

On 07/08/2016 03:35 AM, Alan Pevec wrote: > On Fri, Jul 8, 2016 at 4:00 AM, Haïkel <hguemar(a)fedoraproject.org> wrote: >> 2016-07-07 17:41 GMT+02:00 Jim Perrin <jperrin(a)centos.org>: > ... >>> I might suggest that for now (until we get the mirror bits sorted), we >>> create a centos-release-mitaka-altarch package. This would avoid needing >>> to mess with the existing x86_64 bits. once everything is aligned, then >>> we can obsolete/provides the replacement and use the standard package >>> across all architectures. >> >> Works for me. > > I didn't understand why we need separate release -altarch package. I > understand we do need separate CBS tags but they could be still mapped > into the same per-arch locations under > http://buildlogs.centos.org/centos/7/cloud/ and > http://mirror.centos.org/centos/7/cloud/ so that current OpenStack > CloudSIG .repo [1] which uses $basearch will work. Mappings for > testing repo request (e.g. for RDO Newton [2]) would be: > The problem here is that the aarch64 builds are currently at mirror.centos.org/altarch/ not at /centos/, so either way we'll end up with split repositories for the architecture. I'm only suggesting a second package as a short term solution until we come up with a better way to manage this. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

3 4

Raspberry Pi 3 and Aarch64 image?
by Jeffrey Walton 13 Sep '16

13 Sep '16

I'm having trouble finding an Aarch64 image for a Raspberry Pi 3. The Raspberry Pi 3 was selected as a test device because its ARMv8. Does Cent have any Aarch64 images for the Model 3? Jeff

6 15

Centos 7 - aarch64 gcc spec file bug
by Ed Brand 01 Sep '16

01 Sep '16

Libatomic and libgnat from gcc-4.8.5-4 appear not to be built on aarch64. How to file bug? See below from spec: Summary: Various compilers (C, C++, Objective-C, Java, ...) Name: gcc %if 0%{?rhel} == 7 %global gcc_version 4.8.2 %else %global gcc_version 4.8.5 %endif Version: 4.8.5 Release: %{gcc_release}%{?dist} ... ( Missing aarch64 ) v %ifarch %{ix86} x86_64 ppc ppc64 ppc64le ppc64p7 s390 s390x aarch64 %{arm} %global build_libatomic 1 I did a smoke test and was able to bootstrap both using f21 aarch64. Have the rpms if needed.

2 8

★ Arm Dev, Alan left a message for you
by Alan 19 Aug '16

19 Aug '16

1 0

Query for update on armv7lh GUI release
by Sampad Rout 18 Aug '16

18 Aug '16

Hi All, A newbie here. I am doing some testing on my RPi2 and my plan was to install Centos image on RPi2 board from http://mirror.centos.org/altarch/7/isos/armhfp After installation I realized it is only a CLI. Do we have any GUI option also. If any procedure need to be followed, please share. that would be a great help. In case the GUI support is still under the hood, please help with the tentative release date. sorry if I sound stupid somewhere :)

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev August 2016