Arm-dev

arm-dev@lists.centos.org

686 discussions

USB on PI3
by Björn Dieding 18 Oct '16

18 Oct '16

Hello, I am tying the raspberry image on a pi3. Somehow I am not sure, if USB is properly working. The WIKI pages says it does (https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32/RaspberryPi3) Does someone get the same result or what message do you get? [root@support ~]# export LIBUSB_DEBUG=9 [root@support ~]# lsusb -v libusbx: debug [libusb_init] created default context libusbx: debug [libusb_init] libusbx v1.0.15.10646 libusbx: error [op_init] could not find usbfs unable to initialize libusb: -99 On my regular centos servers I get a proper result. Best regards, Björn Dieding

1 0

[RFC] Bootstrapping a new arch
by Haïkel 17 Oct '16

17 Oct '16

Hi, There was various discussions about enabling aarch64 architecture for Cloud SIG OpenStack repositories. And likely others are coming, so I'd like to confirm with a wider audience about the proper course of action. So we can document it and share that experience with other SIGs. Arrfab suggested the following: * scratch builds with archoverride of existing arch-dependent builds * ask CBS admin to merge the task with existing builds using mergeScratch. I find this process simple and efficient, but I'm worried about how it scales. In my case, I have about 250 binary packages (including the Erlang stack etc.) with many interdependencies, so it can rapidly get bothersome for CBS admins. If we can find a way to automate the mergeScratch operations or temporarily grant that permission to SIGs during bootstrapping phase, I have pretty much no objections for that course. --- As for daily operations, if you can't block on alternate arch build failures, I was recommended to just use %excludearch and move forward. Which gives us the flexibility to move forward and give more time to fix things at our pace. So what do you think? Any other suggestions? Regards, H.

2 1

python34 for aarch64
by Gordan Bobic 14 Oct '16

14 Oct '16

Are there python34 packages for aarch64 already built somewhere? I need them for acd_cli, but they don't seem to be in any of the available repositories I could find. TIA. Gordan

2 1

Repo for ARM
by Nicolas Repentin 11 Oct '16

11 Oct '16

Hello I've got another little question about armv7hl, do you know if an EPEL repository is available for this version? or is planned to? I saw this http://armv7.dev.centos.org/repodir/epel-pass-1/ (http://armv7.dev.centos.org/repodir/epel-pass-1/) Thanks, Nicolas

2 1

Armv7 EOL
by Nicolas Repentin 10 Oct '16

10 Oct '16

Hello Can you tell me if CentOS 7 Armv7hl is maintained, and follow the same versions of packages as x86_64 versions? What is the end of life date for this version? Maybe it's better to use aarch64? Regards

3 3

Kernel Mainline
by Nicolas Repentin 10 Oct '16

10 Oct '16

Hi all, Sorry if it's a repost, I wasn't subscribed on the list. I'm searching the good process to upgrade the kernel on CentOS 7 armv7hl. Actually the 4.2 kernel is not supporting crypto drivers for sunxi, and need to be patched, or need to use a newer kernel. Do you have a process to update correctly the kernel or generate the rpm file for it? I've tried to make the linux tar with (on bananapi): make bananapi_defconfig (getting the old one from actual kernel) make rpm but I've got some errors (don't have the log here). Maybe there is another process? I'm using bananapi M1 (I've helped to validate the actual image of CentOS). Thanks a lot,

5 12

Disk Image Creation Suggestions
by Christopher Covington 05 Oct '16

05 Oct '16

Hi, I'm running Anaconda regularly and I plan on continuing to do so, but there are certain circumstances where I'd like to lock down all the package versions and provision many similar systems as quickly as possible. So I'm looking for an automated and reliable mechanism for generating disk images for use on "bare metal" or physical (not virtualized) installs. The images will probably be copied to SATA*. How are the disk images currently generated? Does Jim manually launch an install with the documented [1] kickstart file and then move the storage medium to another machine and run dd? Or is it more automated? 1. http://mirror.centos.org/altarch/7/isos/aarch64/ReadMe.txt Looking through the archives I see Richard announcing virt-builder and virt-install availability for AArch64. It looks very useful for this sort of task. Are there any reasons to not use its output on a non-virtualized, physical instance? ("V2P"?) Then there's livemedia-creator [2]. Would it be best to use that to wrap the virt-install invocation? 2. http://lorax.readthedocs.io/en/latest/livemedia-creator.html If anyone has experience and guidance with the above tools or alternatives, especially on AArch64, it would be appreciated. The documentation looks very good for these tools but some aspects like authoring kickstart files which are compatible with lorax/livemedia-creator seem particularly tricky. Thanks, Cov * Not essential, but having the option to do some kind of read-only Network Block Device (NBD) root filesystem which many systems could share, with a local, writeable, essentially throw-away overlay might be handy. -- Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

2 1

using built-in wifi on rpi3/centos7/arm7 chokes connection
by Björn Lennestål 02 Oct '16

02 Oct '16

Hi, I recently installed centos on my pi3. The performance is good, however when I started to mess with wifi the network performance started choking. I have around~500ms and 1-10% packetloss locally to my router. This is on the ethernet interface and NOT on the WiFi interface. Basically just masking/disabling wpa_supplicant will make it OK again. I monitored the cpuload and memusage, but I have free memory and the cpu is barely utilized (95% idle). I haven't dug so much into this, I wanted to know if anyone else have experienced anything similiar? Basically the network performance is more or less useless after enabling wifi (installing the drivers & connecting to an AP). [root@centos-rpi3 ~]# uname -a Linux centos-rpi3 4.1.19-v7 #1 SMP Tue Mar 15 14:54:48 UTC 2016 armv7l armv7l armv7l GNU/Linux Currently disabled WiFi: *-network:0 DISABLED description: Wireless interface physical id: 2 logical name: wlan0 serial: b8:27:eb:04:97:f0 capabilities: ethernet physical wireless configuration: broadcast=yes driver=brcmfmac driverversion=7.45.41.23 firmware=01-cc4eda9c multicast=yes wireless=IEEE 802.11bgn Kind Regards, Björn ********* DISCLAIMER ********* This message and any attachment are confidential and may be privileged or otherwise protected from disclosure and may include proprietary information. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other person

1 0

kernel rebase for rpi2/rpi3 : call for feedback !
by Fabian Arrotin 27 Sep '16

27 Sep '16

Hi, I just rebased the raspberry pi 2/3 kernel to 4.4.14, with a specific patch to cover also selinux/auditd support. I'd like to have some additional testers (tested on my rpi2 and rpi3 boards). Create (for example) the /etc/yum.repos.d/kernel.repo file with the following content : [kernel] name=rpi kernel baseurl=http://armv7.dev.centos.org/repodir/arm-kernels/rpi2-4.4.14/ gpgcheck=0 enabled=1 Then a traditional "yum update ; systemctl reboot" If you want to have selinux working, feel free to follow https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32?highlight=%28arm… , except that for rpi2/rpi3, there is no /boot/exlinux/extlinux.conf, but rather edit /boot/cmdline.txt Thanks for the feedback, and then we'll be able to sign/push those to mirrors (and also include those in newer images for rpi2/rpi3) -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

4 12

Re: [Arm-dev] [rdo-list] next steps for altarch with ceph and openstack
by Jim Perrin 20 Sep '16

20 Sep '16

On 07/08/2016 03:35 AM, Alan Pevec wrote: > On Fri, Jul 8, 2016 at 4:00 AM, Haïkel <hguemar(a)fedoraproject.org> wrote: >> 2016-07-07 17:41 GMT+02:00 Jim Perrin <jperrin(a)centos.org>: > ... >>> I might suggest that for now (until we get the mirror bits sorted), we >>> create a centos-release-mitaka-altarch package. This would avoid needing >>> to mess with the existing x86_64 bits. once everything is aligned, then >>> we can obsolete/provides the replacement and use the standard package >>> across all architectures. >> >> Works for me. > > I didn't understand why we need separate release -altarch package. I > understand we do need separate CBS tags but they could be still mapped > into the same per-arch locations under > http://buildlogs.centos.org/centos/7/cloud/ and > http://mirror.centos.org/centos/7/cloud/ so that current OpenStack > CloudSIG .repo [1] which uses $basearch will work. Mappings for > testing repo request (e.g. for RDO Newton [2]) would be: > The problem here is that the aarch64 builds are currently at mirror.centos.org/altarch/ not at /centos/, so either way we'll end up with split repositories for the architecture. I'm only suggesting a second package as a short term solution until we come up with a better way to manage this. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

3 4

← Newer
1
...
38
39
40
41
42
43
44
...
69
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev