Closed geerlingguy closed 2 years ago
CONFIG_R8169=m
is already set in the 32- and 64-bit Pi 4 defconfigs, and the module is shipping as part of our standard firmware: https://github.com/raspberrypi/rpi-firmware/blob/master/modules/5.10.78-v7l%2B/kernel/drivers/net/ethernet/realtek/r8169.ko https://github.com/raspberrypi/rpi-firmware/blob/master/modules/5.10.78-v8%2B/kernel/drivers/net/ethernet/realtek/r8169.ko
Oh, interesting... do you know if that was added more recently? I last tested with a build from a few weeks ago, and I had updated it a few days ago, but it was the Buster image and not the latest Bullseye release.
I performed a dist-upgrade
on a fresh install of Bullseye, and after had:
pi@bullseye:~ $ uname -a
Linux bullseye 5.10.63-v8+ #1459 SMP PREEMPT Wed Oct 6 16:42:49 BST 2021 aarch64 GNU/Linux
Then I ran sudo rpi-update
and ended up with:
pi@bullseye:~ $ uname -a
Linux bullseye 5.10.78-v8+ #1484 SMP PREEMPT Thu Nov 11 16:37:26 GMT 2021 aarch64 GNU/Linux
pi@bullseye:~ $ lspci -v
...
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 04)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller
Flags: bus master, fast devsel, latency 0, IRQ 66
I/O ports at <unassigned> [disabled]
Memory at 600100000 (64-bit, non-prefetchable) [size=64K]
Memory at 600110000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: r8169
Kernel modules: r8169
So... nice! Do you know when this change will trickle down to the stable firmware?
Sorry - I can't put my finger on my crystal ball.
@pelwell - It was worth a try ;)
I'll close this as 'fixed' anyways. That was the easiest feature request ever!
Adding link to the PR where this was merged just for crosslinking/reference purposes: https://github.com/raspberrypi/linux/pull/4625
Is this the right place for my bug report?
Yes*
*Though it's more of a feature request, but let me know if you'd like me to just open a PR for discussion instead.
Describe the bug
The Raspberry Pi Compute Module 4 opens up some new possibilities for networking with a Raspberry Pi. The Pi's exposed PCIe Gen 2 lane is perfect for 2.5 Gbps networking, which is a nice more-than-double speed boost over the built-in 1 Gbps NIC (and it can be used in tandem, for compact router builds).
I have already tested two cards that work with
CONFIG_R8169
enabled, Rosewill's RC-20001 and Syba's Dual-2.5G card. And it seems that Radxa's new Taco board also includes the Realtek 8125b chipset.I can install the driver manually from Realtek's website, and it works at least on the 64-bit Pi OS build, but it would be convenient, since it is a reliable, inexpensive chipset (already being integrated into some CM4 projects), if the support were available in the base release.
To reproduce
Install the default kernel onto a Pi with a Realtek 8125b-based 2.5 Gbps NIC. Try to use the interface.
lspci
will show it, but no kernel module is available for it.Expected behaviour
The NIC should be recognized and available to the system in addition to the built-in Broadcom NIC.
Actual behaviour
The NIC is not visible until after you manually install Realtek's driver or recompile the kernel with
CONFIG_R8169
.System
cat /etc/rpi-issue
)? N/Avcgencmd version
)? N/Auname -a
)? N/ALogs
lspci
output:Click to expand output
``` 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8125 (rev 04) Subsystem: Realtek Semiconductor Co., Ltd. Device 8125 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-Additional context
I would be happy to submit a PR if this change is acceptable.