From owner-freebsd-hardware@FreeBSD.ORG Sun Aug 31 11:01:58 2014 Return-Path: Delivered-To: freebsd-hardware@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 6BC6CE60; Sun, 31 Aug 2014 11:01:58 +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 2E818191C; Sun, 31 Aug 2014 11:01:58 +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 DA3811FE027; Sun, 31 Aug 2014 13:01:55 +0200 (CEST) Message-ID: <540300A7.6050505@selasky.org> Date: Sun, 31 Aug 2014 13:01: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: 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-hardware@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2014 11:01:58 -0000 On 08/30/14 20:42, grarpamp wrote: > The GENERIC 8 STABLE r269631 i386 kernel on a Pentium 4 Prescott > ICH4 era motherboard does nothing when a Sony ICD-PX333 is plugged in. > I believe it should present as mass storage. Other mass storage devices > such as cameras etc work ok in the same USB port. > How can I debug this or send info to you for debugging? > ehci0: > Thx. Hi, Please send output from: usbconfig -d X.Y dump_device_desc dump_curr_config_desc regarding your device. --HPS From owner-freebsd-hardware@FreeBSD.ORG Sun Aug 31 21:38:29 2014 Return-Path: Delivered-To: freebsd-hardware@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 DBED445C; Sun, 31 Aug 2014 21:38:29 +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 8AFBE1CD3; Sun, 31 Aug 2014 21:38:29 +0000 (UTC) Received: by mail-vc0-f173.google.com with SMTP id im17so4697754vcb.32 for ; Sun, 31 Aug 2014 14:38:28 -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=CtCrqQEmwAVNcr4gzGbirSPdNPhSVGZs8iQ8VdU+BH8=; b=HTkGkpMvEXSyt0KRJuMiK9/xs9vihhpNQZG0CgWGbOHkKWOVAlk8RmeTx4QZOiQ1/M ApIEPBciOsQF0/bIazdHhqc86kyx9k9Db4NH8773R5pQsSZglYyOZHkGQGJatk3JWcWx Nm0JwgJFeEy4uLd5KyhQOKeGcgIGaZnSIai9MsVuiLb/JvKYQ9iCdSuZfcsywmCIoGTp KD72pY4BhRpud+FjbZ7NO/eJOH9w+G42BJgGjROf6qelOdgldwxjf08AvMklx4Jaggcr IHMIRLDjywJarQGuUy/09l1r5eYlShtnqhg5MqjXY2dE8/oRn6X8cH5hdB0DmIuOMSQ/ WwGQ== MIME-Version: 1.0 X-Received: by 10.52.61.136 with SMTP id p8mr18711715vdr.15.1409521108532; Sun, 31 Aug 2014 14:38:28 -0700 (PDT) Received: by 10.221.64.74 with HTTP; Sun, 31 Aug 2014 14:38:28 -0700 (PDT) In-Reply-To: <540300A7.6050505@selasky.org> References: <540300A7.6050505@selasky.org> Date: Sun, 31 Aug 2014 17:38:28 -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: Hans Petter Selasky , freebsd-hardware@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2014 21:38:30 -0000 > Please send output from: > usbconfig -d X.Y dump_device_desc dump_curr_config_desc > regarding your device. Nothing happens in verbose dmesg when I plug in the device, other than the device itself turns on. If I plug in another device, such as a USB memory stick to the same port, the stick is accessible. I believe this device is supposed to present as mass storage since similar devices in its class do appear. Anyway, the below output is the same regardless of whether or not the device is plugged in (I used -u 3 to list the entire bus in the case when memory stick is in)... usbdump -v -i usbus3 -f 2 [nothing with device, dumps with memstick] usbconfig -u 3 dump_device_desc dump_curr_config_desc ugen3.1: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0009 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0000 idProduct = 0x0000 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0019 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 bmAttributes = 0x0040 bMaxPower = 0x0000 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0009 bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0008 bInterval = 0x00ff bRefresh = 0x0000 bSynchAddress = 0x0000 From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 1 05:46:13 2014 Return-Path: Delivered-To: freebsd-hardware@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 4F50A78E; Mon, 1 Sep 2014 05:46:13 +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 116C81775; Mon, 1 Sep 2014 05:46:13 +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 E4AA91FE027; Mon, 1 Sep 2014 07:46:10 +0200 (CEST) Message-ID: <54040827.5060002@selasky.org> Date: Mon, 01 Sep 2014 07:46:15 +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> 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-hardware@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2014 05:46:13 -0000 On 08/31/14 23:38, grarpamp wrote: >> Please send output from: >> usbconfig -d X.Y dump_device_desc dump_curr_config_desc >> regarding your device. > > Nothing happens in verbose dmesg when I plug in the device, > other than the device itself turns on. If I plug in another device, such > as a USB memory stick to the same port, the stick is accessible. > I believe this device is supposed to present as mass storage since > similar devices in its class do appear. > Anyway, the below output is the same regardless of whether or > not the device is plugged in (I used -u 3 to list the entire bus > in the case when memory stick is in)... > > usbdump -v -i usbus3 -f 2 > [nothing with device, dumps with memstick] > Hi, Can you send output from "pciconf -lv" maybe there is a USB controller not recognized? --HPS From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 1 16:59:10 2014 Return-Path: Delivered-To: freebsd-hardware@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 203BB51E; Mon, 1 Sep 2014 16:59:10 +0000 (UTC) Received: from mail-vc0-x229.google.com (mail-vc0-x229.google.com [IPv6:2607:f8b0:400c:c03::229]) (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 C13891344; Mon, 1 Sep 2014 16:59:09 +0000 (UTC) Received: by mail-vc0-f169.google.com with SMTP id hq11so5828261vcb.0 for ; Mon, 01 Sep 2014 09:59:08 -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=/2NXylrs6omCXbg3Xc9c/kt5rmzNT6dQuYQIxwXlHJE=; b=XMgwlvLABokvbCrRswXLlcVR5Dttnb31y7aUxRjY1F3hrFQLfFAAoVYEBCM0ZjrQBX uFHQKa6W/rTviBFdrBX6SBl5hyp0TuJT89ZWQ9I3zd4s3tdtVecPE0fsNGr1HieY1rQn bRfCnX4qDjrZUsQ7rtjS7SR5U+n+3D9yva7sf7Pe4e9bde/tW66q82Swwm9uDswCdosZ MUUbUbOY1yJ5R9DVYvu+rWcr2NDCxaoELoIW39NtICC1YIGeSl58llA7ULkrz4COFW22 F5Kh3ORk2JM22pu+RKN13/GBmi0nv/XKwzAP1VtKexFJC6zw5nGTIUwjFvoDdP4jjZfz Qcfg== MIME-Version: 1.0 X-Received: by 10.52.246.198 with SMTP id xy6mr22162905vdc.7.1409590748227; Mon, 01 Sep 2014 09:59:08 -0700 (PDT) Received: by 10.221.64.74 with HTTP; Mon, 1 Sep 2014 09:59:08 -0700 (PDT) In-Reply-To: <54040827.5060002@selasky.org> References: <540300A7.6050505@selasky.org> <54040827.5060002@selasky.org> Date: Mon, 1 Sep 2014 12:59:08 -0400 Message-ID: Subject: Re: USB storage device not recognized From: grarpamp To: Hans Petter Selasky Content-Type: text/plain; charset=UTF-8 Cc: freebsd-usb@freebsd.org, freebsd-hardware@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2014 16:59:10 -0000 > Can you send output from "pciconf -lv" maybe there is a USB controller not > recognized? dmesg and pciconf have them all, the device is always plugged in ehci0. [The other ports act the same way... usbstick recognized, this device isn't.] I should probably try under windows. Is there a way to actively probe out for a device from a usb port? uhci0: port 0xd800-0xd81f irq 16 at device 29.0 on pci0 usbus0 on uhci0 uhci1: port 0xd000-0xd01f irq 19 at device 29.1 on pci0 usbus1 on uhci1 uhci2: port 0xd400-0xd41f irq 18 at device 29.2 on pci0 usbus2 on uhci2 ehci0: mem 0xee080000-0xee0803ff irq 23 at device 29.7 on pci0 usbus3: EHCI version 1.0 usbus3 on ehci0 uhub0: on usbus0 uhub1: on usbus1 uhub2: on usbus2 uhub3: on usbus3 uhci0@pci0:0:29:0: class=0x0c0300 card=0x01471028 chip=0x24c28086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller *1' class = serial bus subclass = USB uhci1@pci0:0:29:1: class=0x0c0300 card=0x01471028 chip=0x24c48086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller *2' class = serial bus subclass = USB uhci2@pci0:0:29:2: class=0x0c0300 card=0x01471028 chip=0x24c78086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller *3' class = serial bus subclass = USB ehci0@pci0:0:29:7: class=0x0c0320 card=0x01471028 chip=0x24cd8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB 2.0 EHCI Controller' class = serial bus subclass = USB From owner-freebsd-hardware@FreeBSD.ORG Tue Sep 2 21:39:04 2014 Return-Path: Delivered-To: freebsd-hardware@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 46889E21; Tue, 2 Sep 2014 21:39:04 +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 E6137182E; Tue, 2 Sep 2014 21:39:03 +0000 (UTC) Received: by mail-vc0-f173.google.com with SMTP id im17so7821519vcb.32 for ; Tue, 02 Sep 2014 14:39:03 -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=Mk9VeXwWq/UcpLlxNixKYEajLN6vZWBGKWQk51pw5sI=; b=lW2EdmeoAkIvyxc4GdFSh7Abd+1dqLUZPF03z/eQMQBq1vbnLvCcQ8CtbHnejwgbBS CXA8jdLVgqPxmSibmJ8L/25ClrJXGR77ctrulEsBWuBI7D2RzDWsMuE+hJYmeOtlleTQ mknULTqSlj/KOZLwY7iv04RUAJih0CMYrqMN9yh+cCTwyMSXKE+3FEPwWb6GAeKmV6S4 7Mg2kQfElZ5vYEMgs0kAg5QTFO3Jpj0YoxedMvgcvvfbyp6v8IyGcuEj1mSak7ROIn5n wKuXa/nSfDD8nDJQSlDAPcO8QEyfL46TihTbd1XVWabvmadftCTksUfqCE3TtPNU0tYV OSwg== MIME-Version: 1.0 X-Received: by 10.220.172.8 with SMTP id j8mr2599494vcz.32.1409693942938; Tue, 02 Sep 2014 14:39:02 -0700 (PDT) Received: by 10.221.64.74 with HTTP; Tue, 2 Sep 2014 14:39:02 -0700 (PDT) In-Reply-To: References: <540300A7.6050505@selasky.org> <54040827.5060002@selasky.org> Date: Tue, 2 Sep 2014 17:39:02 -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: Hans Petter Selasky , freebsd-hardware@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2014 21:39:04 -0000 > 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... k: ugen3.2: at usbus3 k: umass0: on usbus3 k: umass0: SCSI over Bulk-Only; quirks = 0x4000 k: umass0:3:0:-1: Attached to scbus3 k: (probe0:umass-sim0:0:0:0): Down reving Protocol Version from 2 to 0? k: pass2 at umass-sim0 bus 0 scbus3 target 0 lun 0 k: pass2: Removable Direct Access SCSI-0 device k: pass2: Serial Number 0123456789ABCDEF k: pass2: 40.000MB/s transfers k: GEOM: new disk da0 k: da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 k: da0: Removable Direct Access SCSI-0 device k: da0: Serial Number 0123456789ABCDEF k: da0: 40.000MB/s transfers k: da0: 3770MB (7722483 512 byte sectors: 255H 63S/T 480C) k: da0: quirks=0x2 k: da0: Delete methods: k: (probe0:umass-sim0:0:0:1): Down reving Protocol Version from 2 to 0? k: (probe0:umass-sim0:0:0:1): SCSI status error k: (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 00 20 00 00 00 00 k: (probe0:umass-sim0:0:0:1): CAM status: SCSI Status Error k: (probe0:umass-sim0:0:0:1): SCSI status: Check Condition k: (probe0:umass-sim0:0:0:1): SCSI sense: NOT READY asc:3a,0 (Medium not present) k: (probe0:umass-sim0:0:0:1): Error 6, Unretryable error k: pass3 at umass-sim0 bus 0 scbus3 target 0 lun 1 k: pass3: Removable Direct Access SCSI-0 device k: pass3: Serial Number 0123456789ABCDEF k: pass3: 40.000MB/s transfers k: (da1:umass-sim0:0:0:1): SCSI status error k: (da1:umass-sim0:0:0:1): READ CAPACITY(10). CDB: 25 20 00 00 00 00 00 00 00 00 k: (da1:umass-sim0:0:0:1): CAM status: SCSI Status Error k: (da1:umass-sim0:0:0:1): SCSI status: Check Condition k: (da1:umass-sim0:0:0:1): SCSI sense: NOT READY asc:3a,0 (Medium not present) k: (da1:umass-sim0:0:0:1): Error 6, Unretryable error k: da1 at umass-sim0 bus 0 scbus3 target 0 lun 1 k: da1: Removable Direct Access SCSI-0 device k: da1: Serial Number 0123456789ABCDEF k: da1: 40.000MB/s transfers k: da1: Attempt to query device size failed: NOT READY, Medium not present k: da1: quirks=0x2 k: da1: Delete methods: k: GEOM: new disk da1 k: (da1:umass-sim0:0:0:1): SCSI status error k: (da1:umass-sim0:0:0:1): READ CAPACITY(10). CDB: 25 20 00 00 00 00 00 00 00 00 k: (da1:umass-sim0:0:0:1): CAM status: SCSI Status Error k: (da1:umass-sim0:0:0:1): SCSI status: Check Condition k: (da1:umass-sim0:0:0:1): SCSI sense: NOT READY asc:3a,0 (Medium not present) k: (da1:umass-sim0:0:0:1): Error 6, Unretryable error k: Opened disk da1 -> 6 k: (da1:umass-sim0:0:0:1): SCSI status error k: (da1:umass-sim0:0:0:1): READ CAPACITY(10). CDB: 25 20 00 00 00 00 00 00 00 00 k: (da1:umass-sim0:0:0:1): CAM status: SCSI Status Error k: (da1:umass-sim0:0:0:1): SCSI status: Check Condition k: (da1:umass-sim0:0:0:1): SCSI sense: NOT READY asc:3a,0 (Medium not present) k: (da1:umass-sim0:0:0:1): Error 6, Unretryable error k: Opened disk da1 -> 6 k: ugen3.2: at usbus3 (disconnected) k: umass0: at uhub3, port 5, addr 2 (disconnected) k: (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 0 refs k: (da0:umass-sim0:0:0:0): removing device entry k: (pass2:umass-sim0:0:0:0): lost device k: (pass2:umass-sim0:0:0:0): removing device entry k: (da1:umass-sim0:0:0:1): lost device - 0 outstanding, 0 refs k: (da1:umass-sim0:0:0:1): removing device entry k: (pass3:umass-sim0:0:0:1): lost device k: (pass3:umass-sim0:0:0:1): removing device entry From owner-freebsd-hardware@FreeBSD.ORG Wed Sep 3 05:17:02 2014 Return-Path: Delivered-To: freebsd-hardware@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-hardware@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: General discussion of FreeBSD hardware 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 From owner-freebsd-hardware@FreeBSD.ORG Thu Sep 4 06:24:19 2014 Return-Path: Delivered-To: freebsd-hardware@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-hardware@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: General discussion of FreeBSD hardware 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.