Opened 4 years ago
Closed 4 years ago
#1488 closed enhancement (worksforme)
JMicron 152d:0578 USB 3.0 Bridge needs -d sat
Reported by: | János Szigetvári | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Release 6.6 |
Component: | drivedb | Version: | 6.6 |
Keywords: | usb | Cc: |
Description
Similarly to item #338 (ticket) I have an Orico USB 3.0 SATA enclosure that has a JMicron chipset.
This ID is listed in drivedb.h but it is not useable with -d usbjmicron (failed: No device connected)
It works fine with -d sat.
I believe this is already fixed in the latest release, but when I do an update-smart-drivedb, my 6.6 smartmontools will normally not get that updated drive information.
Change History (7)
comment:1 by , 4 years ago
Keywords: | usb added |
---|---|
Milestone: | → undecided |
comment:2 by , 4 years ago
Yes, sure. I have two such enclusres, both show the same output:
Bus 002 Device 021: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x152d JMicron Technology Corp. / JMicron USA Technology Corp. idProduct 0x0578 bcdDevice 2.04 iManufacturer 1 JMicron iProduct 2 External USB 3.0 iSerial 3 201703310007F bNumConfigurations 1
follow-up: 4 comment:3 by , 4 years ago
Further investigation shows that this USB ID was already added in r4482 which should be included in smartmontools 6.6 (r4594).
Please try smartctl -P showall 0x152d:0x0578
.
Output should be:
Drive found in smartmontools Database. Drive identity strings: MODEL: 0x152d:0x0578 FIRMWARE: (any) match smartmontools Drive Database entry: USB Vendor:Product: 0x152d:0x0578 USB bcdDevice: .* USB Device: [unknown] USB Bridge: JMicron JMS578 USB Type sat
comment:4 by , 4 years ago
Replying to Christian Franke:
Hi Christian,
Yes, it seems to be working now. Thank you for your help!
comment:5 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:7 by , 4 years ago
Milestone: | undecided → Release 6.6 |
---|---|
Resolution: | → worksforme |
Status: | reopened → closed |
Already fixed in r4482.
Please provide
bcdDevice
information (e.g. under Linux seelsusb
output). This is required to distinguish old and new firmware.The
update-smart-drivedb
tool from 6.6 should still work. The 6.6 branch is still maintained.