bb-qq / r8152

Synology DSM driver for Realtek RTL8152/RTL8153/RTL8156 based adapters
GNU General Public License v2.0
2.07k stars 184 forks source link

RESOLVED: D-Link DUB-E250: does not appear in DS218+ Network Interface list, but does appear in USB device list #210

Open bobk88 opened 2 years ago

bobk88 commented 2 years ago

Description of the problem

I successfully installed the Apollo Lake driver on my DS218+ per your instructions - version 2.15.0-5 is running, as verified in Package Center.

I happened to have a D-Link DUB-E250 USB-C to Ethernet adapter on hand, so I connected it to one of the rear USB 3.0 ports using a Pearstone (B&H) USB-C to USB-A adapter (USB 3.2 Gen 2, 10 Gbps max).

The DUB-E250 does not appear in the device list in Control Panel > Network > Network interface, but it does appear in the list of USB devices - see lsusb output below. (I assume it should just appear in addition to the existing connection - correct?)

Same results when connected to the front USB port.

The D-Link works fine when plugged into a USB-C port on my hackintosh running macOS 12.3.1, using the driver com.apple.driver.usb.cdc.ncm (no driver installation is required in Big Sur and Monterey).

Happy to provide more info, but as I'm a beginner (and not an engineer), I'll need specific steps.

Thanks!

Description of your products

DS218+ Linux [drive name] 4.4.180+ #42218 SMP Mon Oct 18 19:17:56 CST 2021 x86_64 GNU/Linux synology_apollolake_218+ DSM 7.0.1-42218 D-Link DUB-E250 - a review at Amazon says it uses an 8156b chipset, for what that's worth.

DUB-E250 product page DUB-E250 drivers at D-Link site Drivers, including 8156 and 8156b, at Realtek site

Description of your environment

NAS is connected to a Netgear GS105 unmanaged Gigabit switch. Adapter is connected to NAS with a Cat.5e cable, about 3 feet long. I also tried a Cat 6 cable, 10-15 feet long, and got the same results. Data below was obtained while using the Cat.5e cable.

Output of dmesg command

NOTE: The full output was over 2,000 lines long. When I pasted it here, Github said my comment was too long. I don't know which part is relevant, so I guessed and pasted in the last ~100 lines. Let me know if you need more. Thanks!

[340862.271877] synoboot1 unmounted, process=synowedjat [345317.589096] ata2: wake up from deepsleep, reset link now [345317.839910] ata2: device plugged sstatus 0x133 [345324.588358] ata1: wake up from deepsleep, reset link now [345324.874017] ata1: device plugged sstatus 0x133 [345326.372295] ata2: link is slow to respond, please be patient (ready=0) [345330.768114] ata2: softreset failed (device not ready) [345330.773894] ata2: SRST fail, set srst fail flag [345331.659066] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [345331.666124] ata2: link reset sucessfully clear error flags [345331.677110] ata2.00: disabling queued TRIM support [345331.684638] ata2.00: disabling queued TRIM support [345331.684653] ata2.00: configured for UDMA/133 [345331.689559] ata2: wake up successful, the reset fail can be ignored [345333.365977] ata1: link is slow to respond, please be patient (ready=0) [345337.760797] ata1: softreset failed (device not ready) [345337.766560] ata1: SRST fail, set srst fail flag [345338.652774] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [345338.659819] ata1: link reset sucessfully clear error flags [345338.670786] ata1.00: disabling queued TRIM support [345338.678476] ata1.00: disabling queued TRIM support [345338.678497] ata1.00: configured for UDMA/133 [345338.683410] ata1: wake up successful, the reset fail can be ignored [354125.438299] ata1: wake up from deepsleep, reset link now [354125.725344] ata1: device plugged sstatus 0x133 [354132.447015] ata2: wake up from deepsleep, reset link now [354132.699047] ata2: device plugged sstatus 0x133 [354134.169678] ata1: link is slow to respond, please be patient (ready=0) [354138.615499] ata1: softreset failed (device not ready) [354138.621265] ata1: SRST fail, set srst fail flag [354139.505476] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [354139.512518] ata1: link reset sucessfully clear error flags [354139.523498] ata1.00: disabling queued TRIM support [354139.531104] ata1.00: disabling queued TRIM support [354139.531118] ata1.00: configured for UDMA/133 [354139.536008] ata1: wake up successful, the reset fail can be ignored [354141.227386] ata2: link is slow to respond, please be patient (ready=0) [354145.624194] ata2: softreset failed (device not ready) [354145.629958] ata2: SRST fail, set srst fail flag [354146.516184] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [354146.523225] ata2: link reset sucessfully clear error flags [354146.534182] ata2.00: disabling queued TRIM support [354146.541797] ata2.00: disabling queued TRIM support [354146.541811] ata2.00: configured for UDMA/133 [354146.546709] ata2: wake up successful, the reset fail can be ignored [356208.358781] ata2: wake up from deepsleep, reset link now [356208.611079] ata2: device plugged sstatus 0x133 [356215.358272] ata1: wake up from deepsleep, reset link now [356215.645762] ata1: device plugged sstatus 0x133 [356217.141202] ata2: link is slow to respond, please be patient (ready=0) [356221.538030] ata2: softreset failed (device not ready) [356221.543804] ata2: SRST fail, set srst fail flag [356222.430992] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [356222.438038] ata2: link reset sucessfully clear error flags [356222.448957] ata2.00: disabling queued TRIM support [356222.456532] ata2.00: disabling queued TRIM support [356222.456546] ata2.00: configured for UDMA/133 [356222.461446] ata2: wake up successful, the reset fail can be ignored [356224.138899] ata1: link is slow to respond, please be patient (ready=0) [356228.533723] ata1: softreset failed (device not ready) [356228.539498] ata1: SRST fail, set srst fail flag [356229.425699] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [356229.432744] ata1: link reset sucessfully clear error flags [356229.443908] ata1.00: disabling queued TRIM support [356229.451533] ata1.00: disabling queued TRIM support [356229.451548] ata1.00: configured for UDMA/133 [356229.456455] ata1: wake up successful, the reset fail can be ignored [358035.709868] usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd [358043.229735] igb 0000:01:00.0 eth0: igb: eth0 NIC Link is Down [358048.596997] audit_printk_skb: 45 callbacks suppressed [358048.602763] audit: type=1325 audit(1649884597.827:64): table=filter family=2 entries=26 [358209.589351] igb 0000:01:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [358227.088176] audit: type=1325 audit(1649884776.326:65): table=filter family=2 entries=17 [358227.117586] audit: type=1325 audit(1649884776.355:66): table=filter family=2 entries=21 [358227.307478] audit: type=1325 audit(1649884776.545:67): table=filter family=2 entries=22 [358232.590060] audit: type=1325 audit(1649884781.828:68): table=filter family=2 entries=23 [358232.607190] audit: type=1325 audit(1649884781.845:69): table=filter family=2 entries=22 [358232.643777] audit: type=1325 audit(1649884781.882:70): table=filter family=2 entries=21 [358234.630867] usbcore: registered new interface driver r8152 [358255.748787] EXT4-fs (sdq1): re-mounted. Opts: (null) [358285.172858] xhci_hcd 0000:00:15.0: device is plugged out, empty URBs [358288.002248] usb 2-1: USB disconnect, device number 2 [358326.360824] igb 0000:01:00.0 eth0: igb: eth0 NIC Link is Down [358451.772169] igb 0000:01:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [358465.184437] audit: type=1325 audit(1649885014.432:71): table=filter family=2 entries=17 [358465.213844] audit: type=1325 audit(1649885014.462:72): table=filter family=10 entries=4 [358465.239718] audit: type=1325 audit(1649885014.487:73): table=filter family=2 entries=21 [358465.286065] audit: type=1325 audit(1649885014.534:74): table=filter family=10 entries=8 [358465.324839] audit: type=1325 audit(1649885014.573:75): table=filter family=2 entries=22 [358465.366980] audit: type=1325 audit(1649885014.615:76): table=filter family=10 entries=9 [358468.949676] audit: type=1325 audit(1649885018.198:77): table=filter family=2 entries=23 [358468.967167] audit: type=1325 audit(1649885018.215:78): table=filter family=2 entries=27 [358469.118210] audit: type=1325 audit(1649885018.366:79): table=filter family=2 entries=28 [358474.367544] audit: type=1325 audit(1649885023.616:80): table=filter family=2 entries=29 [358474.384816] audit: type=1325 audit(1649885023.633:81): table=filter family=2 entries=28 [358474.422871] audit: type=1325 audit(1649885023.670:82): table=filter family=2 entries=27 [358503.728251] Synotify use 16384 event queue size [358555.295567] xhci_hcd 0000:00:15.0: device is plugged out, empty URBs [358558.125898] usb 2-3: USB disconnect, device number 3 [358561.097791] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd [358800.258635] xhci_hcd 0000:00:15.0: device is plugged out, empty URBs [358803.087588] usb 2-1: USB disconnect, device number 4 [358816.651032] usb 2-3: new SuperSpeed USB device number 5 using xhci_hcd [358880.783803] xhci_hcd 0000:00:15.0: device is plugged out, empty URBs [358883.613204] usb 2-3: USB disconnect, device number 5 [358893.521795] usb 2-2: new SuperSpeed USB device number 6 using xhci_hcd [359060.305651] audit: type=1325 audit(1649885609.578:83): table=filter family=2 entries=23 [359060.323474] audit: type=1325 audit(1649885609.596:84): table=filter family=2 entries=27 [359060.470566] audit: type=1325 audit(1649885609.743:85): table=filter family=2 entries=28 [359065.716584] audit: type=1325 audit(1649885614.990:86): table=filter family=2 entries=29 [359065.734452] audit: type=1325 audit(1649885615.007:87): table=filter family=2 entries=28 [359065.770275] audit: type=1325 audit(1649885615.043:88): table=filter family=2 entries=27

Output of lsusb command

|usb1 1d6b:0002:0404 09 2.00 480MBit/s 0mA 1IF (Linux 4.4.180+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub |1-4 f400:f400:0100 00 2.00 480MBit/s 200mA 1IF (Synology DiskStation 7F00892FA8CA6035) |usb2 1d6b:0003:0404 09 3.00 5000MBit/s 0mA 1IF (Linux 4.4.180+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub |2-2 2001:b301:3100 00 3.20 5000MBit/s 256mA 2IFs (D-Link DUBE250 2.5GbE Adapter 001000001)

Output of ifconfig -a command

docker0 Link encap:Ethernet HWaddr 02:42:62:C8:B6:BB
inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

eth0 Link encap:Ethernet HWaddr 00:11:32:9B:B9:9B
inet addr:192.168.0.183 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3992636 errors:0 dropped:0 overruns:0 frame:0 TX packets:3997323 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3229989296 (3.0 GiB) TX bytes:3789983403 (3.5 GiB)

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:312456 errors:0 dropped:0 overruns:0 frame:0 TX packets:312456 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:19569824 (18.6 MiB) TX bytes:19569824 (18.6 MiB)

sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

tun1000 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:169.254.241.92 P-t-P:169.254.241.92 Mask:255.255.248.0 inet6 addr: fec0:a2b2:16::15c/112 Scope:Site UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1400 Metric:1 RX packets:4368 errors:0 dropped:0 overruns:0 frame:0 TX packets:2051 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:388880 (379.7 KiB) TX bytes:501322 (489.5 KiB)

imsoso commented 2 years ago

same situation on release: 2.15.0-5 DSM7.x device ds920+,[UGREEN USB C to 2.5G Ethernet Adapter

bb-qq commented 2 years ago

I could not find any output about driver loading from your log. Could you attach the full dmesg logs as a file?

bobk88 commented 2 years ago

See attached. Thanks!

EDIT: Removed attached dmsg because it lacked needed information.

bb-qq commented 2 years ago

Sorry, the logs from the beginning are not included because it has been a long time since the startup. Can you please reboot the NAS once and get the logs again?

bobk88 commented 2 years ago

Here's the output after restart. Is this better?

When I ran dmesg this time, the DUB-E250 was connected to the front USB port per your instructions.

Here's the lsusb output:

|usb1 1d6b:0002:0404 09 2.00 480MBit/s 0mA 1IF (Linux 4.4.180+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub |1-4 f400:f400:0100 00 2.00 480MBit/s 200mA 1IF (Synology DiskStation 7F00892FA8CA6035) |usb2 1d6b:0003:0404 09 3.00 5000MBit/s 0mA 1IF (Linux 4.4.180+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub |2-3 2001:b301:3100 00 3.20 5000MBit/s 256mA 2IFs (D-Link DUBE250 2.5GbE Adapter 001000001)

2022-04-22 dmesg.txt

bb-qq commented 2 years ago

Thank you. I found the current version of driver does not support this device. So I created new the release. Could you try it? https://github.com/bb-qq/r8152/releases/download/2.15.0-7/r8152-apollolake-2.15.0-7.spk

bobk88 commented 2 years ago

Yes, it's working! Thanks very much!

At first it was set to "Manual Configuration" in the "Network Interface" settings, but I changed it to DHCP. Is that OK?

Are there any other settings I need to change to use it?

By the way, it shows as 1 Gbps because I haven’t upgraded my switches yet.

DS218+_DLink_Adapter

bb-qq commented 2 years ago

Is that OK?

It is OK. Many people use this driver with DHCP.