From owner-freebsd-usb@FreeBSD.ORG Wed Sep 3 05:17:02 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 202C0B07; Wed, 3 Sep 2014 05:17:02 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D469B1C57; Wed, 3 Sep 2014 05:17:01 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 142431FE027; Wed, 3 Sep 2014 07:16:59 +0200 (CEST) Message-ID: <5406A44B.2000209@selasky.org> Date: Wed, 03 Sep 2014 07:16:59 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: grarpamp , freebsd-usb@freebsd.org Subject: Re: USB storage device not recognized References: <540300A7.6050505@selasky.org> <54040827.5060002@selasky.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2014 05:17:02 -0000 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: > at scbus3 target 0 lun 0 (da0,pass2) > 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: 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