jinlife

Community Developer
  • Posts

    171
  • Joined

  • Last visited

Posts posted by jinlife

  1. On 2/11/2024 at 3:25 AM, OrdinaryButt said:

    Adding 8125 (Trendnet) adds exactly 4 watts to the kill-a-watt measurement at the tap. The problem is, the card prevents Packaged C-states - with it, I am stuck at C3; with card removed, it goes to C8. 4 watts may not be alot, but put it another way, it is 25% of this system usage (no HDD connected yet). 13 vs 17 watt at idle.

    If you share how to enable ASPM in the driver (I might find it by the time your respond, still reading), I can test to meassure the actual difference with ASPM on vs off. Thanks

    You need to modify the R8125 source code and compile it yourself. Since this is not easy, I recommend you to uninstall the R8125 plugin and use the built-in R8169 driver, probably it doesn't have ASPM settings. If the R8169 linux built-in driver also disables ASPM, then you have to find a solution yourself. 

    BTW: If you are modifying C states in BIOS, it might not only save energy from card but also CPU. 4 watts are too much for just one network card.

    • Like 1
  2. 43 minutes ago, ich777 said:

    Because not every chip is 100% compatible with ASPM or at least the driver has some issues with it.

    Keep in mind these are Community modified drivers because Realtek haven't updated their drivers in !!!!years!!!

     

    One thing to keep in mind is just because it is working for you it doesn't mean that it is working for everyone else.

    Can you upload Diagnostics from your system please?

     

    There are some reports on the forums with ASPM enabled with dropping network connections, constant reconnecting to the network and even loosing the network connectivity entirely.

    You also have to keep in mind that not every N100 is the same and even the Realtek chips don't have to be the same on those boards if newer revisions from the board are released.

    You even have to think about different manufacturers using different Realtek chips that uses the same driver.

     

    Sure then another plugin has to be made with that.

     

    No, not at this time.

    This would also introduce more complexity and even have some downsides in my opinion.

     

     

    I'll need @jinlife's opinion on that but it would be really difficult for users to even choose what driver to use and this would definitely result in unnecessary support requests.

     

    @jinlife I also saw that for the 8125 driver Realtek updated their drivers recently and it is now compatible up to Kernel 6.4

    Have you already seen that?

    I think the pressure on Realtek for Linux drivers will become more and more over time since most new "budget" boards use these chips.

     

    My advice would be to stay away from Realtek chips at all but that maybe change if they update their drivers more frequently.

    I have already updated the r8125 code to latest one v9.012.04. If this version is better, would you please trigger the build? Thanks.

    I would suggest to keep it simple since most of the user don't know the differences. They will ask what it is and we need to explain. Thinking of that, I would like to choose the best compatible one for them.

    Anyone who prefers a different option is welcome to fork the open source repo and build it on their own.

    • Like 2
  3. 1 hour ago, aussie_huddo said:

    I installed the driver from Community Apps, restarted the server and thats when it became inaccessible.

    Thanks for the info, it seems to be other reasons, I may not able to help you.

    Please try the plugin with a brand new unraid system if possible. Or if you have no problem with current driver, better to keep using it.

    • Like 1
  4. On 1/7/2024 at 4:36 AM, oh-tomo said:

    Ethernet speed seems good between Nvidia Shield Pro 2019 and unRAID. What issues am I looking for or should I just leave it alone? 

     

    (Also my receipt and bios say my motherboard is H310M-A but lspci.txt says B450M-A.)

     

    04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
        Subsystem: ASUSTeK Computer Inc. PRIME B450M-A Motherboard [1043:8677]
        Kernel driver in use: r8169
        Kernel modules: r8169
    

     

     

    [  5] 501.00-502.00 sec   111 MBytes   933 Mbits/sec    0    277 KBytes       
    [  5] 502.00-503.00 sec   112 MBytes   944 Mbits/sec    0    305 KBytes       
    [  5] 502.00-503.00 sec   112 MBytes   944 Mbits/sec    0    305 KBytes       
    - - - - - - - - - - - - - - - - - - - - - - - - -
    [ ID] Interval           Transfer     Bitrate         Retr
    [  5]   0.00-503.00 sec  54.1 GBytes   923 Mbits/sec   84             sender
    [  5]   0.00-503.00 sec  0.00 Bytes  0.00 bits/sec                  receiver
    iperf3: error - the server has terminated

     

    I would suggest leave it alone if no issues.

  5. On 1/9/2024 at 7:17 AM, mikl said:

    How do I install this driver if i'm getting this? 😛

     

    plugin: installing: unraid-r8125.plg
    Executing hook script: pre_plugin_checks
    plugin: downloading: unraid-r8125.plg ... done
    
    Executing hook script: pre_plugin_checks
    
    -----------------------Downloading RTL8125 package!-------------------------
    --------This could take some time, please don't close this window!----------
    
    -----------------------Can't download RTL8125 package-----------------------
    plugin: run failed: '/bin/bash' returned 1
    Executing hook script: post_plugin_checks

     

    It seems your network is blocked from github, please make sure you can access github from unraid server.

  6. On 1/8/2024 at 10:28 PM, DWA63 said:

    Hi,

    I have 2 Unraid servers running. Patch is NOT installed.

    One is using the Realtek R8168 (1 gigabit) with driver R8169.

    One is using the Realtek R8125 (2.5 gigabit) also with driver R8169.

    Both have thousands of networkdrops on the receiving side of bond0.

    But operation seems to be fully normal.

    Questions:

    1) is it normal that both use the same driver?

    2) is the thousands of networkdrops a symptom of the problem mentioned in this thread?

    3) is it recommend to install the patch on both server?

    Thanks!

    It is normal, and you can try to install plugin to see whether it is better.

    If not, then uninstall plugin will clean it completely. Better to back up usb disk at first.

  7. On 1/8/2024 at 9:54 AM, aussie_huddo said:

    I upgraded to 6.12.6 and decided to install the Realtek driver to get ahead of any issues but when I did install the 8168 driver and restarted I couldn't access the server by the network. Had to run in GUI mode and uninstall the driver.

     

    Any ideas why this occured. Diagnostics included below from when the server was inaccessable.

     

    huddohub-diagnostics-20240107-2122.zip 149.56 kB · 1 download

     

    System Devices shows:

    	07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16)

     

    have you reboot the Unraid after install plugin? There is no log about loading driver in syslog.

  8. 8 hours ago, cardo said:

    System just hard locked again. I have to power it down when this occurs. Just before it locked up I did see some some warning and errors related to the USB NIC about timeouts, etc. I stream music videos once a week from unRAID to my desktop PC. Both have 2.5Gbps cards. The desktop PC has an onboard NIC and unRAID has the RealTek external USB. The last time this occurred was also when I did 12+ hours of streaming.

     

    The issue started after 6.12.5, but I am not necessarily blaming unRAID or the NIC drivers it could very well be that the external NIC isn't good.

     

    Does anyone know of an external USB 2.5Gbps NIC that has built in unRAID support? I'm tired of fighting with the RealTek.

    Maybe you could post the diagnostics.

    Please take care of overheating issues with USB NICs when used heavily.

    Or maybe you can revert back to 6.12.4. 

    BTW: I'm using 2.5G NIC for months without reboot in 6.11.5. There seems to be no other chips of USB 2.5NIC but realtek.

  9. @JorgeB  @emotion_chip @cardo @ich777

    It looks like the driver cdc_ncm hijacked the usb driver.

    Add blacklist to this driver and reboot, then it will work fine.

    echo "blacklist cdc_ncm" > /boot/config/modprobe.d/cdc_ncm.conf

     

    Please check whether it works.

     

    It seems the CONFIG_USB_NET_CDC_NCM was added in 6.12.5rc, I have no idea why it was added.

    Don't know whether it is conflict with 

     

     

    If it is permanent change, then we might need to add blacklist in the plugin code.

    • Like 2
  10. 1 hour ago, emotion_chip said:

    Sorry, next time I try to troubleshoot I'll download the diagnostics info... I thought it would be helpful to show that other people were having the same issue as cardo

    Looks like an incompatibility issue. The r8156 code has not changed while the Unraid kernel is updated. I guess they don't work properly and I need to find some time to figure out why, in the meantime, I think it's better to stay on 6.12.4 for now.

  11. 15 minutes ago, cardo said:

    To be honest it looked like it happened after me switching primary eth0 back and forth between the internal NIC and the USB one. I was also attempting to try different USB ports because I desperately wanted it to work. Is there any way for me to reset this so eth122 is removed?

    Maybe you can copy a brand new network.cfg file from unraid installer and overwrite yours in the config folder of the USB disk and then reboot. It will reset the network config and then you can start your experiment from the beginning. 

    Better to backup your entire USB disk before this in case any mistake happen.

  12. 2 hours ago, cardo said:

    Hi,

     

    I have the following USB 2.5GB NIC https://www.amazon.com/gp/product/B093FB9QWB/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1, I was using your driver with success up until I updated to 6.12.5 and then it stopped working. When starting up it would say that the eth0 interface was not found. I saw the previous response about updating the driver, so I uninstalled the r8156 driver and then rebooted. I then downloaded the driver again and rebooted and the issue remained. I saw then there was an update to unRAID to 6.12.6 and I updated. The issue still remains

     

    I rebooted a number of times and it just won't work. I have attached the diagnostic logs.

    diagnostics-20231202-1639.zip 141.3 kB · 1 download

    The r8152/6 driver haven't been updated for months, it is still v2.17.1 version. It seems the card was driven succesfully.

    I can see in your log, the eth0 was changed to eth122, that is strange, please check whether some other plugin or configuration changed this.

     

    Dec  2 16:38:07 MojoRyzen kernel: r8152-cfgselector 4-3: reset SuperSpeed USB device number 2 using xhci_hcd
    Dec  2 16:38:07 MojoRyzen kernel: r8152 4-3:1.0 eth0: v2.17.1 (2023/06/13)
    Dec  2 16:38:07 MojoRyzen kernel: r8152 4-3:1.0 eth0: This product is covered by one or more of the following patents:
    Dec  2 16:38:07 MojoRyzen kernel:         US6,570,884, US6,115,776, and US6,327,625.
    Dec  2 16:38:07 MojoRyzen kernel: 
    Dec  2 16:38:07 MojoRyzen kernel: usbcore: registered new interface driver r8152
    Dec  2 16:38:07 MojoRyzen kernel: r8152 4-3:1.0 eth122: renamed from eth0

     

  13. On 11/27/2023 at 9:53 PM, Niklas said:

    Since I updated to 6.12.5-rc1 (and now 6.12.5 release) I have this filling my syslog. Don't know if it's related to .5 or the driver. 5 mins between them
     

    Nov 27 17:00:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:00:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:00:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:00:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:00:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:00:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:00:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:00:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:00:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:00:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:05:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:05:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:05:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:05:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:05:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:05:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:05:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:05:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:05:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:05:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:10:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:10:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:10:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:10:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:10:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:10:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:10:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:10:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:10:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:10:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:15:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:15:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:15:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:15:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:15:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:15:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:15:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:15:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:15:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:15:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:20:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:20:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:20:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:20:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:20:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:20:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:20:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:20:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:20:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:20:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:25:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:25:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:25:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:25:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:25:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:25:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:25:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:25:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:25:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:25:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:30:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:30:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:30:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:30:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:30:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:30:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:30:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:30:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:30:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:30:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:35:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:35:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:35:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:35:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:35:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:35:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:35:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:35:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:35:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:35:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:40:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:40:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:40:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:40:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:40:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:40:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:40:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:40:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:40:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:40:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:45:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:45:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:45:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:45:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:45:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:45:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:45:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:45:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:45:01 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc
    Nov 27 17:45:02 Server kernel: r8125 0000:02:00.0 eth0: rss get rxnfc

     

    This is noisy log info, there is no harm to functions. I have disabled the log in the source code, and following build will be fine.

    @ich777 I have no idea how to trigger the plugin build for 6.12.5 official release, would you please trigger it to apply this change. Thanks.

    • Like 2
    • Thanks 1
  14. 23 hours ago, MEWTWO said:

     

    我也出现了这个问题,我使用的精粤B760i snow dream的板子。有两个网口分别是R8125和R8168,使用unraid6.11.5系统,可以看到使用了r8169的驱动,插上网线2.5G的网口可以使用,RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller无法使用,路由器能识别但是无法下发ip,unraid也显示interface down。屏蔽后直通虚拟机也无法直通,提示PCI Header Type 127。我在unraid自带应用商城安装了RTL8168(B)/RTL8111(B) PCI Drivers插件后,R8168的网卡可以使用了,但是R8125却无法识别了接口无法显示。但是我屏蔽R8125后,它却可以直通给虚拟机使用。太神奇了,所以unraid能不能让两个驱动同时存在呢?目前总会出现一个网口无法使用的情况。

     

    应用市场既有R8111的驱动,也有R8125的驱动。两个plugin都装就行了。我的三个realtek的plugin都可以同时装。

  15. @ich777 @tnthalftime 

    I totally agree with ich777. The R8125 does have performance issues with ASPM enabled sometimes, especially on weaker CPUs, I've encountered it myself, so I disabled it by default as it works for most situations. On the other hand, the network card may only save 0.5~1? watts, which I don't think is a huge cost. I would rather spend some watts to ensure performance.

    BTW: It's free and open source, and I kinda don't want to spend more of my personal time maintaining two source codes. Sorry about that.

     

    • Like 2
  16. On 10/25/2023 at 11:23 AM, always67 said:

    使用插件和替换文件都能正常驱动8156的usb 2.5g网卡,但是大概几分钟就会丢设备。

    已经换了一个usb接口了,问题依旧。

     

    jonsbo-diagnostics-20231025-1122.zip 137.46 kB · 1 download

    看起来网络配置比较高级,看不懂。Unraid貌似不能支持同时用两网卡互联互通,自带默认的网络配置没有交换机的功能。

    驱动应该没问题的。建议弄个干净的Unraid系统试试,每次只用一个网口。排除系统和硬件的问题。再去研究一下网络配置。

  17. On 10/12/2023 at 7:25 PM, qq123456 said:

    大佬你好,很多人在6.11.5和我遇到一样的问题,我是华南b660主板,有的人是铭瑄b660主板,板载的8125b直通后报这个错,你可以分析下是什么原因吗?需要我配合的话,企鹅721509025,万分感谢

    QQ截图20231012192231.png

    QQ截图20231012192302.png

    google搜索一下 PCI Header Type 127, 貌似大多是linux虚拟机用了Q35的原因,换成i440fx可能有用。或者跟主板bios有关,升级或降级bios试试。这个直通出错跟驱动没关系。