July 2016 - Arm-dev - lists.centos.org

Gigabyte MP30-AR0
by Gordan Bobic 05 Aug '25

05 Aug '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

16 206

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 26 Sep '16

26 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

Contribution from NXP Semiconductors
by Jingyu Li 11 Aug '16

11 Aug '16

Hi, all I'm Amy from NXP Semiconductors and I'll be responsible for following the development, contributing fixes and patches submission for NXP productions. Best Regards, Amy

4 5

Pine64 Support
by Mike Calderwood 03 Aug '16

03 Aug '16

Hello all. I was hoping to get some information about how to get CentOS up and running on a board that is not yet on the supported list. I have a brand new Pine64 ( https://www.pine64.com/ ) that I'd love to have CentOS on if possible, so I figured I'd give a go at getting it up and running. And if I can help give back to a project that I've grown very fond of over the years, even better. That's the good news. Now the bad: I have basically no idea where to start. I have zero experience with ARM besides taking existing SD card images and flashing them on devices like a Raspberry Pi. I'm also not a kernel developer or anything else wonderful like that (though I am a software developer by hobby and trade). I apologize for requiring so much hand-holding, but hopefully I can make something resembling progress with enough assistance. If anyone can point to some good resources to give me a basic understanding of what I need (which will tell me if I'm even in a position to do this in the first place), I'd really appreciate it. Thanks for the help and for all the great work you've all done already! Mike

6 13

EPEL 7 for ARM
by Jacob Carey 03 Aug '16

03 Aug '16

Hi all, About a year ago, someone posted here and asked if there were plans for CentOS to host a repository for EPEL7 for ARM. I can't find any more recent discussions so my question is - what can I do to help maintain/introduce such an auxiliary repository? Thanks, Jacob

9 14

TFTP issue with PXE loaded grubaa64.efi
by Sakar Arora 28 Jul '16

28 Jul '16

Hi Jim, While testing CentOS 7 installation on LS2080a RDB, only on one of setups, we found this strange issue, where grub wasn't able to TFTP the boot images from TFTP server. We use grubaa64.efi provided on CentOS website<http://mirror.centos.org/altarch/7/os/aarch64/EFI/BOOT/>. >From the tftp server logs we found that the tftp transaction would always stop with a 'timeout' error. A quick search got me this bug<https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1508893> logged in Ubuntu bug tracking system. There was a mention of a patch, which is supposed to fix this issue. So, I went ahead and created a grub image with the latest upstream grub source code (git.savannah.gnu.org/grub.git) Using this grub image, fixed the issue with TFTP transfers. But, there's different kind of issue with this new grub image. It doesn't seem to be fully compatible with UEFI PXE boot protocol. When loading grub via UEFI PXE boot, the tftp server address does not get set in the grub environment variables, as was the case with grubaa64.efi from CentOS that we use. Can you share you views on this? Thanks, Sakar

2 3

Difficult to edit grub menu options on efi console
by Sakar Arora 28 Jul '16

28 Jul '16

Hi Using CentOS 7 grubaa64.efi. on serial console. It is quite difficult to edit menu options in such a setup. Has anybody faced issues in editing grub menu entries on a serial console? Thanks, Sakar

1 0

Bug: Missing symlink /etc/redhat-release
by Artem Sidorenko 27 Jul '16

27 Jul '16

Hey Centos ARM list, As requested via twitter today [1], On the current Raspberry Pi 3 image the /etc/redhat-release isn't a symlink to centos-release like on x86, but a file with "Derived from Red Hat Enterprise Linux 7.2 (Source)" [2]. This might lead to errors in the OS auto detection, like with Chef [3]. Regards, Artem [1]: https://twitter.com/CentOS/status/756139559801462785 [2]: https://gist.github.com/artem-sidorenko/d69021c66958ba75df23304909493de3 [3]: https://www.sidorenko.io/blog/2016/06/30/install-chef-on-raspberry-pi-with-…

4 7

MariaDB Galera Cluster
by Marc Schieder 25 Jul '16

25 Jul '16

2 1

Additional APM patches for CentOS sig-altarch7-aarch64
by Phong Vo 19 Jul '16

19 Jul '16

Hi Jim, Please help integrate the attached patch from APM. This is a combo patch on top of sig-altarch7-aarch64 git tree. All component patches are roll-ups from upstream kernel. Thanks, -Phong

2 1

Devtoolset and other software collections items for AArch64
by Lamar Owen 19 Jul '16

19 Jul '16

I'm running a couple of ODROID-C2's on C7 with the Hardkernel 3.14 aarch64 kernel. As it stands, the C7-provided GCC 4.8.5 will not successfully compile the kernel; the preferred gcc is 4.9.2, the linaro one for cross-compile. Would it be possible to get devtoolset-3 with gcc4.9.2 built for aarch64?

5 5

Re: [Arm-dev] NXP more driver patches on LS2080 SoC
by Lijun Pan 15 Jul '16

15 Jul '16

Hi Jim, This solution is not acceptable to me. You not only used "git apply", but also changed the commit message of the original patch, which explains you were quite diligent, not sloppy. Please use “git am *Lijun’s.patch”, "git rebase -i HEAD~5" and "git push —-force” to correct this error. After you do that, other users can update their git repo via “git remote update —prune;” to force a update. It does not change their commit content but their SHA. I think the author name changes is a very serious problem. Almost nobody looks at the changelog of the .spec. What people cares is the author name in the commit message. So I insist change it back to me (Lijun Pan) at the commit message not just add something in the .spec. Thanks, Lijun On 7/14/16, 7:00 PM, "Jim Perrin" <jperrin(a)gmail.com on behalf of jperrin(a)centos.org> wrote: >Taking this off-list. > >Hmm, it appears I was sloppy with my git. I did a 'git apply' of your >patch instead of a 'git am'. No offense was intended, but since it's >been pushed, fixing it would require a --force (If there's a way to >rewrite the history without that, please let me know). I would rather >not break the repo for other users by forcing a history rewrite, however >I'm happy to add additional lines in the %changelog of the .spec >referencing the patch, and that it came from you. > >Is that acceptable? > >On 07/14/2016 02:32 PM, Lijun Pan wrote: >> Hi Jim, >> >> I see my patch being merged today. But the author was changed. >> Also I find the previous usb related patch is under your name. >> I request you change the author back to Me (Lijun Pan) as a respect of >> my work. >> >> Thanks, >> >> >> >> _/ _/_/_/_/_/ >> _/ Lijun Pan _/ _/ >> _/ 347-828-1413 _/_/_/_/_/ >> _/ _/ _/ _/ _/ _/_/ _/ _/ _/_/_/_/ >> _/_/ _/ >> _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ >> _/ _/ _/ >> _/_/_/_/ _/ _/ _/_/_/_/ _/ _/_/ _/ _/_/_/_/_/ >> _/ _/_/ >> _/ >> _/ >> _/ _/ >> _/_/ >> >> On Wed, Jun 29, 2016 at 10:00 PM, Jim Perrin <jperrin(a)centos.org >> <mailto:jperrin@centos.org>> wrote: >> >> >> >> On 06/27/2016 05:49 PM, Lijun Pan wrote: >> >> > I have reworded #8 in a more understandable way. #8 is necessary >> > for all the FSL_IFC related configuration on ARM64. #8 only affects >> > FSL_IFC, >> > not affecting other vendor's drivers. That being said, #8 is harmless. >> > I have taken #9 out. >> > I have attached version 2 of the patch. >> >> >> Looks good. Merged and built as the .29 kernel. This should show up as >> an update soon. >> >> -- >> Jim Perrin >> The CentOS Project | http://www.centos.org >> twitter: @BitIntegrity | GPG Key: FA09AD77 >> _______________________________________________ >> Arm-dev mailing list >> Arm-dev(a)centos.org <mailto:Arm-dev@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 >> > >-- >Jim Perrin >The CentOS Project | http://www.centos.org >twitter: @BitIntegrity | GPG Key: FA09AD77

2 2

Pine64, kernel, installer
by Ed Brand 14 Jul '16

14 Jul '16

Not on PC, spawning new thread on topic but would like to help. Need me to test latest 4.x kernel and figure out kernel config diffs needed? Sent from my iPhone

1 0

NXP more driver patches on LS2080 SoC
by Lijun Pan 14 Jul '16

14 Jul '16

Hi Jim, Please review and help merge the attached patch for NXP. The patch is re-based on top of sig-altarch7-aarch64 branch. Thanks, Lijun

3 6

Small announcement: virt-builder CentOS 7.2 aarch64 image
by Richard W.M. Jones 14 Jul '16

14 Jul '16

You can now do: virt-builder centos-7.2 --arch aarch64 to get a CentOS 7.2 aarch64 image. The --arch parameter is not required if your host is aarch64, since it defaults to finding the same guest arch as host arch. Some other things you might try (these work as non-root too): virt-builder centos-7.2 \ --arch aarch64 \ --size 20G \ --hostname myguest --timezone Europe/London \ --root-password password:123456 \ --update --selinux-relabel virt-install --import --name myguest --ram 2048 \ --disk path=centos-7.2.img,format=raw --os-variant centos7.0 Note there is an updated virt-builder package available which is similar to what RHEL and CentOS will have in 7.3: https://people.redhat.com/~rjones/libguestfs-RHEL-7.3-preview/ Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW

2 1

BananaPi R1 - Lamobo R1 DMESG Errors
by mo.ucina 14 Jul '16

14 Jul '16

Hello Hans, I am looking for bit of advice on how to handle these errors I see in the dmesg print , it starts here : [ 0.077227] pinctrl core: initialized pinctrl subsystem [ 0.079533] NET: Registered protocol family 16 [ 0.080837] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.094301] No ATAGs? [ 0.094369] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.094438] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.096654] Serial: AMBA PL011 UART driver [ 0.123022] reg-fixed-voltage ahci-5v: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/ahci_pwr_pin@0, deferring probe [ 0.123139] reg-fixed-voltage usb0-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb0_vbus_pin@0, deferring probe [ 0.123219] reg-fixed-voltage usb1-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb1_vbus_pin@0, deferring probe [ 0.123296] reg-fixed-voltage usb2-vbus: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/usb2_vbus_pin@0, deferring probe [ 0.124307] reg-fixed-voltage gmac-3v3: could not find pctldev for node /soc@01c00000/pinctrl@01c20800/gmac_power_pin@0, deferring probe and then continues with this bit a little later : [ 4.281094] vcc3v0: disabling [ 4.284161] vcc3v3: disabling [ 4.287152] vcc5v0: disabling [ 4.290160] ahci-5v: disabling [ 4.293252] usb0-vbus: disabling [ 4.296498] usb1-vbus: disabling [ 4.299759] usb2-vbus: disabling [ 4.303004] gmac-3v3: disabling I have been compiling my own kernels from Fedora src rpms due to the need to add in the 'b53' switch drivers . I have just used standard Fedora CONFIGs with addition of CONFIG_PHY_SUN4I_USB=y CONFIG_MFD_AXP20X=y CONFIG_AXP20X_POWER=y CONFIG_INPUT_AXP20X_PEK=y CONFIG_REGULATOR_AXP20X=y But this did not seem to make any difference . Is there something that I am missing out in config , or a patch somewhere in the dts ? Any information welcomed . Best Regards Milorad

1 0

RPi 3, CentOS 7 install problem
by Steve Berg 12 Jul '16

12 Jul '16

Trying to get CentOS-Userland-7-armv7hl-Minimal-1603-RaspberryPi3.img installed to a SanDisk 64G SD card for a Raspberry Pi3. The dd goes well, the Pi will boot with no problems. I run "touch /.rootfs-repartition" and then a reboot. It seems to do the repartition but I get a kernel panic at the next reboot. On the console I see: ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,3) Any tips on how to get the SD card repartitioned to use the whole space after install? -- //- Fixer of that which is broke -// //- Home = sberg(a)mississippi.com -// //- Sinners can repent, but stupid is forever. -//

3 5

TFTP issue with PXE loaded grubaa64.efi
by Sakar Arora 12 Jul '16

12 Jul '16

Hi Jim, While testing CentOS 7 installation on LS2080a RDB, only on one of setups, we found this strange issue, where grub wasn't able to TFTP the boot images from TFTP server. We use grubaa64.efi provided on CentOS website<http://mirror.centos.org/altarch/7/os/aarch64/EFI/BOOT/>. >From the tftp server logs we found that the tftp transaction would always stop with a 'timeout' error. A quick search got me this bug<https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1508893> logged in Ubuntu bug tracking system. There was a mention of a patch, which is supposed to fix this issue. So, I went ahead and created a grub image with the latest upstream grub source code (git.savannah.gnu.org/grub.git) Using this grub image, fixed the issue with TFTP transfers. But, there's different kind of issue with this new grub image. It doesn't seem to be fully compatible with UEFI PXE boot protocol. When loading grub via UEFI PXE boot, the tftp server address does not get set in the grub environment variables, as was the case with grubaa64.efi from CentOS that we use. Can you share you views on this? Thanks, Sakar

1 0

next steps for altarch with ceph and openstack
by Jim Perrin 08 Jul '16

08 Jul '16

With the work that Marcin has done for openstack on aarch64, as well as the ceph builds, we need to begin working a plan for publishing these builds to a mirror. I'd like to identify the steps needed, and the ownership for those steps. Thomas please correct/update these as needed 1. new tag in cbs for aarch64 build, with modified dist for mitaka. Will ceph need this as well? 2. If we wish to re-use the centos-release-openstack-mitaka noarch, dependencies of centos-release-ceph-hammer, centos-release-qemu-ev, centos-release-storage-common, and centos-release-virt-common need to be addressed. Alternately we could create a centos-release-openstack-mitaka-experimental for now if it can work stand-alone. 3. Mirror locations on buildlogs and mirrors need to be created and tested. Possible adjustments to existing -release files due to the /altarch/ vs centos path differences. 4. Package signing. This should already work with existing infra, but need to test and validate. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

5 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev July 2016