The EDK2 build you use probably contains a wrong / incomplete DTB / FDT. Welcome in the hell called SBCs without official ACPI support. Enjoy your stay!
Best regards, --ext Peter Andersson írta 2025. jan.. 17, P-n 10:12 órakor: > On 2025-01-17 09:25, MIZSEI Zoltán wrote: >> I don't think booting via u-boot supports HDMI, at least I never managed to >> get picture of it. >> >> >> Peter Andersson írta 2025. jan.. 16, Cs-n 23:07 órakor: >>> On 2025-01-16 10:48, Patrick Wildt wrote: >>>> >>>>> On 16. Jan 2025, at 10:38, Peter Andersson <pe...@it-slav.net> wrote: >>>>> >>>>> Hi >>>>> >>>>> I just purchased a NanoPI R5S as it seems supported by OpenBSD but I have >>>>> some issues getting it installed. >>>>> >>>>> After reading the arm maillist archive it seems like some has gotten it >>>>> running and I found https://personalbsd.org/download/UEFI-RK356x/ where a >>>>> ready made image for installation was done. >>>>> >>>>> Steps I have done: >>>>> -Download and flash >>>>> https://personalbsd.org/download/UEFI-RK356x/NANOPI-R5S_EFI.img to a cf >>>>> -Put the cf in my NanoPI R5S and power on >>>>> -Enter set tty fb0 at boot prompt and boot it up >>>>> -The normal OpenBSD install procedure starts using HDMI connected screen >>>>> and USB keyboard and everything looks fine. So I assume OpenBSD is >>>>> installed at the internal emmc drive. >>>>> -When told, I remove the cf and reboot. The screen is totally blank and >>>>> nothing seems to happen. >>>>> >>>>> There is a UART but it seems it needs soldering to get a serial console >>>>> so I would prefer to avoid that. >>>>> >>>>> I would be very happy if anyone could advise me how to get installation >>>>> on the internal disk working. >>>>> >>>>> Thanks >>>>> Peter Andersson >>>>> >>>> I’d recommend using the corresponding image from our U-Boot package >>>> instead of the UEFI one: >>>> https://cdn.openbsd.org/pub/OpenBSD/snapshots/packages/aarch64/u-boot-rk356x-2024.01p0.tgz >>>> >>>> dd to the CF a la dd if=u-boot-rockchip.bin of=/dev/XXXX bs=512 seek=64 >>>> >>>> Cheers, >>>> Patrick >>> Hi >>> >>> >>> Did these steps: >>> -Inserted a sd card in another working OpenBSD box. >>> -wget https://cdn.openbsd.org/pub/OpenBSD/snapshots/arm64/miniroot76.img >>> -doas pkg_add u-boot-rk356x >>> -doas dd if=miniroot76.img of=/dev/rsd1c bs=1m >>> -doas dd >>> if=/usr/local/share/u-boot/nanopi-r5s-rk3568/u-boot-rockchip.bin >>> of=/dev/rsd1c seek=64 >>> -moved the sd card to my nanopi-r5s and turned on power. >>> -No output at all on the HDMI. >>> >>> I think I followed the instructions at: >>> https://ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/INSTALL.arm64 >>> >>> Thanks >>> Peter > Alot of progress as I got it running but I really do not understand why > all the steps is needed for me to get it working. > > -Installed friendlywrt from > https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R5S#Step_3:_Install_image_to_eMMC > -In friendlywrt it is possible to write an image to emmmc from webgui. > Used that to upload and write miniroot76.img > -dd:ed the image from https://personalbsd.org/download/UEFI-RK356x/ > doas dd if=NANOPI-R5S_EFI.img of=/dev/rsd1c > -boot the NanoPI R5S with the sd card > -Got the OpenBSD boot prompt on the HDMI connected monitor and entered > set tty fb0 > -Booted the default bsd.rd > -Started the usual OpenBSD installation using the whole disk sd1 > -When installation was done reboot with SD card > -Do not touch anything > -After a couple of minutes OpenBSD is up and running headless > > > Things I do not understand > -Why I need to write the miniroot76.img to emmc, I could not get it boot > bsd.rd from the sd card. Might have gotten it working using serial > consol. Maybe I spend some more time to try to get serial consol > working later. > -Why 'set tty fb0' does not work when I boot the "production" kernel > instead of the installation bsd.rd. > If I enter 'set tty fb0' after a while I get "init: can't open > /dev/console" and it hangs > > Issues: > -Need to boot from SD card, have not managed to get the bootloader on > the emmc. This is a minor issue. > -I can only se 2 NICs, this is a major issue. For my use case I need 3 > working NICs. > > nano# ifconfig > lo0: flags=2008049<UP,LOOPBACK,RUNNING,MULTICAST,LRO> mtu 32768 > index 4 priority 0 llprio 3 > groups: lo > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > inet 127.0.0.1 netmask 0xff000000 > dwqe0: flags=808843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF4> > mtu 1500 > lladdr ea:d2:78:6e:04:c2 > index 1 priority 0 llprio 3 > groups: egress > media: Ethernet autoselect (1000baseT full-duplex) > status: active > inet 10.1.1.142 netmask 0xffffff00 broadcast 10.1.1.255 > rge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:00:00:00:00:00 > index 2 priority 0 llprio 3 > media: Ethernet autoselect > status: no carrier > enc0: flags=0<> > index 3 priority 0 llprio 3 > groups: enc > status: active > pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33136 > index 5 priority 0 llprio 3 > groups: pflog > > Why does only one rge inteface show up? there is 2. > > Thanks for all help! > Peter -- --Z--
