Date: Thu, 28 Feb 2002 07:57:50 +0100 (CET) From: Riccardo Torrini <riccardo@torrini.org> To: Scott Long <scott_long@btc.adaptec.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: usb product identified as ugen Message-ID: <XFMail.20020228075750.riccardo@torrini.org> In-Reply-To: <20020228050540.GA4703@hollin.btc.adaptec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28-Feb-2002 (05:05:40/GMT) Scott Long wrote:
>> Anyway, ugen0 disappear from /dev/ but _no_ umass0 appear,
>> only xpt0...
> The debug trace looks very good.
I think this is the only good news...
> No umass0 device should appear in /dev. Instead, you should
> get a da device. Do 'camcontrol devlist -v' and you should
> see the bus (represented as umass-sim) and a 'da' and 'pass'
> device for the drive.
The only difference in /dev was -ugen{0,0.1,0.2} +xpt0 :(
# camcontrol rescan 0
Re-scan of bus 0 was successful
# camcontrol devlist -v
scbus0 on umass-sim0 bus 0:
scbus-1 on xpt0 bus 0:
< > at scbus-1 target -1 lun -1 (xpt0)
> It also sounds like you have other issues with the device
> not always attaching or detaching correctly.
You mean broken usb, broken device or bad luck?
> This is a weakness of the umass driver, so you'll have to
> experiment a bit to see what works for you.
I'm here. I can _any_ sort of experiment you may need (except
opening case of external hd :-)
Riccardo.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20020228075750.riccardo>