Arm-dev

arm-dev@lists.centos.org

1 participants
685 discussions

SD backup and restore
by Chris Szilagyi 23 Jun '18

23 Jun '18

Hello: Just curious if anybody has a known working solution (for Linux, not Windows) to backup and restore the SD card. In particular one that will shrink the image and only use the space utilized on the card itself, and allow restoring to a different size SD card. I figure there might be a process to create the images that are provided for this distro, but I'm unable to figure out how they are created. I've been searching for and trying various scripts for other distros, and so far no luck in getting a working solution for this CentOS distro. Thank you very much. -- Chris

2 1

Support for Raspberry Pi 1 ?
by Chris Szilagyi 07 Jun '18

07 Jun '18

Hello: I have been using CentOS Userland armv7hl for a while now on the officially supported boards. Is there any support at all or any way to run it on a Raspberry Pi 1 board? In particular the Raspberry Pi 1 model B. I haven't been able to find any information, and not sure what the official answer is. Thank you very much for all of the work on this release, it is great stuff! -- Chris

3 4

Centos on RPI3 USB Booting
by Steven Ellis 06 Jun '18

06 Jun '18

Anyone managed to get the latest Centos image to boot via USB rather than microSD Card. I'm trying the following image - CentOS-Userland-7-armv7hl-RaspberryPI-Minimal-1804-sda.raw.xz It works find on a 16 GB MicroSD card I've confirmed that the USB Boot mode is enabled based on - https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/ms… # vcgencmd otp_dump | grep 17: 17:3020000a Steven -- Steven Ellis Senior Solution Architect - Red Hat New Zealand <http://www.redhat.co.nz/> *T:* +64 9 887 3207 *M:* +64 21 321 673 *E:* sellis(a)redhat.com

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

EPEL for ARM testing/validation
by Steven Ellis 06 Jun '18

06 Jun '18

Is there a formal process for testing / validating the ARM builds for EPEL? I'm currently using the following repository # more /etc/yum.repos.d/epel-arm.repo [epel-arm] baseurl = https://armv7.dev.centos.org/repodir/epel-pass-1/ enabled = 1 gpgcheck = 0 name = CentOS EPEL for ARM For example - are their EPEL packages that aren't currently in the ARM release that need validation - is there a process to tag a release as "end user" tested? Steven -- Steven Ellis Senior Solution Architect - Red Hat New Zealand <http://www.redhat.co.nz/> *T:* +64 9 887 3207 *M:* +64 21 321 673 *E:* sellis(a)redhat.com

2 1

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

Fwd: ARM64 CentOS AltArch release 7.5
by Frederik Lotter 01 Jun '18

01 Jun '18

Hi, I have two questions: > (1) In 7.3 CentOS released a rootfs tar for ARM64. I can no longer find this under the 7.5 release. Furthermore, I could also not find anything on the ISO that seems rootfs-like in any near complete state. The closest was the LiveOS/rootfs.img, but it seems this is not a complete fs as yum is missing components, for example. > > So my question is: Is there any way to still use CentOS releases on new ARM64 development environments (without EFI boot support)? I have sent this to the wrong mailing list and I see that 7.5 rootfs images are on their way. However, is there any change on the status of this? (2) In terms of UEFI firmware support in the ARM64 world (e.g. EDKII vs Uboot), is there any officially supported solution for CentOS, or do you simply support whatever supports the UEFI interface? Regards, Fred

1 0

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

← Newer
1
...
16
17
18
19
20
21
22
...
69
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev