Jump to content

6.12 can't recongize my onboard rlt8125 card


Go to solution Solved by xyzeratul,

Recommended Posts

Just upgrade from 6.11.5 to 6.12, I have a Intel i350 T2 card install and also has an onboard rlt 8125 card, all working fine in 6.11.5, in system devices, it show all 3 nic, but in network settings, only the 2 nic from Intel i350 T2 card show up as eth0, 1.

 

a bit more detail:

 

My unraid manage port is one of the nic on that i350 T2 card, the onboard 2.5G nic port I use to directly connect to my PC for faster file transfer.

 

So without the 2.5G nic showing up in the network setting, my direct drive mapping connecting to my PC is gone, but I can still mange my unraid server with local lan.

 

 

 

 

Edited by xyzeratul
Link to comment

The driver for the 8125 card is left out of the kernel / base system in 6.12

 

You can find and install it under Apps. Search for "RTL8152/3/4/6 USB Drivers" from ICH777's Repository.

(Yeah, you have it onboard, but it is usually a very cheap and very bad USB "card")

The info says you may have to reboot twice to bring it to work, dunno why.

 

 

Link to comment
2 hours ago, MAM59 said:

The driver for the 8125 card is left out of the kernel / base system in 6.12

 

You can find and install it under Apps. Search for "RTL8152/3/4/6 USB Drivers" from ICH777's Repository.

(Yeah, you have it onboard, but it is usually a very cheap and very bad USB "card")

The info says you may have to reboot twice to bring it to work, dunno why.

 

 

 

I tried this, after reboot the onboard nic still not showing up in network setting, but I didn't reboot twice

 

edit:

 

reboot twice, still the nic not showing up

Edited by xyzeratul
Link to comment
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 04)
    Subsystem: Micro-Star International Co., Ltd. [MSI] RTL8125 2.5GbE Controller [1462:7c82]
    Kernel modules: r8169

 

The module is there but it's not loading the driver, I have one of these NICs, let me test with v6.12.0 and I'll get back to you in a couple of hours.

Link to comment

Still working for me with v6.12.0:

 

03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
    Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:0123]
    Kernel driver in use: r8169
    Kernel modules: r8169

 

I see mine is rev 05 while yours is rev 04, not sure if that should make any difference, in the syslog you posted there's nothing about the r8169 driver, so it's not an initialization issue, looks more like it's not even trying to load the driver.

Link to comment
1 hour ago, JorgeB said:

Still working for me with v6.12.0:

 

03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
    Subsystem: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:0123]
    Kernel driver in use: r8169
    Kernel modules: r8169

 

I see mine is rev 05 while yours is rev 04, not sure if that should make any difference, in the syslog you posted there's nothing about the r8169 driver, so it's not an initialization issue, looks more like it's not even trying to load the driver.

When I was on 6.11.5, I used this patch:

 

but mainly for put i350 T2 in another group so I can bind one of it to my VM, not sure it's related or not.

 

I check my network.cfg file, the old settings are still there:

# Generated settings:
IFNAME[0]="eth0"
DHCP_KEEPRESOLV="yes"
DNS_SERVER1="1.1.1.1"
DNS_SERVER2="8.8.8.8"
DNS_SERVER3="114.114.114.114"
DHCP6_KEEPRESOLV="no"
DESCRIPTION[0]="Onboard"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="no"
IPADDR[0]="192.168.1.200"
NETMASK[0]="255.255.255.0"
GATEWAY[0]="192.168.1.1"
METRIC[0]="1"
USE_DHCP6[0]="yes"
IFNAME[1]="eth1"
PROTOCOL[1]="ipv4"
METRIC[1]="1"
MTU[1]="1500"
IFNAME[2]="eth2"
DESCRIPTION[2]="Onboard 2.5G"
PROTOCOL[2]="ipv4"
USE_DHCP[2]="no"
IPADDR[2]="10.10.10.1"
NETMASK[2]="255.255.255.0"
MTU[2]="9000"
SYSNICS="3"

 

 

 

Link to comment
  • Solution

I did a clean install and the onborad nic show up in network settings, so that means my old config must have something mess up.

 

edit:

 

found it, in /config/modprobe.d there is a config file blacklist the 8169 driver, I think it's leftover from the patch, delete it and the nic is back

Edited by xyzeratul
  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...