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
2 weeks, 4 days
Details on Raspberry Pi 5 support timelines
by Peter Robinson
Hi Folks,
I finally got some time over the weekend to dig into Fedora on the RPi5.
The TL;DR is that there won't be any way of even basic support
officially for F-40 GA.
For those interested in more details.....
The main pieces missing from the upstream kernel to boot to a login
prompt over serial is appear to be the following:
* The SoC pinctrl driver
* Support in the mmc storage driver for the SoC variant
* Minor bits for the gpio driver
I'm not aware of any efforts to get anything upstream, I've not seen
patches on lists etc.
We have the firmware (bcm/u-boot) pieces in place in Fedora 40 and the
kernel will start to boot and you get serial console output except you
end up at a dracut prompt due to lack of storage.
I am considering doing a Fedora kernel with patches in copr, and
probably a F-40 remix minimal image, to enable minimal boot so other
low level developers can use it as a basis for further investigation
for things like upstream development. I don't have a timeline for this
yet but I suspect late April. At the moment this looks like it'll be
mSD, WiFi, serial console support and not much else. I've not looked
at PCIe, the RP1 chip, or any other peripherals at all.
I'll reply to this thread if/when I have any further updates, feel
free to reference it elsewhere.
Until there's either a kernel or kernel+image unless you can
contribute to upstream kernel pieces there's probably nothing that can
be done like "testing". If you can do kernel and would like to assist
me feel free to reachout outside of this thread.
Peter
1 month, 1 week
2024-03-18 @ ** 16:00 ** UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson
# F40 Blocker Review meeting
# Date: 2024-03-18
# Time: ** 16:00 ** UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[elemen...
Hi folks! It's time for another blocker review meeting. We have 1
proposed freeze exception for Beta, and 10 proposed blockers for Final.
As a reminder, clocks went forward in North America last week, so the
meeting is an hour earlier in UTC than it was before. If you have
changed your clocks forward recently the meeting will be at the same
local time as before, it not it will be earlier.
Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Block...
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.
If you have time today, 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 day and see you tomorrow!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org
https://www.happyassassin.net
1 month, 1 week
Raspberri Pi Zero 2 W fails to boot Fedora 39
by Aleksandar Kostadinov
Hello,
Booting Fedora 39 on Raspberri Pi Zero 2 W freezes after the line "Exiting boot services.."
I setup the card with arm-image-installer-4.1 like:
> sudo arm-image-installer --image=Fedora-Server-39-1.5.aarch64.raw.xz --media=/dev/sda --resizefs --relabel --showboot --sysrq --target=rpi02w
The options `--resizefs --relabel --showboot --sysrq` don't matter, I mean with or without them the system freezes at boot.
And this seems to be a regression because flashing Fedora-Server-37-1.7.aarch64.raw.xz does successfully boot the system /although I can't yet get the setup right to access it with no keyboard access to the device/
Is this a known issue and is there any way to fix that?
Thank you.
1 month, 2 weeks
2024-03-11 @ ** 16:00 ** UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson
# F40 Blocker Review meeting
# Date: 2024-03-11
# Time: ** 16:00 ** UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[elemen...
Hi folks! It's time for another blocker review meeting. We have 2
proposed blockers and 5 proposed freeze exceptions for Beta, and 4
proposed blockers for Final.
Please note that summer time starts in most of North America on Sunday,
and we follow that time for these meetings, so the meeting time in UTC
has changed. If you put your clocks forward this Sunday, the meeting
will be at the same local time as it was last week. If you do not, the
meeting will be one hour *earlier* than it was last week. You can
always run `date -u` to see the current UTC time and check, if you're
not sure. Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Block...
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.
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(a)fosstodon.org
https://www.happyassassin.net
1 month, 2 weeks
