# Mustek Paragon 1200 SP Pro

Miguel Alvarez Blanco (miguel@carbono.quimica.uniovi.es)
Thu, 18 Jun 1998 20:11:20 +0200

- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Simon Redwood: "GI1904 based Hand scanner"
- Previous message: Yuri Dario: "Re: mustek backend in OS/2"
- Next in thread: Miguel Alvarez Blanco: "Re: Mustek Paragon 1200 SP Pro"
- Reply: Miguel Alvarez Blanco: "Re: Mustek Paragon 1200 SP Pro"

Hi to all sane developers!

I have found sane really easy to install (just ./configure ; make ;
make install; that's good installation procedure!), and I have had no
problems in putting a bigger SCSI buffer in /usr/incalude/scsi/sg.h,
recompiling the kernel and sane. My problem is with making the backend
to work. I have used the SCSI card shipped with the scanner, an
ADAPTEC AVA-1505 card, under Linux 2.0.30 (Debian 1.3), and it gets
detected OK. I have used a module, so that I could unload it when I
don't need to scan. It seems to work, and detects the scanner correctly
(I think):

# insmod aha152x aha152x=0x340,11,7,0,1,0,100,0
aha152x: BIOS test: passed, detected 1 controller(s)
aha152x0: vital data: PORTBASE=0x340, IRQ=11, SCSI ID=7, reconnect=disabled, parity=enabled, synchronous=disabled, delay=100, extended translation=disabled
aha152x: trying software interrupt, ok.
scsi1 : Adaptec 152x SCSI driver; $Revision: 1.18 $
scsi : 1 host.
Vendor: SCANNER Model: Rev: 2.01
Type: Scanner ANSI SCSI revision: 00

I have seen that SCANNER as Vendor name is common to some other Mustek
scanners, so I think that it is OK. However, the firmware revision of
2.01 is not listed in the man pages. Is it too new to be supported, or
there are other kind of problems? I am willing to help testing, since I
know how to work and administer linux, but I'm not a good (well, not
even "a") C programmer, so I can't help much with coding.

I'm getting off the point. Once the scanner gets detected, I load the
sg (raw scsi device) module:

# insmod sg
Detected scsi generic sga at scsi1, channel 0, id 6, lun 0

so I symlink /dev/scanner to /dev/sga. Just in case, here is the content
of /proc/scsi/scsi with the scanner info:

# cat /proc/scsi/scsi
Attached devices:
Host: scsi1 Channel: 00 Id: 06 Lun: 00
Vendor: SCANNER Model: Rev: 2.01
Type: Scanner ANSI SCSI revision: 01

Yes, it is the only device in the bus other than the card, and that is
the only SCSI bus on the machine (an old 486 by now). Trying to detect
the scanner with find-scanner works:

# tools/find-scanner
find-scanner: found scanner "SCANNER 2.01" at device /dev/scanner
find-scanner: found scanner "SCANNER 2.01" at device /dev/sg0
find-scanner: found scanner "SCANNER 2.01" at device /dev/sga

(/dev/sg0 is a device provided by Debian with the same major and minor
as sga; I'm not sure if it is correct to use it, so I made the sga
device with mknod). Now, when trying to use scanimage to test the
device:
# scanimage -d mustek:/dev/scanner -h

and it shows me the list of options, moves up and down the scanning
line, and then hangs ... and the machine with it. I can scroll
upwards and downwards (Shift-PgUp/Down), but cannot change VT (I'm
not using X in this machine, although it has 32 MB). I then have to
reboot (too bad for my filesystem) or turn off the scanner, which is
what I did, recovering control of the system, although the SCSI bus
went crazy (well ...), but at least I could shutdown properly. I have
tried again with maximum debugging (SANE_DEBUG_DLL, SANE_DEBUG_MUSTEK,
and SANE_DEBUG_SANEI_SCSI set to 128 and exported), and the output
(which I can't pick with the mouse, so I transcribe what I think is
the main output here) looks like this:

[dll] init: initializing backend `mustek'
[mustek] attach: opening /dev/sga as scsi device
[mustek] attach: sending INQUIRY
[mustek] scsi_wait_ready: sending TEST_UNIT_READY
[mustek] attach: firmware revision 2.01
[mustek] attach: unknown model `FS-1200SPPRO'
[mustek] attach: opening /dev/scanner as scsi device
....repeats with /dev/scanner....
scanimage: open of device mustek:/dev/scanner failed: Invalid argument
....then lots of trials with different backends, being the last:
[dll] init: initializing backend `microtek2'
....and, after some SCSI commands, it hangs.

I hope someone can help me know if this is a problem with my setup, with
the scanner being unsupported yet, and if it's the latter, whether there
is support planned or under development. I have read the archives of the
mailing list (subjects), but didn't found any reference to 1200 SP PRO.
And it seems that the latest problems with 1200 SP scanners (some mails
in May and June) talked about firmware revisions 1.0something.

Many thanks in advance,

Miguel

    ---
     Miguel Alvarez Blanco

     E-mail:    miguel@carbono.quimica.uniovi.es
     HomePage:  http://www.uniovi.es/~quimica.fisica/qcg/mab/miguel.html
     Mail: Dpto. Quimica Fisica y Analitica, Universidad de Oviedo.
           Facultad de Quimica, c/ Julian Claveria, 8. 33006-Oviedo, Spain.
     Phone: +34 8 510 2975  Fax: +34 8 510 3125  Dpt.Office: +34 8 510 30 34

     Never underestimate the bandwidth of a station wagon full of mag tapes.
      -- Dennis Ritchie

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

     Next message: Simon Redwood: "GI1904 based Hand scanner"
     Previous message: Yuri Dario: "Re: mustek backend in OS/2"

     Next in thread: Miguel Alvarez Blanco: "Re: Mustek Paragon 1200 SP Pro"
     Reply: Miguel Alvarez Blanco: "Re: Mustek Paragon 1200 SP Pro"