Thanks - very helpful. I am not yet very experienced with Linux drivers/kernel stuff. Without your pointing out it was possible I would have got stuck.
I tried to get the downloaded driver to work (on Proxmox 9). Using this download from there:
5G Ethernet LINUX driver r8126 for kernel up to 6.15
When I run the
./autorun.sh
I get:
Code:
Check old driver and unload it.
Build the module and install
make[2]: *** No rule to make target 'clean'. Stop.
make[1]: *** [Makefile:202: clean] Error 2
make: *** [Makefile:48: clean] Error 2
Further searching led me to an alternate approach:
https://github.com/awesometic/realtek-r8126-dkms
From there, I had trouble with the .deb install approach...I had errors about the Kernel headers not being installed, even though I have installed
pve-headers
Output of:
apt-cache policy pve-headers
Code:
pve-headers:
Installed: 9.0.0
Candidate: 9.0.0
Version table:
*** 9.0.0 500
500 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 Packages
100 /var/lib/dpkg/status
Output of:
dpkg -i realtek-r8126-dkms_10.015.00-1_amd64.deb
Code:
(Reading database ... 87369 files and directories currently installed.)
Preparing to unpack realtek-r8126-dkms_10.015.00-1_amd64.deb ...
Deleting module realtek-r8126/10.015.00 completely from the DKMS tree.
Unpacking realtek-r8126-dkms (10.015.00-1) over (10.015.00-1) ...
Setting up realtek-r8126-dkms (10.015.00-1) ...
Loading new realtek-r8126/10.015.00 DKMS files...
Building for 6.14.8-2-pve
Building for architecture amd64
Module build for kernel 6.14.8-2-pve was skipped since the
kernel headers for this kernel do not seem to be installed.
The ppa listed is for Ubuntu, so I tried the third option:
https://github.com/awesometic/realtek-r8126-dkms?tab=readme-ov-file#dkms-installsh
I
again had errors about the Kernel headers not being installed...ergh!
I solved this by (from
https://askubuntu.com/questions/714874/how-to-point-dkms-to-kernel-headers):
ln -s /usr/src/linux-headers-$(uname -r) /lib/modules/$(uname -r)/build
Then
dkms_install.sh
worked without errors, and subsequently using
lspci -k
could see:
Code:
83:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 5000 (rev 04)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7e32
Kernel modules: r8126
After all that, the interface still wouldn't show after a reboot with
ip a
I saw this issue:
https://github.com/awesometic/realtek-r8126-dkms/issues/3
And thus followed the instructions to get SecureBoot to accept the changes:
https://wiki.debian.org/SecureBoot#DKMS_and_Secure_Boot
...and then, finally, I could see my interface in the output of
ip a
So then, at last, it was just modifying
/etc/network/interfaces
to swap the device name there and then finally
systemctl restart networking
NIC is up, negotiates correct speed, and is still there after a reboot. (And being DKMS, should be there after a kernel change too, I believe...)