Arm-dev

arm-dev@lists.centos.org

1 participants
685 discussions

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

CentOS 7.x images for ARM
by Stephan Guilloux 07 Dec '18

07 Dec '18

Hi all, Just saw CentOS 7.6 available for ARM. Cool. Now, I had a look to isos/armhfp and saw different images. Can anyone explain the differences between all images ? -KDE- and -GNOME- look obvious, but what about -generic- and -RaspberryPi- ? What about -RootFS- ? Could it be possible to have a README or something to explain all that ? Regards, Stephan.

2 4

Centos aarch64 on Raspberry PI 3B+
by Nick Howitt 06 Dec '18

06 Dec '18

2 1

Re: [Arm-dev] Installing odoo on Centos 7 in raspberry pi 3b
by Jayant Dhole 05 Dec '18

05 Dec '18

Hi Pablo I. Am not using x86_64 as it is not supported on raspberry pi. I. Using either noarch or arm7hl versions. Thankyou On Tue, Dec 4, 2018, 5:36 AM Pablo Sebastián Greco <pablo(a)fliagreco.com.ar wrote: > [image: Boxbe] <https://www.boxbe.com/overview> This message is eligible > for Automatic Cleanup! (pablo(a)fliagreco.com.ar) Add cleanup rule > <https://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Fkey…> > | More info > <http://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=45787961298…> > > Can you tell me where you find the x86_64 versions of the things you're > trying to install? > With that info, I may be able to track down what to build. > The first armhfp server to build things in CBS (where the scls are built) > was added a few days ago, and it has only been used internally, as it is > really behind in content and there is not a plan yet in how to update that > content. > > Pablo. > El 2/12/18 a las 21:47, Jayant Dhole escribiÃ³: > > hi, > I am new to allÂ this and i am trying to install odoo 11 on my raspberry > pi 3 which as centos 7 in it. for some reason i am not able to get all the > packages required for odoo and cannot install python3.5 as well as cannot > get scl repositories. > any help will be appreciated. > Thank you > > JayantÂ > > _______________________________________________ > Arm-dev mailing listArm-dev@centos.orghttps://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 2

Installing odoo on Centos 7 in raspberry pi 3b
by Jayant Dhole 04 Dec '18

04 Dec '18

hi, I am new to all this and i am trying to install odoo 11 on my raspberry pi 3 which as centos 7 in it. for some reason i am not able to get all the packages required for odoo and cannot install python3.5 as well as cannot get scl repositories. any help will be appreciated. Thank you Jayant

2 1

Instructions for installation on an Odroid HC1
by Robert Moskowitz 03 Dec '18

03 Dec '18

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.

1 1

← Newer
1
...
9
10
11
12
13
14
15
...
69
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev