Re: lexar usb media failure to attach

On 10 Dec 2004 at 7:10, Vince Vielhaber wrote:

> On Fri, 10 Dec 2004, Dan Langille wrote:
> 
> > On 9 Dec 2004 at 21:44, Vince Vielhaber wrote:
> >
> > > On Thu, 9 Dec 2004, Dan Langille wrote:
> > >
> > > > On the way home from the meeting, I returned the Lexar and purchased
> > > > a Kingston Data Traveller (KUSBDTI/512CR), which I'm pleased to say
> > > > works under 4.10/
> > >
> > > Man I wish you didn't do that.  I've got a LEXAR MEDIA JUMPDRIVE 2000
> > > that does the exact same thing under 4.10.  Before it fails, if I try
> > > camcontrol devlist it shows as (probe0).  If anyone has any suggestions
> > > I'll give them a try.
> >
> > FWIW:
> >
> > # camcontrol devlist
> > <LEXAR JUMPDRIVE ELITE 1000> at scbus0 target 0 lun 0 (probe0)
> >
> > # camcontrol inq 0:0:0
> > camcontrol: cam_open_btl: no passthrough device found at 0:0:0
> 
> So you still have one available.  

I don't understand what that means.

> I need to correct the actual name of this.  umass reports: LEXAR MEDIA
> JUMPDRIVE PRO and camcontrol reports: LEXAR JUMPDRIVE PRO 2000.  FWIW
> it's a 512MB. 
> 
> When umass is in the kernel I don't see it in kldstat.  When it's not
> in the kernel I only get ugen seeing the drive.  Then is this a problem
> in umass or CAM or somewhere else entirely?

Sorry, I don't know.
-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"