Arm-dev

arm-dev@lists.centos.org

1 participants
685 discussions

Next gen x-gene gpio dwapb support and x-gene i2c SlimPro driver update
by Phong Vo 19 May '17

19 May '17

Hi Jim, Please help integrate the attached patches to sig-altarch7-aarch64. + 1031-add-support-for-next-gen-xgene-gpio-dwapb.patch This is a roll up of the following upstreamed patches for supporting GPIO DWAPB a72b8c4 gpio: dwapb: Add support for next generation of X-Gene SoC bfab7c8 gpio: dwapb: add missing fwnode_handle_put() in dwapb_gpio_get_pdata() 506ebb2 gpio: dwapb: Add ACPI device ID for DWAPB GPIO controller on X-Gene platforms e6cb348 gpio: dwapb: add gpio-signaled acpi event support 4ba8cfa gpio: dwapb: convert device node to fwnode 52bc078 gpio: dwapb: remove name from dwapb_port_property + 1032-update-xgene-i2c-slimpro-driver.patch This is a roll-up of the following upstreamed patches ea73440 i2c: don't print error when adding adapter fails 1635c5d i2c: xgene: Fix missing code of DTB support 92d9d0d i2c: busses: constify i2c_algorithm structures 83345d5 i2c: xgene: Set ACPI_COMPANION_I2C and the following is still going through review. https://lkml.org/lkml/2017/3/28/1103 i2c: xgene-slimpro: Use a single function to send command message https://lkml.org/lkml/2017/3/28/1102 i2c: xgene-slimpro: Add ACPI support by using PCC mailbox + config-centos-sig-enable-gpio-dwapb.patch Enable CONFIG_GPIO_DWAPB Thanks, -Phong

1 0

EPEL AArch64 repo?
by Richard Henwood 13 May '17

13 May '17

Hi All, A colleague pointed me at: https://dl.fedoraproject.org/pub/epel/7/aarch64/ This looks to me like EPEL, but I'm not sure this is an official _CentOS_ EPEL; And I'm not sure I understand if there is a difference anyway... Can someone advise if this is the CentOS EPEL for AArch64 - or what the status of AArch64 EPEL is for CentOS? many thanks,Richard

7 7

Kernel for BananaPi R1 (Lamobo R1)
by mo.ucina 12 May '17

12 May '17

Hello Guys, I have been compiling the Fedora 4.4.2-300 kernel for Centos , using the new Centos image for the Banana-pi . I have used the Fedora src rpm and then added the patch for the switch drivers specific for R1 (Lamobo R1) , then compiled it within the Centos dev arm environment I have . I ran into a couple of things : one cosmetic , the other one not so . Firstly the cosmetic one is that my packages came out looking like this : -rw-rw-r-- 1 user user 49332 Feb 26 07:27 kernel-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 87721969 Feb 26 07:27 kernel-4.4.2-300.LR1.el7.centos.src.rpm -rw-rw-r-- 1 user user 18785384 Feb 26 07:29 kernel-core-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 10452672 Feb 26 07:30 kernel-devel-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 1012496 Feb 26 07:27 kernel-headers-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 11844188 Feb 26 07:31 kernel-modules-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 925980 Feb 26 07:31 kernel-modules-extra-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 105452 Feb 26 07:27 kernel-tools-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 65356 Feb 26 07:27 kernel-tools-libs-4.4.2-300.LR1.el7.centos.armv7hl.rpm -rw-rw-r-- 1 user user 52160 Feb 26 07:27 kernel-tools-libs-devel-4.4.2-300.LR1.el7.centos.armv7hl.rpm They all have "centos" as part of the name , which I did not expect . I did not get that when compiling in Fedora. How do you remove that ? Second observation , a one that is a bit of a concern is that , after installing the new kernel I am missing bits : user@bananapi /boot $ ls -l total 43611 drwxr-xr-x. 5 root root 1024 Feb 25 22:21 38f5ec9e217b471e8adee477d933f640 -rw-r--r--. 1 root root 171924 Nov 26 00:43 config-4.2.3-200.el7.armv7hl drwxr-xr-x. 2 root root 15360 Dec 3 14:37 dtb-4.2.3-200.el7.armv7hl drwxr-xr-x. 2 root root 1024 Dec 3 14:47 extlinux drwxr-xr-x. 2 root root 1024 Jan 1 1970 grub -rw-r--r--. 1 root root 34922581 Dec 3 14:46 initramfs-4.2.3-200.el7.armv7hl.img -rw-r--r--. 1 root root 592347 Dec 3 14:37 initrd-plymouth.img drwxr-xr-x. 3 root root 1024 Dec 3 14:44 loader drwx------. 2 root root 12288 Dec 3 14:31 lost+found -rw-------. 1 root root 2879429 Nov 26 00:43 System.map-4.2.3-200.el7.armv7hl -rwxr-xr-x. 1 root root 5866104 Nov 26 00:43 vmlinuz-4.2.3-200.el7.armv7hl I expected that I would be missing 'initramfs' as the install prog is still work-in-progress. And I was prepared to create it with dracut . However I did not expect not to be missing all the other bits such as : config , dtb, system.map, vmlinuz . I did find my new kernel it was in that dir with a hex name : user@bananapi /boot $ ls -l 38f5ec9e217b471e8adee477d933f640/* 38f5ec9e217b471e8adee477d933f640/0-rescue: total 40652 -rw-r--r--. 1 root root 35427302 Dec 3 14:43 initrd -rwxr-xr-x. 1 root root 6033128 Feb 25 22:26 linux 38f5ec9e217b471e8adee477d933f640/4.2.3-200.el7.armv7hl: total 39995 -rw-r--r--. 1 root root 34923169 Dec 3 14:40 initrd -rw-r--r--. 1 root root 5866104 Dec 3 14:44 linux 38f5ec9e217b471e8adee477d933f640/4.4.2-300.LR1.el7.centos.armv7hl: total 41061 -rw-r--r--. 1 root root 35844934 Feb 25 22:24 initrd -rw-r--r--. 1 root root 6033128 Feb 25 22:36 linux So my question is how do I go from these 2 files above , to the situation where I can boot into the new kernel 4.4.2-300.LR1.el7.centos.armv7hl . Best Regards Milorad PS Once I have verified that the switch driver works , I will post it here .

5 13

kexec: failed to load kdump kernel
by Matt McLean 11 May '17

11 May '17

I have 40 brand new Cavium R270-T60-V6 systems (T32 BIOS) with CentOS 7.3.1611 installed. Five of them are failing at boot with: kdumpctl[9698]: Could not find a free area of memory of 0x10000 bytes... kdumpctl[9698]: locate_hole failed kdumpctl[9698]: kexec: failed to load kdump kernel kdumpctl[9698]: Starting kdump: [FAILED] The systems are identical in every way (Memory, CPU, disks, firmware, network, location....). A comparison of their "dmesg" output shows no smoking gun, but I do not know if differences like this are significant: < efi: ESRT=0x13ffe1b0e98 SMBIOS 3.0=0xfffeb000 ACPI 2.0=0x13feaba0000 --- > efi: ESRT=0x13ffe1b0e98 SMBIOS 3.0=0xfffeb000 ACPI 2.0=0x13feab9f000 < Memory: 533473024K/536820736K available (7232K kernel code, 1406K rwdata, 3456K rodata, 1152K init, 6589K bss, 2823424K reserved, 524288K cma-reserved) --- > Memory: 533473152K/536820736K available (7232K kernel code, 1406K rwdata, 3456K rodata, 1152K init, 6589K bss, 2823296K reserved, 524288K cma-reserved) Any tips on where to look next are appreciated. (Also, if there is a more appropriate distro for this question, please advise). Peace. -- Matt McLean ARC-TS Operations mattmc(a)umich.edu

2 1

Kernel freezes
by Nicolas Repentin 08 May '17

08 May '17

Hi all, Does anyone have problems with kernel 4.9 on armv7 devices? I'm using bananapi M1, and on kernel 4.2 (from original centos 7 image), works very well. I've tried the latest 4.9, and I take freezes some minutes after boot. I just had a "kernel:Internal error: Oops - BUG: 0 [#1] SMP ARM" on prompt before freeze. Thanks to watchdog to have reset the Bpi (it's at 350km to me :p). I don't have actually more logs... and I have to rollback to 4.2. Any feedback on this 4.9 kernel? Thanks

2 5

making a compressed image
by Robert Moskowitz 06 May '17

06 May '17

I have worked out the dd command to copy my work in progress 4Gb image: dd if=/dev/sdb of=cubietruck.img bs=512 count=6268927 and restore it with: dd if=/home/rgm/arm/Centos/cubietruck.img of=/dev/sdb bs=4M; sync But I would like to compress this, making a .xz file that is expanded with xzcat. I have not figured this out, so am asking for a bit of help (I have had to increase the root partition so backing up is a larger file now). thanks

3 3

Updates to basic server howto - Webmin added and stuff
by Robert Moskowitz 03 May '17

03 May '17

I have updated the basic howto: http://www.htt-consult.com/Centos7-armv7.html Webmin is easy to install, but seems a bit slow on the Cubie. Perhaps that is simply due to first time accesses, and what Webmin builds on first access to a function. Webmin is now defaulting to a TLS connection and builds a default cert. You may want to replace that with one more customed to your preferences. Chronyd caveats now reflect best practices for customizing a systemd service. Remaining known changes for this is switching to using nmcli for the interface config. I am close.... Would be nice to figure out what the problem with the SSD and SELinux is so, if needed, I can add in info on that... Now to tackle the SELinux mail problems...

1 0

SELinux relabeling looping
by Robert Moskowitz 02 May '17

02 May '17

I am starting on a fresh install of the 1611 Cubietruck image. This time I am running on a Cubietruck, not a Cubieboard2. I have the cubietruck uboot on a mSD card and the image installed on a Kingston 240Gb SSD drive. I boot up, log in with root with the default password. All I do is change /boot/extlinux/extlinux.conf with: sed -i -e "s/enforcing=0/enforcing=1/w /dev/stdout" /boot/extlinux/extlinux.conf Note that https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32 is wrong saying: If you want to switch to enforcing mode, you'll have so to first modify the following files /etc/sysconfig/selinux : change from "permissive" to "enforcing" * rpi2/rpi3 : /boot/cmdline.txt: change "enforce=0" to "enforcing=1" * other image/board[s]: /boot/extlinux/extlinux.conf : change the "enforce=0" to "enforce=1" It is enforcing=0 on the Cubietruck image. Then: touch /.autorelabel and reboot I get the log message: [ 18.453896] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 *** Warning -- SELinux targeted policy relabel is required. *** Relabeling could take a very long time, depending on file *** system size and speed of hard drives. [ 54.365478] random: nonblocking pool is initialized Warning: Skipping the following R/O filesystems: /sys/fs/cgroup Then after some time, it goes through a shutdown, reboots and comes back to this state. Then reboots again. I have tried this twice. Next I will try on my Cubieboard2, that I will have to take down from its testing position for this test. If it still fails, I will try a HD. These commands have worked for my on the C2 with a HD and a mSD card. I don't recall if I have tried them on a CT. But any thoughts are appreciated! thanks

2 3

SElinux module problem - Re: SELinux policy to allow Dovecot to connect to Mysql
by Robert Moskowitz 26 Apr '17

26 Apr '17

I think I have a module problem with SELinux. Laurent is on an x86_64 box and can't help me any further... On 04/25/2017 11:12 AM, Laurent Wandrebeck wrote: > Le mardi 25 avril 2017 à 11:07 +0200, Robert Moskowitz a écrit : >> On 04/25/2017 10:58 AM, Laurent Wandrebeck wrote: >>> Le mardi 25 avril 2017 à 10:39 +0200, Robert Moskowitz a écrit : >>>> Thanks Laurent. You obviously know a LOT more about SELinux than I. I >>>> pretty much just use commands and not build policies. So I need some >>>> more information here. >>>> >>>> From what you provided below, how do I determine what is currently in >>>> place and how do I add your stuff (changing postgresql with mysql, nat.) >>>> >>>> thanks >>> Quick’n’(really) dirty SELinux howto: >>> 1) Run the service. fails due to missing selinux policy. >>> 2) grep service_pattern /var/log/audit/audit.log | audit2allow -M >>> myservice_policy >> Do you really mean 'service_pattern', or is this a placeholder for >> something like mysql? >> >> As I get 'Nothing to do' > placeholder which changes according to your needs. I just made it worst. I put in mysql for myservice_policy, got a /pp and did: semodule -i myservice_policy.pp Now I get real errors like: Apr 25 05:13:16 z9m9z dovecot: dict: Error: b6fa1000-b6fc0000 r-xp 00000000 08:03 6076 /usr/lib/ld-2.17.so Apr 25 05:13:16 z9m9z dovecot: dict: Error: b6fc5000-b6fc7000 rw-p 00000000 00:00 0 Apr 25 05:13:16 z9m9z dovecot: dict: Error: b6fcd000-b6fcf000 rw-p 00000000 00:00 0 Apr 25 05:13:16 z9m9z dovecot: dict: Error: b6fcf000-b6fd0000 r--p 0001e000 08:03 6076 /usr/lib/ld-2.17.so Apr 25 05:13:16 z9m9z dovecot: dict: Error: b6fd0000-b6fd1000 rw-p 0001f000 08:03 6076 /usr/lib/ld-2.17.so Apr 25 05:13:16 z9m9z dovecot: dict: Error: bee46000-bee67000 rw-p 00000000 00:00 0 [stack] Apr 25 05:13:16 z9m9z dovecot: dict: Error: beec5000-beec6000 r-xp 00000000 00:00 0 [sigpage] Apr 25 05:13:16 z9m9z dovecot: dict: Error: ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors] Which go away if I setenforce 0. :( myservice_policy.te has: module myservice_policy 1.0; require { type dovecot_t; type mysqld_etc_t; type mysqld_t; class unix_stream_socket connectto; class file { getattr open read }; class dir read; } #============= dovecot_t ============== allow dovecot_t mysqld_etc_t:dir read; allow dovecot_t mysqld_etc_t:file { getattr open read }; #!!!! The file '/var/lib/mysql/mysql.sock' is mislabeled on your system. #!!!! Fix with $ restorecon -R -v /var/lib/mysql/mysql.sock #!!!! This avc can be allowed using the boolean 'daemons_enable_cluster_mode' allow dovecot_t mysqld_t:unix_stream_socket connectto; _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 3

Customizing Chronyd for no battery
by Robert Moskowitz 24 Apr '17

24 Apr '17

Fellow armv7-without-rtc-battery users. Maybe you have already learned this, but I THINK I have completed my education on this thanks to Miroslav Lichvar on the Chrony list. There are two issues here: It takes time for chronyd to set the system time. And if it fails to reach the ntp servers, well, it failed to set the time. For the first, we need to delay some services from starting until chronyd is successful. Postfix is one of them. So we need the following commands: systemctl enable chrony-wait systemctl start chrony-wait sed -i '/^After=/ s/$/ time-sync.target/w /dev/stdout' /usr/lib/systemd/system/postfix.service There are some possible instances where you also want to do this to httpd.service, but I have been advised on the postfix list NOT to run postfix if the systemtime is earlier than the postfix build date $ postconf -dh mail_release_date 20130622 Plus the postfix.service runs aliases.db which will mess up your aliases.db timestamp. Next there is that pesky issue about what if no ntp servers reached? First: cat <<EOF>/etc/sysconfig/chronyd || exit 1 OPTIONS=" -s" EOF Since Centos7 has Chronyd 2.1.1, not 2.2, we have extra work to do in chronyd.conf: cat <<EOF>>/etc/chrony.conf || exit 1 rtcdevice /dev/doesnotexist EOF I am adding this to my basic server howto page.

2 8

← Newer
1
...
26
27
28
29
30
31
32
...
69
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev