Arm-dev July 2019

arm-dev@lists.centos.org

7 participants
9 discussions

centos 7 64 bit on raspberry Pi 3
by R 23 Sep '20

23 Sep '20

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

6 16

epel-release
by Robert Moskowitz 30 Jun '20

30 Jun '20

Ok, I see this epel-release in the epel1 repo that I installed via the wiki. So I decide to install it, and it created an epel.repo.rpmnew file. I swicth around the files and try a 'yum update' and get: epel/armhfp/metalink | 47 kB 00:00 Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=armhfp error was No repomd file One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: .... File /var/cache/yum/armhfp/7/epel/metalink.xml does not exist So I put everything back.

3 7

bluetooth on CentOS Linux release 7.6.1810
by R C 31 May '20

31 May '20

Hello, I am going to use a raspberry PI for browsing on a TV, so I want to connect with a wireless keyboard, bluetooth. It looks like bluetooth is "not running"; [rocr@centos-rpi3 ~]$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:bluetoothd(8) I don't have any bluetooth devices connected yet. but the service should be up, right? Is there a write-up, guide, to get bluetooth configured? thanks, Ron

2 4

Re: [Arm-dev] Add Marvell Armada7k8k NIC (mvpp2) support patches
by Marcin Wojtas 26 May '20

26 May '20

Hi Jim, It's been a while, since I sent the patch. Any objections about merging? Is v4.11 kernel still a valid baseline or for the next releases or we should use v4.14? When is that transition and next release supposed to happen? Best regards, Marcinsob., 23 cze 2018 o 08:18 Marcin Wojtas <mw(a)semihalf.com> napisał(a): > > Hi, > > I'm sending a patch that is applicable on top of the kernel > sig-altarch7-aarch64 branch. It enables ACPI support for the Marvell > Armada7k8k NIC - this required backporting very big amount of patches > (all merged upstream), hence I decided to attach the single commit, > instead of issueing 'git send-email' of it. > > Despite many attempts I wasn't able to build entire rpm package with > the mock build utility, however I managed to test the clean kernel > v4.11 with applied all patches and built with updated .config. Please > let know if this patch is sufficient and can be merged. > > Thanks, > Marcin

5 21

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

Missing some debuginfo packages on armv7hl
by Gordan Bobic 08 Aug '19

08 Aug '19

I'm still trying to hunt down where this SIGILL I'm hitting is coming from, and the next obstacle I've hit is some missing debuginfo packages, specifically: libGLEW-debuginfo libXau-debuginfo libXext-debuginfo mesa-libGLU-debuginfo Any chance those could be added the the debuginfo repository? Without them gdb chokes before it gets to the SIGILL line. Gordan

2 13

Tracking Down "Illegal instruction" Sources
by Gordan Bobic 17 Jul '19

17 Jul '19

I'm trying to track down the executables/libraries that are behind the "Illegal instruction" errors I am seeing on my Tegra 2 devices. It seems a given that this is due to some packages from the GL stack (Mesa, libglvnd, etc.) having been build with assumptions of NEON always being present, but I'm trying to figure out a way to determine this definitively. I have tried the approach along the lines of: objdump -Ds $file | grep -E 'vadd\.|vmul\.' since vadd and vmul are both NEON assembly instructions, but this seems to flag up nearly everything, most of which is in fact working (e.g. Firefox 52.x). So either my approach is wrong or there are many binaries that do some kind of runtime detection and selectively use NEON if supported by the hardware. The reason i am looking into this is because gdm doesn't work without working GL (even software mesa GL). It works on my Chromebook without hardware accelerated drivers, but doesn't work on my Tegra laptop without accelerated drivers. On the Chromebook (Exynos) glxgears runs (albeit slowly), but on Tegra, it crashes with "Illegal instruction". I tried rebuilding libglvnd and mesa on the local machine in a hope that NEON capability is auto-detected but that doesn't seem to have made any difference. Any advice/suggestions/insights gratefully received.

3 3

CentOS and Raspberry Pi 4 (four)
by Winfried de Heiden 10 Jul '19

10 Jul '19

3 3

Mesa and NEON
by Gordan Bobic 02 Jul '19

02 Jul '19

Is mesa built with NEON on armv7hl? I'm finding that various things outright crash with an illegal instruction on Tegra 2, and NEON is the only reason I can think of. If it's built with NEON on armv7hl, it really shouldn't be since NEON isn't mandatory on ARMv7.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev July 2019