Re: Nanopi R5S and U-boot from Ports

From: Nenhum_de_Nos <lojas_at_arroway.org>
Date: Tue, 11 Feb 2025 12:12:08 UTC
>
>  Hi,
>
> On Mon, 10 Feb 2025 23:05:01 -0000
> "Nenhum_de_Nos" <lojas@arroway.org> wrote:
>
>> Hi,
>>
>> have anyone ever tested this router and got to have all 3 NIC's?
>>
>> I am trying to use the u-boot r5s package from pkg, as opposed to using
>> edk2 firmware. Using edk2 firmware I get all three NIC's.
>
>  With edk2 you likely booted in acpi-mode while with u-boot you booted
> in fdt mode and if_re-kmod doesn't have fdt attachement.
>
>  Cheers,

Hi Emmanuel,

so there is nothing I can do for now, but wait till the if_re driver to
work on ftd mode?

thanks for the help.

matheus

>> I got to try the u-boot, but I just have the eqos0:
>>
>> root@OPNsense:~ # pciconf -vl
>> pcib1@pci0:0:0:0: class=0x060400 rev=0x01 hdr=0x01 vendor=0x1d87
>> device=0x3566 subvendor=0x0000 subdevice=0x0000
>> vendor = 'Rockchip Electronics Co., Ltd'
>> device = 'RK3568 Remote Signal Processor'
>> class = bridge
>> subclass = PCI-PCI
>> root@OPNsense:~ # cat /boot/loader.conf.local
>> # Realtek kmod R5S - version 1.98
>> if_re_load="YES"
>> if_re_name="/boot/modules/if_re.ko"
>> root@OPNsense:~ # ifconfig
>> eqos0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP>
>> metric 0 mtu 1500
>> description: LAN (lan)
>> options=80008<VLAN_MTU,LINKSTATE>
>> ether xxxxxxxxxxxx
>> inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
>> inet6 fe80::2xxxxxx%eqos0 prefixlen 64 scopeid 0x1
>> media: Ethernet autoselect (1000baseT <full-duplex,master>)
>> status: active
>> nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
>> lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu
>> 16384
>> options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
>> inet 127.0.0.1 netmask 0xff000000
>> inet6 ::1 prefixlen 128
>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
>> groups: lo
>> nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
>> enc0: flags=0 metric 0 mtu 1536
>> options=0
>> groups: enc
>> nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
>> pflog0: flags=20100<PROMISC,PPROMISC> metric 0 mtu 33152
>> options=0
>> groups: pflog
>> pfsync0: flags=0 metric 0 mtu 1500
>> options=0
>> maxupd: 128 defer: off version: 1400
>> syncok: 1
>> groups: pfsync
>>
>> root@OPNsense:~ # kldstat
>> Id Refs Address Size Name
>> 1 29 0xffff000000000000 13d6ba8 kernel
>> 2 1 0xffff0000013d7000 294d8 if_gre.ko
>> 3 1 0xffff000001401000 22f18 pflog.ko
>> 4 3 0xffff000001424000 8f488 pf.ko
>> 5 1 0xffff0000014b5000 2eee8 carp.ko
>> 6 1 0xffff0000014e4000 240f0 if_enc.ko
>> 7 1 0xffff000001509000 2e678 if_bridge.ko
>> 8 2 0xffff000001538000 27470 bridgestp.ko
>> 9 1 0xffff000001560000 31d88 if_lagg.ko
>> 10 2 0xffff000001592000 23460 if_infiniband.ko
>> 11 1 0xffff0000015b6000 305d8 pfsync.ko
>> 12 1 0xffff0000015e7000 a82b0 if_re.ko
>> 13 1 0xffff0000c4a00000 22000 hym8563.ko
>> 14 1 0xffff0000c4a22000 27000 nullfs.ko
>>
>> This is an opnsense for arm64 I built here at home. I use the
>> realtek-re-kmod198.
>>
>> I put some more info on the FreeBSD Forum:
>> https://forums.freebsd.org/threads/nanopi-r5s-and-freebsd-14.88967/
>>
>> thanks,
>>
>> matheus
>>
>>
>
>
> --
> Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
>
>