On Sun, Oct 09, 2016 at 06:20:03PM -0400, fred roller wrote: > On Sun, Oct 9, 2016 at 5:32 PM, Jon LaBadie <jonfu@xxxxxxxxxx> wrote: > > > Anybody recognize this error message? > > > > usb 2-1.5: string descriptor 0 read error: -22 > > > > According to: > > http://www.keil.com/pack/doc/mw/USB/html/_u_s_b__string__descriptor.html > > "String descriptors (USB_STRING_DESCRIPTOR) are optional and add human > readable information to the other descriptors. If a device does not support > string descriptors, all references to string descriptors within device, > configuration, and interface descriptors must be set to zero." > > Just sounds like your system doesn't know and is telling you as much. Look > along your second usb bus line, especially if you have a card reader or > some such. > > -- Fred On Sun, Oct 09, 2016 at 03:21:01PM -0700, Samuel Sieb wrote: > On 10/09/2016 02:32 PM, Jon LaBadie wrote: > > Anybody recognize this error message? > > > > usb 2-1.5: string descriptor 0 read error: -22 > > > I've seen messages like that often. I think some devices don't support all > the descriptors the kernel tries to read or something like that. You can > find out which device it is by going to /sys/bus/usb/devices/2-1.5 and > checking out some of the info there. Particularly try "cat product". Well that got me further, thanks. No "product" listing, but there are vendor and product ids. The device is my "internal" BlueTooth adapter made by Lite-On. Based on adjacent product codes, it uses an Atheros chip. Obviously using a usb interface, much as a BT-dongle would. Sometime when I have the case open for dust bunny removal I'll check to see if the BT adapter hooks into a MB USB header. Though seldom used, the BT device was functioning the few times I've tried it, so I guess I'll just consider the boot message an informational warning. Thanks again, jon -- Jon H. LaBadie jonfu@xxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
