Arm-dev December 2018

arm-dev@lists.centos.org

16 participants
25 discussions

Re: [Arm-dev] centos 7 64 bit on raspberry Pi 3
by Mark Verlinde 15 Dec '18

15 Dec '18

-----Oorspronkelijk bericht----- > Afzender:Pablo Sebastián Greco <pablo(a)fliagreco.com.ar> > Verstuurd: Zaterdag 15 December 2018 14:06 > Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> > Onderwerp: Re: [Arm-dev] centos 7 64 bit on raspberry Pi 3 > > > El 15/12/18 a las 08:58, Pablo Sebastián Greco escribió: > > > > That is my guess too, but we're providing this kernel also > > (http://mirror.centos.org/altarch/7.6.1810/kernel/aarch64/Packages/) > > which is pretty close to the Fedora kernel. > > So if you could create a ISO with that kernel, it "should" work. > > > I meant, to upstream kernel. The one that is close to Fedora is 4.19 > from here > https://armv7.dev.centos.org/repodir/community-kernel-latest/kernel/4.19.7-…, > but that is only built for armhfp at the moment. Some while ago did some work on this, resulting in a prematurely image with a at the time of creation latest kernel 4.18.16-202. It was not my intention to make a aarch64 image for a RPI, nor will it be in the future; Just out of "academic curiosity " installed bcm283x-firmware and rpi3-u-boot.bin to try to boot it with a RPI. And it did :) _Note_ this is far from anything decent at least it boots :) (1) https://drive.google.com/open?id=1RIWYxPadxsf_M-igFxPaP8FmwKA3Jcki It boots very slow! Especially on a RPI going through bootcode.bin > uboot > grubaa64.efi > grub2 > kernel The kernel is cross complied from the equivalent community-kernel source package Pablo made for armhfp with the command (in which you may ignore --define="dist .ns7") : rpmbuild --ba --target aarch64 --with=cross --without=perf --without=tools --without=debuginfo --define="dist .ns7" --define="_arch aarch64" --define="_build_arch aarch64" --define="__strip /usr/bin/aarch64-linux-gnu-strip" kernel.spec cross tools installed: $ rpm -qa | grep aarch64 binutils-aarch64-linux-gnu-2.27-9.el7.1.x86_64 gcc-aarch64-linux-gnu-4.8.5-16.el7.1.x86_64 gcc-c++-aarch64-linux-gnu-4.8.5-16.el7.1.x86_64 It's on my todo list to get this to a next level; Maybe we can cooperate on this, though (as said before) it's not my intend to create (maintain) aarch64 RPI images. AFAIK now, are some of the issues to be dealt with: * uboot-images-armv8 carry a fedora specific patch causing uboot to look in /EFI/fedora for grubaa64.efi * obviously grubby has no understanding for the device-tree on aarch64 and most likely will never have this. * livecd tools, used by the application tools to create images for armhfp has no aarch64 support. (2) * probably a lot more... Grzt Mark (1)l link to kickstart file used to create image : https://github.com/markVnl/nethserver-createimg/blob/ks_wip/ks/Centos-Uboot… (2) patch to provide basic aarch64 support for livecd tools / imgcreate, _Note_ it does not provide full support, among other things EFI/centos/grub.cfg is not created... https://github.com/markVnl/nethserver-createimg/blob/master/SPEC-appliance-… > > > > > > Pablo. > > > > El 14/12/18 a las 19:57, Gordan Bobic escribió: > >> I'm hazarding a guess that the stock CentOS 7 aarch64 kernel isn't > >> built to include support for the Pi. > >> > >> On Fri, 14 Dec 2018, 22:10 Steven Ellis <sellis(a)redhat.com > >> <mailto:sellis@redhat.com> wrote: > >> > >> Ok so I've tried the CentOS-7-aarch64-Minimal-1810.iso with the > >> UEFI tools from > >> - https://github.com/andreiw/RaspberryPiPkg > >> > >> Can't get the ISO to boot. I've tried acpi=off but that hasn't > >> made a difference. > >> > >> Any other tips? > >> > >> On Fri, 14 Dec 2018 at 18:39, Steven Ellis <sellis(a)redhat.com > >> <mailto:sellis@redhat.com>> wrote: > >> > >> Has anyone got this working on a Pi3+ and can provide guidance. > >> > >> I've got UEFI working already but I haven't tried a generic > >> aarch64 centos ISO yet > >> > >> On Wed, 28 Nov 2018 at 12:48, R > >> <riccardo.veraldi(a)presid.infn.it > >> <mailto:riccardo.veraldi@presid.infn.it>> wrote: > >> > >> so for example I could just dd this image after > >> uncompressing it on the SD card and this would work I Suppose > >> > >> http://vault.centos.org/altarch/7.4.1708/isos/aarch64/CentOS-7-aarch64.img.… > >> > >> > >> On 11/27/18 7:09 AM, Gordan Bobic wrote: > >>> AFAIK the official installer only boots on UEFI aarch64. > >>> Otherwise you'll have to get a working image from somewhere. > >>> > >>> > >>> On Tue, Nov 27, 2018 at 5:44 AM R > >>> <riccardo.veraldi(a)presid.infn.it > >>> <mailto:riccardo.veraldi@presid.infn.it>> wrote: > >>> > >>> ok thank you. > >>> so does it mean that Pi 3 needs a UEFI firmware if I > >>> Want to run CentOS/aarch64 while it does not need if > >>> running CentOS/armhfp ? > >>> thanks > >>> > >>> > >>> On 11/26/18 3:05 PM, Gordan Bobic wrote: > >>>> I haven't tried it yet, but you should be able to > >>>> get UEFI firmware for Pi 3 from here: > >>>> https://github.com/andreiw/RaspberryPiPkg > >>>> > >>>> If you can get that to boot off the ISO, you should > >>>> be able to use the installer. > >>>> > >>>> On Mon, Nov 26, 2018 at 11:01 PM R > >>>> <riccardo.veraldi(a)presid.infn.it > >>>> <mailto:riccardo.veraldi@presid.infn.it>> wrote: > >>>> > >>>> 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 > >>>> > >>>> > >>>> _______________________________________________ > >>>> 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 <mailto:Arm-dev@centos.org> > >>>> https://lists.centos.org/mailman/listinfo/arm-dev > >>> > >>> > >>> > >>> _______________________________________________ > >>> 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 <mailto:Arm-dev@centos.org> > >> https://lists.centos.org/mailman/listinfo/arm-dev > >> > >> > >> > >> -- > >> > >> Steven Ellis > >> > >> APAC PRINCIPAL PRODUCT MANAGER - STORAGE > >> > >> TECHNICAL PORTFOLIO EVANGELIST - APAC > >> > >> Red Hat Asia Pacific - Auckland NZ <https://www.redhat.com/> > >> > >> sellis(a)redhat.com <mailto:sellis@redhat.com> M: > >> +64 21 321 673 > >> > >> <https://www.redhat.com/en>TRIED. TESTED. TRUSTED. > >> <https://redhat.com/trusted> > >> > >> > >> > >> -- > >> > >> Steven Ellis > >> > >> APAC PRINCIPAL PRODUCT MANAGER - STORAGE > >> > >> TECHNICAL PORTFOLIO EVANGELIST - APAC > >> > >> Red Hat Asia Pacific - Auckland NZ <https://www.redhat.com/> > >> > >> sellis(a)redhat.com <mailto:sellis@redhat.com> M: +64 21 > >> 321 673 > >> > >> <https://www.redhat.com/en>TRIED. TESTED. TRUSTED. > >> <https://redhat.com/trusted> > >> _______________________________________________ > >> 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 > > > > _______________________________________________ > > 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 >

1 0

Re: [Arm-dev] Instructions for installation on an Odroid HC1
by Robert Moskowitz 13 Dec '18

13 Dec '18

Pablo, I have been busy on the Fedora-arm list getting F29 working on the Odroid-HC1. I figured if I could get F29 working, I could port that knowledge over to Centos-arm. More on what I accomplished later... I grabbed this image, dropped it on a uSD, did the various needed steps and tried to boot. It failed because there is nothing really in /boot! ============== U-Boot 2018.09 (Sep 11 2018 - 09:51:41 +0000) for ODROID-XU3/XU4/HC1 CPU: Exynos5422 @ 800 MHz Model: Odroid XU3 based on EXYNOS5422 Board: Odroid XU3 based on EXYNOS5422 Type: hc1 DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2 Loading Environment from MMC... Card did not respond to voltage select! *** Warning - No block device, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 MMC Device 1 not found no mmc device at slot 1 Card did not respond to voltage select! switch to partitions #0, OK mmc2 is current device Scanning mmc 2:2... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 685 bytes read in 4 ms (167 KiB/s) Ignoring unknown command: ui Ignoring malformed menu command: autoboot Ignoring malformed menu command: hidden Ignoring unknown command: totaltimeout CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 Boot Options. 1: CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 (4.19.5-300.el7.armv7 hl) Enter choice: 1: CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 (4.19 .5-300.el7.armv7hl) Retrieving file: /initrd-4.19.5-300.el7.armv7hl.img ** File not found /initrd-4.19.5-300.el7.armv7hl.img ** Skipping CentOS-Userland-7-armv7hl-generic-Minimal-419-1810 (4.19.5-300.el7.armv 7hl) for failure retrieving initrd SCRIPT FAILED: continuing... starting USB... USB0: USB EHCI 1.00 USB1: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 ====================== no initrd for starters... Bob On 12/3/18 5:45 AM, Pablo Sebastián Greco wrote: > > Robert, I didn't want to send this to the list, but the image that > will appear on the mirrors are temporarily hosted here > https://armv7.dev.centos.org/repos/images/. > > You'll see that there is a generic-419, it is a test image I built > (never had time to test myself), that comes with kernel 4.19 instead > of 4.14, so it can be used with newer devices. > > Let me know how it goes..... :) > > Pablo. > > El 2/12/18 a las 22:59, Robert Moskowitz escribió: >> The power supply and serial connection came today, so now to build my >> first image. >> >> I see that we are still on the 1804 images, and seem to recall that >> there was work to do to get that working. >> >> Can someone give me the current recommended installation steps? >> >> I would prefer that all partitions are on the sata drive, only uboot >> on the uSD. >> >> thanks. >> >> _______________________________________________ >> Arm-dev mailing list >> Arm-dev(a)centos.org >> https://lists.centos.org/mailman/listinfo/arm-dev

2 27

xscreensaver missing from xfce group
by Robert Moskowitz 13 Dec '18

13 Dec '18

I am trying to add xscreensaver manually. I did a yum install xscreensaver and it also installed the following dependencies: 1:xscreensaver-gl-base-5.39-3.el7.armv7hl 1:xscreensaver-5.39-3.el7.armv7hl 1:xscreensaver-base-5.39-3.el7.armv7hl 1:xscreensaver-extras-5.39-3.el7.armv7hl 1:xscreensaver-gl-extras-5.39-3.el7.armv7hl And when I vnc to the system and wait, xscreensaver kicks in with the defaults. But the control app is not in applications > settings And I can't figure out what to install. greping for xscreensaver frm a yum list, I get: cinnamon-screensaver.armv7hl 3.6.1-2.el7 epel cinnamon-screensaver-unsupported.noarch 3.6.1-2.el7 epel gnome-screensaver.armv7hl 3.6.1-14.el7 epel kdeartwork-screensavers.armv7hl 4.10.5-4.el7 base mate-screensaver.armv7hl 1.16.1-1.el7 epel mate-screensaver-devel.armv7hl 1.16.1-1.el7 epel xscreensaver.armv7hl 1:5.39-3.el7 epel xscreensaver-base.armv7hl 1:5.39-3.el7 epel xscreensaver-extras.armv7hl 1:5.39-3.el7 epel xscreensaver-extras-gss.armv7hl 1:5.39-3.el7 epel xscreensaver-gl-base.armv7hl 1:5.39-3.el7 epel xscreensaver-gl-extras.armv7hl 1:5.39-3.el7 epel xscreensaver-gl-extras-gss.armv7hl 1:5.39-3.el7 epel What of the above might be the control app? thanks

2 2

Re: [Arm-dev] File system corruption
by Gordan Bobic 13 Dec '18

13 Dec '18

> Are you using GPT partitions? GPT will lose the backup partition label > since it is at the back of the block device. Easy way to spot a "fake" > flash card as those just throw away everything past the end of the actual > data. > > A stress test will kill an under managed flash device VERY quickly, a > typical USB stick or SD card might only survive 4 passes of badblocks from > new due to poor management, garbage collection and large erase blocks. > > If you are suspecting actual genuine corruption, try ZFS (if you are > struggling, ask, I'll do my best to talk you through it). It yields better > performance and less wear on low end flash due to it's copy on write nature > and compression, and will confirm corruption beyond any doubt because it > checksums every block it writes. >

1 0

Xfce desktop works
by Robert Moskowitz 12 Dec '18

12 Dec '18

Even on the headless Odroid-HC1! Pablo, thanks for getting the Xfce group into epel! Steps I took was: Add epel repo per the CentOS arm web site. yum groupinstall xfce This should be enough for those of you with a standard video console. But the HC1 is headless, and if you also want to use vnc.... first follow the instructions to install vncserver per my instructions at http://medon.htt-consult.com/Centos7-armv7.html I will be updating this... log into the user account. run vncpasswd You typically have to do this after installing vncserver and before starting it. after getting a successful start of vncserver (may take a system reboot), log into the user account, and edit ~/.vnc/xstartup, delete the last two lines and append: exec /bin/sh /etc/xdg/xfce4/xinitrc xrdb $HOME/.Xresources startxfce4 & restart vncserver and you can now vnc into your server. Even a headless HC1.

1 1

Observations regarding armhfp images
by Mark Verlinde 12 Dec '18

12 Dec '18

Hi list, Utilizing the appliance tools to create (custom) images for a while and going through this process again with the 7.6 release,; I’d like to share some observations / topics and (if applicable) workarounds for them with you. Being aware it is not considered good practice to address multiple topics in one post, opted to do this as you see in an attempt not to spam this list to much. If someone wants to discuss one specific topic I suggest to reply with an altered subject to split this of in a separate thread. Note all references to an image are always to the minimal image without a DE __ CPU-governor defaults to powersave on RaspberryPI image __ # cat /sys/devices/system/cpu/cpufreq/policy0/scaling_governor powersave In practice this means our RPI's permanently clock on the minimal cpu frequency In absence of user-space tools opted to create a (system) service unit which echoes _ondemand_ in the scaling governor of each cpu: # cat /etc/systemd/system/multi-user.target.wants/cpu_governor.service [Unit] Description=Set cpu governor to ondemand [Service] Type=oneshot ExecStart=/bin/sh -c " for i in {0..3}; do echo ondemand > sys/devices/system/cpu/cpu$i/cpufreq/scaling_governor; done" [Install] WantedBy=multi-user.target __ kdump service fails on RPI and Generic image __ RPI image (with raspberrypi2 kernel) : # journalctl | grep kdump .… kdumpctl[1569]: Kdump is not supported on this kernel … . kdumpctl[1569]: Starting kdump: [FAILED] Generic image (with generic kernel): # journalctl | grep kdump … . kdumpctl[3764]: No memory reserved for crash kernel … . kdumpctl[3764]: Starting kdump: [FAILED] Workaround in place is simply mask the kdump.service (systemctl mask kdump.service) __(unneeded?) creation of legacy _uImage_ and _uInitrd_ by grubby on Generic image __ In an attempt to reduce the size of the shipped image and (ultimately) the boot partition I had a look at the content of /boot. AFIAK the _uImage_ and _uInitrd_ are not used by syslinux (extlinux) boot method and can safely, with their (versioned) copies, be removed. # df -h | grep /boot /dev/mmcblk0p2 641M 166M 469M 27% /boot /dev/mmcblk0p1 29M 13M 17M 45% /boot/fw # rm -f uI* # df -h | grep /boot /dev/mmcblk0p2 641M 71M 564M 12% /boot /dev/mmcblk0p1 29M 13M 17M 45% /boot/fw To make this behavior persistent grubby would need a quite comprehensive patch containing more or less the commit linked below: https://src.fedoraproject.org/cgit/rpms/grubby.git/diff/drop-uboot-uImage-c… also see: https://src.fedoraproject.org/cgit/rpms/grubby.git/commit/?id=c5aefcde03e38… __ Kernel dependency on kernel-headers __ This seems to be caused by the xorg-x11-drv-vmmouse dependency of the kernel provided by kernel-headers. # rpm -q --requires kernel kernel-core-uname-r = 4.14.82-201.el7.armv7hl kernel-modules-uname-r = 4.14.82-201.el7.armv7hl xorg-x11-drv-vmmouse >= 14.0.0 … . # rpm -q --whatprovides xorg-x11-drv-vmmouse kernel-headers-4.14.82-201.el7.armv7hl Why the (vmware?) mouse driver is so essential on arm beats me. Grtz Mark

2 1

Re: [Arm-dev] Instructions for installation on an Odroid HC1
by Mark Verlinde 12 Dec '18

12 Dec '18

-----Oorspronkelijk bericht----- > Afzender:Robert Moskowitz <rgm(a)htt-consult.com> > Verstuurd: Dinsdag 11 December 2018 19:42 > Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> > Onderwerp: Re: [Arm-dev] Instructions for installation on an Odroid HC1 > > > > On 12/10/18 2:22 PM, Robert Moskowitz wrote: > > > > YES!!!! > > > > Here is the instructions for installation on the HC1. > > http://medon.htt-consult.com/Centos7-armv7-odroid.html > > Please review and comment. I will link it in and make it generally > available when Pablo gets the image into 'production'. > One little side note: As far as I understand: the concatenation of bootloaders exceeds the start of the first partition @2048KB. Due to ware-leveling algorithms this may be no a issue at all but to be save i'll guess its recommendable to (re)move the first partition. If the image contains the FAT "fw" partition for the Raspberry PI bootloaders i'll sugest to remove the RPI packages and this (first) partition. Grtz Mark

2 1

Which R PI boards are supported?
by david 11 Dec '18

11 Dec '18

Folks I'd like to get the latest Raspberry Pi 3 model B+, which has a 64-bit quad core, wireless, etc, but am concerned whether Centos 7 runs on that system. If not, I'd be happy with an earlier Raspberry Pi system. My choices could be: Raspberry Pi 3 Model B Raspberry Pi 3 model A+ Anyone who has played with these? Thanks David

2 1

weston and chromium
by Skorpeo Skorpeo 10 Dec '18

10 Dec '18

Hi, What are the chances of getting chromium and weston on aarch64? They do exist in fedora if that helps or makes a difference. Fingers crossed!

2 3

Re: [Arm-dev] Instructions for installation on an Odroid HC1
by Mark Verlinde 10 Dec '18

10 Dec '18

-----Oorspronkelijk bericht----- > Afzender:Robert Moskowitz <rgm(a)htt-consult.com> > Verstuurd: Zondag 9 December 2018 23:45 > Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org>; Pablo Sebastián Greco <pablo(a)fliagreco.com.ar> > Onderwerp: Re: [Arm-dev] Instructions for installation on an Odroid HC1 > > > > On 12/9/18 3:45 PM, Pablo Sebastián Greco wrote: > > <snip> > >>> Thanks! Getting it now.... > >> > >> Looks like the same dracut failure. > >> > >> :( > >> > >> > > There must be another module missing, can you decompress the fedora > > initramfs and list the used modules? For the odroid HC1 i added textra drivers as sown below in /etc/dracut.conf.d/odroid_hc1.conf add_dracutmodules+=" dm " omit_dracutmodules+=" network ifcfg plymouth " add_drivers+=" exynosdrm exynos_bus exynos_trng exynos_nocp exynos_rng phy_exynos_dp_video " add_drivers+=" phy_exynos_mipi_video dwc3_exynos clk_exynos_audss i2c_exynos5 dw_mmc_exynos " add_drivers+=" dw_mmc_pltfm dw_mmc phy_exynos_usb2 phy_exynos5_usbdrd pwm_samsung " add_drivers+=" dwc3 ledtrig-heartbeat " also see: https://lists.centos.org/pipermail/arm-dev/2018-October/003578.html and https://gist.github.com/markVnl/7adf25cebfdce5d5009d93b7b4caae96 Hope it helps > > > > You may need to use this command in an empty dir > > > > /usr/lib/dracut/skipcpio $your-img | gunzip -c | cpio -id > > > I will get it to you. Don't know if it will be today, anymore... > > Robert > > _______________________________________________ > Arm-dev mailing list > Arm-dev(a)centos.org > https://lists.centos.org/mailman/listinfo/arm-dev >

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev December 2018