[sane-devel] sane-find-scanner finds multiple scanners

Ray Curtis Ray Curtis <ray@ccux.com>
Mon, 6 May 2002 13:21:39 -0400


>>>>> "jw" == Johan Wehtje <joweht@tpgi.com.au> writes:

    jw> Sorry, did forget to say what the problem is with this setup.
    jw> Currently whenever I try to scan , whether from the comand line or from 
    jw> xscanimage or using the KDE3 scan utility I hear the scanner move for a 
    jw> couple of seconds then I get a total system freeze , no coredump or any other 
    jw> messages , just a total kernel freeze.
    jw> Re Ray Curtis's sugestion that I move the LUN to 4 or 5 , How do I do that? I 
    jw> have tried using the wheel dial on the scanner and turning it to 4 or 5 but I 
    jw> get the same result, Do I use a Symlink in the dev directory or do I have to 
    jw> pass paramateers to the modprobe of aha52x?
    jw> Any help is much appreciated as at the moment sane is driving me .... well you 
    jw> know the rest.
    jw> Cheers
    jw> Johan Wehtje

I doubt that will solve your problem it was just a shot in the dark
since you didn't say what was happening other than the scsi board
was recoginizing the scanner on multilple Luns.
However you can change the id of the device on the scanner itself
should have a jumper or thumbwheel switch to select the ID.

The suggestions to change it in the kernel to not support mulitple
Luns or if the scsi board can be configured not to recoginze mulitple
Luns are better suggestions.

As far as locking up your machine when trying to scan, it sounds as
though it still may have something to do with the problem.



>>>>> "cn" == Carsten Neumann <deltor@snafu.de> writes:

    cn> Hi, Johan,
    cn> you've missed to tell what your problems actually are!
    cn> I don't see any problem why you can't use your scanner.
    cn> But you haven't told that you cannot use it.
    cn> What are the errors you get, if there are any?

    cn> Carsten


    jw> I think from looking at the listing below it is pretty obvious that
    jw> the scsi card is detecting muliple scanners, at ID 1 Lun 00-07.
    jw> Not being familiar with this scsi card I can't really help much
    jw> except the suggest moving the ID from 1 to maybe 4 or 5. The lower
    jw> scsi ID's are usually used for hard drives.






    cn> On Mon, 06 May 2002, Johan Wehtje wrote:
    >>> have read the docs as well as the SCSI 2.4 how to but am still none the 
    >>> wiser as to why I get the following output from sane-find-scanner
    >>> ===========================================
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/scanner
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sg1
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sg2
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sg3
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sg4
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sg5
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sg6
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sg7
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sg8
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sgb
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sgc
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sgd
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sge
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sgf
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sgg
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sgh
    >>> sane-find-scanner: found SCSI scanner " Scanner 1.40" at device 
    jw> /dev/sgi
    >>> ======================================================
    >>> I only have one scanner , microtek e3 connected to a adpaptec 1524 scsi 
    jw> card 
    >>> (shipped with scanner). The aha152x scsi driver is loaded as a module. 
    jw> The 
    >>> kernel is 2.4.18. The correct irq and io are passed as params to the 
    jw> module. 
    >>> The system is a PII 400 MHZ , Asus MBrd , 128 mb RAM, Pheonix BIOS. I 
    jw> have an 
    >>> older Zip 100 disk (parralell) that is loaded as a module and sits at 
    jw> sda4. I 
    >>> have my own script for loading the zip as I need to modprobe lp before 
    jw> I do, 
    >>> then modprobe ppa.
    >>> I get the same result even if I don't load the zip and lp modules but 
    jw> only 
    >>> prob the aha152x module manually.
    >>> I am probably missing something really simple here but I can't see what 
    jw> it is 
    >>> so would appreciate some help as i have been fiddling with thsi for the 
    jw> past 
    >>> few weeks trying to get it to work.
    >>> BTW this is a dual boot system (win 98 SE) and the scanner works just 
    jw> fine in 
    >>> Windows , but i would really like to skip booting into windows every 
    jw> time i 
    >>> want to use the scanner.
    >>> anf FYI the out of "cat /proc/scsi/scsi" is below:
    >>> ==================================
    >>> Attached devices: 
    >>> Host: scsi0 Channel: 00 Id: 06 Lun: 00
    >>> Vendor: IOMEGA   Model: ZIP 100          Rev: D.17
    >>> Type:   Direct-Access                    ANSI SCSI revision: 02
    >>> Host: scsi1 Channel: 00 Id: 01 Lun: 00
    >>> Vendor:          Model: Scanner          Rev: 1.40
    >>> Type:   Scanner                          ANSI SCSI revision: 04
    >>> Host: scsi1 Channel: 00 Id: 01 Lun: 01
    >>> Vendor:          Model: Scanner          Rev: 1.40
    >>> Type:   Scanner                          ANSI SCSI revision: 04
    >>> Host: scsi1 Channel: 00 Id: 01 Lun: 02
    >>> Vendor:          Model: Scanner          Rev: 1.40
    >>> Type:   Scanner                          ANSI SCSI revision: 04
    >>> Host: scsi1 Channel: 00 Id: 01 Lun: 03
    >>> Vendor:          Model: Scanner          Rev: 1.40
    >>> Type:   Scanner                          ANSI SCSI revision: 04
    >>> Host: scsi1 Channel: 00 Id: 01 Lun: 04
    >>> Vendor:          Model: Scanner          Rev: 1.40
    >>> Type:   Scanner                          ANSI SCSI revision: 04
    >>> Host: scsi1 Channel: 00 Id: 01 Lun: 05
    >>> Vendor:          Model: Scanner          Rev: 1.40
    >>> Type:   Scanner                          ANSI SCSI revision: 04
    >>> Host: scsi1 Channel: 00 Id: 01 Lun: 06
    >>> Vendor:          Model: Scanner          Rev: 1.40
    >>> Type:   Scanner                          ANSI SCSI revision: 04
    >>> Host: scsi1 Channel: 00 Id: 01 Lun: 07
    >>> Vendor:          Model: Scanner          Rev: 1.40
    >>> Type:   Scanner                          ANSI SCSI revision: 04
    >>> =========================================
    >>> Cheers
    >>> Johan Wehtje
    >>> 
    >>> _______________________________________________
    >>> Sane-devel mailing list
    >>> Sane-devel@www.mostang.com
    >>> http://www.mostang.com/mailman/listinfo/sane-devel
    cn> _______________________________________________
    cn> Sane-devel mailing list
    cn> Sane-devel@www.mostang.com
    cn> http://www.mostang.com/mailman/listinfo/sane-devel

    jw> -- 
    jw> Ray Curtis
    jw> mailto:ray@ccux.com                           http://www.ccux.com
    jw> _______________________________________________
    jw> Sane-devel mailing list
    jw> Sane-devel@www.mostang.com
    jw> http://www.mostang.com/mailman/listinfo/sane-devel


    jw> _______________________________________________
    jw> Sane-devel mailing list
    jw> Sane-devel@www.mostang.com
    jw> http://www.mostang.com/mailman/listinfo/sane-devel

-- 
Ray Curtis
mailto:ray@ccux.com                           http://www.ccux.com