> >
> > Ok, so it looks like a problem with the scsi-card or driver or the sg driver.
> > I don`t know if the umax backend is ever tested on a big endian machine,
> > but if the inquiry command returns with an error I don't think it is a problem
> > with the umax backend.
> >
>
> As I posted recently, if a problem with the sg driver is
> suspected then the user should download the utility and
> test program tarball from:
> http://www.torque.net/sg
>
> and run "sg_scan -i". This goes through ever SCSI
> device mapped to /dev/sg* and sends an INQUIRY command
> to it and outputs the result. That program should work
> on any linux kernel from from 2.0 to 2.3.8 .
OK. Here is the results from sg_scan -i:
/dev/sga: scsi0, channel=0, id=0, lun=0, type=0
QUANTUM FIREBALL ST2.1S 0F0C, byte_7=0x1a
/dev/sgb: scsi0, channel=0, id=2, lun=0, type=0
QUANTUM FIREBALL ST2100S 0F0D, byte_7=0x1a
/dev/sgc: scsi0, channel=0, id=3, lun=0, type=5
PIONEER CD-ROM DR-U10X 1.07, byte_7=0x10
/dev/sgd: scsi0, channel=0, id=4, lun=0, type=0
QUANTUM FIREBALL ST2100S 0F0J, byte_7=0x1a
/dev/sge: scsi1, channel=0, id=2, lun=0, type=0
SyQuest EZ135S 1_13, byte_7=0x18
/dev/sgf: scsi1, channel=0, id=5, lun=0, type=6
UMAX Astra 1200S V1.3, byte_7=0x0
The output is very similar to ./tools/findscanner:
# ./find-scanner
find-scanner: found scanner "UMAX Astra 1200S V1.3" at device
/dev/scanner
find-scanner: found scanner "UMAX Astra 1200S V1.3" at device /dev/sg5
find-scanner: found scanner "UMAX Astra 1200S V1.3" at device /dev/sgf
> BTW The mapping of SCSI devices to /dev/sg* file names
> is in the same order as those devices appear in
> 'cat /proc/scsi/scsi'.
>
Thanks for the information
Simon
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com