coolinx

Hi Gianvito, This topic is addressing a very specific issue about the absence of the USB1.1 driver in DSM7 for the HP N54L, or also the N40L and N36L gen7 microserver. For other servers like your gen8 you can follow the instructions on enabling USB support on DSM7 in general. The jadahl.com site was working for me earlier this week, so I'd give it some time...

Ok, I found a fix and a potential workaround for this: I successfully used the fix proposed in this French topic: https://xpenology.com/forum/topic/18601-tuto-hp-n54l-gen7-dsm-7-et-dsm-623/ Which is translated to English here: https://xpenology-com.translate.goog/forum/topic/18601-tuto-hp-n54l-gen7-dsm-7-et-dsm-623/page/1/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=nl#comments So you need this driver: ohci-hcd.ko and DS3615XS. I used DSM 7.1 and it works great for me. With these instructions you can complete the process: https://mariushosting.com/synology-how-to-add-usb-support-on-dsm-7/ The workaround I have not completely tested, but it could work: The cause of this issue is that DSM7 does not have a driver for the HP N54L Microserver USB 1.1 ports. So you see the 480Mbit devices, but not the 12Mbit. If you connect a USB2 hub to the server and connect the 12Mbit devices like Zwave, Zigbee sticks, they should show up with lsusb.

I'm suffering the same: I have the most basic configuration; tinycore to install DS3622xs+ with DSM 7.1-42661 Update 1 on my N54L hardware. I use the "dresden ConBee II" zigbee stick which is among the most used zigbee sticks around, so nothing exotic. This Conbee has been working fine for some years on this hardware with DSM 6.2. Just after migrating to DSM7.1 it is not detected anymore. I believe the issue is not about drivers but starts at plugging in the stick. There is no logfiles in the /var/log that have any new line related to usb device. Also dmesg does not show anything. lsusb shows only the tinycore usb drive: lsusb |__usb1 1d6b:0002:0404 09 2.00 480MBit/s 0mA 1IF (ehci_hcd 0000:00:12.2) hub |__usb2 1d6b:0002:0404 09 2.00 480MBit/s 0mA 1IF (ehci_hcd 0000:00:13.2) hub |__2-3 f400:f400:0110 00 2.00 480MBit/s 300mA 1IF (Kingston DataTraveler 2.0 408D5CE57214B0806957D11E) |__usb3 1d6b:0002:0404 09 2.00 480MBit/s 0mA 1IF (ehci_hcd 0000:00:16.2) hub So it is as if the system just not detects it being inserted. I tried the following: Insert a usb disk in the N54L with dsm7.1; this is registered by lsusb and dmesg shows lines about this action. Inserted the Conbee stick in a real synology running DSM7.1; The lsusb command shows the Conbee stick (so even without drivers, it is detected) Inserted the Conbee stick in an arpl xpenology DVA1622 with DSM7.1; It is shown by lsusb like this: |__usb1 1d6b:0002:0404 09 2.00 480MBit/s 0mA 1IF (ehci_hcd 0000:00:1a.0) hub |__1-1 8087:0020:0000 09 2.00 480MBit/s 0mA 1IF ( ffffffd1ffffffb2ffffffdbffffffa0) hub |__1-1.1 1cf1:0030:0100 02 2.01 12MBit/s 100mA 2IFs (dresden elektronik ingenieurtechnik GmbH ConBee II DE2486521) |__1-1.5 0409:005a:0100 09 2.00 480MBit/s 100mA 1IF ( ffffffd1ffffffb2ffffffdbffffffa1) hub |__1-1.5.4 f400:f400:0100 00 2.00 480MBit/s 200mA 1IF (Kingston DataTraveler G2 001372982BA9EA51361D0147) |__usb2 1d6b:0002:0404 09 2.00 480MBit/s 0mA 1IF (ehci_hcd 0000:00:1d.0) hub |__2-1 8087:0020:0000 09 2.00 480MBit/s 0mA 1IF ( ffffffd1ffffffb2ffffffdbffffffad) hub |__2-1.1 08ff:2550:1900 ff 2.00 12MBit/s 100mA 1IF ( ffffffc6ffffffa9ffffffdaffffffb4) |__2-1.3 0408:1322:1203 ef 2.00 480MBit/s 168mA 2IFs (QCM USB Webcam ffffffd9ffffffb8ffffffdbffffffb9) |__2-1.4 1690:0741:5276 e0 2.00 12MBit/s 0mA 2IFs ( ffffffd1ffffffb2ffffffdbffffffa2) Interesting is that it found also the built in webcam on that machine. So the Conbee stick is detected in other machines with DSM7.1, both real synology and xpenology. I did notice that on the N54L with dsm7.1 only usb drives are detected with lsusb. If I insert a usb wifi adapter or something else, it is not shown. Perhaps some restriction on low level that blocks all except usb drives? Maybe a bios setting I need to change? I wonder if the topic starter has ever managed to fix this. @blamaster