Julian Elischer: |Randall Hopper wrote: |> SCENARIO 1 : SCANNER OFF, BOOT UP FREEBSD, THEN TURN SCANNER ON |> # dmesg | grep uk0 |> # echo < /dev/uk0 |> /dev/uk0: Device not configured. |> # scsi -f /dev/uk0 -d 255 |use scsi -f /dev/rsd0 -r | |remember WHAT scsi device you use is irrelevant. you just need one |that IS there.. (any one).

Oh! [light goes on], OK. Thanks. Now I see the disconnect.

Specifying an already-attached device to reprobe another device not yet attached seemed so odd it just didn't even register.

I just tried this, and this will work for my situation. I have a ZIP on sd0, but unfortunately I have to go dig up a disk to stick in it for "scsi -f /dev/rsd0 -r" not to return "Device not configured".

Now that we're on the same page, you may find my trials getting here a bit amusing, and possibly could help me with where I've gone wrong trying to get -p to work (sounds like that's the best option):

1. Earlier in the this thread, you mentioned:

|use the scsi -r command. you will need to use it against an already |existing device, e.g. /dev/rsd0 |man 8 scsi

By existing, I thought you meant that the special device file existed in /dev). Not that a physical device had been probed and successfully attached to the existing device file (and in the ZIPs case, that a disk had been loaded).

2. In scsi(8), it says this "-r" form of scsi isn't needed in FreeBSD >= 2.1 since "opening a fixed SCSI device has the side effect of reprobing it".

When I reopened the wired-down /dev/uk0, no such reprobe/attach seemed to occur -- it was still "Device not configured".

3. scsi(8) goes on to say in the reprobe paragraph:

and probing with the bus with the -p option should bring on line any newly found devices. See scsi(4) for a description of fixed scsi devices.

a. (nit) scsi(4) didn't even contain the word fixed.

b. Following up on -p (mentioned above), scsi(8) also goes on to say:

The -p option can be used against the "super scsi" device /dev/scsi/super to probe all devices with a given SCSI lun on a given SCSI bus. The bus can be selected with the -b option and the default is 0. The lun can be selected with the -l option and the default is 0. See scsi(4) for a description of the "super scsi" device.

c. It sounded like -p was what I wanted. So to try -p, I built a kernel with SuperSCSI ("su" & "ssc"), but I couldn't figure out how to mknod the "scsi/super" SuperSCSI device. There was no reference to it in MAKEDEV.

So I'm not sure how to use -p, or if it still works. Brian Somers mentioned it earlier in this thread I noticed, so I assume there's "some" way to use it.

|if not try the device ssc (if you configured it in) After that you can |use uk..

This sounds like it'd be the best option for me (so I don't have to go find a ZIP disk to load into my ZIP drive to be able to use "scsi -r").

So I guess my question here is, what device file path do I specify for the "scsi -p" command line?:

# scsi -f /dev/uk0 -p -b 0 -l 6 scsi: unable to open device /dev/uk0: Device not configured # scsi -f /dev/rsd0 -p -b 0 -l 6 scsi: unable to open device /dev/rsd0: Device not configured # cd /dev /dev # sh MAKEDEV ssc ssc - no such device name /dev # sh MAKEDEV scsi/super scsi/super - no such device name /dev # ls -l ssc* scsi/* ls: No match.

Thanks. I appreciate your help!