Re: Acer scanner + ACARD SCSI controller

Nikolay N. Igotti (inn@sparc.spb.su)
Tue, 14 Sep 1999 14:45:14 -0700 (MST)

On Mon, 13 Sep 1999, Alexey Zilber wrote:

> That's a negative. The scsi card IS a real scsi card, in fact the
> scanner is also a real scsi scanner. It uses the 25 pin scsi connector
> which is popular on the older style MAC's. If you look close, you'll
> see PC/MAC on one of the scanner ports and the scsi symbol on the other.
> If you had a 25 pin active scsi terminator you could stick it on that second 25 pin port.
OK, maybe I'm wrong, but why this card is so cheap, it should be some
useful features removed, what I meant as "not real" :).
Maybe I should use other words :).
> There's no such thing as "standard scsi ini processes",
OK, I meant reset.
> the drivers for ACARD are specifically tailored for their cards. It
> looks to me like the ACARD shipped with the acer scanner is an OEM card
> built specifically for ACER, since ACARD does not sell 25 pin scsi cards
> that are Ultra (kinda retarded that they'd make it 25pin and ultra).
Yrs, I mailed to Acer with request, but no answer yet.

> What I think is happining, and I could be very wrong here, is if you use the Acer drivers, you don't need a terminator. I don't know whether those drivers tell the scanner to autoterminate or if they simply ignore any errors on the bus.
> The errors you get under linux, look like the same kinds of errors
> I would get when I used an older Tekram driver for a new Tekram scsi
> card. I'm sure that the ACARD drivers are not compatible with the
> ACARD shipped with the acer scanner. I also doubt ACARD would directly
> support that card, since it's really acer's responsibility to make a
> driver.
> You can either get a cheapo Tekram card (about $40), or call acer
> and ask them for a driver. If enough people call, I'm sure something
> will get done.
Maybe, but there's no support for Acer backend anyway :).

>
>
>
> >>> "Nikolay N. Igotti" <inn@sparc.spb.su> 9/14/99 12:18:36 AM >>>
>
>
>
> On Mon, 13 Sep 1999, Alexey Zilber wrote:
>
> > Hmmm, could be the fact that that scanner doesn't ship with a terminator. I also noticed a sad fact. The ACARD scsi card that ships with the scanner is not a standard ACARD. I myself experimented with
> > the NT drivers from ACARD, and while they detected the card, they
> > couldn't "see" the scanner, and then promptly hung the NT box.
> > I assume this is the same prob under linux.
> > those drivers weren't designed for that particular card. I could be
> > wrong though. If you have a 25pin active terminator laying about
> > somewhere I'd hook it up to the scanner to test it.
> I think that terminator is embedded to the scaner, as it works good enough
> under Win95. And there's no place on scanner to put it :).
> It connected with SCSI card by LPT-like connector.
> I think that problem is that this scaner/card is not _real_ SCSI device,
> and standard SCSI init process failed on it.
>
> Nikolay.
>
>
> >
> > >>> "Nikolay N. Igotti" <inn@sparc.spb.su> 9/13/99 6:47:37 PM >>>
> > Hello,
> > Recently, I've bought new Acer scaner 620S with ACARD SCSI controller.
> > It works good enough with Win95, but under linux with atp870u.o with
> > turned on scanner insmod atp870u gives:
> > ________________________________________________________________________
> > Sep 13 12:17:23 hell kernel: scsi0 : ACARD AEC-6710/6712 PCI Ultra/W
> > SCSI-3 Adap
> > ter Driver V1.0
> > Sep 13 12:17:23 hell kernel: scsi : 1 host.
> > Sep 13 12:17:25 hell kernel: scsi : aborting command due to timeout : pid
> > 18, sc
> > si0, channel 0, id 2, lun 0 0x12 00 00 00 ff 00
> > Sep 13 12:17:25 hell kernel: workingu=1 last_cmd=2 quhdu=2 quendu=2 r
> > 0= 6 r
> > 1=2c r 2=cf r 3=12 r 4= 0 r 5= 0 r 6= 0 r 7=24 r 8= 0 r 9= 0 r a= 0 r b= 0
> > r c=
> > 0 r d= 0 r e= 0 r f= 0 r10=36 r11=20 r12= 0 r13= 0 r14=18 r15= 2 r16=80
> > r1c=a1 r
> > 1f=37 in_snd= 0 r20= 9 r22= 1
> > Sep 13 12:17:27 hell kernel: scsi : aborting command due to timeout : pid
> > 18, sc
> > si0, channel 0, id 2, lun 0 0x12 00 00 00 ff 00
> > Sep 13 12:17:27 hell kernel: workingu=1 last_cmd=2 quhdu=2 quendu=2 r
> > 0= 6 r
> > 1=2c r 2=cf r 3=12 r 4= 0 r 5= 0 r 6= 0 r 7=24 r 8= 0 r 9= 0 r a= 0 r b= 0
> > r c=
> > 0 r d= 0 r e= 0 r f= 0 r10=36 r11=20 r12= 0 r13= 0 r14=18 r15= 2 r16=80
> > r1c=a1 r
> > 1f=37 in_snd= 0 r20= 9 r22= 1
> > Sep 13 12:17:27 hell kernel: SCSI host 0 abort (pid 18) timed out -
> > resetting
> > Sep 13 12:17:27 hell kernel: SCSI bus is being reset for host 0 channel 0.
> > Sep 13 12:17:27 hell kernel: SCSI host 0 channel 0 reset (pid 18) timed
> > out - tr
> > ying harder
> > Sep 13 12:17:27 hell kernel: SCSI bus is being reset for host 0 channel 0.
> > ________________________________________________________________
> > With turned off scanner insmod OK, but I can't add scanner with
> > echo "..">/proc/scsi/scsi.
> > Maybe some ideas.
> > I don't want to buy new SCSI controller, as ACARD already supported by
> > kernel.
> > Ideas, suggestions?
> >
> > Nikolay.
> >
> >
> >
> >
> > --
> > Source code, list archive, and docs: http://www.mostang.com/sane/
> > To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
> >
>
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
>

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com