Re: USB storage device not recognized

grarpamp <[email protected]>
Newsgroups gmane.os.freebsd.devel.usb,gmane.os.freebsd.devel.hardware
Message-ID <CAD2Ti2_cu0wkmhh2d-7ZbQEDyJh=i69nsGFa7Jn94Rut_qt+ag@mail.gmail.com>
>>> Is there a way to actively probe out for a device from a usb port?

>> New problem... the kernel is picking up what might be a second
>> LUN and throwing a lot of errors. If this LUN is real and intentional
>> I have no idea what purpose it would be for. It is not accessible
>> in a usual way with dd...
>> dd: /dev/da1: Device not configured
>>
>> [Update: This has both soldered flash and microSD slot,
>> the second LUN may be the SD slot. Will test...]

Tested... the second LUN is the SD slot. With card in
both da0 and da1 are then usable in parallel.

> There is a quirk to force a single LUN:
> usbconfig -d X.Y add_quirk UQ_MSC_NO_GETMAXLUN

This quiets the errors when that empty LUN, but I wouldn't add it
as default to the kernel because then it does not detect
card in slot. Here is device quirk if anyone wants...

VID=0x054c PID=0x082a REVLO=0x0100 REVHI=0x0100 QUIRK=UQ_MSC_NO_GETMAXLUN


>> Also the kernel does not print USB 'port' number except on disconnect...
>>   kernel: umass0: at uhub3, port 5, addr 2 (disconnected)
>> It needs to print a corresponding 'connected' line on connect,
>> or perhaps add the 'port' in here...
>>   kernel: umass0: <NAME, class 0/0, rev 2.00/1.00, addr 2> on usbus3


In addition to fixing the above port printf, I believe this sense string
needs to delete the ' to ready change' part.

(probe0:umass-sim0:0:0:1): SCSI status error
(probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 00 20 00 00 00 00
(probe0:umass-sim0:0:0:1): CAM status: SCSI Status Error
(probe0:umass-sim0:0:0:1): SCSI status: Check Condition
(probe0:umass-sim0:0:0:1): SCSI sense: UNIT ATTENTION asc:28,0 (Not
ready to ready change, medium may have changed)
(probe0:umass-sim0:0:0:1): Retrying command (per sense data)

Thanks.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.