arm April 2019

arm@lists.fedoraproject.org

7 participants
15 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

Kernel 5.0 value add for Fedora arm?
by Robert Moskowitz 22 Jun '19

22 Jun '19

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.

3 2

Bug report for IP address changes?
by Jeffrey Walton 01 May '19

01 May '19

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

4 5

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

28 Apr '19

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-04-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/9431/

1 0

Aromic Host on Aarch64
by Pierre-Francois RENARD 21 Apr '19

21 Apr '19

Hello guys, is there any specific way to write an Atomic Host image on a sd card for raspberrypi (3 or 3+ in my case). I used this one : https://mirrors.dotsrc.org/fedora-buffet/alt/atomic/stable/Fedora-29-update…. with a classical dd and also with fedora-arm-installer. Same result .. no boot and no message on HDMI. Thanks

5 8

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 21 Apr '19

21 Apr '19

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2019-04-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/9431/

1 0

Koji builder for both aarch64 and armv7hl
by Shad L. Lords 21 Apr '19

21 Apr '19

I've got a koji instance I've setup that is building for both aarch64 and armv7hl. Right now I need two separate hosts. One for each arch. I notice that the fedora koji instance has most of their arm builders dedicated to one arch or the other as well. However, there are 3 builders ( buildhw-aarch64-01.arm.fedoraproject.org, buildhw-aarch64-02.arm.fedoraproject.org, buildhw-aarch64-03.arm.fedoraproject.org) that show arches of aarch64, armhfp. I'm wondering if there is anything special setup on those builders that allow them to build both 32 and 64-bit arm packages. I've tried searching for anything related to setting up both arches for a builder but am unable to find anything. If there is any documentation on how to set this up just point me in the right direction and I'll go try it out. If not any help would be appreciated. Thanks, -Shad

2 1

Re: Problems with Uboot
by Peter Robinson 20 Apr '19

20 Apr '19

On Sat, 20 Apr 2019, 10:41 JAMES TATE, <binarynut(a)comcast.net> wrote: > It's not KDE that giving me Errors it's Linux, The KDE desktop is working > fine with out any errors. > Something else that has got me confused is the problems with the USB ports > in Linux with the Wifi and Rii adapters plugged in USB ports, In Raspbien > OS there are no problems with having the Wifi and Rii adapters plugged in. > > The raspberry pi kernel shipped with Raspbian is quite significantly different to the upstream Linux kernel, they use a completely different USB host driver. Also what is the chipset/driver of the WiFi adapter? > On April 20, 2019 at 4:16 AM Peter Robinson <pbrobinson(a)gmail.com> wrote: > > > > > > On Sat, Apr 20, 2019 at 12:37 AM JAMES TATE <binarynut(a)comcast.net> > wrote: > > > > > > > > > > On April 19, 2019 at 6:29 PM Peter Robinson <pbrobinson(a)gmail.com> > wrote: > > > > > > > > > > > > On Fri, Apr 19, 2019 at 6:18 PM JAMES TATE <binarynut(a)comcast.net> > wrote: > > > > > > > > > > Error message on uboot. > > > > > > > > > > "Timeout poll on Interrupt endpoint" > > > > > > > > > > > > > > > I have a Raspberry pi 2 B+ and Fedora-KDE-armhfp-29-1.2-sda.raw.xz > installed on a 32gb SD card. > > > > > > > > > > > > > > > I gather that it has something to do with USB ports. I have a > WiFi adapter and a wireless keyboard adapter plugged in two USB ports of > the Raspberry Pi, and that's it. > > > > > > > > > > > > > > > Does anyone have any ideals ? > > > > > > > > At what point in the boot do you get that error, is it in linux, or > > > > before linux starts? What happens if you remove the wifi/keyboard and > > > > see if it boots to completion and then plug them in? > > > > > > > > Can you try the latest Fedora 30 nightly? F-29 is quite old now. > > > > > > > > Peter > > > > > > The error occures just as Linux starts loading. > > > The problem is with the Wifi and Rii keyboard adapters loading down > the power on USB ports. I removed both adapters and it started loading > normally. > > > I need to modify the +5v supply to Raspberry Pi. > > > > Yes, a good quality PSU for the RPii3 is critical, see details in the > FAQ: > > https://fedoraproject.org/wiki/Raspberry_Pi > > > > > I also loaded Fedora-KDE GUI onto a 64gb SD card and got errors > running out of space. > > > I ordered a 128gb Micro SD card, I hope that will be enough space for > loading a GUI Arm OS > > > > We don't have a lot of interest in KDE so I'm not sure of the state of > it. >

1 0

Problems with Uboot
by JAMES TATE 19 Apr '19

19 Apr '19

Error message on uboot. "Timeout poll on Interrupt endpoint" I have a Raspberry pi 2 B+ and Fedora-KDE-armhfp-29-1.2-sda.raw.xz installed on a 32gb SD card. I gather that it has something to do with USB ports. I have a WiFi adapter and a wireless keyboard adapter plugged in two USB ports of the Raspberry Pi, and that's it. Does anyone have any ideals ?

3 3

Problem with uboot 2019.04-rc2 and Cubieboad2
by Robert Moskowitz 19 Apr '19

19 Apr '19

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

3 9

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm April 2019