Re: [snapscan] Core testing group

From: abel deuring (a.deuring@satzbau-gmbh.de)
Date: Sat Nov 04 2000 - 11:02:06 PST

  • Next message: Henning Meier-Geinitz: "Re: Mustek (Trust Imagery 1200SP) scanner prob"

    Chris Bagwell wrote:

    > My model still hangs at the "mini_inquiry" stage. Switching on
    > SANE_DEBUG_SANEI_SCSI in addition to SANE_DEBUG_SNAPSCAN yields
    >
    > [snapscan] mini_inquiry
    > [sanei_scsi] scsi_req_enter: entered 0x80505b8
    > [sanei_scsi] sanei_scsi.issue: 0x80505b8
    > [sanei_scsi] sanei_scsi.issue: bad write (errno=62) Timer expired -1
    > [sanei_scsi] scsi_req_enter: queue_used: 0, queue_max: 1
    > [sanei_scsi] sanei_scsi_req_wait: waiting for 0x80505b8
    > [sanei_scsi] sanei_scsi.issue: 0x80505b8
    > [snapscan] mini_inquiry: sanei_scsi_cmd command failed: Error during
    > device I/O
    >
    > Unfortunately, I don't know how to find out for sure whether it's SANE
    > that's at fault or something else in my system. I am using an
    > outdated experimental kernel (2.4.0-test9), though it has worked
    > previously with the older usb-patched sane-1.0.3.

    Strange error. mini_inquiry simply sends the standard INQUIRY command
    and expects that the scanner returns the standard 36 bytes. Since
    INQUIRY is also used by the Linux SCSI system: Does the scanner appear
    in the output of "cat proc/scsi/scsi"?

    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 : Sat Nov 04 2000 - 09:49:34 PST