From owner-freebsd-usb@FreeBSD.ORG Fri Dec 24 05:00:42 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF8CF106564A for ; Fri, 24 Dec 2010 05:00:42 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5B4E78FC13 for ; Fri, 24 Dec 2010 05:00:41 +0000 (UTC) Received: by fxm16 with SMTP id 16so7344556fxm.13 for ; Thu, 23 Dec 2010 21:00:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=z/1hCH+b2sKkzeg5VodNKlUkRxlXvXVIR7il0Cna7RQ=; b=YZzXjlPmIvjV0fqry1u6qXoMQU6aBL9rr/4Ueq7dt9Nny9kjnzHCV6CZ6hkUjmBuxs OpsBOCIpuZwgUPob06CXPxWwKajPjcujt/I7Ed7qUqwQN1Z6lhhyRPbQSjg5I5lit6L9 PqMBqFs3W2596CzbzMLI0gWczRAW1ZjAiyQjo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=jj4lrrD6IDyeTYdAT0HA824vxzwSldkoQU3rxrUb9JMxytwEenu9soGC9CwxIyFREr t4zoN8ag2u4Qe13ttK3ehu5BNK3T2F2eZj1JGAtURYBphk70km017ZshBpxwS1O7Lqo7 FtK/cKyelxlpWa6/x4RkTh5fuPpg1jdTZLcNY= MIME-Version: 1.0 Received: by 10.223.85.203 with SMTP id p11mr101998fal.108.1293165265751; Thu, 23 Dec 2010 20:34:25 -0800 (PST) Received: by 10.223.114.4 with HTTP; Thu, 23 Dec 2010 20:34:25 -0800 (PST) Date: Thu, 23 Dec 2010 22:34:25 -0600 Message-ID: From: Adam Vande More To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Android 2.2 umass -> da failure X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Dec 2010 05:00:42 -0000 I'm having some trouble get my android phone's usb storage to work. It did work at first and I was able to mount the SD card and transfer files. Something has changed however and I'm not sure what. Here's a dmesg from a failed attempt to assign the device: ugen1.4: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:8:0:-1: Attached to scbus8 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI status: Check Condition (probe0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:24,0 (Invalid field in CDB) (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): SCSI sense: Error code 0x72 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry FreeBSD 8.2-PRERELEASE #5: Thu Nov 25 19:14:00 CST 2010 adam@galacticdominator.com:/usr/obj/usr/src/sys/GENERIC amd64 So as you can see no /dev/da0 is created, although a /dev/passX is. I've got two micro SD cards and both result in the same current symptoms. Perhaps a quirk is needed? I can handle the quirks file well enough to add one, but I don't have the knowledge to know if that is the problem or what particular quirk can resolve it. My usb device is as follows: galacticdominator# usbconfig -u 1 -a 4 dump_device_desc ugen1.4: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x1004 idProduct = 0x61cc bcdDevice = 0x0100 iManufacturer = 0x0003 iProduct = 0x0002 iSerialNumber = 0x0001 bNumConfigurations = 0x0001 ----------------------------------------------------------------------------------------------------------------------------------- Additional info It seems have something to do with how fast your at pressing the "Turn on USB Storage" on the Android interface. After connecting the usb device, if you wait a couple of seconds before pressing "Turn on USB Storage" button you won't be able to get a /dev/daX. camcontrol functions don't seem to work to get a /dev/daX either, a physical unplug, plug-in, quickly press the button is the only way I've found to mount the device. -- Adam Vande More