Re: Scanmaker 636

From: abel deuring (a.deuring@satzbau-gmbh.de)
Date: Thu Jan 25 2001 - 11:33:53 PST

  • Next message: Nils Gundelach: "Re: Scanmaker 636"

    Nils Gundelach wrote:
    >
    > Hello,
    >
    > I don't know if this is the right place to post, forgive me if it's not :)
    >
    > I run a Microtek Scanmaker 636 together with a Tekram dc-395.
    >
    > dc-395 -> scanner(TERM)
    >
    > If i don't disable "Allow disconnect" in the scsi bios i get the following
    > error message:

    Niels,

    Some scanners don't support disconnect. I don't know if this is the case
    for the Scanmaker 636.

    >
    > Jan 22 03:21:13 darkstar kernel: scsi : aborting command due to timeout : p=
    > id
    > 0, scsi1, channel 0, id 6, lun 0 Read (10) 00 83 00 60 00 00 00 00 00
    > Jan 22 03:21:13 darkstar kernel: DC395x_abort: pid=3D0, target=3D06-0
    > Jan 22 03:21:13 darkstar kernel: DC395x: abort: Lower SyncFreq to for dev
    > 06-0!
    > Jan 22 03:21:13 darkstar kernel: pid 0(28666):28 00..(6-0) Start 00 60 MI=
    > P1
    > #MIP0(02).MIP1 #MIP0(04).DISC +abort (SN)!*
    > Jan 22 03:21:13 darkstar kernel: TmpSRB:
    > Jan 22 03:21:13 darkstar kernel: DC395x: Aborted pid 0 with status 0
    > Jan 22 03:21:14 darkstar kernel: DC395x: Disc: SRB_ABORT_SENT!
    > Jan 22 03:21:14 darkstar kernel: DC395x_DoingSRB_Done: pids (G)pid
    > 0(28666):28 00..(6-0) Start 00 60 MIP1 #MIP0(02).MIP1 #MIP0(04).DISC +abort
    > (SN)!RSel ##MOP1#(06 )DISC Reset(29749):00050000*
    >
    > The scanner doesn't allow synchronous scsi, so i set the asynchron option in
    > my scsi bios, no success :/
    > I tried this also with my adaptec 7890 (Asus P2B-s) and result was the same.
    > If i leave this option enabled, the scanner scans 1/4 of a page and then
    > stops. The image is full off red, green, blue lines... (the same with 7890)
    >
    > I thought the scanner is broken, but i tested the scanner by a friend and it
    > works fine. He also uses Debian (woody) with kernel 2.4.0.

    If you are using the 2.4.0 kernel, the time out might related to the too
    short time out I put into sanei_scsi.c for the SG3 interface.

    Near line 1900, you'll find:

          req->sgdata.sg3.hdr.timeout = 10000;

    Try to change this to

          req->sgdata.sg3.hdr.timeout = 1000 * 60 *
    10;

    This increases the timeout for a SCSI command from 10 seconds to 10
    minutes.

    Abel

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



    This archive was generated by hypermail 2b29 : Thu Jan 25 2001 - 10:30:00 PST