On 09/02/14 23:39, grarpamp wrote:
Is there a way to actively probe out for a device from a usb port?

[The other ports act the same way... a usbstick is recognized,
this device isn't.]

The problem was bad cable mating... power pair connected but
data pair did not. Cutting back some plastic shroud let USB
seat further in and fixed it. Mountable and files accessible now.

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...

# camcontrol devl -v
scbus3 on umass-sim0 bus 0:
<NAME 3.00> at scbus3 target 0 lun 0 (da0,pass2)
<NAME 3.00> at scbus3 target 0 lun 1 (da1,pass3)
# ls /dev/*da*
/dev/da0        /dev/da0s1      /dev/da1
# dd if=/dev/da1 of=/dev/null
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...]

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

Here's the full LUN / port issue log...


There is a quirk to force a single LUN:

usbconfig -d X.Y add_quirk UQ_MSC_NO_GETMAXLUN


freebsd-usb@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Reply via email to