brucerry
January 5, 2026, 7:43am
1
Linux 6.18
A r4lite device plugged with a RTL8125 (PCIe Ethernet) module via PCIe slot CN13.
The R8169 Linux driver is installed. It supports to drive the RTL8125 firmware. In case of BPI-R4 (not Lite), I have configured and confirmed the RTL8125 operations.
CONFIG_R8169=y
For BPI-R4Lite, the R8169 driver probed fail with PHY ID 0x00000000 . Thus, the RTL8125 Ethernet does not work.
I am not sure if the issue is related to the MT7987 / DTS setup.
Could any experts help resolving this?
Debug log:
root@bpi-r4:/# dmesg | grep -i -e 8169 -e 8125
[ 1.753964] pci 0000:01:00.0: [10ec:8125] type 00 class 0x020000 PCIe Endpoint
[ 2.465771] r8169 0000:01:00.0: vgaarb: pci_notify
[ 2.470585] r8169 0000:01:00.0: assign IRQ: got 82
[ 2.475413] r8169 0000:01:00.0: enabling device (0000 -> 0003)
[ 2.481255] r8169 0000:01:00.0: enabling Mem-Wr-Inval
[ 2.787690] r8169 0000:01:00.0: no dedicated PHY driver found for PHY ID 0x00000000, maybe realtek.ko needs to be added to initramfs?
[ 2.799697] r8169 0000:01:00.0: probe with driver r8169 failed with error -49
[ 2.806835] r8169 0000:01:00.0: vgaarb: pci_notify
root@bpi-r4:/#
root@bpi-r4:/# lspci
00:00.0 PCI bridge: MEDIATEK Corp. Device 7987 (rev 01)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
root@bpi-r4:/#
root@bpi-r4:/# cat /proc/bus/pci/devices
0000 14c37987 53 20300004 0 0 0 0 0 0 8000 0 0 0 0 0 0 pcieport
0100 10ec8125 52 1001 0 20200004 0 20220004 0 20210000 100 0 10000 0 4000 0 10000
root@bpi-r4:/#
The error message comes from: BPI-Router-Linux/drivers/net/ethernet/realtek/r8169_main.c at 6.18-main · frank-w/BPI-Router-Linux (same as official Linux 6.18 code)
More logs can be traced:
[ 2.460607] pcieport 0000:00:00.0: vgaarb: pci_notify
[ 2.465771] r8169 0000:01:00.0: vgaarb: pci_notify
[ 2.470585] r8169 0000:01:00.0: assign IRQ: got 82
[ 2.475413] r8169 0000:01:00.0: enabling device (0000 -> 0003)
[ 2.476538] usb 1-1: new high-speed USB device number 2 using xhci-mtk
[ 2.481255] r8169 0000:01:00.0: enabling Mem-Wr-Inval
[ 2.506734] mtk-pcie-gen3 11280000.pcie: msi#0x1 address_hi 0x0 address_lo 0x11280c00 data 1
[ 2.515755] ------------[ cut here ]------------
[ 2.520363] WARNING: CPU: 2 PID: 45 at kernel/module/kmod.c:143 __request_module+0x1b8/0x220
[ 2.528796] Modules linked in:
[ 2.531846] CPU: 2 UID: 0 PID: 45 Comm: kworker/u16:3 Not tainted 6.18.0-bpi-r4-main #1 NONE
[ 2.540356] Hardware name: Bananapi BPI-R4-LITE (DT)
[ 2.545308] Workqueue: async async_run_entry_fn
[ 2.549832] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 2.556781] pc : __request_module+0x1b8/0x220
[ 2.561126] lr : __request_module+0x1b4/0x220
[ 2.565471] sp : ffffffc0822234e0
[ 2.568773] x29: ffffffc082223560 x28: ffffff8002543000 x27: ffffff800255d0c8
[ 2.575899] x26: ffffffc081237ae0 x25: ffffff800255d0c8 x24: 0000000000000000
[ 2.583023] x23: ffffff8002543000 x22: ffffffc080932b4c x21: 0000000000000001
[ 2.590148] x20: 0000000000000000 x19: ffffffc08122eda8 x18: 00000000ffffffff
[ 2.597272] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
[ 2.604397] x14: 0000000000000001 x13: 0000000000000000 x12: 0000000000000000
[ 2.611521] x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000
[ 2.618646] x8 : ffffff8000ef6180 x7 : 0000000000000000 x6 : 0000000000000000
[ 2.625770] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
[ 2.632894] x2 : 0000000000000000 x1 : ffffffc08008a980 x0 : 0000000000000001
[ 2.640019] Call trace:
[ 2.642455] __request_module+0x1b8/0x220 (P)
[ 2.646802] phy_request_driver_module+0x11c/0x17c
[ 2.648333] hub 1-1:1.0: USB hub found
[ 2.651587] phy_device_create+0x230/0x25c
[ 2.655418] hub 1-1:1.0: 4 ports detected
[ 2.659405] get_phy_device+0x78/0x154
[ 2.659411] mdiobus_scan+0x34/0x118
[ 2.670704] __mdiobus_register+0x204/0x450
[ 2.674877] __devm_mdiobus_register+0x70/0xe8
[ 2.679310] rtl_init_one+0x84c/0x1020
[ 2.683051] pci_device_probe+0x9c/0x140
[ 2.686966] really_probe+0xc0/0x390
[ 2.690533] __driver_probe_device+0x7c/0x15c
[ 2.694879] driver_probe_device+0x3c/0x110
[ 2.699051] __device_attach_driver+0xbc/0x158
[ 2.703484] bus_for_each_drv+0x84/0xe4
[ 2.707309] __device_attach+0xa0/0x1b4
[ 2.711135] device_initial_probe+0x14/0x20
[ 2.715307] pci_bus_add_device+0x90/0x148
[ 2.719394] pci_bus_add_devices+0x3c/0x88
[ 2.723480] pci_bus_add_devices+0x68/0x88
[ 2.727566] pci_host_probe+0x90/0x108
[ 2.731306] mtk_pcie_probe+0x2a4/0x444
[ 2.735133] platform_probe+0x5c/0x9c
[ 2.738787] really_probe+0xc0/0x390
[ 2.742353] __driver_probe_device+0x7c/0x15c
[ 2.746699] driver_probe_device+0x3c/0x110
[ 2.750871] __device_attach_driver+0xbc/0x158
[ 2.755304] bus_for_each_drv+0x84/0xe4
[ 2.759129] __device_attach_async_helper+0xb4/0x110
[ 2.764083] async_run_entry_fn+0x38/0x1a8
[ 2.768170] process_one_work+0x164/0x3ac
[ 2.772173] worker_thread+0x284/0x46c
[ 2.775913] kthread+0x114/0x1c8
[ 2.779132] ret_from_fork+0x10/0x20
[ 2.782701] ---[ end trace 0000000000000000 ]---
[ 2.787690] r8169 0000:01:00.0: no dedicated PHY driver found for PHY ID 0x00000000, maybe realtek.ko needs to be added to initramfs?
[ 2.799697] r8169 0000:01:00.0: probe with driver r8169 failed with error -49
[ 2.806835] r8169 0000:01:00.0: vgaarb: pci_notify
frank-w
January 5, 2026, 8:05am
2
Pcie is probed really early. Maybe you need to make the realtek phy driver also builtin including firmware blob
https://forums.gentoo.org/viewtopic-p-8801241.html?sid=c000ab276090eb125e0396823d42268b#8801241
But do both builtin…
brucerry
January 5, 2026, 10:35am
3
Do you mean to download the corresponding RTL8125 firmware and build it in like the link said “rtl_nic/rtl8125b-2.fw”?
If so, do you have experience on adding firmware blob?
In BPI-R4 (MT7988), we do not need to do such things manually.
frank-w
January 5, 2026, 11:19am
4
The bpi-r4 from my repo does this for mt7988/87 and r3mini phy to be loaded from utils/firmware directory,just copy it there and extend the option in defconfig
Get it from here and add it to the dir in my repo
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtl_nic
brucerry
January 6, 2026, 6:38am
5
Thanks a lot.
I have added rtl_nic firmware in utils/firmware and extended CONFIG_EXTRA_FIRMWARE in defconfig:
ubuntu@c40702609f18:~/BPI-Router-Linux$ ls utils/firmware/rtl_nic/
rtl8105e-1.fw rtl8107e-2.fw rtl8125bp-2.fw rtl8126a-2.fw rtl8153a-3.fw rtl8156a-2.fw rtl8168e-1.fw rtl8168f-2.fw rtl8168g-3.fw rtl8411-1.fw
rtl8106e-1.fw rtl8125a-3.fw rtl8125d-1.fw rtl8126a-3.fw rtl8153a-4.fw rtl8156b-2.fw rtl8168e-2.fw rtl8168fp-3.fw rtl8168h-1.fw rtl8411-2.fw
rtl8106e-2.fw rtl8125b-1.fw rtl8125d-2.fw rtl8127a-1.fw rtl8153b-2.fw rtl8168d-1.fw rtl8168e-3.fw rtl8168g-1.fw rtl8168h-2.fw rtl9151a-1.fw
rtl8107e-1.fw rtl8125b-2.fw rtl8125k-1.fw rtl8153a-2.fw rtl8153c-1.fw rtl8168d-2.fw rtl8168f-1.fw rtl8168g-2.fw rtl8402-1.fw
ubuntu@c40702609f18:~/BPI-Router-Linux$
ubuntu@c40702609f18:~/BPI-Router-Linux$ ack EXTRA_FIRMWARE arch/arm64/configs/mt7988a_bpi-r4_defconfig
CONFIG_EXTRA_FIRMWARE="aeonsemi/as21x1x_fw.bin mediatek/mt7987/i2p5ge-phy-DSPBitTb.bin mediatek/mt7987/i2p5ge-phy-pmb.bin rtl_nic/rtl8105e-1.fw rtl_nic/rtl8106e-1.fw rtl_nic/rtl8106e-2.fw rtl_nic/rtl8107e-1.fw rtl_nic/rtl8107e-2.fw rtl_nic/rtl8125a-3.fw rtl_nic/rtl8125b-1.fw rtl_nic/rtl8125b-2.fw rtl_nic/rtl8125bp-2.fw rtl_nic/rtl8125d-1.fw rtl_nic/rtl8125d-2.fw rtl_nic/rtl8125k-1.fw rtl_nic/rtl8126a-2.fw rtl_nic/rtl8126a-3.fw rtl_nic/rtl8127a-1.fw rtl_nic/rtl8153a-2.fw rtl_nic/rtl8153a-3.fw rtl_nic/rtl8153a-4.fw rtl_nic/rtl8153b-2.fw rtl_nic/rtl8153c-1.fw rtl_nic/rtl8156a-2.fw rtl_nic/rtl8156b-2.fw rtl_nic/rtl8168d-1.fw rtl_nic/rtl8168d-2.fw rtl_nic/rtl8168e-1.fw rtl_nic/rtl8168e-2.fw rtl_nic/rtl8168e-3.fw rtl_nic/rtl8168f-1.fw rtl_nic/rtl8168f-2.fw rtl_nic/rtl8168fp-3.fw rtl_nic/rtl8168g-1.fw rtl_nic/rtl8168g-2.fw rtl_nic/rtl8168g-3.fw rtl_nic/rtl8168h-1.fw rtl_nic/rtl8168h-2.fw rtl_nic/rtl8402-1.fw rtl_nic/rtl8411-1.fw rtl_nic/rtl8411-2.fw rtl_nic/rtl9151a-1.fw"
CONFIG_EXTRA_FIRMWARE_DIR="utils/firmware/"
ubuntu@c40702609f18:~/BPI-Router-Linux$
Flashed to r4lite and checked in system:
root@bpi-r4:/# zcat proc/config.gz | grep EXTRA_FIRMWARE
CONFIG_EXTRA_FIRMWARE="aeonsemi/as21x1x_fw.bin mediatek/mt7987/i2p5ge-phy-DSPBitTb.bin mediatek/mt7987/i2p5ge-phy-pmb.bin rtl_nic/rtl8105e-1.fw rtl_nic/rtl8106e-1.fw rtl_nic/rtl8106e-2.fw rtl_nic/rtl8107e-1.fw rtl_nic/rtl8107e-2.fw rtl_nic/rtl8125a-3.fw rtl_nic/rtl8125b-1.fw rtl_nic/rtl8125b-2.fw rtl_nic/rtl8125bp-2.fw rtl_nic/rtl8125d-1.fw rtl_nic/rtl8125d-2.fw rtl_nic/rtl8125k-1.fw rtl_nic/rtl8126a-2.fw rtl_nic/rtl8126a-3.fw rtl_nic/rtl8127a-1.fw rtl_nic/rtl8153a-2.fw rtl_nic/rtl8153a-3.fw rtl_nic/rtl8153a-4.fw rtl_nic/rtl8153b-2.fw rtl_nic/rtl8153c-1.fw rtl_nic/rtl8156a-2.fw rtl_nic/rtl8156b-2.fw rtl_nic/rtl8168d-1.fw rtl_nic/rtl8168d-2.fw rtl_nic/rtl8168e-1.fw rtl_nic/rtl8168e-2.fw rtl_nic/rtl8168e-3.fw rtl_nic/rtl8168f-1.fw rtl_nic/rtl8168f-2.fw rtl_nic/rtl8168fp-3.fw rtl_nic/rtl8168g-1.fw rtl_nic/rtl8168g-2.fw rtl_nic/rtl8168g-3.fw rtl_nic/rtl8168h-1.fw rtl_nic/rtl8168h-2.fw rtl_nic/rtl8402-1.fw rtl_nic/rtl8411-1.fw rtl_nic/rtl8411-2.fw rtl_nic/rtl9151a-1.fw"
CONFIG_EXTRA_FIRMWARE_DIR="utils/firmware/"
root@bpi-r4:/#
However, there is no rtl_nic or related firmware installed in device:
root@bpi-r4:/# ll /lib/firmware/
total 32
drwxr-xr-x 5 root root 4096 Jan 6 2026 ./
drwxr-xr-x 42 root root 4096 Jan 6 2026 ../
drwxr-xr-x 2 root root 4096 Jan 6 2026 aeonsemi/
drwxr-xr-x 2 root root 4096 Jan 6 2026 airoha/
drwxr-xr-x 15 root root 4096 Jan 6 2026 mediatek/
lrwxrwxrwx 1 root root 31 Jan 6 2026 regulatory.db -> /etc/alternatives/regulatory.db
-rw-r--r-- 1 root root 4896 Jan 6 2026 regulatory.db-git
lrwxrwxrwx 1 root root 35 Jan 6 2026 regulatory.db.p7s -> /etc/alternatives/regulatory.db.p7s
-rw-r--r-- 1 root root 1182 Jan 6 2026 regulatory.db.p7s-git
root@bpi-r4:/#
root@bpi-r4:/# find -type d -name *rtl_nic*
root@bpi-r4:/#
root@bpi-r4:/# find -name *8125*
root@bpi-r4:/#
How to ensure the extra firmware images are installed to device?
And the r4 (mt7988) does not have the same error as r4lite (mt7987). Both of them have no rtl_nic firmware loaded. Is the PHY setup of r4lite different to r4?
[ 2.800015] r8169 0000:01:00.0: no dedicated PHY driver found for PHY ID 0x00000000, maybe realtek.ko needs to be added to initramfs?
[ 2.812024] r8169 0000:01:00.0: probe with driver r8169 failed with error -49
frank-w
January 6, 2026, 7:04am
6
It is builtin in kernel,not image…i guess image is too late because filesystem is not yet mounted when cie is probed. But your config.gz shows the firmware is there…else build would have fail.
So is the driver builtin too? What does dmesg now say about phy? If the new rtl driver is also loaded maybe it prints the firmware version
Do you have the realtek card in both devices? R4 lite has both pcie lanes mapped to the first mpcie slot per default because of the be14 card. You can split pcie lanes to both slots with overlay. But have bot tested this completely…only have be14 card in the r4lite.
brucerry
January 6, 2026, 9:06am
7
Both R4 and R4Lite devices have tested with the same RTL8125 NIC module. They are just enabled “CONFIG_R8169=y” driver in Linux. No “rtl_nic” firmware needed to add manually.
R4: RTL8125 operated and at least pingable with peer devices. (I tested 2 months ago in this thread: [RESOLVED] Support PCIe Ethernet RTL8125 - #12 by brucerry )
R4Lite: no dedicated PHY driver found for PHY ID 0x00000000.
root@bpi-r4:/# dmesg | grep -e PHY -e mdio -e 8125 -e 8169
[ 1.412643] MediaTek MT7987 2.5GbE PHY mdio-bus:0f: Firmware date code: 2025/8/22, version: 7.10
[ 1.432948] MediaTek MT7987 2.5GbE PHY mdio-bus:0f: Firmware loading/trigger ok.
[ 1.440388] MediaTek MT7987 2.5GbE PHY mdio-bus:0f: DEBUG: mt7987 detected!
[ 1.736128] mt7530-mdio mdio-bus:1f: no interrupt support
[ 1.768091] pci 0000:01:00.0: [10ec:8125] type 00 class 0x020000 PCIe Endpoint
[ 1.846919] mt7530-mdio mdio-bus:1f: configuring for fixed/2500base-x link mode
[ 1.861023] mt7530-mdio mdio-bus:1f: Link is Up - 2.5Gbps/Full - flow control rx/tx
[ 1.862572] mt7530-mdio mdio-bus:1f lan0 (uninitialized): PHY [mt7530-0:00] driver [Generic PHY] (irq=POLL)
[ 1.868642] mt7530-mdio mdio-bus:1f lan1 (uninitialized): PHY [mt7530-0:01] driver [Generic PHY] (irq=POLL)
[ 1.874774] mt7530-mdio mdio-bus:1f lan2 (uninitialized): PHY [mt7530-0:02] driver [Generic PHY] (irq=POLL)
[ 1.894651] mt7530-mdio mdio-bus:1f lan3 (uninitialized): PHY [mt7530-0:03] driver [Generic PHY] (irq=POLL)
[ 2.490008] r8169 0000:01:00.0: vgaarb: pci_notify
[ 2.494819] r8169 0000:01:00.0: assign IRQ: got 82
[ 2.499660] r8169 0000:01:00.0: enabling device (0000 -> 0003)
[ 2.505497] r8169 0000:01:00.0: enabling Mem-Wr-Inval
[ 2.610117] x20: 0000000000000000 x19: ffffffc081257350 x18: 00000000ffffffff
[ 2.679386] mdiobus_scan+0x34/0x118
[ 2.682951] __mdiobus_register+0x204/0x450
[ 2.687123] __devm_mdiobus_register+0x70/0xe8
[ 2.799888] r8169 0000:01:00.0: no dedicated PHY driver found for PHY ID 0x00000000, maybe realtek.ko needs to be added to initramfs?
[ 2.811939] r8169 0000:01:00.0: probe with driver r8169 failed with error -49
[ 2.819081] r8169 0000:01:00.0: vgaarb: pci_notify
[ 2.981258] /sbin/init
[ 8.713301] mt7530-mdio mdio-bus:1f lan0: entered allmulticast mode
[ 8.715679] mt7530-mdio mdio-bus:1f lan0: entered promiscuous mode
[ 8.719115] mt7530-mdio mdio-bus:1f lan1: entered allmulticast mode
[ 8.720593] mt7530-mdio mdio-bus:1f lan1: entered promiscuous mode
[ 8.723820] mt7530-mdio mdio-bus:1f lan2: entered allmulticast mode
[ 8.725279] mt7530-mdio mdio-bus:1f lan2: entered promiscuous mode
[ 8.728269] mt7530-mdio mdio-bus:1f lan3: entered allmulticast mode
[ 8.729884] mt7530-mdio mdio-bus:1f lan3: entered promiscuous mode
[ 8.790817] mt7530-mdio mdio-bus:1f lan0: configuring for phy/gmii link mode
[ 8.794659] mt7530-mdio mdio-bus:1f lan1: configuring for phy/gmii link mode
[ 8.798875] mt7530-mdio mdio-bus:1f lan2: configuring for phy/gmii link mode
[ 8.803051] mt7530-mdio mdio-bus:1f lan3: configuring for phy/gmii link mode
root@bpi-r4:/#
root@bpi-r4:/# zcat proc/config.gz | grep EXTRA_FIRMWARE
CONFIG_EXTRA_FIRMWARE="aeonsemi/as21x1x_fw.bin mediatek/mt7987/i2p5ge-phy-DSPBitTb.bin mediatek/mt7987/i2p5ge-phy-pmb.bin rtl_nic/rtl8105e-1.fw rtl_nic/rtl8106e-1.fw rtl_nic/rtl8106e-2.fw rtl_nic/rtl8107e-1.fw rtl_nic/rtl8107e-2.fw rtl_nic/rtl8125a-3.fw rtl_nic/rtl8125b-1.fw rtl_nic/rtl8125b-2.fw rtl_nic/rtl8125bp-2.fw rtl_nic/rtl8125d-1.fw rtl_nic/rtl8125d-2.fw rtl_nic/rtl8125k-1.fw rtl_nic/rtl8126a-2.fw rtl_nic/rtl8126a-3.fw rtl_nic/rtl8127a-1.fw rtl_nic/rtl8153a-2.fw rtl_nic/rtl8153a-3.fw rtl_nic/rtl8153a-4.fw rtl_nic/rtl8153b-2.fw rtl_nic/rtl8153c-1.fw rtl_nic/rtl8156a-2.fw rtl_nic/rtl8156b-2.fw rtl_nic/rtl8168d-1.fw rtl_nic/rtl8168d-2.fw rtl_nic/rtl8168e-1.fw rtl_nic/rtl8168e-2.fw rtl_nic/rtl8168e-3.fw rtl_nic/rtl8168f-1.fw rtl_nic/rtl8168f-2.fw rtl_nic/rtl8168fp-3.fw rtl_nic/rtl8168g-1.fw rtl_nic/rtl8168g-2.fw rtl_nic/rtl8168g-3.fw rtl_nic/rtl8168h-1.fw rtl_nic/rtl8168h-2.fw rtl_nic/rtl8402-1.fw rtl_nic/rtl8411-1.fw rtl_nic/rtl8411-2.fw rtl_nic/rtl9151a-1.fw"
CONFIG_EXTRA_FIRMWARE_DIR="utils/firmware/"
root@bpi-r4:/#
frank-w
January 6, 2026, 9:23am
8
If same kernel works with r4 you can try applying the overlay for splitting pcie lanes
Ignore name of variable it is just to add another overlay
wificfg=#ov-lite-2pcie1l
In your uEnv.txt on BPI-BOOT partition (no reflash of card,just edit txt file). Then boot this card and look just before linux starts if the overlay is correctly applied.
I do not know these cards only read about firmware so wanted to be sure it is not the issue…if you have it working you can drop your changes regarding firmware. You have driver enabled for the phy?
brucerry
January 6, 2026, 9:47am
9
frank-w:
If same kernel works with r4 you can try applying the overlay for splitting pcie lanes
Ignore name of variable it is just to add another overlay
wificfg=#ov-lite-2pcie1l
In your uEnv.txt on BPI-BOOT partition (no reflash of card,just edit txt file). Then boot this card and look just before linux starts if the overlay is correctly applied.
I guess the way to edit uEnv.txt you meant is to insert the SD card in PC, but I’m playing with eMMC instead, not installing the Ubuntu firmware in SD.
How to test “splitting PCIe lanes” with eMMC based on your recommendation?
In arch/arm64/configs/mt7988a_bpi-r4_defconfig
CONFIG_R8169=y
CONFIG_R8169_LEDS=y
No other changes needed for operating RTL8125 in R4.
frank-w
January 6, 2026, 10:01am
10
brucerry:
I guess the way to edit uEnv.txt you meant is to insert the SD card in PC, but I’m playing with eMMC instead, not installing the Ubuntu firmware in SD.
How to test “splitting PCIe lanes” with eMMC based on your recommendation?
For emmc you have to change the uEnv.txt from booted linux.
brucerry
January 6, 2026, 10:09am
11
How to do so?
Or I can edit the uEnv_r4.txt. What is the variable to be added?
frank-w
January 6, 2026, 10:15am
12
Boot you linux and use
nano /boot/uEnv.txt
Not change builtin env as long as you do not know what it does
brucerry
January 6, 2026, 10:30am
13
Here is the new boot after modifying /boot/uEnv.txt. It seems not work?
root@bpi-r4:~# dmesg | grep -e 8125 -e 8169
[ 1.810921] pci 0000:01:00.0: [10ec:8125] type 00 class 0x020000 PCIe Endpoint
[ 2.228169] mtk-pcie-gen3 11280000.pcie: msi#0xd address_hi 0x0 address_lo 0x11280c00 data 13
[ 2.526068] r8169 0000:01:00.0: vgaarb: pci_notify
[ 2.537385] r8169 0000:01:00.0: assign IRQ: got 82
[ 2.542213] r8169 0000:01:00.0: enabling device (0000 -> 0003)
[ 2.548055] r8169 0000:01:00.0: enabling Mem-Wr-Inval
[ 2.659703] x20: 0000000000000000 x19: ffffffc081257350 x18: 00000000ffffffff
[ 2.857173] r8169 0000:01:00.0: no dedicated PHY driver found for PHY ID 0x00000000, maybe realtek.ko needs to be added to initramfs?
[ 2.869194] r8169 0000:01:00.0: probe with driver r8169 failed with error -49
[ 2.876334] r8169 0000:01:00.0: vgaarb: pci_notify
root@bpi-r4:~#
root@bpi-r4:~# lspci
00:00.0 PCI bridge: MEDIATEK Corp. Device 7987 (rev 01)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
root@bpi-r4:~#
root@bpi-r4:~# cat /boot/uEnv.txt
# is2g5=1
# isr4pro=1
isr4lite=1
wificfg=#ov-lite-2pcie1l
abc=123
efg=#bruce
root@bpi-r4:~#
Shouldn’t it be saved to u-boot-env?
BPI-R4L> pri wificfg
## Error: "wificfg" not defined
BPI-R4L>
frank-w
January 6, 2026, 10:37am
14
My uboot loads this file directly before display bootmenu (bootcmd - reloadmenu - loadenv) and overwrites/extend the builtin env. Have you wait bootmenu displayed?
