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
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 foundHit 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
Am 28.03.2023 um 14:09 schrieb Peter Robinson pbrobinson@gmail.com:
Yes, it's a known problem, it will be fixed with the U-Boot rc5 build which should be done later today.
thanks for the info. I just checked, today’s built 20230329 is rc4. looking forward.
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.
Peter
-- 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
"
On Wed, Mar 29, 2023 at 6:18 PM Peter Boy pboy@uni-bremen.de wrote:
Am 28.03.2023 um 14:09 schrieb Peter Robinson pbrobinson@gmail.com:
Yes, it's a known problem, it will be fixed with the U-Boot rc5 build which should be done later today.
thanks for the info. I just checked, today’s built 20230329 is rc4. looking forward.
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.
Peter
On Wed, Mar 29, 2023 at 12:38 PM Peter Robinson pbrobinson@gmail.com wrote:
"
On Wed, Mar 29, 2023 at 6:18 PM Peter Boy pboy@uni-bremen.de wrote:
Am 28.03.2023 um 14:09 schrieb Peter Robinson pbrobinson@gmail.com:
Yes, it's a known problem, it will be fixed with the U-Boot rc5 build which should be done later today.
thanks for the info. I just checked, today’s built 20230329 is rc4.
looking forward.
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 reminds me I should document how I built a Fedora based NAS with 10 drives using a RockPro64. It is not the most performant but suits me
Dennis
Dennis
On Wednesday, 29 March 2023 at 19:42, Dennis Gilmore wrote: [...]
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 reminds me I should document how I built a Fedora based NAS with 10 drives using a RockPro64. It is not the most performant but suits me
Yes, please do that. I'm keeping an eye out for a replacement of my current Atom-based NAS and this could be it. Please include some benchmarks and power consumption info.
Regards, Dominik
Have you tried any HAT's with those systems? I am looking to move away from PI as it is giving me supply chain issues and would like to settle on something a bit more plentiful and not made in China.
On Thu, Mar 30, 2023 at 1:53 PM Dominik 'Rathann' Mierzejewski < dominik@greysector.net> wrote:
On Wednesday, 29 March 2023 at 19:42, Dennis Gilmore wrote: [...]
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 reminds me I should document how I built a Fedora based NAS with 10 drives using a RockPro64. It is not the most performant but suits me
Yes, please do that. I'm keeping an eye out for a replacement of my current Atom-based NAS and this could be it. Please include some benchmarks and power consumption info.
Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan _______________________________________________ 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
On Thu, Mar 30, 2023 at 10:04 PM Gregory Carter gjcarter2@gmail.com wrote:
Have you tried any HAT's with those systems? I am looking to move away from PI as it is giving me supply chain issues and would like to settle on something a bit more plentiful and not made in China.
Pine64, and most things rockchip, are made in China, and Rockchip is a Chinese silicon vendor.
On Thu, Mar 30, 2023 at 1:53 PM Dominik 'Rathann' Mierzejewski dominik@greysector.net wrote:
On Wednesday, 29 March 2023 at 19:42, Dennis Gilmore wrote: [...]
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 reminds me I should document how I built a Fedora based NAS with 10 drives using a RockPro64. It is not the most performant but suits me
Yes, please do that. I'm keeping an eye out for a replacement of my current Atom-based NAS and this could be it. Please include some benchmarks and power consumption info.
Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan _______________________________________________ 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
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
On Thu, Mar 30, 2023 at 9:53 PM Dominik 'Rathann' Mierzejewski dominik@greysector.net wrote:
On Wednesday, 29 March 2023 at 19:42, Dennis Gilmore wrote: [...]
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 reminds me I should document how I built a Fedora based NAS with 10 drives using a RockPro64. It is not the most performant but suits me
Yes, please do that. I'm keeping an eye out for a replacement of my current Atom-based NAS and this could be it. Please include some benchmarks and power consumption info.
Depending on how much of a rush you're in I would look for something based on the rk3568 [1], as it has 3x sata, 2x NIC and 2x pcie options, or the rk3588 series. We don't support them fully as yet, especially the later, but they'll be more performant and will quickly start to replace the venerable rk3399. F-38 should support the rk356x series pretty well outside of the firmware support which still needs improvement.
[1] https://www.cnx-software.com/2020/12/16/rockchip-rk3566-and-rk3568-datasheet...
Am 29.03.2023 um 19:42 schrieb Dennis Gilmore dennis@ausil.us:
On Wed, Mar 29, 2023 at 12:38 PM Peter Robinson pbrobinson@gmail.com wrote:
On Wed, Mar 29, 2023 at 6:18 PM Peter Boy pboy@uni-bremen.de 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?
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/f...
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.
@Dennis Gilmore
It reminds me I should document how I built a Fedora based NAS with 10 drives using a RockPro64. It is not the most performant but suits me
I would appreciate that, too. And just in case that you used Fedora Server, I would like to publish it as part of the Fedora Server documentation (). I can help with the technical part. I'm making an effort to give more consideration to SBCs right now.
Peter
-- 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
Hi,
I'm not sure if it will help, but I had a lot of problems booting Fedora on the PineBook Pro that were solved by switching to tow-boot instead of u-boot. RockPro64 is on their list of supported devices.
https://tow-boot.org/devices/index.html
- Adam
On 3/31/23 11:44 AM, Peter Boy wrote:
Am 29.03.2023 um 19:42 schrieb Dennis Gilmore dennis@ausil.us:
On Wed, Mar 29, 2023 at 12:38 PM Peter Robinson pbrobinson@gmail.com wrote:
On Wed, Mar 29, 2023 at 6:18 PM Peter Boy pboy@uni-bremen.de 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?
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/f...
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.
@Dennis Gilmore
It reminds me I should document how I built a Fedora based NAS with 10 drives using a RockPro64. It is not the most performant but suits me
I would appreciate that, too. And just in case that you used Fedora Server, I would like to publish it as part of the Fedora Server documentation (). I can help with the technical part. I'm making an effort to give more consideration to SBCs right now.
Peter
-- 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
Hi Adam
Am 31.03.2023 um 18:28 schrieb Adam Sher adam@shernet.com:
Hi,
I'm not sure if it will help, but I had a lot of problems booting Fedora on the PineBook Pro that were solved by switching to tow-boot instead of u-boot. RockPro64 is on their list of supported devices.
thanks for the information. The website makes a very good, systematic and trustworthy impression. For Fedora Server Edition we need a way officially supported in Fedora. But I will try tow in any case. I have there discovered a version for Radxa Rockpi4, where the SPI is not supported by Fedora/u-boot so far. At the moment I use a "wild construction" with Armbian. Maybe it works better and more elegant with tow.
Thanks Peter
-- 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
Peter,
Makes total sense. Good luck!
On 3/31/23 2:37 PM, Peter Boy wrote:
Hi Adam
Am 31.03.2023 um 18:28 schrieb Adam Sher adam@shernet.com:
Hi,
I'm not sure if it will help, but I had a lot of problems booting Fedora on the PineBook Pro that were solved by switching to tow-boot instead of u-boot. RockPro64 is on their list of supported devices.
thanks for the information. The website makes a very good, systematic and trustworthy impression. For Fedora Server Edition we need a way officially supported in Fedora. But I will try tow in any case. I have there discovered a version for Radxa Rockpi4, where the SPI is not supported by Fedora/u-boot so far. At the moment I use a "wild construction" with Armbian. Maybe it works better and more elegant with tow.
Thanks Peter
-- 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
On Friday, 31 March 2023 at 18:28, Adam Sher wrote:
Hi,
I'm not sure if it will help, but I had a lot of problems booting Fedora on the PineBook Pro that were solved by switching to tow-boot instead of u-boot. RockPro64 is on their list of supported devices.
Without giving any specifics, that's just not helpful. As a counter-point, I can say that I've had zero problems with booting the PineBook Pro using u-boot image in SPI after following Peter Robinson's blog post: https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/ .
Regards,
On Fri, Mar 31, 2023 at 4:44 PM Peter Boy pboy@uni-bremen.de wrote:
Am 29.03.2023 um 19:42 schrieb Dennis Gilmore dennis@ausil.us:
On Wed, Mar 29, 2023 at 12:38 PM Peter Robinson pbrobinson@gmail.com wrote:
On Wed, Mar 29, 2023 at 6:18 PM Peter Boy pboy@uni-bremen.de 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?
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/f...
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.
@Dennis Gilmore
It reminds me I should document how I built a Fedora based NAS with 10 drives using a RockPro64. It is not the most performant but suits me
I would appreciate that, too. And just in case that you used Fedora Server, I would like to publish it as part of the Fedora Server documentation (). I can help with the technical part. I'm making an effort to give more consideration to SBCs right now.
Peter
-- 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
Am 31.03.2023 um 19:08 schrieb Peter Robinson pbrobinson@gmail.com:
On Fri, Mar 31, 2023 at 4:44 PM Peter Boy pboy@uni-bremen.de wrote:
Am 29.03.2023 um 19:42 schrieb Dennis Gilmore dennis@ausil.us:
On Wed, Mar 29, 2023 at 12:38 PM Peter Robinson pbrobinson@gmail.com wrote:
On Wed, Mar 29, 2023 at 6:18 PM Peter Boy pboy@uni-bremen.de 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/f...
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@fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member Fedora docs team contributor Java developer and enthusiast
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 foundHit 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
Am 03.04.2023 um 00:35 schrieb Peter Robinson pbrobinson@gmail.com:
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:
...
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.
I hope, my question is not too uninitiated. With your link I get uboot-tools-2023.04-0.4.rc5.fc38.x86_64.rpm as far as I can see. But I didn’t (and didn’t need to) install uboot-tools on my x86-64 box to create the Fedora mSD using arm-image-installer so far.
What I’m missing here?
-- 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
On Mon, Apr 3, 2023 at 8:10 AM Peter Boy pboy@uni-bremen.de wrote:
Am 03.04.2023 um 00:35 schrieb Peter Robinson pbrobinson@gmail.com:
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:
...
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.
I hope, my question is not too uninitiated. With your link I get uboot-tools-2023.04-0.4.rc5.fc38.x86_64.rpm as far as I can see. But I didn’t (and didn’t need to) install uboot-tools on my x86-64 box to create the Fedora mSD using arm-image-installer so far.
What I’m missing here?
Nothing. In most cases these days the utilities in uboot-tools are only needed for advanced use.
Am 03.04.2023 um 09:25 schrieb Peter Robinson pbrobinson@gmail.com:
On Mon, Apr 3, 2023 at 8:10 AM Peter Boy pboy@uni-bremen.de wrote:
Am 03.04.2023 um 00:35 schrieb Peter Robinson pbrobinson@gmail.com:
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:
...
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.
I hope, my question is not too uninitiated. With your link I get uboot-tools-2023.04-0.4.rc5.fc38.x86_64.rpm as far as I can see. But I didn’t (and didn’t need to) install uboot-tools on my x86-64 box to create the Fedora mSD using arm-image-installer so far.
What I’m missing here?
Nothing. In most cases these days the utilities in uboot-tools are only needed for advanced use.
OK, but with the currently distributed version (branched 2023-03-31 / u-boot 2023.04-rc4) I still get the message
Hit any key to stop autoboot: 0 ## Error: "distro_bootcmd" not definded
if I remember correctly and didn’t mess my notes and testing procedures.
Will that get fixed with / before F38 release?
-- 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
Nothing. In most cases these days the utilities in uboot-tools are only needed for advanced use.
OK, but with the currently distributed version (branched 2023-03-31 / u-boot 2023.04-rc4) I still get the message
Hit any key to stop autoboot: 0 ## Error: "distro_bootcmd" not definded
if I remember correctly and didn’t mess my notes and testing procedures.
Will that get fixed with / before F38 release?
That is fixed with the rc5 build that's in updates-testing, you need to have uboot-images-armv8-2023.04-0.4.rc5.fc38, you're testing with rc4.
Am 03.04.2023 um 09:53 schrieb Peter Robinson pbrobinson@gmail.com:
Nothing. In most cases these days the utilities in uboot-tools are only needed for advanced use.
OK, but with the currently distributed version (branched 2023-03-31 / u-boot 2023.04-rc4) I still get the message
Hit any key to stop autoboot: 0 ## Error: "distro_bootcmd" not definded
if I remember correctly and didn’t mess my notes and testing procedures.
Will that get fixed with / before F38 release?
That is fixed with the rc5 build that's in updates-testing, you need to have uboot-images-armv8-2023.04-0.4.rc5.fc38, you're testing with rc4.
Well, I’m testing Fedora 38 release (beta / branched). Do you plan to get rc5 into the (initial) release media or will we start with a not-working arm installer in F38? Or what needs to be done to get in into the release media? Do we need testing? karma? …?
-- 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
On Mon, Apr 3, 2023 at 9:10 AM Peter Boy pboy@uni-bremen.de wrote:
Am 03.04.2023 um 09:53 schrieb Peter Robinson pbrobinson@gmail.com:
Nothing. In most cases these days the utilities in uboot-tools are only needed for advanced use.
OK, but with the currently distributed version (branched 2023-03-31 / u-boot 2023.04-rc4) I still get the message
Hit any key to stop autoboot: 0 ## Error: "distro_bootcmd" not definded
if I remember correctly and didn’t mess my notes and testing procedures.
Will that get fixed with / before F38 release?
That is fixed with the rc5 build that's in updates-testing, you need to have uboot-images-armv8-2023.04-0.4.rc5.fc38, you're testing with rc4.
Well, I’m testing Fedora 38 release (beta / branched). Do you plan to get rc5 into the (initial) release media or will we start with a not-working arm installer in F38? Or what needs to be done to get in into the release media? Do we need testing? karma? …?
I asked for karma and testing when I replied linking to the update in this thread.
I've already stated that I intend it to go into stable, which was why I asked for testing. In fact we will ship with the GA release which is due out today or tomorrow, we will request a FE to ensure this lands (which we've done basically every release due to the upstream GA generally landing on freeze day).
Am 03.04.2023 um 10:18 schrieb Peter Robinson pbrobinson@gmail.com:
On Mon, Apr 3, 2023 at 9:10 AM Peter Boy pboy@uni-bremen.de wrote:
Am 03.04.2023 um 09:53 schrieb Peter Robinson pbrobinson@gmail.com:
Nothing. In most cases these days the utilities in uboot-tools are only needed for advanced use.
OK, but with the currently distributed version (branched 2023-03-31 / u-boot 2023.04-rc4) I still get the message
Hit any key to stop autoboot: 0 ## Error: "distro_bootcmd" not definded
if I remember correctly and didn’t mess my notes and testing procedures.
Will that get fixed with / before F38 release?
That is fixed with the rc5 build that's in updates-testing, you need to have uboot-images-armv8-2023.04-0.4.rc5.fc38, you're testing with rc4.
Well, I’m testing Fedora 38 release (beta / branched). Do you plan to get rc5 into the (initial) release media or will we start with a not-working arm installer in F38? Or what needs to be done to get in into the release media? Do we need testing? karma? …?
I asked for karma and testing when I replied linking to the update in this thread.
I've already stated that I intend it to go into stable, which was why I asked for testing. In fact we will ship with the GA release which is due out today or tomorrow, we will request a FE to ensure this lands (which we've done basically every release due to the upstream GA generally landing on freeze day).
Thanks. I’ll use testing as soon as I get my box up and running again
Am 03.04.2023 um 10:10 schrieb Peter Boy pboy@uni-bremen.de:
That is fixed with the rc5 build that's in updates-testing, you need to have uboot-images-armv8-2023.04-0.4.rc5.fc38,
Do yo have a direct link to the rpm? Sorry, for some reason all my searches and links end up with the uboot-tools rpm
-- 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
On Mon, Apr 3, 2023 at 1:01 PM Peter Boy pboy@uni-bremen.de wrote:
Am 03.04.2023 um 10:10 schrieb Peter Boy pboy@uni-bremen.de:
That is fixed with the rc5 build that's in updates-testing, you need to have uboot-images-armv8-2023.04-0.4.rc5.fc38,
Do yo have a direct link to the rpm? Sorry, for some reason all my searches and links end up with the uboot-tools rpm
It's a subpackage of the uboot-tools package so if you go there and look down the list you will find it:
uboot-tools-2023.04-0.4.rc5.fc38 -> https://koji.fedoraproject.org/koji/buildinfo?buildID=2180089
It's in the noarch section
-- 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
Am 03.04.2023 um 14:39 schrieb Peter Robinson pbrobinson@gmail.com:
On Mon, Apr 3, 2023 at 1:01 PM Peter Boy pboy@uni-bremen.de wrote:
Am 03.04.2023 um 10:10 schrieb Peter Boy pboy@uni-bremen.de:
That is fixed with the rc5 build that's in updates-testing, you need to have uboot-images-armv8-2023.04-0.4.rc5.fc38,
Do yo have a direct link to the rpm? Sorry, for some reason all my searches and links end up with the uboot-tools rpm
It's a subpackage of the uboot-tools package so if you go there and look down the list you will find it:
uboot-tools-2023.04-0.4.rc5.fc38 -> https://koji.fedoraproject.org/koji/buildinfo?buildID=2180089
It's in the noarch section
Thanks for the info. I followed every link without success. The Fedora build system is obviously still too much of a labyrinth for me. Anyway, put the devices aside and wait patiently for the next rc.
-- 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
-
Adam Sher -
Dennis Gilmore -
Dominik 'Rathann' Mierzejewski -
Gregory Carter -
Peter Boy -
Peter Robinson