Yes, it's a known problem, it will be fixed with the U-Boot rc5 build which should be done later today.
Peter
On Tue, Mar 28, 2023 at 1:08 PM Peter Boy pboy@uni-bremen.de wrote:
Fedora 37 aarch64 Server edition works just fine.
With F38 beta 1 & branched 20230326 it starts:
U-Boot 2023.04-rc2 (Feb 17 2023) SoC: Rockchip rk 3399 Reset cause: POR Model: Pine64 RockPro64 v2.1 ... Core: 394 devices, 33 uclasses, devicetree: separate MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0 Loading environment from SPIFlash... SF: Detected .... total 16 MiB *** Warning - bad CRC, using default evironment .... In: serial ...
scanning usb for storage devices... 0 Storage Devices found
Hit any key to stop autoboot: 0 ## Error: "distro_bootcmd" not definded =>
With F37 the first part is the same: but at the end
scanning for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 2 - 1 - 0 switch to partitions #0, OK mmc1 us current device Scanning mmc 1:1 … …
and continues to boot.
Sorry to be so late with testing. Would be nice to get it work, nevertheless.
-- Peter Boy https://fedoraproject.org/wiki/User:Pboy pboy@fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member Fedora docs team contributor Java developer and enthusiast
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