[3229] in linux-scsi channel archive
[Fwd: Micotek E3, SANE-0.69] re: sg.o driver problem
daemon@ATHENA.MIT.EDU (Peter JD Hall)
Fri Feb 6 07:01:01 1998
Date: Thu, 05 Feb 1998 21:41:27 -0500
From: Peter JD Hall <phall@ilap.com>
To: "linux-scsi@vger.rutgers.edu" <linux-scsi@vger.rutgers.edu>
This is a multi-part message in MIME format.
--------------D8CF38A1666F463CBF368F90
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
--------------D8CF38A1666F463CBF368F90
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-ID: <34DA7189.B6773E4B@ilap.com>
Date: Thu, 05 Feb 1998 21:12:25 -0500
From: Peter JD Hall <phall@ilap.com>
Organization: Oak Devices
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; uuencode=0; html=0; linewidth=79
X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.33 i486)
MIME-Version: 1.0
To: Matto Marjanovic <maddog@mir.com>
Subject: Re: Micotek E3, SANE-0.69
References: <199802042116.QAA18243@yoo-hoo.ai.mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Matto Marjanovic wrote:
> hmm... I'm no SCSI expert...
>
> Here are some ideas:
>
> 1) what happens if you forget about find-scanner (just a convenience util)
> and try "scanimage -L", with SANE_DEBUG_MICROTEK at 128? What does the
> backend think it sees on /dev/sge and/or /dev/scanner?
>
> 2) how exactly are you loading the aha152x module? you should be able to
> specify the parameters for the single adapter, and not have anything
> load up for the Sound Blaster controller.
>
> 3) is there any reason why the controller on the Sound Blaster is no good?
>
> -matt m.
Hi Matto, Thank you very much for your reply. I have tried what said
and
enclosed the log file:
bash# scanimage -L,SANE_DEBUG_MICROTEK 128
========== Scanner Inquiry Block ==========
12 00 00 00 ff 2a 00 00 00 27 01 00 00 01 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 12 00 02 00 03 00 00
2a 00 00 00 00 16 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 12 00 00 00 ff 00 2a 00 00 00 00 18
========== Scanner Inquiry Report ==========
===== Scanner ID...
Device Type Code: 0x12
Model Code: 0x00
Vendor Name: '' Model Name: ''
Firmware Rev: ''
SCSI F/W version: 0.0 Scanner F/W version: 0.0
Response data format: 0x00
device `pnm:0' is a Noname PNM file reader virtual device
device `pnm:1' is a Noname PNM file reader virtual device
It seems to me with the limited knowledge that I have the problem is
the
scsi high level driver "sg.o" is picking up the previously install
devices:
three hard drives, one cd-rom. At the end it is attaching the scanner
as
/dev/sge.
I have both the sg driver and the aha152x driver installed in the
kernel as
loadable modules. These are loaded at boot time by rc.d modules under
slackware 3.3.0. The scanner card and the soundblaster card are both
picked
up. The scanner card is picked up first according to the options I have
specified aha152x=0x140,10,7,1. The soundblaster card is identified by
the
autoprobe and is also correctly installed.
The problem would seem to be that the sg driver and the scsi driver
are
conflicting. I am not quite sure how to fix this.
Cheers,
Peter Hall
--------------D8CF38A1666F463CBF368F90--
