On 5/8/2026 at 1:16 AM, OrdinaryButt said:

How exactly does one install the 8127 driver? Please explained for someone that has never done custom driver install outside of the Unraid app store. Thanks.

I've put together a new build for the r8127 driver using GitHub Actions! You can install it manually through the Plugins tab.

Installation URL:

https://raw.githubusercontent.com/ERSTT/unraid-r8127-driver/refs/heads/main/unraid-r8127.plg

I'm not sure about the 8127AF compatibility since I don't have the hardware to test it. It might work, it might not

You can check out the repo here: https://github.com/ERSTT/unraid-r8127-driver. Feel free to peek at the GitHub Actions tab if you want to see how the whole build process works.

Edited May 9May 9 by ERST

On 5/9/2026 at 2:31 PM, ERST said:

I've put together a new build for the r8127 driver using GitHub Actions! You can install it manually through the Plugins tab.

Installation URL:

https://raw.githubusercontent.com/ERSTT/unraid-r8127-driver/refs/heads/main/unraid-r8127.plg

I'm not sure about the 8127AF compatibility since I don't have the hardware to test it. It might work, it might not

You can check out the repo here: https://github.com/ERSTT/unraid-r8127-driver. Feel free to peek at the GitHub Actions tab if you want to see how the whole build process works.

Thank you so much! I did not know plugins can be installed this way. Shame on me.

@JorgeB I had above plugin installed, and the SFP+ variation of the card started working on 7.3 rc1. BUT, I am confused, because unRaid still reports using the r8169 driver as seen in screenshot below. Also, GitHub readme states that ASPM is disabled for above plugin/driver, but I see otherwise (and I am not complaining). Did I get into the some sort of "in between" situation here?





EDIT:
I also tried on 7.2.3 and this time the system reports using the r8127 driver (ASPM is still enabled, so perhaps that was not relevant). Still works

Edited May 11May 11 by OrdinaryButt

8 hours ago, OrdinaryButt said:

BUT, I am confused, because unRaid still reports using the r8169 driver as seen in screenshot below.

Post new diags from 7.3

11 hours ago, OrdinaryButt said:

Thank you so much! I did not know plugins can be installed this way. Shame on me.

@JorgeB I had above plugin installed, and the SFP+ variation of the card started working on 7.3 rc1. BUT, I am confused, because unRaid still reports using the r8169 driver as seen in screenshot below. Also, GitHub readme states that ASPM is disabled for above plugin/driver, but I see otherwise (and I am not complaining). Did I get into the some sort of "in between" situation here?





EDIT:
I also tried on 7.2.3 and this time the system reports using the r8127 driver (ASPM is still enabled, so perhaps that was not relevant). Still works

Regarding your confusion about the ASPM status and the driver name:

ASPM Status: The CONFIG_ASPM = n build flag in the Makefile only defaults the driver to a disabled state, but the OS or BIOS may still override this.

Driver Name: The plugin explicitly blacklists the native driver to ensure the OOT driver works properly. You can verify this by checking the configuration file:

cat /boot/config/modprobe.d/r8169.conf

If it contains blacklist r8169, then the native driver is successfully disabled.

You should check the terminal instead to see the actual driver currently handling the hardware:

Run lspci -k (or lspci -k -s 01:00.0) and look for the "Kernel driver in use" line.

Or run ethtool -i ethXXX to check the driver version.

Edited May 12May 12 by ERST

1 hour ago, ERST said:

Regarding your confusion about the ASPM status and the driver name:

ASPM Status: The CONFIG_ASPM = n build flag in the Makefile only defaults the driver to a disabled state, but the OS or BIOS may still override this.

Driver Name: The plugin explicitly blacklists the native driver to ensure the OOT driver works properly. You can verify this by checking the configuration file:

cat /boot/config/modprobe.d/r8169.conf

If it contains blacklist r8169, then the native driver is successfully disabled.

You should check the terminal instead to see the actual driver currently handling the hardware:

Run lspci -k (or lspci -k -s 01:00.0) and look for the "Kernel driver in use" line.

Or run ethtool -i ethXXX to check the driver version.

Great explanation. Looks like blacklisted, but there is some sort of "Kernel module" r8169 in use?

5 hours ago, JorgeB said:

Post new diags from 7.3

tower-diagnostics-20260512-0700.zip

01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8127 10GbE Controller [10ec:8127] (rev 08)

Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]

Kernel driver in use: r8127

Kernel modules: r8169, r8127

The GUI may still be picking up the r8169 driver from here, but the one in use is the out-of-tree driver.

Installed unraid 7.3 and the 2.5GB Realtek is detected without installing any drivers.

Can i install the RTL8126 PCI Drivers jinlife to get the latest version of the driver or is ithis not necessary?

Current driver from the install:

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8126 5GbE Controller (rev 01)

root@nas:~# ethtool -i eth0

driver: r8169

version: 6.18.33-Unraid

firmware-version: rtl8126a-3_0.0.5 08/30/24

expansion-rom-version:

bus-info: 0000:01:00.0

supports-statistics: yes

supports-test: no

supports-eeprom-access: no

supports-register-dump: yes

supports-priv-flags: no

If everything works as it should, don't.

I recently bought a Ugreen 5GbE usb ethernet adapter (r8157) - I loaded up the plugin, links at 5Gbps just fine, but unfortunately I am getting NETDEV WATCHDOG errors after a while and I have to reboot the server, making it unusable. Tried:
- ethtool -K eth0 rx off tx off gso off gro off tso off
- passing pcie_aspm=off in the boot parameters
- interestingly, while the array is down, no problem at all. As soon as the array is up (and my NFS shares, which I suspect from some posts I saw), errors.

I noticed Realtek has a new driver out (2.22.1) - anyone knows whether the plugin will get updated or whether I can do it myself somehow? Thanks!

Edited July 1Jul 1 by Kombatant

is this plugin works with unraid 7.3.1？

On 5/9/2026 at 4:31 PM, ERST said:

I've put together a new build for the r8127 driver using GitHub Actions! You can install it manually through the Plugins tab.

Installation URL:

https://raw.githubusercontent.com/ERSTT/unraid-r8127-driver/refs/heads/main/unraid-r8127.plg

I'm not sure about the 8127AF compatibility since I don't have the hardware to test it. It might work, it might not

You can check out the repo here: https://github.com/ERSTT/unraid-r8127-driver. Feel free to peek at the GitHub Actions tab if you want to see how the whole build process works.

@ERST I have problem with installation? Manual option to install?

I just ran into a plugin error while initiating the 7.3.2 update:

For now, I have canceled the update process to reboot and install 7.3.2. Any advice?

3 hours ago, JayDee73 said:

I just ran into a plugin error while initiating the 7.3.2 update:

For now, I have canceled the update process to reboot and install 7.3.2. Any advice?

Did a little research myself. I found @ich777 Plugin Helper Github repo (https://github.com/ich777/unraid-plugin_update_helper/blob/master/README.md) and executed the mentioned command in Unraid terminal. Output was:

Force Plugin Updates script version: 2026.05.04 by ich777

Please don't close this window until it says finished!

/boot/config/plugins/it87-driver/packages/6.18.33/: Is a directory

/boot/config/plugins/r8125-driver/packages/6.18.33/: Is a directory

Finished, please take a look at your unRAID notifications if all packages where downloaded correctly!

So for both my problematic plugins (RTL8125 and IT87) there was an output. After that, Unraid again pushed an error notification.

So maybe ich777 can shed a little light on this?

On 7/10/2026 at 11:36 PM, ArusHear said:

@ERST I have problem with installation? Manual option to install?

If you are using Unraid version 7.3.2, this issue should be fixed now.

The installation failed because the 6.18.38 kernel source files were initially missing from the ich777/unraid_kernel repository, which caused the GitHub Actions automatic workflow to fail to compile the driver. The developer (ich777) has since uploaded the missing kernel source, so the plugin should be working properly now.

Reference: https://github.com/ich777/unraid_kernel/issues/16

On 7/19/2026 at 10:56 PM, ERST said:

The installation failed because the 6.18.38 kernel source files were initially missing from the ich777/unraid_kernel repository, which caused the GitHub Actions automatic workflow to fail to compile the driver. The developer (ich777) has since uploaded the missing kernel source, so the plugin should be working properly now.

No, that's actually not true, only the upload from the Kernel archive failed, the drivers where compiled just fine.

GitHub is lately under heavy load (I assume because of heavy load because of AI pushing so much new code) and it doesn't always work as intended.

On 7/13/2026 at 7:45 PM, JayDee73 said:

So maybe ich777 can shed a little light on this?

You should try to remove the plugin from your server and then try to install it again, if that works then simply run this from an Unraid terminal, but usually you have to wait a few hours until everything works on GitHub as usual:

wget -qO- https://raw.githubusercontent.com/ich777/unraid-plugin_update_helper/master/force_package_update | bash