New Device Request: LLANO Wired 2500Mbps USB C 2.5G External Network Card Type-A To RJ45 #142
Comments
|
Hi @zhuanyi , just had a look on the debug output of yours. with best regards Jens |
|
Hi @zhuanyi , took a look into the code: rtl8152_get_version() does this when the return value is not known. The version query is masked (0x7cf0, "111110011110000"), so if there is a version and not really 0, we won't see it. So to get closer I would first show the unmasked value. But now we're talking driver hacking, your dongle won't work with this driver. Sorry. with best regards Jens |
|
Mmm...I am afraid you are right... I have shutdown the DS, unplugged the USB hub (almost forgot about it) and then power on the DS again, and this is what I get from the output (after the DS comes back online): but this is what scared me: so I guess it wasn't getting detected after all... Oh well, at least we tried, and thanks a lot for your help! |
|
Also, @jglathe Is there anything I could do to help to make this work though? Never played with driver hacking but I can code in C++ and Python if those helps! |
|
Well it is quite a way to get a working build environment - I haven’t gotten one available, yet. Just looking at the dongle picture I see a further complication: this is a USB type C dongle, not type A like mine. So you will be using some kind of adapter which will have its own electronics in it? Translating between the protocols? It registers as 3.20, not 3.00. This could be enough to let this be a futile exercise. I would suggest to try getting a type A dongle, should be the better way. And with this dongle you have, I would first take a look on a normal current pc if it works with linux. If that is made sure of, it would be time to compare the version of r8152.c used. |
|
I see, thanks for your help, looks like it is definitely beyond my skill level then (I wish I had studied for electrical engineering back in school!) I actually bought the USB-A type (they have both and I used USB-A as that's what my DS has. |
|
Still worth a try on a „normal“ PC or laptop with linux on it. |
|
Mmm...you actually gave me a hint here...I do have an old laptop running Minx Linux (a fork of Ubuntu) and when I plugged the dongle into the only USB port it has, this is what I saw in dmesg: And the dongle worked without any installation required (I have disabled Wifi to make sure it wasn't wifi connecting). So somehow it does gets recognized in Ubuntu even with that weird S/N. (I assume it was negotiated to 1Gbps because of the USB 2.0 connector the old laptop has). |
|
A bit more progress....so all my tests previously done were plugged into the back of the DS, but I decided to give the front USB a try and after stop and start the driver package in Package Centre, it seems to work, although only at the Gigabit speed as the front panel port for DS412+ is only USB 2.0.
So I guess there must be something different between the USB at the front vs at the back (other than 2.0 vs 3.0). |
|
Hey not bad, congratulations. But now this will not get easier: what do we know about the USB3 chip? It is not part of the ATOM CPU, so would probably be some kind of extra chip... ASMedia or something. What does lspci say? |
|
OTOH, do you have a USB3 hub you could plug in? Could also be one of those pesky R8153 USB dongles with 3 USB3 slots. Maybe this masks the protocol deficiency/quirk of the host chip. |
|
mmm....my guess is the one in the red box is the USB 3.0 ports since the two attached USB external HDDs are connected to it:
this is my lspci output....not sure if the numbers would make any sense to me though :( |
Yap I do, that was the dongle with the Gigabit Ethernet port that initially confused me! Good point, let me give that a shot! |
|
Etron Technology, Inc. EJ168 USB 3.0 Host Controller Hardware ID PCI\VEN_1B6F&DEV_7023 |
|
Incredible, worked!!!
Kinda weird to have a LAN4, but no complains!!! Thanks for your help!!!! |
|
Well. I did some search, and... the fixes in https://github.com/torvalds/linux/blob/master/drivers/usb/host/xhci-pci.c#L258 are dangerously close to the hardware release date of the DS-412+. Some are newer. Which could mean that they're not in the kernel that is used by it. |
Ah I see....I don't have any hope that DSM6 will still be updated, hopefully one day people would be able to port DSM 7 into my old NAS...but for now at least something works.
Wouldn't have been possible without your help! Has been spending days trying to figure it out, thanks again! Just tried to copy a large file to my laptop (with another USB-C 2.5G adapter plugged in and connected to my DS via a QNAP 2.5G hub), speed is incredible! |
|
I get up to 2Gb/s writing while doing image backup from my living room PC, which is kinda „main“. The board has a RTL8125 on it, backbone is 5GB/s (two stories down to the NAS). You get used to these kinds of speeds, just about halves backup time. But: I also got a 10Gb link in a DS1517+, with mainly RAID6 arrays, and writing speed would barely creep above 100MiB/s. Reading can top the 250MiB/s of the receiving interface, but takes some time. Horses four courses, I guess. |
Description of the problem
VID: 0bda
PID: 8156
REV: 31.00
Product with the different brand but same VID, PID and REV seems to work as reported in here: #115. (unsure DSM version though).
The light on the converter is on and there is occasional blinking but DSM is showing disconnected and no valid IP was obtained. Also the hub I connect DS to is blinking yellow on the port connected with DS which indicates the speed negotiated is less than 2.5Gbps.
Description of your products
Description of your environment
Connect via QNAP hub to laptop which has another 2.5G USB-C adapter with the same chipset (same VID/PID and REV number)
QNAP hub is QSW-1105-5T
Cable is Cat. 5E
Output of
dmesgcommandThis is the part I think that's relevant only as the full dmesg output is quite long, feel free to let me know if you'd like me to send a full output.
Output of
lsusbcommandNote that there appears to be 2 RT devices, one of them was another dongle I have previously plugged in but is no longer active and attached to the DS.
Output of
ifconfig -acommandeth2 is what I'd expect the dongle device would be.
The text was updated successfully, but these errors were encountered: