Arm-dev

arm-dev@lists.centos.org

686 discussions

Re: [Arm-dev] Community kernel 4.18.x
by Mark Verlinde 23 Oct '18

23 Oct '18

-----Oorspronkelijk bericht----- > Afzender:Mark Verlinde <mark(a)havak.nl> > Verstuurd: Maandag 22 Oktober 2018 14:27 > Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> > Onderwerp: Re: [Arm-dev] Community kernel 4.18.x > > Thank you for the hints, it Led to a booting setup! > > Still need to fine tine, some customization may not be needed howerever this configuration led to the booting odroid HC1. > > Appended cpuidle.off=1 console=tty1 console=ttySAC2,115200n8 to the cmdline: > > # cat /boot/extlinux/extlinux.conf > # extlinux.conf generated by appliance-creator > ui menu.c32 > menu autoboot Welcome to Centos-Uboot-Community-kernel. Automatic boot in # second{,s}. Press a key for options. > menu title Centos-Uboot-Community-kernel Boot Options. > menu hidden > timeout 20 > totaltimeout 600 > > default=Centos-Uboot-Community-kernel (4.18.14-200.el7.armv7hl) > label CentOS Linux (4.18.16-200.el7.armv7hl) 7 (AltArch) > kernel /vmlinuz-4.18.16-200.el7.armv7hl > append cpuidle.off=1 console=tty1 console=ttySAC2,115200n8 ro root=UUID=a306d630-4957-4da0-8dd6-79f943147d61 LANG=en_US.UTF-8 > fdtdir /dtb-4.18.16-200.el7.armv7hl > initrd /initramfs-4.18.16-200.el7.armv7hl.img > > label Centos-Uboot-Community-kernel (4.18.14-200.el7.armv7hl) > kernel /vmlinuz-4.18.14-200.el7.armv7hl > append cpuidle.off=1 console=tty1 console=ttySAC2,115200n8 ro root=UUID=a306d630-4957-4da0-8dd6-79f943147d61 > fdtdir /dtb-4.18.14-200.el7.armv7hl > initrd /initramfs-4.18.14-200.el7.armv7hl.img > > In an effort to mimic the FC28 intenramfs added/omitted some modules and > added _all_ exynos and samsung divers loaded by the booting FC28 setup: > > #cat /etc/dracut.conf.d/odroid_hc1.conf > add_dracutmodules+="dm" > omit_dracutmodules+="network ifcfg" > add_drivers+="exynosdrm exynos_bus exynos_trng exynos_nocp exynos_rng phy_exynos_dp_video phy_exynos_mipi_video dwc3_exynos clk_exynos_audss i2c_exynos5 dw_mmc_exynos dw_mmc_pltfm dw_mmc phy_exynos_usb2 phy_exynos5_usbdrd pwm_samsung " > > (AGAIN) NOTE: some may be necessary others may be ommited.. Turns out one additional driver - dwc3 - is needed to boot the odroid HC1 with a rootfs residing on a SATA device. My best guess is dwc3_exynos actually depends on dwc3 and/or (one of) the dependencies of dwc3. #cat /etc/dracut.conf.d/odroid_hc1.conf add_dracutmodules+="dm" omit_dracutmodules+="network ifcfg" add_drivers+=" exynosdrm exynos_bus exynos_trng exynos_nocp exynos_rng phy_exynos_dp_video phy_exynos_mipi_video dwc3_exynos clk_exynos_audss i2c_exynos5 dw_mmc_exynos dw_mmc_pltfm dw_mmc phy_exynos_usb2 phy_exynos5_usbdrd pwm_samsung " add_drivers+=" dwc3"

2 1

Re: [Arm-dev] Community kernel 4.18.x
by Mark Verlinde 22 Oct '18

22 Oct '18

-----Oorspronkelijk bericht----- > Afzender:Pablo Sebastián Greco <pablo(a)fliagreco.com.ar> > Verstuurd: Zondag 21 Oktober 2018 23:58 > Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> > Onderwerp: Re: [Arm-dev] Community kernel 4.18.x > > > El 21/10/18 a las 17:06, Mark Verlinde escribió: > > -----Oorspronkelijk bericht----- > >> Afzender:Mark Verlinde <mark(a)havak.nl> > >> Verstuurd: Woensdag 17 Oktober 2018 18:49 > >> Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> > >> Onderwerp: Re: [Arm-dev] Community kernel 4.18.x > >> > >> > >> -----Oorspronkelijk bericht----- > >>> Afzender:Pablo Sebastián Greco <pablo(a)fliagreco.com.ar> > >>> Verstuurd: Woensdag 17 Oktober 2018 18:09 > >>> Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> > >>> Onderwerp: Re: [Arm-dev] Community kernel 4.18.x > >>> > >>> > >>> > >>> El 17/10/18 a las 11:47, Mark Verlinde escribió: > >>>> Hi, > >>>> > >>>> Kernel 4.18.x brings nice features, CPUFreq for Allwinner H3 SOC's being among them. > >>>> > >>>> Therefore I had a go on updating to the community-kernel-latest version 4.18.14-200.el7 which failed; > >>>> Dracut could not (re)build a intitramfs-4.18.14-.. and (probably because of this) uInitrd-4.18.14-.. was missing to. > >>>> Unfortunately did not write the exact error message down; next time will do so. > >>> Does /boot have enough space?, I usually try to have 3 kernels at most. > >>> I've been using that kernel in 3 different SoCs without problems, > >>> including Bananapi M3 (same SoC as the cubieboard5) > >> I do not doubt it had because it was the second kernel update done (i.e would be the 3rd installed) > >> > >> However : just successfully installed with a more conservative approach 4.17.17 > 4.18.9 > 4.18.14 > >> Side note is: this is on a home brew image without RPI bits and peaces, 786MB boot partition with ext4 file-system. > >> In time I will try again with default Centos-Generic image. > >> > >> i'm happy now:) > >> cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor > >> ondemand > >> > >>>> BTW: Update to Kernel 4.17.17-200.el7 was successful on my oragngepi-plus2e > >>>> > >>>> In my own interest i'd really want to help to debug this; > >>>> but to be able to do this i need to understand in more detail how we boot Centos on our u-boot based SBC's. > >>>> I got the broad picture: u-boot >> extlinux bootloader >> kernel >> > >>> Correct > >>>> Getting lost however looking at extlinux/extlinux.conf , grub/grub.conf and not knowing the content of boot.scr > >>> You can ignore grub.conf and boot.scr, extlinux.conf is all you need > >> Sorry to persist, I'd really like to understand in more detail; > >> Questions circling in my head (among others) are: > >> Why do we have a uInitrd _and_ initramfs ? > >> Why do we have a uimage _and_ vmlinux ? > >> Why does my odroid HC1 boot with a Fedora image but not with Centos (kernel 4.14.71 nor 4.17.17)? (despite specific USB3 patches are backported to 4.14) > >> > >>>> Can somebody enlighten me on this, or show me some further reading. > >>>> > >>>> (I did search fedora's arm documentation without getting smarter..) > >>>> > >>>> Actually in response to "Cubieboard5 performance" > >>>> (https://lists.centos.org/pipermail/arm-dev/2018-October/003515.html) > >>>> > >>>> > > Just a heads up, update to 4.18.16 works flawless on the above described setup on a oragngepi-plus2e. > > Did not find the time to test it with a default img as I'm still in a fight with the odroid HC1. > > For the latter the good new is: it's not an issue with the kernel but with the initramfs. > > > Thanks for testing!! > WRT the odroid, do you have an error log? > I've had my share of boot problems with supported devices, and they end > up being solved by something like what I said in this mail > https://lists.centos.org/pipermail/arm-dev/2018-August/003399.html Thank you for the hints, it Led to a booting setup! Still need to fine tine, some customization may not be needed howerever this configuration led to the booting odroid HC1. Appended cpuidle.off=1 console=tty1 console=ttySAC2,115200n8 to the cmdline: # cat /boot/extlinux/extlinux.conf # extlinux.conf generated by appliance-creator ui menu.c32 menu autoboot Welcome to Centos-Uboot-Community-kernel. Automatic boot in # second{,s}. Press a key for options. menu title Centos-Uboot-Community-kernel Boot Options. menu hidden timeout 20 totaltimeout 600 default=Centos-Uboot-Community-kernel (4.18.14-200.el7.armv7hl) label CentOS Linux (4.18.16-200.el7.armv7hl) 7 (AltArch) kernel /vmlinuz-4.18.16-200.el7.armv7hl append cpuidle.off=1 console=tty1 console=ttySAC2,115200n8 ro root=UUID=a306d630-4957-4da0-8dd6-79f943147d61 LANG=en_US.UTF-8 fdtdir /dtb-4.18.16-200.el7.armv7hl initrd /initramfs-4.18.16-200.el7.armv7hl.img label Centos-Uboot-Community-kernel (4.18.14-200.el7.armv7hl) kernel /vmlinuz-4.18.14-200.el7.armv7hl append cpuidle.off=1 console=tty1 console=ttySAC2,115200n8 ro root=UUID=a306d630-4957-4da0-8dd6-79f943147d61 fdtdir /dtb-4.18.14-200.el7.armv7hl initrd /initramfs-4.18.14-200.el7.armv7hl.img In an effort to mimic the FC28 intenramfs added/omitted some modules and added _all_ exynos and samsung divers loaded by the booting FC28 setup: #cat /etc/dracut.conf.d/odroid_hc1.conf add_dracutmodules+="dm" omit_dracutmodules+="network ifcfg" add_drivers+="exynosdrm exynos_bus exynos_trng exynos_nocp exynos_rng phy_exynos_dp_video phy_exynos_mipi_video dwc3_exynos clk_exynos_audss i2c_exynos5 dw_mmc_exynos dw_mmc_pltfm dw_mmc phy_exynos_usb2 phy_exynos5_usbdrd pwm_samsung " (AGAIN) NOTE: some may be necessary others may be ommited.. > > > Pablo. > > _______________________________________________ > Arm-dev mailing list > Arm-dev(a)centos.org > https://lists.centos.org/mailman/listinfo/arm-dev >

3 3

SELinux warnings?
by Robert Moskowitz 19 Oct '18

19 Oct '18

I am assuming that none of these are a problem, other than they occur anytime you do anything with SELinux, like get an update: Updating : selinux-policy-targeted-3.13.1-192.el7_5.6.noarch 52/163 [ 864.238915] SELinux: Permission getrlimit in class process not defined in policy. [ 864.255572] SELinux: Permission map in class file not defined in policy. [ 864.271347] SELinux: Permission map in class dir not defined in policy. [ 864.287009] SELinux: Permission map in class lnk_file not defined in policy. [ 864.302952] SELinux: Permission map in class chr_file not defined in policy. [ 864.318679] SELinux: Permission map in class blk_file not defined in policy. [ 864.334072] SELinux: Permission map in class sock_file not defined in policy. [ 864.349585] SELinux: Permission map in class fifo_file not defined in policy. [ 864.364986] SELinux: Permission map in class socket not defined in policy. [ 864.380106] SELinux: Permission map in class tcp_socket not defined in policy. [ 864.395447] SELinux: Permission map in class udp_socket not defined in policy. [ 864.410657] SELinux: Permission map in class rawip_socket not defined in policy. [ 864.425984] SELinux: Permission map in class netlink_socket not defined in policy. [ 864.441531] SELinux: Permission map in class packet_socket not defined in policy. [ 864.457032] SELinux: Permission map in class key_socket not defined in policy. [ 864.472253] SELinux: Permission map in class unix_stream_socket not defined in policy. [ 864.488097] SELinux: Permission map in class unix_dgram_socket not defined in policy. [ 864.503933] SELinux: Permission map in class netlink_route_socket not defined in policy. [ 864.519918] SELinux: Permission map in class netlink_tcpdiag_socket not defined in policy. [ 864.536181] SELinux: Permission map in class netlink_nflog_socket not defined in policy. [ 864.552161] SELinux: Permission map in class netlink_xfrm_socket not defined in policy. [ 864.568076] SELinux: Permission map in class netlink_selinux_socket not defined in policy. [ 864.584204] SELinux: Permission map in class netlink_iscsi_socket not defined in policy. [ 864.600178] SELinux: Permission map in class netlink_audit_socket not defined in policy. [ 864.616037] SELinux: Permission map in class netlink_fib_lookup_socket not defined in policy. [ 864.632237] SELinux: Permission map in class netlink_connector_socket not defined in policy. [ 864.648096] SELinux: Permission map in class netlink_netfilter_socket not defined in policy. [ 864.663754] SELinux: Permission map in class netlink_dnrt_socket not defined in policy. [ 864.678752] SELinux: Permission map in class netlink_kobject_uevent_socket not defined in policy. [ 864.694514] SELinux: Permission map in class netlink_generic_socket not defined in policy. [ 864.709433] SELinux: Permission map in class netlink_scsitransport_socket not defined in policy. [ 864.724784] SELinux: Permission map in class netlink_rdma_socket not defined in policy. [ 864.739110] SELinux: Permission map in class netlink_crypto_socket not defined in policy. [ 864.753607] SELinux: Permission map in class appletalk_socket not defined in policy. [ 864.767591] SELinux: Permission map in class dccp_socket not defined in policy. [ 864.781189] SELinux: Permission map in class tun_socket not defined in policy. [ 864.794607] SELinux: Class sctp_socket not defined in policy. [ 864.806570] SELinux: Class icmp_socket not defined in policy. [ 864.818225] SELinux: Class ax25_socket not defined in policy. [ 864.829649] SELinux: Class ipx_socket not defined in policy. [ 864.840752] SELinux: Class netrom_socket not defined in policy. [ 864.851923] SELinux: Class atmpvc_socket not defined in policy. [ 864.862911] SELinux: Class x25_socket not defined in policy. [ 864.873393] SELinux: Class rose_socket not defined in policy. [ 864.883767] SELinux: Class decnet_socket not defined in policy. [ 864.894133] SELinux: Class atmsvc_socket not defined in policy. [ 864.904385] SELinux: Class rds_socket not defined in policy. [ 864.914444] SELinux: Class irda_socket not defined in policy. [ 864.924608] SELinux: Class pppox_socket not defined in policy. [ 864.934862] SELinux: Class llc_socket not defined in policy. [ 864.944876] SELinux: Class can_socket not defined in policy. [ 864.954877] SELinux: Class tipc_socket not defined in policy. [ 864.964974] SELinux: Class bluetooth_socket not defined in policy. [ 864.975659] SELinux: Class iucv_socket not defined in policy. [ 864.985843] SELinux: Class rxrpc_socket not defined in policy. [ 864.996237] SELinux: Class isdn_socket not defined in policy. [ 865.006492] SELinux: Class phonet_socket not defined in policy. [ 865.017007] SELinux: Class ieee802154_socket not defined in policy. [ 865.027974] SELinux: Class caif_socket not defined in policy. [ 865.038332] SELinux: Class alg_socket not defined in policy. [ 865.048641] SELinux: Class nfc_socket not defined in policy. [ 865.058824] SELinux: Class vsock_socket not defined in policy. [ 865.069225] SELinux: Class kcm_socket not defined in policy. [ 865.079405] SELinux: Class qipcrtr_socket not defined in policy. [ 865.090009] SELinux: Class smc_socket not defined in policy. [ 865.100225] SELinux: the above unknown classes and permissions will be allowed [ 870.760142] SELinux: Context unconfined_u:unconfined_r:sandbox_t:s0-s0:c0.c1023 became invalid (unmapped). [ 871.187593] SELinux: Context system_u:unconfined_r:sandbox_t:s0-s0:c0.c1023 became invalid (unmapped). [ 872.635092] SELinux: policy capability network_peer_controls=1 [ 872.645801] SELinux: policy capability open_perms=1 [ 872.655404] SELinux: policy capability extended_socket_class=0 [ 872.666023] SELinux: policy capability always_check_network=0 [ 872.676507] SELinux: policy capability cgroup_seclabel=1 [ 872.686511] SELinux: policy capability nnp_nosuid_transition=1 that is quite an extensive list...

1 0

Re: [Arm-dev] Community kernel 4.18.x
by Mark Verlinde 17 Oct '18

17 Oct '18

-----Oorspronkelijk bericht----- > Afzender:Pablo Sebastián Greco <pablo(a)fliagreco.com.ar> > Verstuurd: Woensdag 17 Oktober 2018 18:09 > Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> > Onderwerp: Re: [Arm-dev] Community kernel 4.18.x > > > > El 17/10/18 a las 11:47, Mark Verlinde escribió: > > Hi, > > > > Kernel 4.18.x brings nice features, CPUFreq for Allwinner H3 SOC's being among them. > > > > Therefore I had a go on updating to the community-kernel-latest version 4.18.14-200.el7 which failed; > > Dracut could not (re)build a intitramfs-4.18.14-.. and (probably because of this) uInitrd-4.18.14-.. was missing to. > > Unfortunately did not write the exact error message down; next time will do so. > Does /boot have enough space?, I usually try to have 3 kernels at most. > I've been using that kernel in 3 different SoCs without problems, > including Bananapi M3 (same SoC as the cubieboard5) I do not doubt it had because it was the second kernel update done (i.e would be the 3rd installed) However : just successfully installed with a more conservative approach 4.17.17 > 4.18.9 > 4.18.14 Side note is: this is on a home brew image without RPI bits and peaces, 786MB boot partition with ext4 file-system. In time I will try again with default Centos-Generic image. i'm happy now:) cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand > > > > BTW: Update to Kernel 4.17.17-200.el7 was successful on my oragngepi-plus2e > > > > In my own interest i'd really want to help to debug this; > > but to be able to do this i need to understand in more detail how we boot Centos on our u-boot based SBC's. > > I got the broad picture: u-boot >> extlinux bootloader >> kernel >> > Correct > > Getting lost however looking at extlinux/extlinux.conf , grub/grub.conf and not knowing the content of boot.scr > You can ignore grub.conf and boot.scr, extlinux.conf is all you need Sorry to persist, I'd really like to understand in more detail; Questions circling in my head (among others) are: Why do we have a uInitrd _and_ initramfs ? Why do we have a uimage _and_ vmlinux ? Why does my odroid HC1 boot with a Fedora image but not with Centos (kernel 4.14.71 nor 4.17.17)? (despite specific USB3 patches are backported to 4.14) > > > > Can somebody enlighten me on this, or show me some further reading. > > > > (I did search fedora's arm documentation without getting smarter..) > > > > Actually in response to "Cubieboard5 performance" > > (https://lists.centos.org/pipermail/arm-dev/2018-October/003515.html) > > > > > > _______________________________________________ > > 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

Community kernel 4.18.x
by Mark Verlinde 17 Oct '18

17 Oct '18

Hi, Kernel 4.18.x brings nice features, CPUFreq for Allwinner H3 SOC's being among them. Therefore I had a go on updating to the community-kernel-latest version 4.18.14-200.el7 which failed; Dracut could not (re)build a intitramfs-4.18.14-.. and (probably because of this) uInitrd-4.18.14-.. was missing to. Unfortunately did not write the exact error message down; next time will do so. BTW: Update to Kernel 4.17.17-200.el7 was successful on my oragngepi-plus2e In my own interest i'd really want to help to debug this; but to be able to do this i need to understand in more detail how we boot Centos on our u-boot based SBC's. I got the broad picture: u-boot >> extlinux bootloader >> kernel >> Getting lost however looking at extlinux/extlinux.conf , grub/grub.conf and not knowing the content of boot.scr Can somebody enlighten me on this, or show me some further reading. (I did search fedora's arm documentation without getting smarter..) Actually in response to "Cubieboard5 performance" (https://lists.centos.org/pipermail/arm-dev/2018-October/003515.html)

2 1

Qemu Arm Emulator in CentOS host(x86)
by karthi mohanraj 17 Oct '18

17 Oct '18

Hi All, I’m trying to install fedora on QEMU emulator for the ARM. I have followed this documentation using virt-manager in this link: https://fedoraproject.org/wiki/Architectures/ARM/F26/Installation#For_Versa… <https://fedoraproject.org/wiki/Architectures/ARM/F26/Installation#For_Versa…> I was getting USB PCI device error as below. 2018-10-17 12:18:35.914+0000: starting up libvirt version: 3.9.0, package: 14.el7_5.8 (CentOS BuildSystem <http://bugs.centos.org <http://bugs.centos.org/>>, 2018-09-26-18:30:11, x86-01.bsys.centos.org <http://x86-01.bsys.centos.org/>), qemu version: 2.0.0, hostname: localhost.localdomain LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-arm -name guest=fedora22-arm,debug-threads=on -S -machine virt,accel=tcg,usb=off,dump-guest-core=off -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid fc26e72b-3aaa-407b-a4fa-8896bbb8c580 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-30-fedora22-arm/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -kernel /var/lib/libvirt/images/arm/vmlinuz-4.8.6-300.fc25.armv7hl -initrd /var/lib/libvirt/images/arm/initramfs-4.8.6-300.fc25.armv7hl.img -append 'console=ttyAMA0 rw root=LABEL=_/ rootwait' -device ich9-usb-ehci1,id=usb -device ich9-usb-uhci1,masterbus=usb.0,firstport=0 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4 -device virtio-scsi-device,id=scsi0 -device virtio-serial-device,id=virtio-serial0 -drive file=/var/lib/libvirt/images/arm/Fedora-Minimal-armhfp-25-1.3-sda.raw,format=raw,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=27,id=hostnet0 -device virtio-net-device,netdev=hostnet0,id=net0,mac=52:54:00:46:70:cb -chardev pty,id=charserial0 -serial chardev:charserial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-30-fedora22-arm/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-device,rng=objrng0,id=rng0 -msg timestamp=on (process:12978): GLib-WARNING **: gmem.c:483: custom memory allocation vtable not supported char device redirected to /dev/pts/2 (label charserial0) 2018-10-17T12:18:36.052249Z qemu-system-arm: -device ich9-usb-ehci1,id=usb: No 'PCI' bus found for device 'ich9-usb-ehci1' 2018-10-17 12:18:36.282+0000: shutting down, reason=failed Thanks, Karthi

1 0

wlan0: link is not ready
by Robert Moskowitz 15 Oct '18

15 Oct '18

On my Cubietruck, I keep getting: [ 716.571958] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready How can I stop this, as I am not using the wifi? thanks

2 3

Re: [Arm-dev] Cubieboard5 performance
by Pablo Sebastián Greco 13 Oct '18

13 Oct '18

El 9/10/18 a las 14:41, Andreas Reschke escribió: > Am 21.08.18 um 12:14 schrieb arm_ml(a)rirasoft.de: >> El 20/8/18 a las 15:57, Iván Chavero escribió: >>>>>>> >>>>>> I had to apply some patches to the sunxi kernel that were pending >>>>>> to >>>>>> be merged upstream in order to have SMP and HDMI running. >>>>>> I also had to patch the kernel's dtb for the HDMI running (i've >>>>>> been >>>>>> to lazy to send the patch to the kernel list), if you need it i >>>>>> can >>>>>> upload this code to github or i can pack you a kernel+initramfs >>>>>> for >>>>>> you to use it with your cubieboard5 >>>>>> Cheers, >>>>>> Ivan >>>>>> >>>>> Ivan, that kernel has both smp and your patch included ;-). >>>>> Either way, I'll try to update to 4.18 in a few days. >>>>> >>>> Let me know if i can help, i have my cubieboard5 clusters running if >>>> there's need for testing and other stuff. >>>> >>> Iván, I didn't have time today to build 4.18 today, but I pushed >>> 4.17.17, and it should appear here >>> https://armv7.dev.centos.org/repodir/community-kernel-latest/kernel/ >>> between today and tomorrow. >>> It has smp for a83t (bananapi-m3 and cubieborard5) >>> Your hdmi patch for cubieboard5. >>> Some other fixes for R40. >>> >>> It would be great if you could test it. >> >> Hello Pablo, Iván, >> >> thank you very much for your work. With this kernel everything seems >> to work: 8CPUs, Ethernet, USBtoSATA, not tested: HDMI >> >> I'm now in the process to copy everything from SD-Card to the onboard >> EMMC, so I can boot from it. >> >> >> With your work I have a powerfull device. >> >> Thanks >> Andreas >> >> (thinking what can I do with the cubietruck plus: Time-Server (DCF77) >> ? DNS-Server? Pi-Hole? ...?) >> >> PS: sometimes I get these messages in the syslog: >> [ 286.918766] usb usb2-port1: attempt power cycle >> [ 287.295335] ehci-platform 1c1b000.usb: port 1 reset error -110 >> [ 288.193314] ehci-platform 1c1b000.usb: port 1 reset error -110 >> [ 289.033322] ehci-platform 1c1b000.usb: port 1 reset error -110 >> [ 289.873370] ehci-platform 1c1b000.usb: port 1 reset error -110 >> [ 290.713280] ehci-platform 1c1b000.usb: port 1 reset error -110 >> [ 291.344084] usb usb2-port1: Cannot enable. Maybe the USB cable is >> bad? >> >> No USB-Device plugged in. >> _______________________________________________ >> Arm-dev mailing list >> Arm-dev(a)centos.org >> https://lists.centos.org/mailman/listinfo/arm-dev > > Hello Pablo, > > I'm getting more and more failures at the syslog concerning USB (see > above). Is there a solution? Kernel-Update? Sorry, no news about that, have you tested the latest fedora kernel (4.19.x based)?, just to see if anything changes? > > BTW: did the HDD-RAID board work with CentOS and this kernel > (4.17.17-200.el7.armv7hl) ? Haven't tested, but if it doesn't work, let me know and we'll investigate. BTW, I'll be building a test 4.18.14, it should appear tomorrow. (takes a while to build :-)) > > Thanks > > Andreas > > > Pablo

1 0

Re: [Arm-dev] Using zram-swap
by Mark Verlinde 12 Oct '18

12 Oct '18

Being the hidden source of this discussion it's only fair to try to explain the origin. ;) First objective was to get rid of the swap partition: - we do not know upfront the amount of ram and the appropriate swap size for a particular SBC/system - being a hardware guy it does not make sense to me to provide a sap partition while in realty data is written all over the medium (SD card) to level out wear. NOTE this is from my low level hardware perspective there may be compelling arguments from a (high level) system perspective. And yes the most commly offerd 1G is a little comes a little to short for us: We would love to offer a mail-server with antivirus capabilities utilizing Rspamd and ClamAV, and unfortunately CalmAV has a memory foot print of about 650 MB. You may argue this is not feasible. My vredo is you can't be sure before you tried and and squeeze every drop of performance out of out out ar boards. That's why compressed swap-space in memory came up the table. Reading on it got me convinced it's a solution wort to persuit and we are moving to it until proven faulty. here the kickstart files we currently using to make images: https://github.com/markVnl/nethserver-createimg/tree/ks_wip/ks Would love to benchmark; ie craft a test to get some numbers on the table Unfortunaly my knowlage comes to sort to provode this. What can say is my compile time of big demanding packages on a odroid HC1 drop about 20-25%; especially "linking" speeds up remarkable! How can we craft a test? -----Oorspronkelijk bericht----- Afzender: Robert Moskowitz<rgm(a)htt-consult.com> Verstuurd: Vrijdag 12 Oktober 2018 19:36 Aan: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org>; Fred Gleason <fredg(a)paravelsystems.com> Onderwerp: Re: [Arm-dev] Using zram-swap On 10/12/18 1:24 PM, Fred Gleason wrote: On Oct 12, 2018, at 13:15, Gordan Bobic <gordan(a)redsleeve.org <mailto:gordan@redsleeve.org>> wrote: It depends on what you are running on that system. If you have 1GB of RAM and want to run a desktop environment web browser, that'll go pretty poorly without swap. So how does putting swap on RAM help that situation? You’re not increasing the overall memory space by doing so, but merely partitioning it into two different buckets (while also adding the complexity and performance overhead of accessing the part that is now ‘swap’). See Gordon's earlier comment on Firefox's bad memory allocation. Zram is a big help there; I see this on my F29 system. # free total used free shared buff/cache available Mem: 1022148 655520 107204 22284 259424 327636 Swap: 487304 253952 233352 # zramctl NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lz4 475.9M 246.4M 109.1M 114.2M 2 [SWAP] My mail server can be all over the place on memory and swap usage (it uses real swap file on sata) depending on what all the scanning software is doing and who is using roundcubemail. So YMMV, and this should not hurt if your system does not need to swap. # free total used free shared buff/cache available Mem: 2060396 189332 1189972 26432 681092 1766392 Swap: 982420 0 982420 # zramctl NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lz4 959.4M 4K 64B 4K 2 <swap> I may switch this setup to a Cubeboard2 (1GB mem) from the Cubietruck. I have a number of C2 and only a couple CT, so if it does not need the memory... Cheers! |----------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |----------------------------------------------------------------------| | A room without books is like a body without a soul. | | -- Cicero | |----------------------------------------------------------------------| _______________________________________________ Arm-dev mailing list Arm-dev(a)centos.org <mailto:Arm-dev@centos.org> https://lists.centos.org/mailman/listinfo/arm-dev <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

2 1

Using zram-swap
by Robert Moskowitz 12 Oct '18

12 Oct '18

I have very recently learned about zram-swap. Fedora-29-arm is using it. It supposedly makes a considerable difference even over HD swap. Since many (potential) users of Centos-arm do not have a ready HD, perhaps we can switch the image from a physical partition to zram? Or at least instructions to change to this on the wiki. Perhaps target the 7.6 image? (is there any information as to when 7.6 may be available?) thanks

4 18

← Newer
1
...
12
13
14
15
16
17
18
...
69
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev