Re: scanimage hangs on 'scanimage -L'

From: Shea Martin (snowsquirrel@home.com)
Date: Tue Jan 23 2001 - 10:58:23 PST

  • Next message: Shea Martin: "frontend 1.0.4 ./configure can't run sane test program???????"

    I am not sure what happened, but I ran scanimage -L with in the debug mode. The scanner was recognized?????? All is well that ends well. The only thing that may have been different was that I mounted the usbdevfs before running scanimage. I have been fooling with this stuff for so long now, who knows what I did diff this time around. Anyway, I really appreciate the effort you went to to help me out. The debug mode may help me help myself out if I encounter this prob again. Hopefully things keep working.
    FYI here is output:

    [sanei_debug] Setting debug level of snapscan to 255.
    [snapscan] sane_snapscan_init
    [snapscan] add_device(/dev/usbscanner)
    [snapscan] add_device: Detected (kind of) an USB device
    [snapscan] usb_open(/dev/usbscanner)
    [snapscan] mini_inquiry
    [snapscan] snapscan_cmd
    [snapscan] sanei_usb_cmd(5,0xbfffe4a4,6,0xbfffe480,0xbfffe47c (36))
    [snapscan] atomic_usb_cmd(5,0xbfffe4a4,6,0xbfffe480,0xbfffe47c (36))
    [snapscan] usb_cmd(5,0xbfffe4a4,6,0xbfffe480,0xbfffe47c (36))
    [snapscan] usb_cmd: cmdlen=6, datalen=0
    [snapscan] usb_write: writing: 0x12 0x00 0x00 0x00 0x24 0x00
    [snapscan] usb_read: reading: 0xf9 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    [snapscan] usb_read: reading: 0x06 0x00 0x02 0x02 0x49 0x00 0x00 0x00 0x43 0x6f ...
    [snapscan] usb_read: reading: 0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    [snapscan] add_device: Is vendor "Color" model "FlatbedScanner13" a supported scanner?
    [snapscan] usb_close(5)
    [snapscan] sane_snapscan_get_devices (0xbffff638, 0)
    device `snapscan:/dev/usbscanner' is a Color FlatbedScanner13 flatbed scanner
    [snapscan] sane_snapscan_exit

    On Tue, 23 Jan 2001 19:25:14 +0100
    Oliver Schwartz <Oliver.Schwartz@gmx.de> wrote:

    > Hi,
    >
    > > I am not sure how to set SANE_SNAPSCAN_DEBUG=255? Should I enter this line
    > > in the make file, pass the line as an arguement to ./configure? I ran the
    > > following command 'grep -l SANE_SNAPSCAN_DEBUG=255 *' in the sane-backend
    > > dir, the backend dir, and the frontend dir but came up with nothing.
    >
    > Actually it's SANE_DEBUG_SNAPSCAN ... just execute
    > "export SANE_DEBUG_SNAPSCAN=255" in your shell before running scanimage.
    >
    > Oliver
    >
    > --
    > --------------------------------------------------------
    > ! Oliver Schwartz !
    > ! Heidberg 19A Tel. : 040 / 27 80 62 46 !
    > ! D-22301 Hamburg E-Mail: Oliver.Schwartz@gmx.de !
    > --------------------------------------------------------
    >
    >
    > --
    > Source code, list archive, and docs: http://www.mostang.com/sane/
    > To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

    -- 
    ...elbows out,
    stick on the ice!
    

    -- 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 : Tue Jan 23 2001 - 10:45:04 PST