[sane-devel] DocketPORT 487: "scanimage: sane_start: Error during device I/O"

Stef stef.dev at free.fr
Wed Aug 19 20:26:49 UTC 2015

On 19/08/2015 02:11, Robert Fleming wrote:
> Greetings,
> Having trouble getting a DocketPORT 487 going:
> # env SANE_DEBUG_DLL=255 scanimage --resolution 75 >output
> [sanei_debug] Setting debug level of dll to 255.
> [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.25git
> ....
> [dll] sane_open: trying to open `genesys:libusb:002:086'
> [genesys] WARNING: Your scanner is not fully supported or at least
> [genesys]          had only limited testing. Please be careful and
> [genesys]          report any failure/success to
> [genesys]          sane-devel at lists.alioth.debian.org. Please provide as many
> [genesys]          details as possible, e.g. the exact name of your
> [genesys]          scanner and what does (not) work.
> [dll] sane_open: open successful
> [dll] sane_get_option_descriptor(handle=0x8af33d8,option=0)
> [dll] sane_control_option(handle=0x8af33d8,option=0,action=0,value=0xffc481d4,info=(nil))
> ....
> scanimage: sane_start: Error during device I/O
> [dll] sane_cancel(handle=0x8af33d8)
> [dll] sane_close(handle=0x8af33d8)
> [dll] sane_exit: exiting
> [dll] sane_exit: calling backend `genesys's exit function
> [dll] sane_exit: finished
> Same problem with versions 1.0.23-3ubuntu3.1 and
> 1.0.25-git20150811-trusty0 of the SANE packages.
> I do have the scanner working correctly in Windows (in VirtualBox)
> with the vendor drivers.
> Any ideas? Is there anything else I can do to debug it? Would it be
> helpful to get a USB trace (of the Linux and/or Windows cases)?
> Thanks,
> Robert

     it is slow and difficult to add support for a scanner just by 
exchanging USB log. However, having a log could give us an estimate of 
the work to do:
     see https://github.com/stefdev49/syseneg/analyze/README.md for a 
start. Then post the pcap file in some place where I can grab it.


More information about the sane-devel mailing list