-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WAVLINK WS-NWU340G-A does not work in DS920+ using driver v2.18.1-1 #436
Comments
Does disconnecting other devices change the situation? |
I just disconnected the other adapter and reset the DiskStation. Still doesn't show. |
@valerie16901 Did you try a clean uninstall of the package? I have the same adapter and it showed up after removing the package, directorys and then i rebooted. After the clean reboot i reinstalled the package and the adapter shows up. I used a 2.5GBe before so i think that was the issue here. I'm using a DS920+ running 7.2.2-72806 and the WL-NWU340G-A with the 2.18.1-1 package. |
@almir1904 I will try that and report back, thank you! |
I observe very similar / same behavior. My setup is DS 920+ with no other USB devices than the network adapter. lsusb looks fine:
dmesg shows similar errors as in the log of @valerie16901:
But I also see some errors and crash dumps (?):
@bb-qq any suggestions or further logs needed? |
@koch86 try to uninstall the package, clean the data folder of the application, reboot and then do a clean install.
with the newly released DSM 7.2.2-72806 Update 1 on the DS920+ its even showing 5000Mbits as supported Link speed
|
@almir1904 thanks for the suggestion, unfortunately no success :-( Removed old package with cleanup of data -> reboot -> installed package again -> reboot
In dmesg there are several errors, seems like driver crashes and the stick is resetting
|
What TypeC-A conversion adapter do you use? |
Description of the problem
Description of your products
Description of your environment
Output of
dmesg
commandOutput of
lsusb
commandOutput of
ifconfig -a
commandThe text was updated successfully, but these errors were encountered: