Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Mar 2005 11:29:52 -0500
From:      Mikhail Teterin <mi+mx@aldan.algebra.com>
To:        Dan Nelson <dnelson@allantgroup.com>
Cc:        questions@freebsd.org
Subject:   Re: umass0 -- yes, daX -- no?
Message-ID:  <200503161129.53065.mi%2Bmx@aldan.algebra.com>
In-Reply-To: <20050316030414.GA91721@dan.emsphone.com>
References:  <200503151243.19596.mi%2Bmx@aldan.algebra.com> <20050316030414.GA91721@dan.emsphone.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> In the last episode (Mar 15), Mikhail Teterin said:
> > I'm trying to access the file system on a usb memory key. When I
> > insert it, however, kernel duly reports creation of umass0, but not
> > the da1 (da0 is my ZIP drive).
> >
> > According to usbdevs -d, I have:
> >
> > 	addr 1: OHCI root hub, SiS
> > 	  uhub0
> > 	 addr 2: Dell USB Memory Key, M-Systems
> > 	   umass0
>
> You might have a device that's not known in umass's table.  It looks
> like it needs to know the protocol before it will create a da* device;
> try editing /sys/dev/usb/usbdevs and adding a DISKONKEY3 entry (usbdevs
> -dv should print the hex IDs you need), and copy one of the existing
> DISKONKEY array entries in umass.c.

Thanks, I'll try. This is disheartening, however... I was pretty sure, 
anything, that support USB Mass Storage would work "out of the box" :-(

	-mi



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503161129.53065.mi%2Bmx>