On April 17, 2023 8:26:29 AM GMT+02:00, David Gwynne <da...@gwynne.id.au> wrote:
>On Sat, Apr 15, 2023 at 08:14:10AM -0600, Andrew Klaus wrote:
>> I'm trying to figure out as well.
>>
>> I built u-boot from the official R5S build guide:
>>
>http://wiki.friendlyelec.com/wiki/index.php/NanoPi_R5S#Build_u-boot_only
>>
>> I placed the resulting rk3568-nanopi5.dtb file into the vendor/
>folder,
>> after writing the miniroot73.img to the disk. This wasn't enough to
>boot
>> alone, so I followed the other part of the INSTALL.arm64 guide by
>writing
>> idbloader.img and uboot.itb to the SD card. I still can't get to the
>OpenBSD
>> bootloader.
>>
>> I used a UART connection and saw that it does some initialization
>(see
>> below), but doesn't get to u-boot.
>
>The rockchip and vendor u-boots do not provide EFI support, and OpenBSD
>relies on an EFI capable boot environment for the BOOTAA64.EFI loader
>to
>function. Another (simplistic) way to look at it is that u-boot
>does not support OpenBSD disklabels and filesystems, so it can't
>read and load the kernel. The openbsd boot loader does understand
>openbsd disks, and uses EFI services to read and load the kernel.
>
>mainline u-boot has almost got enough rk3568 support that it can
>be used on these systems. You could say the same about
>https://github.com/jaredmcneill/quartz64_uefi. In both cases they need
>config added to support the nanopi r5s specifically.
>
>Once you do have a working boot environment, you'll need to prepare
>media to install with. That's still very DIY, especially compared to
>systems where OpenBSD support is more mature. OpenBSD itself is
>still rough on these devices. It might work fine, but I also wouldn't
>be surprised if you have trouble.
>
>If you want some dmesg pr0n, this is the best I can do. My nanopi
>isn't plugged in at the moment, so this is from a while ago.
>
> OpenBSD 7.3-current (GENERIC.MP) #169: Wed Mar 29 16:35:40 AEST 2023
>d...@o1000.eait.uq.edu.au:/home/dlg/src/sys/arch/arm64/compile/GENERIC.MP
>real mem = 2143797248 (2044MB)
>avail mem = 2043351040 (1948MB)
>random: good seed from bootblocks
>mainbus0 at root: FriendlyElec NanoPi R5S
Hi David,
I see here the R5S name.
>rge0 at pci1 dev 0 function 0 "Realtek RTL8125" rev 0x05: msi, address
>00:00:00:00:00:00
>pci2 at dwpcie1
>ppb1 at pci2 dev 0 function 0 "Rockchip RK3566" rev 0x00
>pci3 at ppb1 bus 1
>rge1 at pci3 dev 0 function 0 "Realtek RTL8125" rev 0x05: msi, address
>00:00:00:00:00:00
>dwpcie2: can't initialize hardware
>scsibus0 at sdmmc0: 2 targets, initiator 0
>sd0 at scsibus0 targ 1 lun 0: <SD/MMC, SC16G, 0080> removable
>sd0: 15193MB, 512 bytes/sector, 31116288 sectors
>ure0 at uhub1 port 2 configuration 1 interface 0 "Realtek USB
>10/100/1G/2.5G LAN" rev 3.20/31.00 addr 2
>ure0: RTL8156B (0x7410), address a0:ce:c8:f7:94:72
>uhub4: device problem, disabling port 1
>vscsi0 at root
>scsibus1 at vscsi0: 256 targets
>softraid0 at root
>scsibus2 at softraid0: 256 targets
>root on sd0a (cfa631a8cbbccf24.a) swap on sd0b dump on sd0b
>rkdrm0: no display interface ports configured
And the ethernet devices show as two as gigabit and one as 2.5Gbps. Is this R5S
a regular one?
Thanks,
Matheus
---
"We will call you Cygnus,
the God of balance you shall be."
