arm October 2018

arm@lists.fedoraproject.org

13 participants
18 discussions

Bluetooth on Udoo Neo ?
by Ken Harris 25 Jun '19

25 Jun '19

Is it possible to enable Bluetooth on Udoo Neo ? FYI, it uses the TI WL1831 module. I tried : hciattach -n ttymxc2 texas ... but got "Initialization timed out." I also tried various combinations of bit rates and flow control. Any tips are welcome. -K

2 2

how to make a working f28 sd card for odroid-hc2 ?
by Torbjorn Jansson 14 Mar '19

14 Mar '19

Hello for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers. the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora. all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host) 1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch 2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8" (sdf in this case is my sd card) 3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd 4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin . ./sd_fusing.sh /dev/sdf ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck. last few lines on serial console is something like: Starting firewalld - dynamic firewall daemon... Starting Initial Setup configuration program... then some stuff related to usb & my disk then on first boot a few lines related to OpenSSH key generation rebooting hangs at same place with exception of SSH keys. to get a bit further i can mount the root filesystem manually on my other computer and remove the following two files: rm /etc/systemd/system/graphical.target.wants/initial-setup.service rm /etc/systemd/system/multi-user.target.wants/initial-setup.service this gets rid of the initial setup but then i get a whole bunch of services failing and boot being really really slow, it takes probably 10-15 minutes for everything to time out and get to the logon prompt. when i get it root doesn't work. this is where i kind of gave up. i know i somehow managed to get a bootable image several months ago, but i'm not sure if i then had to manually set root password by editing passwd or shadow before trying to boot. things on my wish list for this board: easier installation and updated packages that work. for example arm-image-installer with a board definition for odroid. may be usefull even if we have to run sd_fusing manualy after anyway, possibly with a text saying so. this also would help to make --addconsole work uboot that recognized hc2 so it loads the right file dtb file for hc2, one that works and is appropriate.

7 19

Odroid C2
by Dr. Zenzic 16 Dec '18

16 Dec '18

Hello All, Has anyone had any luck getting Fedora 28 to work on the Odroid C2? I've tried downloading the Fedora 28 Server aarch.raw.xz image which i put onto my sd card. I then moved the Archlinux aarch64 boot parition into boot along with the lib/modules and lib/firmware folders from Archlinux. This has been to no avail. I'm working on building the hardkernel kernel myself now but have never actually compiled a kernel myself so I'm not sure what I fully need to get the Fedora rootfs to boot with the kernel. If anyone has some guidance or a nice writeup on getting a bootable kernel recognized by Fedora on the Odroid C2 that would be greatly appreciated.

5 14

no hdmi audio on older tv
by Jiri Vanek 31 Oct '18

31 Oct '18

Hello! I have f29 (kernel-4.18.12-300.fc29.aarch64 ) on machine, which is changing its place from time to time - between two TVs. Old, and older:) Both are connected by HDMI. Video output is fine, even acceleration is working, but sound work only on newer of those two. I don't know if this is regression, because this machine replaced 32b rapbery2 with kodi, which was working without issues on both TVs (but was eaten by (not mine) dog) I was following https://fedoraproject.org/wiki/How_to_debug_sound_problems but had not found much: - with removed pulseaudio, the aplay -vv segfaults - I really on pulseaudio anyway, as I need to transfer sound to this machine over network - the diff of alsa-info.sh's is really minimal [1], only [cite] state.vc4hdmi { control.1 { iface PCM name ELD value '100007006712000100000000000000004c2d9d02 for non working and value '100007006712000100000000000000004c2d9b03 for working [/cite] - when alsamixer is opened, then the default looks like working, and the job on old tv; but not do nothing older tv. - when alsamixer -c0 is opened, then the vc4-hdmi reports no control for selected device for *both* tvs (which is same as f6 and selecting vc4-hdmi) Does anybody have a clue what to try? Thanx in advance form java world, J. [1] --- /home/jvanek/Desktop/workingAudio +++ /home/jvanek/Desktop/nonWorkingAudio @@ -1,5 +1,5 @@ STDERR: -cat: /tmp/alsa-info.TzPwpaQcKW/acpidevicestatus.tmp: No such file or directory +cat: /tmp/alsa-info.GXybsmPDbN/acpidevicestatus.tmp: No such file or directory cat: '/sys/module/(null)/parameters/*': No such file or directory @@ -8,7 +8,7 @@ !!ALSA Information Script v 0.4.64 !!################################ -!!Script ran on: Mon Oct 29 14:09:06 UTC 2018 +!!Script ran on: Mon Oct 29 14:15:02 UTC 2018 !!Linux Distribution @@ -152,7 +152,7 @@ control.1 { iface PCM name ELD - value '100007006712000100000000000000004c2d9b0353414d53554e470907070000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' + value '100007006712000100000000000000004c2d9d0253414d53554e470907070000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' comment { access 'read volatile' type BYTES -- Jiri Vanek Senior QE engineer, OpenJDK QE lead, Mgr. Red Hat Czech jvanek(a)redhat.com M: +420775390109

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 28 Oct '18

28 Oct '18

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2018-10-30 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/9202/

1 0

Fwd: raspberry pi aarch64 bcm2835-v4l2 (camera module)
by Jiri Vanek 26 Oct '18

26 Oct '18

Hello! Have somebody sucsesfully run the official[1] rpi camera on Fedora, aarch64? I have f29 sucesfully running on pi 3B+ and the only glitch is my inability tu run cammera:( Best regards from Java world J. [1] https://www.raspberrypi.org/products/camera-module-v2/

2 15

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 22 Oct '18

22 Oct '18

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2018-10-23 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora ARM & AArch64 weekly status meeting. More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://apps.fedoraproject.org/calendar/meeting/9202/

2 1

Cubox-i ethernet broken on 4.18.x Kernels
by Siavash Safi 21 Oct '18

21 Oct '18

Hello, I mentioned this issue on IRC but also posting here: I've been using Fedora on Cubox-i for a long time, I noticed that 4.18.x kernels broke networking. Booting to 4.17.19-200.fc28 fixes the issue for me. The eth0 interface is still visible on 4.18.x kernels but it does not work: - The interface was connected to an Amplifi HD, the link kept going up/down every few seconds (no such issue on older kernels) - Connecting the interface to a Cisco switch fixes the unstable link issue, the rest of the tests were done with this switch - DHCP hangs (tested manually with dhclient, no output) - Setting an static IP on the interface works but no traffic passes through (tested ICMP, etc.) I can provide more technical details and kernel log messages if required. Thanks, Siavash

2 1

f2fs install ?
by Ken Harris 20 Oct '18

20 Oct '18

I'm interested to install Fedora ARM on an F2FS file system. Are there tips or scripts to do this ? It looks like "arm-image-installer" basically uses "dd" to copy an image to storage. I had a script once that created partitions and file systems and copied (and then had to twiddle with the UUIDs in file systems or /etc/fstab) ... but I think I lost that script. I suppose I could make a kickstart file and use livemedia-creator or appliance-tools to create an image ... but I've never got that to work. Tips appreciated. Thanks, K

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 some 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>, 2018-09-26-18:30:11, 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

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm October 2018