On Tue, Mar 28, 2023 at 1:08 PM Peter Boy <pboy@xxxxxxxxxxxxx> 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. The F-38 build should now be fixed: https://bodhi.fedoraproject.org/updates/FEDORA-2023-8ba62c0e8c If people could test and add karma that would be great. P _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue