Date: Fri, 24 Dec 2010 10:58:50 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-usb@freebsd.org Cc: mav@freebsd.org Subject: Re: Android 2.2 umass -> da failure Message-ID: <201012241058.50100.hselasky@c2i.net> In-Reply-To: <AANLkTing%2BuW2J4eq137%2BXnWnsGBD7tNac--Qq7a=dNgd@mail.gmail.com> References: <AANLkTinMx-zNRFj%2BZLN2qP_Pa5whU8t0d2LteS%2Bjrf%2Ba@mail.gmail.com> <AANLkTing%2BuW2J4eq137%2BXnWnsGBD7tNac--Qq7a=dNgd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 24 December 2010 07:21:57 Adam Vande More wrote: > On Thu, Dec 23, 2010 at 10:34 PM, Adam Vande More <amvandemore@gmail.com>wrote: > > 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. > > Also the partition table doesn't seem to be correctly recognized after > this. Only /dev/da0 is present, not /dev/da0s1 Once I preform an action > on /dev/da0 then the slice is seen. This there a way to automate this > tasting? Can you try 9-current. I think there might be a fix for this issue there. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201012241058.50100.hselasky>