From owner-freebsd-usb@FreeBSD.ORG Thu Sep 4 06:24:19 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE2A5EB0; Thu, 4 Sep 2014 06:24:19 +0000 (UTC) Received: from mail-vc0-x22d.google.com (mail-vc0-x22d.google.com [IPv6:2607:f8b0:400c:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AF94137A; Thu, 4 Sep 2014 06:24:19 +0000 (UTC) Received: by mail-vc0-f173.google.com with SMTP id im17so10077111vcb.18 for ; Wed, 03 Sep 2014 23:24:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+3ka/BD0EaKAuzmoIp2+YIJZHgmTSHYBa93JfQpctY0=; b=NLEUpqBuVtP2OSb/pByRjw4GlC0XyvkR6JHgahuIQUMgtoK31SiuzR7HKYPLle80mM C16CALVAYC64MZYB1lh0Ia9aHVOWrNU2/xrdIe9t87wx2TxN80GE23SaWNyi3EnFHkSL KFEVh82YucyqiyRMuew5ohBlD+IN+044+KL0rI3QyMd1nNIgy7LhkiejY/M2Zr0Wsk1X 3P7goiS84DFZHmWVavK4ZbqPlLWZ3L1KtHfRXOWLtRDM7XX3AjPobtA27Bq/jJwVLjJV WTNEV2dcKn/GWlZQD2EChFCiaWtICLV5yyR4ia9g00CCsPhtvn9NyBYp9/MMqzqWxPiB oeMA== MIME-Version: 1.0 X-Received: by 10.52.148.2 with SMTP id to2mr1545750vdb.38.1409811858477; Wed, 03 Sep 2014 23:24:18 -0700 (PDT) Received: by 10.221.64.74 with HTTP; Wed, 3 Sep 2014 23:24:18 -0700 (PDT) In-Reply-To: <5406A44B.2000209@selasky.org> References: <540300A7.6050505@selasky.org> <54040827.5060002@selasky.org> <5406A44B.2000209@selasky.org> Date: Thu, 4 Sep 2014 02:24:18 -0400 Message-ID: Subject: Re: USB storage device not recognized From: grarpamp To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 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: Thu, 04 Sep 2014 06:24:20 -0000 >>> 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: 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.