>> Hi Matheus,
>>
>> Can you double check that you're saving the UEFI settings after setting
>> "ACPI + DTB"? You need to hit F10 for the changes to stick.
>>
>> I just downloaded and wrote the latest version of the bootloader, forgot
>> to save after setting, and never got network devices during boot.
>>
>> I just want to make sure that you aren't running into this.
>>
>> Cheers!
>
> I got curious to know. Once I pass the install process, I use one USB nic
> and its fine, where the OpenBSD stores this device tree for future boot? I
> get to install, I imagine that if I can find it I can fix it pass install
> and never make them all appear in the final system, which is fine for me.
>
> Thanks,
>
> Matheus
I get to boot, but no ethernet from it. Here the dmesg, should it help:
I use the EFI image for it I got on personalbsd as for the April 23 build.
The April 29 build I cannot get it to boot (stuck in the first kernel load
line and keeps there forever. Tried to set serial stty and no way it got
to boot. It gets to:
>> OpenBSD/arm64 BOOTAA64 1.16
boot>
booting sd0a:/bsd: 10393424+2487312+294968+835560
[784339+91+1207920+723881]=0x1
1ab578
I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
I/TC: Secondary CPU 2 initializing
I/TC: Secondary CPU 2 switching to normal world boot
I/TC: Secondary CPU 3 initializing
I/TC: Secondary CPU 3 switching to normal world boot
And halts).
OpenBSD 7.3 (GENERIC.MP) #2080: Sat Mar 25 14:20:25 MDT 2023
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
real mem = 3984670720 (3800MB)
avail mem = 3785691136 (3610MB)
random: good seed from bootblocks
mainbus0 at root: ACPI
psci0 at mainbus0: PSCI 1.1, SMCCC 1.2, SYSTEM_SUSPEND
cpu0 at mainbus0 mpidr 0: ARM Cortex-A55 r2p0
cpu0: 32KB 64b/line 4-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu0: 512KB 64b/line 16-way L2 cache
cpu0:
DP,RDM,Atomic,CRC32,SHA2,SHA1,AES+PMULL,LRCPC,DPB,ASID16,PAN+ATS1E1,LO,HPDS,HAFDBS
cpu1 at mainbus0 mpidr 100: ARM Cortex-A55 r2p0
cpu1: 32KB 64b/line 4-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu1: 512KB 64b/line 16-way L2 cache
cpu1:
DP,RDM,Atomic,CRC32,SHA2,SHA1,AES+PMULL,LRCPC,DPB,ASID16,PAN+ATS1E1,LO,HPDS,HAFDBS
cpu2 at mainbus0 mpidr 200: ARM Cortex-A55 r2p0
cpu2: 32KB 64b/line 4-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu2: 512KB 64b/line 16-way L2 cache
cpu2:
DP,RDM,Atomic,CRC32,SHA2,SHA1,AES+PMULL,LRCPC,DPB,ASID16,PAN+ATS1E1,LO,HPDS,HAFDBS
cpu3 at mainbus0 mpidr 300: ARM Cortex-A55 r2p0
cpu3: 32KB 64b/line 4-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu3: 512KB 64b/line 16-way L2 cache
cpu3:
DP,RDM,Atomic,CRC32,SHA2,SHA1,AES+PMULL,LRCPC,DPB,ASID16,PAN+ATS1E1,LO,HPDS,HAFDBS
efi0 at mainbus0: UEFI 2.7
efi0: EDK2 rev 0x10000
smbios0 at efi0: SMBIOS 3.3.0
smbios0: vendor EDK2 version "EDK2-DEV" date 04/16/2023
smbios0: FriendlyElec NanoPi-R5S
apm0 at mainbus0
agintc0 at mainbus0 shift 4:4 nirq 352 nredist 4 ipi: 0, 1, 2:
"interrupt-controller"
ampintcmsi0 at agintc0: nspi 24
agtimer0 at mainbus0: 24000 kHz
acpi0 at mainbus0: ACPI 6.0
acpi0: sleep states
acpi0: tables DSDT FACP DBG2 GTDT APIC MCFG SPCR
acpi0: wakeup devices
acpimcfg0 at acpi0
acpimcfg0: addr 0x380008000, bus 1-1
"ACPI0007" at acpi0 not configured
"ACPI0007" at acpi0 not configured
"ACPI0007" at acpi0 not configured
"ACPI0007" at acpi0 not configured
com0 at acpi0 COM0 addr 0xfe660000/0x1000 irq 150: ns16550, no working fifo
com0: console
ohci0 at acpi0 OHC0 addr 0xfd840000/0x40000 irq 163: version 1.0
ehci0 at acpi0 EHC0 addr 0xfd800000/0x40000 irq 162
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Generic EHCI root hub" rev
2.00/1.00 addr 1
ohci1 at acpi0 OHC1 addr 0xfd8c0000/0x40000 irq 166: version 1.0
ehci1 at acpi0 EHC1 addr 0xfd880000/0x40000 irq 165
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Generic EHCI root hub" rev
2.00/1.00 addr 1
xhci0 at acpi0 XHC0 addr 0xfcc00000/0x400000 irq 201, xHCI 1.10
usb2 at xhci0: USB revision 3.0
uhub2 at usb2 configuration 1 interface 0 "Generic xHCI root hub" rev
3.00/1.00 addr 1
xhci1 at acpi0 XHC1 addr 0xfd000000/0x400000 irq 202, xHCI 1.10
usb3 at xhci1: USB revision 3.0
uhub3 at usb3 configuration 1 interface 0 "Generic xHCI root hub" rev
3.00/1.00 addr 1
"PRP0001" at acpi0 not configured
"PRP0001" at acpi0 not configured
"RKCP0D40" at acpi0 not configured
acpipci0 at acpi0 PCI0
pci0 at acpipci0
nvme0 at pci0 dev 0 function 0 vendor "SanDisk", unknown product 0x5009
rev 0x01: msix, NVMe 1.4
nvme0: WDC WDS100T2B0C-00PXH0, firmware 211210WD, serial 211689450612
scsibus0 at nvme0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <NVMe, WDC WDS100T2B0C-, 2112>
sd0: 953869MB, 512 bytes/sector, 1953525168 sectors
acpitz0 at acpi0: critical temperature is 115 degC
acpitz1 at acpi0: critical temperature is 115 degC
usb4 at ohci0: USB revision 1.0
uhub4 at usb4 configuration 1 interface 0 "Generic OHCI root hub" rev
1.00/1.00 addr 1
usb5 at ohci1: USB revision 1.0
uhub5 at usb5 configuration 1 interface 0 "Generic OHCI root hub" rev
1.00/1.00 addr 1
simplefb0 at mainbus0: 1920x1080, 32bpp
wsdisplay0 at simplefb0 mux 1
wsdisplay0: screen 0-5 added (std, vt100 emulation)
axen0 at uhub3 port 2 configuration 1 interface 0 "ASIX Elec. Corp.
AX88179" rev 3.00/1.00 addr 2
axen0: AX88179, address 2c:53:4a:xx:xx:xx
rgephy0 at axen0 phy 3: RTL8169S/8110S/8211 PHY, rev. 5
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on sd0a (31b631ff87307a65.a) swap on sd0b dump on sd0b
>> On April 25, 2023 7:04:15 PM MDT, Nenhum_de_Nos <lo...@arroway.org>
>> wrote:
>>>> I just tested with the NANOPI-R5S_EFI.img on the personalbsd.org and
>>>> it
>>>> definitely works.
>>>
>>>Hi, good to know.
>>>
>>>> Did you make sure to copy the rk3568-nanopi-r5s.dtb into the vendor/
>>>> folder on the miniroot73.img USB drive?
>>>
>>>I used the install73.img, and after dd'ing it to the USB drive I did
>>>create the vendor folder to the FAT volume labeled BOOT. The
>>> installation
>>>couldn't find the sets on the usb drive, I got it to install using a
>>>separate usb ethernet and http for the sets.
>>>
>>>After reading this I tried using miniroot73.img as well. Same result. No
>>>ethernet at all.
>>>
>>>> You may also need to set "AHCI + DTB" under device configuration in
>>>> the
>>>> UEFI config on boot (hit ESC at the prompt). That should allow it to
>>>> use
>>>> the dtb file.
>>>
>>>After reading here I changed, but nothing new.
>>>
>>>> Let me know if you still run into issues after that.
>>>>
>>>> Cheers!
>>>
>>>Thanks,
>>>
>>>matheus
>>>
>>>> On 4/24/23 20:48, Nenhum_de_Nos wrote:
>>>>>> You will need UART. I never soldered a header on the TX/RX/GND --
>>>>>> just
>>>>>> placing a header in the holes seems to do the trick.
>>>>>>
>>>>>> dwqe0 works and rge0 works. I get watchdog timeouts with rge1
>>>>>> though,
>>>>>> but I haven't troubleshot that. Also, the MAC address on rge0 is
>>>>>> null
>>>>>> by
>>>>>> default, so you have to set that before it will function. But I can
>>>>>> confirm both of these NICs work.
>>>>> Hi Andrew,
>>>>>
>>>>> there must be something I am not doing, doing it wrong. I got it
>>>>> installed, but I see no network interfaces at all, only the USB I
>>>>> placed
>>>>> there.
>>>>>
>>>>> Can you send me the diff you told in the first email? I used the img
>>>>> NANOPI-R5S_EFI.img on the sdcard and I can boot OpenBSD fine, just no
>>>>> network interfaces.
>>>>>
>>>>> Thanks for the help,
>>>>>
>>>>> matheus
>>>>>
>>>>>> On 4/24/23 04:09, Nenhum_de_Nos wrote:
>>>>>>>> So I managed to get it booting. There's an open issue here that
>>>>>>>> discusses having NanoPi R5S support added to the
>>>>>>>> bootloader:ÃÂâÂÂÃÂÃÂ
>>>>>>>> https://github.com/jaredmcneill/quartz64_uefi/issues/40.
>>>>>>>>
>>>>>>>> I built the EFI image myself from
>>>>>>>> https://github.com/S199pWa1k9r/quartz64_uefi/tree/nanopi-r5s repo
>>>>>>>> though. If you go that route, there are some modifications you
>>>>>>>> need
>>>>>>>> to
>>>>>>>> make to get it compiling for the NanoPi R5S (email me for a diff
>>>>>>>> if
>>>>>>>> you
>>>>>>>> need). However, the developer also has a pre-built
>>>>>>>> NANOPI-R5S_EFI.img
>>>>>>>> image available here:
>>>>>>>> https://personalbsd.org/download/UEFI-RK356x/.
>>>>>>>> I
>>>>>>>> haven't tried that one, but it's reported to work.
>>>>>>>>
>>>>>>>> I wrote the OpenBSD arm64 miniroot73.img file to a USB drive, and
>>>>>>>> then
>>>>>>>> copied the rk3568-nanopi-r5s.dtb file under the vendors/ directory
>>>>>>>> (as
>>>>>>>> the INSTALL.arm64 guide says). The NanoPi boots the bootloader
>>>>>>>> stored
>>>>>>>> on
>>>>>>>> the microSD card, and then boots the OpenBSD USB drive.
>>>>>>>>
>>>>>>>> Make sure to use 115200 as your baud rate when accessing UART
>>>>>>>> though.ÃÂâÂÂÃÂàI
>>>>>>>> kept using 1500000 (the default according to FriendlyElec docs),
>>>>>>>> and
>>>>>>>> was
>>>>>>>> not getting any output.
>>>>>>>>
>>>>>>>> Cheers!
>>>>>>> Hi Andrew,
>>>>>>>
>>>>>>> thanks for the information. Mine just arrived and I will now try
>>>>>>> it.
>>>>>>> Do
>>>>>>> all the networks interfaces work on OpenBSD 7.3? I need serial
>>>>>>> console
>>>>>>> for
>>>>>>> installation right?
>>>>>>>
>>>>>>> Will begin to work on the serial installation today.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> matheus
>>>>>>>
>>>>>>>> On 4/17/23 02:01, Matheus wrote:
>>>>>>>>> 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."
>>>>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
>
