Arm-dev May 2018

arm-dev@lists.centos.org

9 participants
10 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

Generic armhfp / aarch64 root filesystem for CentOS 7.5.1804
by Uli Middelberg 17 Sep '18

17 Sep '18

Hi Fabian, hi Jim, the CentOS 7.5.1804 iso images have been released for a while now and I'm wondering if you have plans to provide a generic armhfp / aarch64 root filesystem [1],[2] as well? Cheers Uli [1] https://armv7.dev.centos.org/repodir/images-testing/CentOS-Userland-7-armv7… [2] http://mirror.centos.org/altarch/7.4.1708/isos/aarch64/CentOS-7-aarch64-roo…

2 2

Changes for the next armhfp release/images
by Fabian Arrotin 06 Jun '18

06 Jun '18

Hi list, Time permitting, in the last days/weeks, we worked with Pablo (thanks again) to catch up with some things in the CentOS armhfp land. So we'd like to discuss some of the changes we'll probably implement for the next 7.5.18xx release (we still don't know when that will happen though) : # images : - we'll switch from our current rbf scripts to appliance-creator, and we'll host the used kickstart files so that everybody can also respin various images or variants - as we now have Gnome/KDE working correctly and all built, we'll probably start building such images (like for Fedora) - selinux context is now good so doesn't need the "touch /.autorelabel && systemctl reboot" to then switch to enforcing mode - one "Generic" image to rule them all ! Idea is to not build/test for boards like cubietruck/bananapi/etc, as it's all supported upstream, but only one generic image/variant (like minimal or gnome) and just adapt the uboot bootloader. The only exception though will be for raspberrypi (2 and 3 ) : while the Generic image will work (tested already) with upstream kernel, we'll still offer a variant using the rpi foundation kernel, as we did in the past, as that will ensure that such users will also continue to get kernel updates as they get those right now # kernel: - we'll rebase to 4.14.x (new upstream LTS version, even if 4.9.x is still maintained upstream) : that will permit to support more boards probably (rpi kernel will also get a bump, already built too in testing) # uboot-tools : already updated to 2018.03 to also support more boards, but that will become mandatory as we'll *not* build specific images for specific board (as the Generic one can be used everywhere, and will only need the dd if= of=/dev/mmbclk0 for the uboot bootloader -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

4 9

That was exciting! :-/
by Ian Pilcher 01 Jun '18

01 Jun '18

Ran a 'yum update' on my Banana Pi firewall this morning and ended up with an unbootable system. (The previous kernel wouldn't boot either.) I ended up copying my entire SD card, installing the latest image, growing the / partition, and copying the old root filesystem over. Ultimately, I was able to get everything up and running. This system was originally installed with CentOS-Userland-7-armv7hl-Minimal-1611-BananaPi.img.xz. I'm mainly wondering if this was expected. If so, did I miss the warnings? If not, I do still have the dump of the unbootable post- upgrade SD card sitting around, if anyone who understands the boot process on these things wants to investigate. Either way, thanks for all the work that you all do! -- ======================================================================== Ian Pilcher arequipeno(a)gmail.com -------- "I grew up before Mark Zuckerberg invented friendship" -------- ========================================================================

2 7

Is there any tool to create live cd for CentOs ?
by Aung PhyoKyaw 30 May '18

30 May '18

Hi I was able to cerate a customized live CentOS iso on x86_64 architecture using LiveCD -tools But I was trying to create the LIve CD on ARM64 architecture system using that tools but so far i was not able to create it. So is there any alternative tools to create a customized Live CD for ARM64. Thanks Aung

4 8

Fwd: rainbow screen after "yum update" on 5/18/2018
by Kenneth Freidank 20 May '18

20 May '18

---------- Forwarded message ---------- From: Kenneth Freidank <kenneth.freidank(a)gmail.com> Date: Sat, May 19, 2018 at 8:02 PM Subject: Re: [Arm-dev] rainbow screen after "yum update" on 5/18/2018 To: Pablo Sebastián Greco <pablo(a)fliagreco.com.ar> Thank you for the suggestion. I burned another sd card, and my PI3 booted, so it is definitely the sd card with the problem. After booting, I was able to mount the bad sd card with a USB port adapter. # mount /dev/sda3 /mnt <-- the main linux partition df on /mnt showed 46% full # mount /dev/sda1 /mnt <-- the ms-dos boot partition df on /mnt showed 32% full but I did get an "unmounted properly", may contains errors, run fsck On Sat, May 19, 2018 at 4:44 PM, Pablo Sebastián Greco < pablo(a)fliagreco.com.ar> wrote: > Hi Kenneth > > El 19/5/18 a las 14:18, Kenneth Freidank escribió: > >> I just updated my Centos7 Pi3 "yum update" on 5/18/2018, and now I am >> facing a rainbow screen. Red pwr light is nice and strong, even changed >> power supplies. Green ACK light blinks 2 times and stays off. Screen is >> stuck on the rainbow - no activity, nothing, with or without the USB drive, >> nothing. USB drive does not power up either - nothing. Tried pressing the >> keys 1 to 4 at power up, then any key on multiple pwr ups, no effect. >> Found a similar post on https://www.raspberrypi.org/forums, search >> "raspberry pi3 stuck on rainbow screen after Jessie update". >> >> Removed micro card and read files on another machine >> >> Without listing all the files individually, kernel7.img, the dtb files >> bcm2708-rpi-xxx.dtb, bcm2710-rpi-xxx.dtb, bcm2835-rpi-xxx.dtb, >> bcm2836-rpi-xxx.dtb, gcm2837-rpi-xxx.dtb. All are dated 5/18/2018, the day >> of my yum update. >> >> The kernel is kernel-4.14.27-v7.1.e7.img dated 3/19/2018. >> >> Other files bookcode.bin, fixup*.*, LICENCE.broadcom, start*.elf, >> COPYING.linux all date 3/16/2018. >> >> A file initrd-plymouth.img dates 2/26/2018. >> >> I also see what look like older kernel files: kernel-4.9.75-v7.1.el7.img >> - 1/9/2018; kernel-4.9.70-v7.1.el7.img - 12/19/2017; >> kernel-4.9.64-v7.1.el7.img - 11/24/2017; kernel-4.4.26-v7.1.el7.img - >> 10/22/2016. >> > Looking at that amount of older kernels makes me suspect that you run out > of space in /boot while updating, please check that . > >> >> Any ideas on how to downgrade to previous kernel or how to fix this? >> Can't get into single user mode - pressing keys on pwr up has no effect. I >> don't know enough about the kernel and the boot process to start messing >> with them. I am stuck. >> > > Copying some of the older files in /boot should make the older kernel > work, but please don't do that until we checked for disk space. > Thanks. > Pablo > >

1 0

rainbow screen after "yum update" on 5/18/2018
by Kenneth Freidank 19 May '18

19 May '18

I just updated my Centos7 Pi3 "yum update" on 5/18/2018, and now I am facing a rainbow screen. Red pwr light is nice and strong, even changed power supplies. Green ACK light blinks 2 times and stays off. Screen is stuck on the rainbow - no activity, nothing, with or without the USB drive, nothing. USB drive does not power up either - nothing. Tried pressing the keys 1 to 4 at power up, then any key on multiple pwr ups, no effect. Found a similar post on https://www.raspberrypi.org/forums, search "raspberry pi3 stuck on rainbow screen after Jessie update". Removed micro card and read files on another machine Without listing all the files individually, kernel7.img, the dtb files bcm2708-rpi-xxx.dtb, bcm2710-rpi-xxx.dtb, bcm2835-rpi-xxx.dtb, bcm2836-rpi-xxx.dtb, gcm2837-rpi-xxx.dtb. All are dated 5/18/2018, the day of my yum update. The kernel is kernel-4.14.27-v7.1.e7.img dated 3/19/2018. Other files bookcode.bin, fixup*.*, LICENCE.broadcom, start*.elf, COPYING.linux all date 3/16/2018. A file initrd-plymouth.img dates 2/26/2018. I also see what look like older kernel files: kernel-4.9.75-v7.1.el7.img - 1/9/2018; kernel-4.9.70-v7.1.el7.img - 12/19/2017; kernel-4.9.64-v7.1.el7.img - 11/24/2017; kernel-4.4.26-v7.1.el7.img - 10/22/2016. Any ideas on how to downgrade to previous kernel or how to fix this? Can't get into single user mode - pressing keys on pwr up has no effect. I don't know enough about the kernel and the boot process to start messing with them. I am stuck.

2 1

Re: [Arm-dev] Fwd: Re: [question] sig-altarch repo updates
by Vadim Lomovtsev 17 May '18

17 May '18

Hi Pablo, > > Vadim, is this what you are looking for > https://git.centos.org/log/rpms!kernel-alt.git/c7-alt ? Yes, it seems that this one I was looking for. Thank you. WBR, Vadim > > Pablo. > > El 17/5/18 a las 05:50, Vadim Lomovtsev escribió: > > Hi all, > > > > As the 1804 is announced by following: > > https://lists.centos.org/pipermail/centos-announce/2018-May/022829.html > > > > would the SIG AltArch git repo > > https://git.centos.org/log/sig-altarch!kernel.git/sig-altarch7-aarch64 > > be updated accordingly ? > > > > WBR, > > Vadim > > _______________________________________________ > > Arm-dev mailing list > > Arm-dev(a)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 >

2 1

[question] sig-altarch repo updates
by Vadim Lomovtsev 17 May '18

17 May '18

Hi all, As the 1804 is announced by following: https://lists.centos.org/pipermail/centos-announce/2018-May/022829.html would the SIG AltArch git repo https://git.centos.org/log/sig-altarch!kernel.git/sig-altarch7-aarch64 be updated accordingly ? WBR, Vadim

2 1

Question
by Aung PhyoKyaw 10 May '18

10 May '18

Hi I am new to the CentOS dev group and I would like to know how can i post the CentOS ARM64 architecture related issue? Thanks Allan

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev May 2018