[3171] in linux-scsi channel archive
[Fwd: Micotek E3, SANE-0.69]
daemon@ATHENA.MIT.EDU (Peter JD Hall)
Mon Feb 2 21:05:09 1998
Date: Mon, 02 Feb 1998 19:45:33 -0500
From: Peter JD Hall <phall@ilap.com>
To: linux-scsi@vger.rutgers.edu
This is a multi-part message in MIME format.
--------------CEF6000DBFE4623E5FFDE6AA
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
--------------CEF6000DBFE4623E5FFDE6AA
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
>From phall Sun Feb 1 20:30:37 1998
Return-Path: <phall@ilap.com>
Received: from ilap.com (root@async20.ilap.com [204.50.90.69])
by server01.ilap.com (8.8.7/Internet.Light.and.Power.Inc.) with ESMTP id UAA14840;
Sun, 1 Feb 1998 20:30:31 -0500 (EST)
Sender: root
Message-ID: <34D521B1.500FE1C1@ilap.com>
Date: Sun, 01 Feb 1998 20:30:25 -0500
From: Peter JD Hall <phall@ilap.com>
Organization: Oak Devices
X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.33 i486)
MIME-Version: 1.0
To: sane-devel@mostang.com
Subject: Re: Micotek E3, SANE-0.69
References: <199801311710.MAA17381@yoo-hoo.ai.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Matto Marjanovic wrote:
> Has anyone had any luck with SANE-0.69, Microtek E3 with "stock"
> Adaptec 1502AE scsi card, and RH 5.0?
>
> I don't know how RH takes care of setting up scsi drivers, but the
> 1502AE card will work. You need to use the aha152x driver, and you
> need to specify the IRQ/base address manually.
>
> In my /etc/conf.modules (for a Debian-based box):
>
> options aha152x aha152x=0x140,9,7,0,1,1
>
> This is described in the source file, .../linux-xxx/drivers/scsi/aha152x.c
>
> -matt m.
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
Hi Matt, I have the Microtek E3 scanner on the ava1502e card which is the
stock card that the scanner comes with in the box. The scanner runs fine
under win 3.11. I have been struggling with getting this card to work under
linux, running Slackware 3.3.0, kernel 2.0.33. I have finally succeded in
getting the card recognized with the generic scsi driver and the aha152x
driver loaded as modules at boot time:
Adding Swap: 16556k swap-space (priority -1)
aha152x: BIOS test: passed, auto configuration: ok, detected 2 controller(s)
aha152x0: vital data: PORTBASE=0x140, IRQ=10, SCSI ID=7, reconnect=enabled,
parity=enabled, synchronous=disabled, delay=100, extended
translation=disabled
aha152x: trying software interrupt, ok.
aha152x1: vital data: PORTBASE=0x340, IRQ=12, SCSI ID=7, reconnect=enabled,
parity=disabled, synchronous=disabled, delay=100, extended
translation=disabled
aha152x: trying software interrupt, ok.
scsi1 : Adaptec 152x SCSI driver; $Revision: 1.18 $
scsi2 : Adaptec 152x SCSI driver; $Revision: 1.18 $
scsi : 3 hosts.
Vendor: Model: Scanner Rev: 1.40
Type: Scanner ANSI SCSI revision: 04
Detected scsi generic sge at scsi1, channel 0, id 5, lun 0
ncr53c810-0-<2,0>: SLOW SCSI 4.0 MB/s (250 ns, offset 8)
Max size:326563 Log zone size:2048
First datazone:36 Root inode number 73728
The second card is my Sound blaster card which has a scsi controller on it
that I do not use but I am unable to disable the scsi chip so it is
recognized.
The real problem is the following:
find-scanner: checking /dev/sga...
find-scanner: found disk "QUANTUM MAVERICK 540S 0901" at device /dev/sga
find-scanner: checking /dev/sgb...
find-scanner: found disk "QUANTUM FIREBALL_TM2110S 300X" at device /dev/sgb
find-scanner: checking /dev/sgc...
find-scanner: found CD-drive "TOSHIBA CD-ROM XM-3501TA 2694" at device
/dev/sgc
find-scanner: checking /dev/sgd...
find-scanner: found disk "QUANTUM FIREBALL_TM2110S 300X" at device /dev/sgd
find-scanner: checking /dev/sge...
find-scanner: found disk " " at device /dev/sge.
I can not get sane to see the scanner as other than a hard drive. The
other scsi devices are on the ncr controller. There is a symbolic link from
scanner to /dev/sge.
Any pointers would be appreciated. I have been struggling with this for
several weeks and reading over the various howtos.
Cheers,
Peter Hall
--------------CEF6000DBFE4623E5FFDE6AA--
