> Am 31.03.2023 um 19:08 schrieb Peter Robinson <pbrobinson@xxxxxxxxx>: > > On Fri, Mar 31, 2023 at 4:44 PM Peter Boy <pboy@xxxxxxxxxxxxx> wrote: >> >> >> >>> Am 29.03.2023 um 19:42 schrieb Dennis Gilmore <dennis@xxxxxxxx>: >>> >>> >>> >>> On Wed, Mar 29, 2023 at 12:38 PM Peter Robinson <pbrobinson@xxxxxxxxx> wrote: >>> >>> On Wed, Mar 29, 2023 at 6:18 PM Peter Boy <pboy@xxxxxxxxxxxxx> wrote: >>>> >>>> Just another question: How do I get the Fedora spi image onto the device? As I found on the internet, the description at https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/ for the Pinebook doesn’t work for the RockPro64. And indeed, it still does not. In another thread was noted that you are about to update the documentation to describe the process for RockPro64. Unfortunately, I couldn’t find it in my internet researches. >>> >>> The process is the same as the PBP you just have to adjust the names >>> so for example "sudo spi-flashing-disk --target=rockpro64-rk3399 >>> --media=/dev/XXX". I have has reports from a number of people it works >>> just fine. >>> >>> I can confirm that this works just fine. I have 2 RockPro64's running Fedora 37 here and using u-boot on SPI from there. >> >> It did some experimentation and internet search that took its time. >> >> For me, it doesn’t work, unfortunately. >> >> I get: >> >>> U-Boot (2022.10 (Oct 10 2022...) >>> >>> Soc: Rockchiop rk3399 >>> Reset cause: POR >>> Model: Pine64 RockPro64 v2.1 >>> … >>> MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0 >>> Loading Environment from SPIFlash... SF: Detected gd25q128 … >>> *** Warning - bad CRC, using default environment >>> >>> In: serial >>> Out: vidconsole >>> starting USB... >>> .... >>> scanning usb for storage devices...0 found >>> Hit any key to stop autoboot: >>> switch to partitions #0, OK >>> mmc1 is current device >>> Scanning mmc 1:1... >>> Card did not respond to voltage select! : -110 >>> rockship_pcie pcie@f8000000: failed to find ep-gpios property >>> scanning bus for devices.... >>> >>> Device 0: unknown device >>> Device 0: unknown device >>> rockship_pcie pcie@f8000000: failed to find ep-gpios property >>> Speed: 1000, full duplex >>> BOOTP broadcast 1 >>> DHCP client bound to address 192.168.158.150 (6 ms) >>> *** Warning: no boot file name: using 'COA89E98.img‘ >>> … >> >> >> Any idea what I might have missed? > > That is working fine, it's not finding the storage/OS, what are you > trying to boot off, what image are you trying to boot? On a F37 system (fresh install and fully updated as of today) I did: […]# dnf install arm-image-installer uboot-images-armv8 […]# spi-flashing-disk --target=rockpro64-rk3399 —-media=/dev/mmcblk0 (mmcblk0 is the internal card reader of my test system) Then I inserted the mSD card into the RockPro64 and turned power on. That produced the output as listed. > >> I noticed that a booted F37 shows no SPI storage, only mSD mmcblk0. When I boot the Armbian included in the board delivery, lsblk additionally shows a mtd 0, size 16m. >> >> I found an SPI flash at https://github.com/sigmaris/u-boot/releases/download/v2021.04-rockpro64-ci/flash_spi.img.gz >> >> The SPI storage was written with it and the board does boot from it. However, Fedora cannot be booted with it, a lack of an EFI partition is complained about and the file system is not recognized. >> >> Any help appreciated. >> -- Peter Boy https://fedoraproject.org/wiki/User:Pboy pboy@xxxxxxxxxxxxxxxxx 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@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
