Re: [snapscan] Agfa 1212U problems?

From: Timothy Little (tim@lilly-villa.little-possums.net)
Date: Sat Nov 04 2000 - 16:00:47 PST

  • Next message: Oliver Rauch: "is lalloca.h installed on any system? [was:#include <sane...> instead of "sane..."]"

    I've fixed the USB stuff in my computer with a reboot. (Maybe the
    experimental kernel is to blame?)

    My AGFA 1212U scanner now works, mostly.

    After scanimage -T succeeded, I tried xsane. It is a *really* bad
    idea to select 600 dpi resolution in the main window, then try to
    acquire a preview in the preview window. The scanner made grinding
    noises and refused to work until I switched it off and back on.

    This is exactly the same problem I had a number of weeks ago -- you'd
    think I'd learn.

    Today I tried scanning a few small areas. I noticed that scanimage
    fails to work with some combinations of width and resolution. For
    example,
    "scanimage --resolution=50 -l9 -t10 -x56 -y17" works,
    "scanimage --resolution=50 -l9 -t10 -x55 -y17" works,

    "scanimage --resolution=100 -l9 -t10 -x56 -y17" works,
    "scanimage --resolution=100 -l9 -t10 -x55 -y17" fails,

    "scanimage --resolution=300 -l9 -t10 -x56 -y17" works,
    "scanimage --resolution=300 -l9 -t10 -x55 -y17" works,

    "scanimage --resolution=600 -l9 -t10 -x56 -y17" fails,
    "scanimage --resolution=600 -l9 -t10 -x55 -y17" works.

    Changing "-y", "-l", and "-t" don't seem to have any effect on the
    above results. When it fails, the scanner does not even start to
    scan, nor does the status light blink. Scanimage hangs, but can be
    killed.

    I have debug info for the two "100 dpi" cases. There appears to be
    little difference between them up until the moment of failure.
    Nothing that jumps out at me as being wrong, anyway.

    The failed one stops here:

    [snapscan] usb_cmd(27,0x8059e70,10,0x8059f70,0x8061b78 (31104))
    [snapscan] usb_cmd: cmdlen=10, datalen=0
    [snapscan] usb_write: writing: 0x28 0x00 0x80 0x00 0x00 0x00 0x00 0x79 0x80 0x00
    [snapscan] usb_read: reading: 0xf9 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    [snapscan] usb_read: reading: 0xc4 0xc2 0xc6 0xc6 0xc9 0xcd 0xcc 0xc9 0xcc 0xcd ...
    [snapscan] usb_read: reading: 0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00

    The successful one continues:

    [snapscan] usb_cmd(27,0x8059e70,10,0x8059f70,0x8061b78 (31744))
    [snapscan] usb_cmd: cmdlen=10, datalen=0
    [snapscan] usb_write: writing: 0x28 0x00 0x80 0x00 0x00 0x00 0x00 0x7c 0x00 0x00
    [snapscan] usb_read: reading: 0xf9 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    [snapscan] usb_read: reading: 0xbe 0xbe 0xc3 0xc2 0xc4 0xc6 0xc4 0xc8 0xc7 0xc7 ...
    [snapscan] usb_read: reading: 0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    [snapscan] scsi_read
    [snapscan] sanei_usb_cmd(27,0x8059e70,10,0x8059f70,0x8061b78 (0))
    [snapscan] atomic_usb_cmd(27,0x8059e70,10,0x8059f70,0x8061b78 (0))
    [snapscan] usb_cmd(27,0x8059e70,10,0x8059f70,0x8061b78 (0))
    [snapscan] usb_cmd: cmdlen=10, datalen=0
    [snapscan] usb_write: writing: 0x28 0x00 0x80 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    [snapscan] usb_read: reading: 0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    [snapscan] measure_transfer_rate: successfully calibrated transfer rate.

    I can mail the full debug logs to anyone interested in looking at
    them. They're about 20kB each.

    - Tim

    --
    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 - 15:56:54 PST