Grant <emailgrant <at> gmail.com> writes:
> > Look at: > > /usr/share/misc/* > > to get an idea of the numberings for various > > hardware devices. > lsusb shows the following for my SSD: > Bus 004 Device 002: ID 174c:07d1 ASMedia Technology Inc. > I updated to hwids-99999999 but 174c:07d1 doesn't match any device in > /usr/share/misc/usb.ids that I can see. Could that be the problem? Hard to say. These sort of things are difficult to flush out. You do need to find a dev in this area and make inqueries, and just keep googling..... and digging. Look for a firmware dev that works for the company, or open up a trouble ticket with the company that manufactures the device (if you can find them). > I also noticed these messages in dmesg after removing and reloading > the xhci_hcd module: > Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK > Parent hub missing LPM exit latency info. Power management will be > impacted. This stuff is complicated hooking up SD(hard drives) that are connected via the usb(3) buss. I use to have some usb buss analyzer software, but it was MS based and I do not have access to such fancy commercial software at this time. It looks like you've found the error trail. How to fix it, from my experience, is all about using googl until you find somebody with the right knowledge. I'd suggest going to the dev (kernel docs) for that part of the kernel for these things to find somebody qualified to really help you. Somebody to advise you who really knows what's going on. Read the comments for the various parts of the kernel and track down the maintainers or devs..... Sorry I could not be of more help. Good Hunting! James
