March 2019 - arm - Fedora Mailing-Lists

by Ken Harris

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

4 years, 5 months

2
2
0 / 0

Kernel 5.0 value add for Fedora arm?

by Robert Moskowitz

I am looking at summaries of features in the 5.0 kernel. I will have to dig into what the Fscrypt algorithm is and what that means, but.. I see support for RPi touchscreen. Will this add RPi touchscreen support for Fedora-arm? I suspect a lot more is needed than just a driver. What about other touchscreen for other arm SOC? Anything else I should look at and maybe take advantage of.... thanks. Good weekend to all.

4 years, 5 months

3
2
0 / 0

Bug report for IP address changes?

by Jeffrey Walton

Hi Everyone, What component should receive the bug report for the IP address changes on armv7 and aarch64? Jeff

4 years, 7 months

4
5
0 / 0

Problem with uboot 2019.04-rc2 and Cubieboad2

by Robert Moskowitz

The environment is only the uboot on the uSD and all partitions on the sata HD. I have been doing this for years now with no problem. uboot has always switched to looking for the sata hd for partitions if no partitions on the uSD: U-Boot SPL 2018.09-rc3 (Sep 05 2018 - 19:12:48 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2018.09-rc3 (Sep 05 2018 - 19:12:48 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubieboard2 I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 Loading Environment from FAT... ** No valid partitions found ** In: serial Out: serial Err: serial SCSI: Target spinup took 0 ms. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ** Invalid partition 1 ** scanning bus for devices... Device 0: (0:0) Vendor: ATA Prod.: WDC WD800BEVS-75 Rev: 04.0 Type: Hard Disk Capacity: 76319.0 MB = 74.5 GB (156301488 x 512) Found 1 device(s). Device 0: (0:0) Vendor: ATA Prod.: WDC WD800BEVS-75 Rev: 04.0 Type: Hard Disk Capacity: 76319.0 MB = 74.5 GB (156301488 x 512) ... is now current device Scanning scsi 0:2... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 567 bytes read in 33 ms (16.6 KiB/s) Ignoring unknown command: ui Ignoring malformed menu command: autoboot Ignoring malformed menu command: hidden Ignoring unknown command: totaltimeout CentOS-Userland-7-armv7hl-generic-Minimal-1810 Boot Options. 1: CentOS-Userland-7-armv7hl-generic-Minimal-1810 (4.14.82-201.el7.armv7hl) Enter choice: 1: CentOS-Userland-7-armv7hl-generic-Minimal-1810 (4.14.82- 201.el7.armv7hl) Retrieving file: /initramfs-4.14.82-201.el7.armv7hl.img Yes, this particular event is with the current Centos arm image, but that should not matter. I have to get this Centos image built and installed before I can test with Fedora arm image.... I grabbed a more recent uboot via: Fedora-Minimal-armhfp-30-20190301.n.0-sda When I try booting with the uboot in that image I get: U-Boot SPL 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubieboard2 I2C: ready DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... ** No valid partitions found ** In: serial Out: serial Err: serial SCSI: Target spinup took 0 ms. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: sunxi_set_gate: (CLK#66) unhandled eth0: ethernet@1c50000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 3 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ** Invalid partition 1 ** scanning bus for devices... data abort pc : [<7ef86b0e>] lr : [<7ef82d89>] reloc pc : [<4a01ab0e>] lr : [<4a016d89>] sp : 7af43ad0 ip : 0000001c fp : 000000c0 r10: 00000000 r9 : 7af4bed8 r8 : 00000000 r7 : 7af43d50 r6 : 7efc4894 r5 : 7efcc2f8 r4 : 7efcc2f8 r3 : 00000000 r2 : 00000000 r1 : ea000016 r0 : 7efcc2f8 Flags: nZcv IRQs off FIQs off Mode SVC_32 Code: e92dbd10 f8d045f0 b0858080 1000f8d8 (f8d14604) Resetting CPU ... resetting ... U-Boot SPL 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubieboard2 I2C: ready DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... ** No valid partitions found ** In: serial Out: serial Err: serial and so forth.... If there is a rc3 available, please tell me what image to grab for it and I can test with that. Meanwhile, it seems there is a problem here. thanks

4 years, 7 months

3
9
0 / 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by pwhalen＠redhat.com

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-04-02 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.o... Source: https://apps.fedoraproject.org/calendar/meeting/9431/

4 years, 8 months

1
0
0 / 0

grub2-mkconfig: command not found

by Jeffrey Walton

Hi Everyone, I deleted several old kernels today. grub.cfg listed an old kernel. I attempted to regenerate grub.cfg but experienced: grub2-mkconfig: command not found What tool do we use to generate the grub menu? Thanks in advance.

4 years, 8 months

1
0
0 / 0

Problem with kernel-5.0.3-200.fc29.armv7hl on Raspberry PI 3B/3B+

by William Jacobs

Yesterday I installed the above referenced kernel on two Raspberry PIs, a 3B+ and a 3B. I also installed it on a BeagleBone Black and a Hummingboard2 (nxp i.mx6 Quad CPU). On the BeagleBone Black and the Hummingboard, no problems at all, so this appears to be specific to the Raspberry PI platform or CPU. The Raspberry PI's are both actually running, but I noticed that top tells me that the load average is 4.0. But these things are not actually doing anything. Top does not show any process using more than 0.7% CPU and that it tells me that each core is nearly 100% idle. dmesg is not giving me any significant errors. I have worked at finding the problem for a few hours and have not found a lot. But here is what I have found: If I reboot to kernel 4.20.16, the problem goes away. When booted into kernel 5.0.3 dmesg gives this line: [ 16.342693] systemd[1]: Mounting Kernel Debug File System... but I see nothing that indicated why this might be happening. Anyone else try kernel 5.0.3 on a Raspberry Pi? Any thoughts on where to look for the problem? Thanks very much! Will

4 years, 8 months

2
2
0 / 0

testing Fedora-Minimal-armhfp-30-20190326.n.0-sda on Cubieboard2

by Robert Moskowitz

I am at IETF104, and only brought a Cubieboard2 and forgot my sata drive and sata adapter. Thus all testing is uSD and USB only until next Monday. I installed minimal on a 4GB uSD and deleted all partitions, leaving only the uboot. I installed minimal on a 16GB uSD and expanded the rootfs to the full size of the card. First test was uboot only in the uSD slot and the full image USB connected (uSD USB adapter). The boot failed. We are still on the rc2 broken uboot: U-Boot SPL 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2019.04-rc2 (Feb 19 2019 - 10:00:37 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubieboard2 I2C: ready DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... ** No valid partitions found ** In: serial Out: serial Err: serial SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: sunxi_set_gate: (CLK#66) unhandled eth0: ethernet@1c50000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning bus 2 for devices... 2 USB Device(s) found scanning bus 3 for devices... 1 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ** Invalid partition 1 ** scanning bus for devices... Found 0 device(s). Device 0: unknown device Device 0: EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80008d80 ... EHCI timed out on TD - token=0x80008d80 Vendor: Mass Rev: Prod: Storage Device Type: Removable Hard Disk Capacity: 14992.0 MB = 14.6 GB (30703616 x 512) ... is now current device EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80008d80 ... The uboot DID recognize the USB device, but did not boot it. The second test was to put the full image in the uSD slot. This booted up properly, went through the console first boot dialog and then I could log in as root. Next test used the F29 uboot on the 4Gb uSD in the uSD slot and the full image on the USB adapter: U-Boot SPL 2018.09 (Sep 11 2018 - 10:09:46 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2018.09 (Sep 11 2018 - 10:09:46 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubieboard2 I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 Loading Environment from FAT... ** No valid partitions found ** In: serial Out: serial Err: serial SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ** Invalid partition 1 ** scanning bus for devices... Found 0 device(s). Device 0: not available Device 0: device type unknown ... is now current device Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 10.0.6.251 (20 ms) *** ERROR: `serverip' not set etc.... So this uboot seems better, but it is not recognizing the USB drive. Is there a later uboot than that in F29 (Fedora-Minimal-armhfp-29-1.2-sda) for me to test with? Otherwise I don't see any other testing I can do until I get back Monday.

4 years, 8 months

1
0
0 / 0

ASUS Tinkerboard support

by Jeffrey Walton

Hi Everyone, I've got a ASUS Tinkerboard. I like ASUS motherboards, but I am not happy with the Debian 9 image and its performance. MySQL performance blows, and takes over 2 minutes to create 4 tables. I'd like to try a Fedora image if possible. I found some past posts about Fedora for the board, like [1], but I can't tell if it is supported. [1] https://ask.fedoraproject.org/en/question/119755/fedora-27-pi-working-on-... [2] https://tinkerboarding.co.uk/forum/archive/index.php/thread-1826.html Does Fedora support the Tinkerboard? Jeff

4 years, 8 months

4
4
0 / 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

by pwhalen＠redhat.com

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-03-26 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.o... Source: https://apps.fedoraproject.org/calendar/meeting/9431/

4 years, 8 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm March 2019