Fedora on ROCK 5 Model B
by Andreas Reschke
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...
dd this Image on a SD-Card
2)
https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everyth...
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
1 month
Fedora on Rock 5B
by Andreas Reschke
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...
on SD-Card and source from
https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everyth....
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
2 months, 3 weeks
Lenovo Thinkpad X13s Black Screen
by Luke Short
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
2 months, 4 weeks
Arm Minimal Image OS-Build available for testing?
by Patrick Laimböck
Hi,
I have an ODROID-M1 and would like to test those new OS-Build Arm
minimal images that were mentioned in the F40 change proposal. Are they
available somewhere?
Best,
Patrick
3 months, 3 weeks
LVM configuration change issue - urgent
by Peter Boy
We have new additional business for our meeting today.
We had a long discussion about arm-image-installer and various issues with maintaining LVM devices.
As it has now become clear, all this is the result of an unannounced silent change in LVM, which has led to a drastically different behavior of the software.
See https://bugzilla.redhat.com/show_bug.cgi?id=2258764
Obviously with F38 LVM changed from searching all devices with pvs and vgscan to searching just devices listed in /etc/devices/system.devices it it exists. Even worse, the update using dnf upgrade plugin create that directory, but not the file, whereas a new installation also creates the file. This gives us two fundamentally different behaviors of the same release status.
In my opinion, this change would have required a change proposal and also a detailed explanation in the release notes. Unfortunately, that approach has led to considerable unnecessary and wasted extra work for many people.
Anyway, now we have to find a solution. The LVM behavior is apparently controlled by a parameter that currently limits the search for VGs to devices listed in the file in question. I suggest to change the behavior to search on all devices via Change Proposal, and thus restore the behavior of F37 and earlier.
There seems to be an option use_devicesfile in lvm.conf. Details in the bug report above.
--
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
3 months, 3 weeks
The arm-image-installer issue
by Peter Boy
As discussed on the meeting yesterday I filed a bug against lvm.
See https://bugzilla.redhat.com/show_bug.cgi?id=2258764
As to my findings it is an LVM issue, specifically a regression from F37. Arm-image-installer works fine and there is no problem if you install the script on F37.
Please, could someone with a more complete orientation to the Fedora universe than me suggest this bug as a blocker?
--
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
3 months, 3 weeks
