I'll start with the current symptoms. /proc/scsi/scsi shows the following:
Attached devices:
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: A F Model: S A S A 2 6 Rev: 1 5
Type: Scanner ANSI SCSI revision: 02
and /var/log/messages shows:
Oct 11 20:05:23 localhost kernel: aha152x0: vital data: PORTBASE=0x340, IRQ=10,
SCSI ID=7, reconnect=enabled, parity=enabled, synchronous=disabled, delay=100, extended translation=disabled
Oct 11 20:05:23 localhost kernel: aha152x: trying software interrupt, ok.
Oct 11 20:05:23 localhost kernel: scsi0 : Adaptec 152x SCSI driver; $Revision: 1.7 $
Oct 11 20:05:24 localhost kernel: Vendor: AÿFÿ þ þ Model: SþAþSÿAþ ÿ2ÿ6þ þ Rev: 1þ5þ
Oct 11 20:05:24 localhost kernel: Type: Scanner ANSI SCSI revision: 02
What seems to be happening is that every second character is mangled. Sane, of
couse, is completely unable to detect any scanner that it knows about. And even
if it did, who knows what would be happening to any data transmitted through
this interface.
I thought this may be a termination problem: the scanner doesn't come with any
terminator, but the docs state (if you read them very carefully), that you
might need one "if you use a cable longer than the one supplied" (I'm a little
surprised at AGFA supplying the scanner without termination, and, apparently,
just keeping their fingers crossed that it'll work anyway - seems a touch
irresponsible). Anyway, I don't have a terminator, but I've borrowed a
self-terminating Zip drive, and plugged it into the scanner, on the end of the
bus. After this is done, the contents of /proc/scsi/scsi become:
Attached devices:
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: A F Model: S A S A 2 6 Rev: 1 5
Type: Scanner ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 06 Lun: 00
Vendor: I M G Model: Z P 1 0 Rev: J 0
Type: Direct-Access ANSI SCSI revision: 02
So clearly it sees the Zip drive, but we have the same problem with losing
every second character. This apparently means that either termination is not the
problem, or the termination of the Zip drive doesn't work.
So that's what's going wrong now. Any ideas, anyone? Getting this far was
non-trivial; when (if?) I finally get it going I shall write up my memoirs
for the benefit of future sufferers. I had to switch off the plug-and-play
support on the board using a DOS utility supplied with the scanner; which
meant I had to borrow a Win95 boot floppy so I could run the DOS program.
I also had to remove the jumper from the board so it used I/O 340, and set
it to use IRQ 10. And tell my BIOS that IRQ 10 is not plug-and-play.
Before I did all of that, I couldn't even get the SCSI driver (aha152x) to
load at all.
I'd be very grateful for any suggestions about this. I gather many people have
this scanner working under Linux - please do tell me how you did it.
Thanks,
Tim Allen
-----------------------------------------------
Tim Allen
Proximity Pty Ltd http://www.proximity.com.au
-----------------------------------------------
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com