[fedora-arm] Re: RK3568 + Panfrost needs clk-scmi.ko on F40 Live iso

Hi Peter,

Thank you for your feedback. Comments inline.

On 30-07-2024 15:30, Peter Robinson wrote:
> Hi.
>
>> I'm installing F40 on an Odroid M1 (RK3568) NVMe. After writing
>> Fedora-Workstation-Live-osb-40-1.14.aarch64.iso [0] to an eMMC card and
>> booting it I see lots of:
>>
>> [ 69.233581] panfrost fde60000.gpu: get clock failed -517
>>
>> [ 69.233617] panfrost fde60000.gpu: clk init failed -517
>>
>> On RK3568 the Panfrost driver needs the clk-scmi kernel module to be
>> loaded to be functional. Where to report this?
>
> We build that driver in, if you run "modinfo clk-scmi" you should get
> the following:
>
> name: clk_scmi
> filename: (builtin)
> license: GPL v2
> file: drivers/clk/clk-scmi
> description: ARM SCMI clock driver
> author: Sudeep Holla <sudeep.holla@arm.com>

I don't see that:

$ grep CLK_SCMI /boot/config-6.9.10-200.fc40.aarch64
CONFIG_COMMON_CLK_SCMI=m

$ modinfo clk-scmi
filename:
/lib/modules/6.9.10-200.fc40.aarch64/kernel/drivers/clk/clk-scmi.ko.xz
license: GPL v2
description: ARM SCMI clock driver
author: Sudeep Holla <sudeep.holla@arm.com>
depends:
intree: Y
name: clk_scmi
vermagic: 6.9.10-200.fc40.aarch64 SMP preempt mod_unload aarch64
sig_id: PKCS#7
signer: Fedora kernel signing key
sig_key: 1A:CA:3B:BF:6E:5C:47:0B:D0:FC:24:2A:F9:91:07:D6:8A:7A:3A:F4
sig_hashalgo: sha256
signature: [snip]

>> FWIW: when F40 Live is booted, it says "PRE-RELEASE/TESTING" in the top
>> right corner and there are no options to select packages nor add a repo
>> with updates (IIRC this was possible with F40 Live x86_64?)
>
> For live images you can not select packages, it's basically dd:ing the
> live image to disk, you can do that post install.

Got it, thanks.

> The pre-release is due to the artiefact you're using being done by
> os-build, it was a bug, it is the GA release.

Ditto.

>> At the end the installer reports an error that it could not remove
>> something old EFI related, that the system would not be bootable and
>> that it's due to a bug. After finishing the installation, U-boot could
>> not find/boot Fedora on the NVMe. So it's a known issue but is there a fix?
>
> What firmware are you using? It's because the firmware doesn't support
> EFI set variable, it will still boot but use the EFI fallback method.
> It doesn't make much difference except for that one error.

IIRC the issue was with installing with the F40 Server netinst image.
The F40 Workstation image had the same message but did boot.

I built u-boot from 20240721 git 5024a96 for the Odroid M1. Copr here:
https://copr.fedorainfracloud.org/coprs/patrickl/u-boot-rockchip/

FWIW, the u-boot built with BL31 (for rk3568) from
arm-trusted-firmware-arm8 hung after loading BL31 so I reverted to using
BL31 from rkbin which booted fine.

Best,
Patrick
--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue