Re: USB-to-SCSI converter

2000-11-14 Thread James FitzGibbon

* Chris Dillon ([EMAIL PROTECTED]) [001113 08:22]:

 Since you can select the LUN and not the ID, maybe they've mapped SCSI
 ID0:LUN0 to ID0:LUN0 (duh), ID1:LUN0 to ID0:LUN1, ID2:LUN0 to
 ID0:LUN2, and so on, which would explain why we only see a device at
 ID0:LUN0 if we aren't looking at the remaining LUNs (are we?).  This
 would mean that you can't use multi-LUN devices with the USB-SCSI
 converter, but that is much more acceptable than only being able to
 use ID0 with it.

I think this is what they do, as my test with a multi-LUN CD changer which
works find as a SCSI device only shows up as one CD-ROM under both Windows
and BSD.  Time to hit up Microtech support to see if they'll at least admit
that this is what their driver does.  The question then is if we are to
implement this kind of ID-to-LUN mapping in the umass driver, what do we
predicate that behaviour on ?

-- 
j.

James FitzGibbon   [EMAIL PROTECTED]
Targetnet.com Inc.  Voice/Fax +1 416 306-0466/0452


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-13 Thread Nick Hibma


In that case it might be that they are using some kind of private
command to set the SCSI subsequently to different IDs.

I'll check whether I have the device here and if so, I will try and
snoop that command off the wire.

Thanks for the pointer!

Nick

On Sun, 12 Nov 2000, James FitzGibbon wrote:

 * Nick Hibma ([EMAIL PROTECTED]) [001112 06:01]:
 
  I don't know. The only thing  I know is that the protocol on the USB
  wire does not let you select the SCSI id, just the LUN.
 
 I've confirmed that under Windows this cable works with any SCSI ID, but
 only if you install the Microtech driver.  Otherwise, it doesn't show up
 (i.e. identical to FBSD).  Presuming that their driver is actually just a
 ID mapping layer, would the same thing be feasible under BSD?
 
 I'll fire off a note to their support people and see if they can at least
 confirm my line of thinking here.
 
 -- 
 j.
 
 James FitzGibbon   [EMAIL PROTECTED]
 Targetnet.com Inc.  Voice/Fax +1 416 306-0466/0452
 

--
Qube Software, Ltd. Private:
[EMAIL PROTECTED]  [EMAIL PROTECTED]
 [EMAIL PROTECTED]
http://www.qubesoft.com/   http://www.etla.net/~n_hibma/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-13 Thread Chris Dillon

On Sun, 12 Nov 2000, Nick Hibma wrote:

 I don't know. The only thing I know is that the protocol on the
 USB wire does not let you select the SCSI id, just the LUN.

Since you can select the LUN and not the ID, maybe they've mapped SCSI
ID0:LUN0 to ID0:LUN0 (duh), ID1:LUN0 to ID0:LUN1, ID2:LUN0 to
ID0:LUN2, and so on, which would explain why we only see a device at
ID0:LUN0 if we aren't looking at the remaining LUNs (are we?).  This
would mean that you can't use multi-LUN devices with the USB-SCSI
converter, but that is much more acceptable than only being able to
use ID0 with it.


-- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED]
   FreeBSD: The fastest and most stable server OS on the planet.
   For IA32 and Alpha architectures. IA64 and PowerPC under development.
   http://www.freebsd.org




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-13 Thread James FitzGibbon

* Chris Dillon ([EMAIL PROTECTED]) [001113 08:22]:

 On Sun, 12 Nov 2000, Nick Hibma wrote:
 
  I don't know. The only thing I know is that the protocol on the
  USB wire does not let you select the SCSI id, just the LUN.
 
 Since you can select the LUN and not the ID, maybe they've mapped SCSI
 ID0:LUN0 to ID0:LUN0 (duh), ID1:LUN0 to ID0:LUN1, ID2:LUN0 to
 ID0:LUN2, and so on, which would explain why we only see a device at
 ID0:LUN0 if we aren't looking at the remaining LUNs (are we?).  This
 would mean that you can't use multi-LUN devices with the USB-SCSI
 converter, but that is much more acceptable than only being able to
 use ID0 with it.

I've got a Nakamichi mj-4.8s (4 disc scsi jukebox) at home that I can put in
an external case to test this premise.  It comes up as the chosen ID and
LUNS 0-3.

-- 
j.

James FitzGibbon   [EMAIL PROTECTED]
Targetnet.com Inc.  Voice/Fax +1 416 306-0466/0452


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-13 Thread Wilko Bulte

On Mon, Nov 13, 2000 at 10:38:44AM -0500, James FitzGibbon wrote:
 * Chris Dillon ([EMAIL PROTECTED]) [001113 08:22]:

  On Sun, 12 Nov 2000, Nick Hibma wrote:
  
   I don't know. The only thing I know is that the protocol on the
   USB wire does not let you select the SCSI id, just the LUN.
  
  Since you can select the LUN and not the ID, maybe they've mapped SCSI
  ID0:LUN0 to ID0:LUN0 (duh), ID1:LUN0 to ID0:LUN1, ID2:LUN0 to
  ID0:LUN2, and so on, which would explain why we only see a device at
  ID0:LUN0 if we aren't looking at the remaining LUNs (are we?).  This
  would mean that you can't use multi-LUN devices with the USB-SCSI
  converter, but that is much more acceptable than only being able to
  use ID0 with it.
 
 I've got a Nakamichi mj-4.8s (4 disc scsi jukebox) at home that I can put in
 an external case to test this premise.  It comes up as the chosen ID and
 LUNS 0-3.

And the nice thing is that it is known-good on FreeBSD on plain SCSI. I have
one here on 4.2-beta which works like a charm.

-- 
Wilko Bulte Arnhem, the Netherlands
[EMAIL PROTECTED]   http://www.freebsd.org  http://www.nlfug.nl



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-12 Thread James FitzGibbon

* Nick Hibma ([EMAIL PROTECTED]) [001112 06:01]:

 I don't know. The only thing  I know is that the protocol on the USB
 wire does not let you select the SCSI id, just the LUN.

I've confirmed that under Windows this cable works with any SCSI ID, but
only if you install the Microtech driver.  Otherwise, it doesn't show up
(i.e. identical to FBSD).  Presuming that their driver is actually just a
ID mapping layer, would the same thing be feasible under BSD?

I'll fire off a note to their support people and see if they can at least
confirm my line of thinking here.

-- 
j.

James FitzGibbon   [EMAIL PROTECTED]
Targetnet.com Inc.  Voice/Fax +1 416 306-0466/0452


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-10 Thread James FitzGibbon

* Nick Hibma ([EMAIL PROTECTED]) [001109 17:31]:

 Hm, I missed the zip story. You seem to have all the bits that are
 necessary in your kernel.
 
 Could you compile your kernel/module with UMASS_DEBUG defined and send
 me the output after an attach?

As it turns out, I got it working, but only when the device is on SCSI ID 0. 
Any other SCSI id and the device is not found when I run 'camcontrol rescan
0'

The output is rather large, so I put it on a web server:

http://people.targetnet.com/~james/dmesg.plugin
http://people.targetnet.com/~james/dmesg.rescan

(plugin is the dmesg output when I plugged it into the USB port, and rescan
is the additional output when I ran camcontrol rescan 0).

Thanks.

-- 
j.

James FitzGibbon   [EMAIL PROTECTED]
Targetnet.com Inc.  Voice/Fax +1 416 306-0466/0452


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-10 Thread Nick Hibma


This makes sense as the adapter is not a ful controller, just a cheapo
interface.

You cannot select the SCSI id from the USB driver.

Nick


On Fri, 10 Nov 2000, James FitzGibbon wrote:

 * Nick Hibma ([EMAIL PROTECTED]) [001109 17:31]:
 
  Hm, I missed the zip story. You seem to have all the bits that are
  necessary in your kernel.
  
  Could you compile your kernel/module with UMASS_DEBUG defined and send
  me the output after an attach?
 
 As it turns out, I got it working, but only when the device is on SCSI ID 0. 
 Any other SCSI id and the device is not found when I run 'camcontrol rescan
 0'
 
 The output is rather large, so I put it on a web server:
 
 http://people.targetnet.com/~james/dmesg.plugin
 http://people.targetnet.com/~james/dmesg.rescan
 
 (plugin is the dmesg output when I plugged it into the USB port, and rescan
 is the additional output when I ran camcontrol rescan 0).
 
 Thanks.
 
 -- 
 j.
 
 James FitzGibbon   [EMAIL PROTECTED]
 Targetnet.com Inc.  Voice/Fax +1 416 306-0466/0452
 

--
Qube Software, Ltd. Private:
[EMAIL PROTECTED]  [EMAIL PROTECTED]
 [EMAIL PROTECTED]
http://www.qubesoft.com/   http://www.etla.net/~n_hibma/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-10 Thread Chris Dillon

On Fri, 10 Nov 2000, Nick Hibma wrote:

 This makes sense as the adapter is not a ful controller, just a
 cheapo interface.
 
 You cannot select the SCSI id from the USB driver.

Hmm.. Since I was looking for a "true" USB-SCSI controller, obviously
this thing won't work.  If it only works with devices set to ID 0, it
will never work with a SCSI ZIP drive which only has settings for ID 5
or 6 (which is one thing I would use it with).  Do the Shuttle-based
USB-SCSI adapters have the same limitation?


-- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED]
   FreeBSD: The fastest and most stable server OS on the planet.
   For IA32 and Alpha architectures. IA64 and PowerPC under development.
   http://www.freebsd.org




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-09 Thread Nick Hibma


This is not a problem as the thing works although it displays the
message. Because it does not support the call it gives an indication
that multi LUN devices are not supported.

I have one of these cables and managed to newfs a 4Gb SCSI drive.

Was anything connected to the cable when you connected it?

Nick


 I have a Microtech USB to SCSI converter (see
 http://www.microtechint.com/qs-usbscsi.html for details).
 
 Under Windows (having installed the driver that comes with), everything
 works without issue.  Under BSD, I get this on boot:
 
 umass0: Microtech International, Inc. USB-SCSI-HD50, rev 1.00/1.00, addr 3
 umass0: Get Max Lun not supported (STALLED)
 
 Are there any known workarounds for this problem ? In my particular
 application I won't be using multi-lun devices, but I don't think that
 making a "maxlun=0" assumption is a good thing to do.
 
 Are there any known workarounds for this problem ?
 
 Thanks.
 
 -- 
 j.
 
 James FitzGibbon   [EMAIL PROTECTED]
 Targetnet.com Inc.  Voice/Fax +1 416 306-0466/0452
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-scsi" in the body of the message
 

--
Qube Software, Ltd. Private:
[EMAIL PROTECTED]  [EMAIL PROTECTED]
 [EMAIL PROTECTED]
http://www.qubesoft.com/   http://www.etla.net/~n_hibma/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-09 Thread Chris Dillon

On Thu, 9 Nov 2000, Nick Hibma wrote:

 This is not a problem as the thing works although it displays the
 message. Because it does not support the call it gives an
 indication that multi LUN devices are not supported.
 
 I have one of these cables and managed to newfs a 4Gb SCSI drive.
 
 Was anything connected to the cable when you connected it?

I'm looking for a USB to SCSI converter myself... are there any that
are a little more well-behaved and work great with FreeBSD and Windows
(preferably one that Win98+ will see without having to carry around a
driver disk)?  I doubt I'll ever attach multi-lun devices to it
either, but I don't like my options limited. :-)


-- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED]
   FreeBSD: The fastest and most stable server OS on the planet.
   For IA32 and Alpha architectures. IA64 and PowerPC under development.
   http://www.freebsd.org




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-09 Thread James FitzGibbon

* Nick Hibma ([EMAIL PROTECTED]) [001109 14:52]:

 
 This is not a problem as the thing works although it displays the
 message. Because it does not support the call it gives an indication
 that multi LUN devices are not supported.
 
 I have one of these cables and managed to newfs a 4Gb SCSI drive.
 
 Was anything connected to the cable when you connected it?

Yes, I've tried with a Yahama external CDR and a Syquest Syjet drive.  In
neither case did the device show up on the probe.  I do have "SCSI over USB"
working on the box, since I regularly use a USB zip drive on the same
machine and it comes up as device da0 right after the 'umass-sim0' probe.

Can you share your kernel config and/or dmesg for that 4gb drive you mention
?

Thanks.

-- 
j.

James FitzGibbon   [EMAIL PROTECTED]
Targetnet.com Inc.  Voice/Fax +1 416 306-0466/0452


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-09 Thread Nick Hibma


Which version of the OS? Please update to a recent release of 4-STABLE
if you are not there.

Did you do a camcontrol rescan 0? What does that produce?

All you will need is

kldload usb
kldload cam
kldload umass

or compile with the following options (I am not sure whether the CAM
module is available in stable)

device  scbus
device  da
device  usb
device  umass

Hope this helps.

Nick

On Thu, 9 Nov 2000, James FitzGibbon wrote:

 * Nick Hibma ([EMAIL PROTECTED]) [001109 14:52]:
 
  
  This is not a problem as the thing works although it displays the
  message. Because it does not support the call it gives an indication
  that multi LUN devices are not supported.
  
  I have one of these cables and managed to newfs a 4Gb SCSI drive.
  
  Was anything connected to the cable when you connected it?
 
 Yes, I've tried with a Yahama external CDR and a Syquest Syjet drive.  In
 neither case did the device show up on the probe.  I do have "SCSI over USB"
 working on the box, since I regularly use a USB zip drive on the same
 machine and it comes up as device da0 right after the 'umass-sim0' probe.
 
 Can you share your kernel config and/or dmesg for that 4gb drive you mention
 ?
 
 Thanks.
 
 -- 
 j.
 
 James FitzGibbon   [EMAIL PROTECTED]
 Targetnet.com Inc.  Voice/Fax +1 416 306-0466/0452
 

--
Qube Software, Ltd. Private:
[EMAIL PROTECTED]  [EMAIL PROTECTED]
 [EMAIL PROTECTED]
http://www.qubesoft.com/   http://www.etla.net/~n_hibma/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-09 Thread Nick Hibma


Hm, I missed the zip story. You seem to have all the bits that are
necessary in your kernel.

Could you compile your kernel/module with UMASS_DEBUG defined and send
me the output after an attach?

The 'GetMAXLUN not supported' thing does not make the driver fail, it
makes it just assume that the LUN is always 0.

Nick


On Thu, 9 Nov 2000, James FitzGibbon wrote:

 * Nick Hibma ([EMAIL PROTECTED]) [001109 14:52]:
 
  
  This is not a problem as the thing works although it displays the
  message. Because it does not support the call it gives an indication
  that multi LUN devices are not supported.
  
  I have one of these cables and managed to newfs a 4Gb SCSI drive.
  
  Was anything connected to the cable when you connected it?
 
 Yes, I've tried with a Yahama external CDR and a Syquest Syjet drive.  In
 neither case did the device show up on the probe.  I do have "SCSI over USB"
 working on the box, since I regularly use a USB zip drive on the same
 machine and it comes up as device da0 right after the 'umass-sim0' probe.
 
 Can you share your kernel config and/or dmesg for that 4gb drive you mention
 ?
 
 Thanks.
 
 -- 
 j.
 
 James FitzGibbon   [EMAIL PROTECTED]
 Targetnet.com Inc.  Voice/Fax +1 416 306-0466/0452
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-hackers" in the body of the message
 

--
Qube Software, Ltd. Private:
[EMAIL PROTECTED]  [EMAIL PROTECTED]
 [EMAIL PROTECTED]
http://www.qubesoft.com/   http://www.etla.net/~n_hibma/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: USB-to-SCSI converter

2000-11-09 Thread Nick Hibma


The cable is pretty decent and the fact that it does not support the
call is not a problem.

Nick

On Thu, 9 Nov 2000, Chris Dillon wrote:

 On Thu, 9 Nov 2000, Nick Hibma wrote:
 
  This is not a problem as the thing works although it displays the
  message. Because it does not support the call it gives an
  indication that multi LUN devices are not supported.
  
  I have one of these cables and managed to newfs a 4Gb SCSI drive.
  
  Was anything connected to the cable when you connected it?
 
 I'm looking for a USB to SCSI converter myself... are there any that
 are a little more well-behaved and work great with FreeBSD and Windows
 (preferably one that Win98+ will see without having to carry around a
 driver disk)?  I doubt I'll ever attach multi-lun devices to it
 either, but I don't like my options limited. :-)
 
 
 -- Chris Dillon - [EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD: The fastest and most stable server OS on the planet.
For IA32 and Alpha architectures. IA64 and PowerPC under development.
http://www.freebsd.org
 
 
 

--
Qube Software, Ltd. Private:
[EMAIL PROTECTED]  [EMAIL PROTECTED]
 [EMAIL PROTECTED]
http://www.qubesoft.com/   http://www.etla.net/~n_hibma/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message