arm September 2018

arm@lists.fedoraproject.org

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

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

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

30 Sep '18

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2018-10-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.org… Source: https://apps.fedoraproject.org/calendar/meeting/9202/

1 0

F29 dnf update problem
by Robert Moskowitz 28 Sep '18

28 Sep '18

DOn't know if this is a general F29 problem... Skipping packages with broken dependencies: authselect armv7hl 1.0.1-1.fc29 updates-testing 55 k authselect-libs armv7hl 1.0.1-1.fc29 updates-testing 108 k looking up in the messages I see: Problem 1: cannot install the best update candidate for package authselect-libs-1.0-3.fc29.armv7hl - nothing provides systemctl needed by authselect-libs-1.0.1-1.fc29.armv7hl Problem 2: cannot install the best update candidate for package bubblewrap-0.3.0-2.fc29.armv7hl - package bubblewrap-0.3.0-2.module_2123+73a9ef6f.armv7hl is disabled Problem 3: cannot install the best update candidate for package libnghttp2-1.33.0-1.fc29.armv7hl - package libnghttp2-1.33.0-1.module_2177+2526c218.armv7hl is disabled Problem 4: cannot install the best update candidate for package libpeas-1.22.0-9.fc29.armv7hl - package libpeas-1.22.0-9.module_2123+73a9ef6f.armv7hl is disabled Problem 5: cannot install the best update candidate for package libpeas-gtk-1.22.0-9.fc29.armv7hl - package libpeas-gtk-1.22.0-9.module_2123+73a9ef6f.armv7hl is disabled Problem 6: cannot install the best update candidate for package perl-HTTP-Tiny-0.076-1.fc29.noarch - package perl-HTTP-Tiny-0.076-1.module_2073+eebc5b71.noarch is disabled Problem 7: package authselect-1.0.1-1.fc29.armv7hl requires authselect-libs(armv7hl-32) = 1.0.1-1.fc29, but none of the providers can be installed - cannot install the best update candidate for package authselect-1.0-3.fc29.armv7hl - nothing provides systemctl needed by authselect-libs-1.0.1-1.fc29.armv7hl ================================================================================ I have other things to do today. Hopefully this well get fixed. Or should I go ahead and update what will update?

4 4

Cubietruck wifi
by Robert Moskowitz 28 Sep '18

28 Sep '18

Interesting observation. With the latest uboot (2018.09) and Fedora 29-beta-Xfce No wifi. Nothing shows when I do 'ip a' BUT... Same uboot, but the Centos7 image: CentOS-Userland-7-armv7hl-generic-GNOME-1804-sda There is the wifi interface. The Gnome install asks me if I want to connect to any of the visible SSIDs. How did the Centos arm team get this to work and not Fedora? :) Really not so important RIGHT now, as my CT is for a Centos server. I am only planning on running Fedora on Cubieboard2 which do not have their own embedded wifi. Just a data point for now.

3 8

F29 beta - why does fsck not work from su?
by Robert Moskowitz 27 Sep '18

27 Sep '18

No fsck! 'man fsck' works... # fsck /dev/sdb bash: fsck: command not found [root@localhost rgm]# man fsck [root@localhost rgm]# dnf whatprovides fsck Last metadata expiration check: 2:12:23 ago on Wed 26 Sep 2018 07:28:29 PM EDT. util-linux-2.32.1-1.fc29.armv7hl : A collection of basic system utilities Repo : @System Matched from: Filename : /usr/sbin/fsck util-linux-2.32.1-1.fc29.armv7hl : A collection of basic system utilities Repo : fedora Matched from: Filename : /usr/sbin/fsck [root@localhost rgm]# dnf install util-linux Last metadata expiration check: 2:13:38 ago on Wed 26 Sep 2018 07:28:29 PM EDT. Package util-linux-2.32.1-1.fc29.armv7hl is already installed, skipping. Dependencies resolved. Nothing to do. Complete! ls /usr/sbin/fs* /usr/sbin/fsadm /usr/sbin/fsck.ext3 /usr/sbin/fsck.ntfs /usr/sbin/fsck /usr/sbin/fsck.ext4 /usr/sbin/fsck.vfat /usr/sbin/fsck.btrfs /usr/sbin/fsck.fat /usr/sbin/fsck.xfs /usr/sbin/fsck.cramfs /usr/sbin/fsck.minix /usr/sbin/fsfreeze /usr/sbin/fsck.ext2 /usr/sbin/fsck.msdos /usr/sbin/fstrim ================ works fine from console, logged in as root.

3 3

Rock64 support for F28?
by Jonathan Vaughn 26 Sep '18

26 Sep '18

I see a few months ago in the mailing list that support was brought up (in the context of F27) and it was mentioned that improving support for Rockchips devices in general was intended for F28. It doesn't appear that fedora-arm-installer currently supports the Rock64 board as far as I can tell. I'm trying to figure out how to add support by adding to /usr/share/arm-image-installer/boards.d and socs.d, as well as solving the lack of appropriate uboot in /usr/share/uboot for Rock64. I flashed (and tested successfully) a community built Debian Stretch image and by comparing it's partition layout and some information from OpenSUSE I can guess at what some of it should be, but I'm not entirely sure how to make the appropriate files in socs.d, boards.d, and what all is needed in uboot ... Debian Stretch image that boots : https://github.com/ayufan-rock64/linux-build/releases/download/0.7.8/stretc… U-boot used in the above build : https://github.com/ayufan-rock64/linux-u-boot OpenSUSE info : https://en.opensuse.org/HCL:Rock64 working stretch partition layout : # gdisk -l /dev/sdc GPT fdisk (gdisk) version 1.0.4 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sdc: 62333952 sectors, 29.7 GiB Model: Storage Device Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 9CFDF7D8-766C-43DE-9354-57097D428E8F Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 62333918 Partitions will be aligned on 64-sector boundaries Total free space is 30 sectors (15.0 KiB) Number Start (sector) End (sector) Size Code Name 1 64 8063 3.9 MiB 8300 loader1 2 8064 8191 64.0 KiB 8300 reserved1 3 8192 16383 4.0 MiB 8300 reserved2 4 16384 24575 4.0 MiB 8300 loader2 5 24576 32767 4.0 MiB 8300 atf 6 32768 262143 112.0 MiB 0700 boot 7 262144 62333918 29.6 GiB 8300 root loader1 (partition 1) is the SPL, loader2 (partition 4) is the U-Boot. atf (partition 5) per OpenSUSE is apparently some kind of "trust" image. The reserved partitions (partitions 2 and 3) seem to just be all nulls. The boot partition (partition 6) has extlinux/extlinux.conf apparently as well as 'System Volume Information' (guessing that the origin of that partition was built on Windows), and partition 7 is of course regular old Linux filesystem. I'm not sure how fedora-arm-installer decides to partition things, it wasn't obvious from socs.d/boards.d, so I'm not sure how to ensure that when creating the soc/board scripts that the correct layout is maintained. From glancing at the source code for fedora-arm-installer it seems like it just extracts the image onto the media and assumes the layout based on what was in the image, which might present a problem if the unified AArch64 image has only 3 partitions? Unless it would be expected that Fedora would have it's own build of uboot that would ensure things didn't need all those other partitions ? Anyways, I'm happy to either figure this out on my own if you can point me in the right direction or if you already have some WIP that needs a volunteer to test it, to do be your guinea pig.

2 5

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

23 Sep '18

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2018-09-25 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

OrangePI Plus2
by Pierre-Francois RENARD 21 Sep '18

21 Sep '18

Hello guys, what is the status of OrangePi support within fedora these days ? do you have any feedback regarding these boards ? See ya Fox

3 3

Re: F28 installation fails on ThunderX2 CN99xx
by Peter Robinson 19 Sep '18

19 Sep '18

Robert, > we see the f28 installer failing with: The Fedora 28 ship has long sailed, please test on Fedora 29 Beta RCs and provide feedback on that: https://dl.fedoraproject.org/pub/alt/stage/ > [ 43.222590] Internal error: Oops: 96000021 [#1] SMP > [ 43.227456] Modules linked in: > [ 43.230500] CPU: 87 PID: 1 Comm: swapper/0 Not tainted 4.16.3-301.fc28.aarch64 #1 > [ 43.237968] Hardware name: Cavium Inc. Saber/Saber, BIOS Cavium reference firmware version 6.4 05/30/2018 > [ 43.247521] pstate: 20400009 (nzCv daif +PAN -UAO) > [ 43.252304] pc : test_atomic64+0x134c/0x152c > > Kernel and initrd from: > > https://dl.fedoraproject.org/pub/fedora/linux/releases/28/Server/aarch64/os… > > This is due to this upstream fix from v4.17-rc7 missing: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… Sure, all of the above isn't solvable now, we need to look at F-29+ Now is the time to ensure everything that is needed here for F-29 to be there and all testing should be done there. > Also, a workaround that uses kernel and initrd from f29 or rawhide for > f28 installation does not work as the bootchain of the installer needs > files from the same media. Otherwise boot fails with "Pane is dead" > and "new value non-existent xfs filesystem is not valid as a default > fs type", see also: > > https://access.redhat.com/solutions/697913 > > Do you see an alternative workaround to pxe boot f28? Use Fedora 29. > Would it be possible to update the installer's kernel and initrd? No. > Another question: Would it be possible to include early silicon (Rev > Ax) Errata workarounds to f28, f29 and rawhide? There are 2 patches > required, both are in this branch: Are these patches expected to go upstream? What impact would those patches have on other ARM platforms or even other architectures? If they are not planned to go upstream how long would you expect Fedora to carry them before we dropped them? > https://github.com/cavium/thunderx-linux/commits/thunder-4.16 > > PCI: Vulcan: AHCI PCI bar fix for Broadcom Vulcan early silicon > https://github.com/cavium/thunderx-linux/commit/940d574d4ef0 > > ahci: thunderx2: Fix for errata that affects stop engine > https://github.com/cavium/thunderx-linux/commit/6fb2dd30218a > > There are still some Ax systems around that wouldn't be supported > otherwise. > > Btw, the f29 kernel was not available for installation: You need kernel/kernel-core/kernel-modules. dnf --disablerepo=\* --enablerepo=f29 repoquery kernel\* Peter

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm September 2018