arm December 2023

arm@lists.fedoraproject.org

15 participants
10 discussions

Fedora on Rock 5B
by Andreas Reschke 11 Jun '24

11 Jun '24

Hi there, I've tried to install Fedora on my Rock 5 without success. Booting with https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.7.1/rock-5… on SD-Card and source from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everythin…. Board boots up fine but later starting in loop with 350.456154] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors end ############### [ 352.156835] dracut-initqueue[1065]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 352.161387] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh: "[ -e "/dev/root" ]" [ 352.164564] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_disks.sh: "[ "$main_loop" -ge "10" ]" [ 352.167716] dracut-initqueue[1065]: Warning: /lib/dracut/hooks/initqueue/finished/wait_for_settle.sh: "[ -f /tmp/settle.done ]" [ 352.171999] dracut-initqueue[1065]: Warning: dracut-initqueue: starting timeout scripts [ 352.172610] dracut-initqueue[1065]: Warning: ############# Anaconda installer errors begin ############# [ 352.172852] dracut-initqueue[1065]: Warning: # # [ 352.173097] dracut-initqueue[1065]: Warning: It seems that the boot has failed. Possible causes include [ 352.173296] dracut-initqueue[1065]: Warning: missing inst.stage2 or inst.repo boot parameters on the [ 352.173537] dracut-initqueue[1065]: Warning: kernel cmdline. Please verify that you have specified [ 352.173731] dracut-initqueue[1065]: Warning: inst.stage2 or inst.repo. [ 352.173918] dracut-initqueue[1065]: Warning: Please also note that the 'inst.' prefix is now mandatory. [ 352.174156] dracut-initqueue[1065]: Warning: # # [ 352.174354] dracut-initqueue[1065]: Warning: #### Installer errors encountered during boot: #### [ 352.174543] dracut-initqueue[1065]: Warning: # # [ 352.174775] dracut-initqueue[1065]: Warning: Reason unknown [ 352.174970] dracut-initqueue[1065]: Warning: # # Full log file: see rock.txt Has anybody more succcess ? Greetings Andreas

3 10

Fedora on ROCK 5 Model B
by Andreas Reschke 08 Apr '24

08 Apr '24

Hello, I've installed Fedora 40 Rawhide on my Rock 5 Short howto: What you need: 1) https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.9.1/rock-5… dd this Image on a SD-Card 2) https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everythin… dd this Image on a USB stick Put both in your Rock 5B and boot. I've done the Net-install installation with KDE Wayland. The SD-Card with UEFI is needed for booting. Questions: 1. GPU: root@rockpi5:~# inxi -Gx Graphics: Message:No PCI device data found. Display:server:X.Org v:23.2.2 with:Xwayland v:23.2.2 driver:X: loaded:modesetting dri:swrast gpu:N/A resolution:1920x1080~60Hz API:EGL v:1.5 drivers:kms_swrast,swrast platforms: active:gbm,x11,surfaceless,device inactive:wayland API:OpenGL v:4.5 vendor:mesa v:23.3.0 glx-v:1.4 direct-render:yes renderer:llvmpipe (LLVM 17.0.4 128 bits) API:Vulkan v:1.3.268 drivers:llvmpipe surfaces:xcb,xlib devices:1 root@rockpi5:~# How can I improve GPU Performance ? Mali / Panfrost Driver are available but not loaded /used root@rockpi5:~# rpm -ql mesa-dri-drivers-23.3.0-1.fc40.aarch64 | grep -i pan /usr/lib64/dri/panfrost_dri.so root@rockpi5:~# rpm -ql mesa-dri-drivers-23.3.0-1.fc40.aarch64 | grep -i mali /usr/lib64/dri/mali-dp_dri.so root@rockpi5:~# Creating a custom xorg.conf doesn't make sense while using Wayland ? 2. Boot Is there any way to boot Fedora direct from NVME instead using rock-5b_UEFI_Release_v0.9.1.img on SD-Card ? Thanks Andreas

4 7

Lenovo Thinkpad X13s Black Screen
by Luke Short 13 Feb '24

13 Feb '24

Hey folks, I recently purchased the X13s Qualcomm Arm laptop. I am very excited to try Linux on it! I'd like to use Fedora to align with what I use for work. The [Fedora Wiki](https://fedoraproject.org/wiki/Thinkpad_X13s) page appears to be out-of-date for this laptop and I would be happy to help update it once I get it working on my end. From what I've read online, Linux support for it is good these days with many users reporting success with Arch Linux, Debian (Armbian, specifically), Ubuntu, and even Fedora running on it. However, I am having issues with Fedora and always end up with a black screen once the GPU gets loaded. I have tested with Fedora 39 (fully updated with the latest firmware and Linux 6.6) and Rawhide/40 (Linux 6.7.0-rc4 currently). Both GNOME (Workstation) and Xfce (Spin) desktop builds have been tested (I can never actually get that far to see them, though). From my research, these are all of the steps required to get the laptop to even boot (kernel modules are missing from the initramfs and additional boot arguments are needed). ``` $ export DEVICE=sda $ sudo -E mount -t btrfs -o subvol=root /dev/${DEVICE}3 /mnt $ sudo -E mount -t btrfs -o subvol=home /dev/${DEVICE}3 /mnt/home $ sudo -E mount -t ext4 /dev/${DEVICE}2 /mnt/boot $ sudo -E mount -t vfat /dev/${DEVICE}1 /mnt/boot/efi $ sudo mount -t proc none /mnt/proc $ sudo mount --rbind /dev /mnt/dev $ sudo mount --rbind /sys /mnt/sys $ sudo mkdir -p /mnt/run/systemd/resolve/ $ echo "nameserver 8.8.8.8" | sudo tee /mnt/run/systemd/resolve/stub-resolv.conf $ sudo nano /mnt/etc/dracut.conf.d/20_thinkpad-x13s.conf force_drivers+=" nvme phy_qcom_qmp_pcie i2c_hid_of i2c_qcom_geni leds_qcom_lpg pwm_bl qrtr pmic_glink_altmode gpio_sbu_mux phy_qcom_qmp_combo panel-edp msm phy_qcom_edp i2c_hid_of i2c_qcom_geni qcom_q6v5_pas usb_storage uas " $ sudo chroot /mnt dracut --regenerate-all --force $ sudo nano /mnt/etc/default/grub GRUB_CMDLINE_LINUX="efi=noruntime clk_ignore_unused pd_ignore_unused arm64.nopauth iommu.passthrough=0 iommu.strict=0 pcie_aspm.policy=powersupersave console=tty1 splash plymouth.ignore-serial-consoles loglevel=3" GRUB_DEFAULT_DTB="dtb/qcom/sc8280xp-lenovo-thinkpad-x13s.dtb" $ sudo chroot /mnt grub2-mkconfig -o /boot/grub2/grub.cfg $ sudo sync ``` Vanilla/upstream Fedora Arm raw image builds do not even boot without these tweaks. With these tweaks, I can boot to the GRUB menu and eventually see the Plymouth boot screen which shows the Fedora logo and then a loading spinner. When it switches to a graphical environment, the screen flashes and goes blank. I also seem to be unable to switch to a TTY console which could be due to the F keys not working properly. There is a kernel thread [here](https://lore.kernel.org/all/ZUidVUomjf8GMzrG@hovoldconsulting.com/T/) that explains how to get the stable Fedora 39 working. I did all of the steps but the same thing happened: the screen ends up being black once the system is fully booted up. I have tested using USB and the internal drive. The USB, despite historically being unreliable, has been more reliable in my testing. I believe those issues with low power voltage for USB devices have been fixed. Does anyone have any advice on how to get graphics working so I can get to the desktop environment? I feel so close to a solution but I seem to be missing a piece of the puzzle here. Thank you for any insight you may have! Research references: - [Thinkpad X13s - Fedora Project Wiki](https://fedoraproject.org/wiki/Thinkpad_X13s) - [ThinkPad X13s - Gentoo wiki](https://wiki.gentoo.org/wiki/ThinkPad_X13s) - [External display on the x13s?](https://lore.kernel.org/all/ZUidVUomjf8GMzrG@hovoldconsulting.com/T/) - [HCL:ThinkpadX13s - openSUSE Wiki](https://en.opensuse.org/HCL:ThinkpadX13s) Sincerely, Luke Short

3 10

Raspberry Pi 5 support - how to contribute?
by Daniel Miranda 01 Jan '24

01 Jan '24

Hello, I've recently - and somewhat surprisingly - already got my hands into a Raspberry Pi 5. I would like to contribute to make it supported , as the Pi4 is. I have extensive Fedora experience, but not with ARM, and how the whole ecosystem works. What would be useful to get started with a test image for the Pi5? Or if that's not yet possible, what information or resources can be of use to get to that points? Thanks! Daniel M

7 15

State of the mibility SIG, dec 2023
by Kevin Fenzi 26 Dec '23

26 Dec '23

Greetings. This will be a bit long, but I hope it will explain the current unfortunate state of the mobility sig. First a bit of history. The mobility sig was originally formed back in 2010. The goal then was “… a group of Fedora contributors that are interested in Fedora on small devices. Initially aimed at supporting NetBooks, Mobile Internet devices” A good deal of progress on small devices like netbooks and tablets was made, but then the members of the SIG moved on to other concerns. Then, in 2020 the most recent version of the SIG formed. The goal was focused on getting Fedora working well on the new pine64 pinephone, and then later when announced the new pine64 pinephone pro. In the last 3 years we have accomplished a lot: The phosh stack has been packaged up We have been producing Fedora Remixes with 3rd party kernels to provide support for pinephone and pinephone pro. a Phosh spin has been created and officially produced There was a effort to get a remix working for the oneplus 6, but still requiring a lot of manual tweaking. Unfortunately, the active members of the sig are not able to move things forward right now. The pinephone and pinephone pro are both old devices at this point. They were slow when released, and thats not improved. Worse, upstreaming of patches to get either of them working with a Fedora/Mainline kernel seems unlikely to us for a lot of reasons, including that many of the 3rd party patches aren’t in a state that upstream would accept and many authors of them have no particular desire to upstream them. The phosh spin is largely not useful in the current situation as the Fedora mainline kernel barely boots on the pinephone pro (not at all on the pinephone) and has no wireless or display. The image could be of use to other aarch64 single board style devices, but since they usually don’t have displays or modems, the phosh interface isn’t of particular insterest. Until the advent of some performant mobile device to target or more contributors who wish to drive things forward, I think we should just mark the Mobility sig inactive at this point, including: Retire the Phosh spin in f40 Hopefully find new maintainers for the phosh stack if there’s folks that want to keep them alive. Mark the sig inactive on wiki and matrix. respins will move to against a stable fedora release once a week or so, instead of against rawhide and more often. Hopefully there is someday a brighter day for Fedora mobile devices. Folks that want to try and revive the SIG and/or are able to see a good path forward are invited to join #mobility:fedoraproject.org. kevin

4 7

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 25 Dec '23

25 Dec '23

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2023-12-26 from 16:00:00 to 17:00:00 UTC At fedora-meeting-2(a)irc.libera.chat 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://calendar.fedoraproject.org//meeting/10455/

1 0

DELL Inspiron 14 3420
by aram.minasyan＠yahoo.com 22 Dec '23

22 Dec '23

Dear Fedora Arm I have come into possession of a DELL Inspiron 14 3420 laptop with Qualcomm 8cx Gen 2 soc (sc8180xp) Fedora rawhide boots with acpi, but with limitations, keyboard/trackpad not recognized (I suspect it is related to I2C bus), even the devices on PCIe bus, NVME & Wifi that have drivers don't seem to work. Seems like what is missing is the device tree, which I'm hoping isn't too different from some existing ones under arch/arm64/boot/dts/qcom/sc8180x-lenovo-flex-5g.dts or sc8180x-primus.dts Can the installed Win 11 be used to collect information for construction of DTS? Finally there is an MS Surface pro X DTS on github (https://github.com/linux-surface/surface-pro-x) which could be closer to this since it is an sc8180xp device? Any help in generating a DTS for this device will be greatly appreciated, thanks.

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 18 Dec '23

18 Dec '23

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2023-12-19 from 16:00:00 to 17:00:00 UTC At fedora-meeting-2(a)irc.libera.chat 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://calendar.fedoraproject.org//meeting/10455/

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 11 Dec '23

11 Dec '23

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2023-12-12 from 16:00:00 to 17:00:00 UTC At fedora-meeting-2(a)irc.libera.chat 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://calendar.fedoraproject.org//meeting/10455/

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 04 Dec '23

04 Dec '23

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2023-12-05 from 16:00:00 to 17:00:00 UTC At fedora-meeting-2(a)irc.libera.chat 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://calendar.fedoraproject.org//meeting/10455/

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm December 2023