arm February 2024

arm@lists.fedoraproject.org

8 participants
13 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

Update U-Boot on Pinebook Pro ?
by Andreas Reschke 14 Mar '24

14 Mar '24

Hello together, hello Peter, I've on my Pinebook Pro U-Boot 2022.10. Howto: https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/ Does it make sence to update U-Boot to up2date Version from Fedora 39 (uboot-images-armv8-2023-07-3.fc39.noarch) ? Are there any significant changes ? Thanks Andreas

3 9

Arm Meeting today - bugs 2247872 and 2265422 Server image
by Peter Boy 27 Feb '24

27 Feb '24

Unfortunately I can’t attend the meeting today and I didn’t manage to contact David Teigland as discussed last meeting. For bug 2265422 (arm-image-installer) there was an update today, but I couldn’t text yet. Maybe it’s already fixed. Best Peter -- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy(a)fedoraproject.org Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 26 Feb '24

26 Feb '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-02-27 from 16:00:00 to 17:00:00 UTC The meeting will be about: Fedora ARM & AArch64 weekly status meeting. Join us on Matrix at [https://matrix.to/#/#meeting-2:fedoraproject.org](https://matrix.to/#/#meet… through [chat.fedoraproject.org](through chat.fedoraproject.org) More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/10455/

1 0

2024-02-26 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson 23 Feb '24

23 Feb '24

# F40 Blocker Review meeting # Date: 2024-02-26 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for another blocker review meeting. We have 7 proposed blockers and 4 proposed freeze exception for Beta, and 5 proposed blockers for Final. The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. I'll be on vacation on Monday, so Frantisek Zatloukal will be running the meeting, thanks Franta! If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 19 Feb '24

19 Feb '24

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2024-02-20 from 16:00:00 to 17:00:00 UTC The meeting will be about: Fedora ARM & AArch64 weekly status meeting. Join us on Matrix at [https://matrix.to/#/#meeting-2:fedoraproject.org](https://matrix.to/#/#meet… through [chat.fedoraproject.org](through chat.fedoraproject.org) More information available at: [https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org… Source: https://calendar.fedoraproject.org//meeting/10455/

1 0

2024-02-19 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson 16 Feb '24

16 Feb '24

# F40 Blocker Review meeting # Date: 2024-02-19 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for another blocker review meeting. We have 6 proposed blockers and 1 proposed freeze exception for Beta, and 4 proposed blockers for Final. The meeting will be on Matrix, as we're trying to move to more modern systems and the meeting bot is working on Matrix now. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by coremodule＠fedoraproject.org 14 Feb '24

14 Feb '24

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

3 2

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm February 2024