From owner-freebsd-current@FreeBSD.ORG Sun Dec 8 21:54:30 2013 Return-Path: Delivered-To: current@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 E3B19658 for ; Sun, 8 Dec 2013 21:54:29 +0000 (UTC) Received: from mail-bk0-x235.google.com (mail-bk0-x235.google.com [IPv6:2a00:1450:4008:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7474A1283 for ; Sun, 8 Dec 2013 21:54:29 +0000 (UTC) Received: by mail-bk0-f53.google.com with SMTP id na10so1085484bkb.12 for ; Sun, 08 Dec 2013 13:54:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=aAOOlqp8jjLmh1CO1S8GLUhtG/FLdQOpikBccjrERd8=; b=jss9NrNhCX85r/4C3Shs73x2EVyI7mbap6wxUQGxFMrtGy27Clvd+TfX/rGPTBOHlg ZOZCGHj7WMCUCI3Kl9HpzLTv7KTbxfbAE5ZxrEFz7ZZwlDk2phzam8NVf5iEG72z7WzJ 5oRZMLwjP1GQ6DNgUf2NHjAJntkeNgu7Ye/oyT3Yl5ePMOAUoDMon8KYOHfw2kOeO51q aGRf1zpc73BnWQ2UZ0pNew0W0huFBM4tgwZGVvNI+qpx1LuJc2W33aMDB8tYFvcqjpEP UTui8LhniOXDg8Hjuw2q88erTx2KluArB/wcYoQ6lGwMRlOAetaLT+awY4223BOtlyHu A8dQ== X-Received: by 10.204.165.79 with SMTP id h15mr102292bky.148.1386539667783; Sun, 08 Dec 2013 13:54:27 -0800 (PST) Received: from ubm.strangled.net (g229022230.adsl.alicedsl.de. [92.229.22.230]) by mx.google.com with ESMTPSA id z6sm6555484bkn.8.2013.12.08.13.54.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 08 Dec 2013 13:54:27 -0800 (PST) Date: Sun, 8 Dec 2013 22:54:25 +0100 From: Marc UBM To: current@freebsd.org Subject: Re: Problem with ebook reader on usb Message-Id: <20131208225425.2953c653576e55db2855a88c@gmail.com> In-Reply-To: <20131208224433.a8cfe7924fd540e8f4d1484c@gmail.com> References: <20131208224433.a8cfe7924fd540e8f4d1484c@gmail.com> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Dec 2013 21:54:30 -0000 On Sun, 8 Dec 2013 22:44:33 +0100 Marc "UBM" Bocklet wrote: > > Hiho! :-) > > I got myself a new ebook reader (Onyx M92), but encountered a strange > problem when connecting it to my freebsd machine. Shortly after > mounting it, the device gets disconnected (causing the mounted storage > to disappear). There is no such behavior with Windows 7. > > uname -a: > FreeBSD xxx 11.0-CURRENT FreeBSD 11.0-CURRENT #11 > r258254M: Sun Nov 17 13:38:01 CET 2013 > xxx:/usr/obj/usr/src/sys/SUBMARINE_SMP amd64 > > > The device identifies as follows: > > Dec 2 17:45:51 ubm kernel: ugen4.2: with fsl-usb2-udc> at usbus4 > > Dec 2 17:45:51 ubm kernel: umass0: on usbus4 > > Dec 2 17:45:51 ubm kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun > 0 > > Dec 2 17:45:51 ubm kernel: da0: > Removable Direct Access SCSI-2 device > > Dec 2 17:45:51 ubm kernel: da0:40.000MB/s transfers > > Dec 2 17:45:51 ubm kernel: da0: 3156MB (6463552 512 byte sectors: 255H > 63S/T 402C) > > Dec 2 17:45:51 ubm kernel: da0: quirks=0x2 > > I tried setting (widly guessing): > hw.usb.power_timeout: 30 -> 0 > hw.usb.no_cs_fail: 0 -> 1 > > but to no avail. > > Setting "hw.usb.debug: 1" yields no additional output. > > usbconfig dump_device_desc yields: > ugen4.2: fsl-usb2-udc> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x0525 > idProduct = 0xa4a5 > bcdDevice = 0x0326 > iManufacturer = 0x0001 fsl-usb2-udc> iProduct = 0x0002 > iSerialNumber = 0x0003 <3230204E6F76> > bNumConfigurations = 0x0001 > > Anybody got any ideas? :-) Some further data: the mass storage usually remains mounted if there is NO read/write activity. Read activity seems to immediately cause a disconnect. Writing behaves differently, I just managed to copy a 1.4M file onto it, it disconnected seconds after finishing. The copied file is not corrupted. Bye Marc