Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Sep 2014 07:16:59 +0200
From:      Hans Petter Selasky <hps@selasky.org>
To:        grarpamp <grarpamp@gmail.com>, freebsd-usb@freebsd.org
Cc:        freebsd-hardware@freebsd.org
Subject:   Re: USB storage device not recognized
Message-ID:  <5406A44B.2000209@selasky.org>
In-Reply-To: <CAD2Ti2_XtJUdkMTaSqp6WMo3pF9oazj7t66BzQ6udn_PtXDkfg@mail.gmail.com>
References:  <CAD2Ti2_CZzvB2zudHBgc5K%2BqCnt2Mz8y9A6MrgYnPPqE646J=g@mail.gmail.com> <540300A7.6050505@selasky.org> <CAD2Ti2_KsGWiEY3rh73C8L62fkitTeZosN7p%2Bo%2B_i6w5m_BETA@mail.gmail.com> <54040827.5060002@selasky.org> <CAD2Ti28Y5i5MQjc8A%2B3ib1PDW8crgK7v05xQo39OP94bD0f=iA@mail.gmail.com> <CAD2Ti2_XtJUdkMTaSqp6WMo3pF9oazj7t66BzQ6udn_PtXDkfg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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...
>

Hi,

There is a quirk to force a single LUN:

usbconfig -d X.Y add_quirk UQ_MSC_NO_GETMAXLUN

--HPS




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5406A44B.2000209>