Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
I'm using USB2, and the git repo checkout was Monday late evening, less than an hour before I sent my last email. I already destroyed the test environment I used on Monday which is why I can't tell you the exact time or commit hash that was checked out. I can try again tomorrow morning if there have been relevant changes in the repo since Monday night. -Jonas On Wed, 18 Mar 2015 17:39:13 -0700 m. allan noahkitno...@gmail.com wrote That kind of error implies that we are having a usb problem, where perhaps a command is being lost, or the data toggle is not being reset. How old is your git repo checkout? Are you using USB 3 ports? allan On Tue, Mar 17, 2015 at 1:34 AM, Jonas Neubert jonas.neub...@gmail.com wrote: I just did a few successful scans! The patch does indeed make the scanner work, with two caveats: 1) Only every other call to scanimage results in a successful scan, the 2nd, 4th, 6th, etc scan fails the same way as before. 2) Even during successful scans the debug output contains an 'Error during device I/O', although I'm not sure if this is even a problem. Debug output from a successful scan (1st, 3rd, 5th, ... call to scanimage): https://gist.github.com/jonemo/489414e8bc5590998890 Debug output from an unsuccessful scan (2nd, 4th, 6th, ... call to scanimage): https://gist.github.com/jonemo/8a4cf7d13a50556b3c41 I also tried scanning at 600dpi and it worked successfully (every other time). -Jonas -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
There have been no recent changes that would improve the situation. Can you run scanimage -L repeatedly without error? or maybe scanimage --help? allan On Thu, Mar 19, 2015 at 2:06 AM, Jonas Neubert jonas.neub...@gmail.com wrote: I'm using USB2, and the git repo checkout was Monday late evening, less than an hour before I sent my last email. I already destroyed the test environment I used on Monday which is why I can't tell you the exact time or commit hash that was checked out. I can try again tomorrow morning if there have been relevant changes in the repo since Monday night. -Jonas On Wed, 18 Mar 2015 17:39:13 -0700 m. allan noahkitno...@gmail.com wrote That kind of error implies that we are having a usb problem, where perhaps a command is being lost, or the data toggle is not being reset. How old is your git repo checkout? Are you using USB 3 ports? allan On Tue, Mar 17, 2015 at 1:34 AM, Jonas Neubert jonas.neub...@gmail.com wrote: I just did a few successful scans! The patch does indeed make the scanner work, with two caveats: 1) Only every other call to scanimage results in a successful scan, the 2nd, 4th, 6th, etc scan fails the same way as before. 2) Even during successful scans the debug output contains an 'Error during device I/O', although I'm not sure if this is even a problem. Debug output from a successful scan (1st, 3rd, 5th, ... call to scanimage): https://gist.github.com/jonemo/489414e8bc5590998890 Debug output from an unsuccessful scan (2nd, 4th, 6th, ... call to scanimage): https://gist.github.com/jonemo/8a4cf7d13a50556b3c41 I also tried scanning at 600dpi and it worked successfully (every other time). -Jonas -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
Both scanimage -L and scanimage --help show the same behavior: Works once,
fails second time. Debug outputs:
scanimage -L: https://gist.github.com/jonemo/c0e508baf4533d79a2ea
scanimage --help: https://gist.github.com/jonemo/6879f07a590d8a5f3fe2
-Jonas
On Thu, 19 Mar 2015 05:26:34 -0700 m. allan noahkitno...@gmail.com wrote
There have been no recent changes that would improve the situation.
Can you run scanimage -L repeatedly without error? or maybe scanimage
--help?
allan
On Thu, Mar 19, 2015 at 2:06 AM, Jonas Neubert jonas.neub...@gmail.com
wrote:
I'm using USB2, and the git repo checkout was Monday late evening, less
than an hour before I sent my last email. I already destroyed the test
environment I used on Monday which is why I can't tell you the exact time
or commit hash that was checked out. I can try again tomorrow morning if
there have been relevant changes in the repo since Monday night.
-Jonas
On Wed, 18 Mar 2015 17:39:13 -0700 m. allan noahkitno...@gmail.com
wrote
That kind of error implies that we are having a usb problem, where
perhaps a command is being lost, or the data toggle is not being
reset. How old is your git repo checkout? Are you using USB 3 ports?
allan
On Tue, Mar 17, 2015 at 1:34 AM, Jonas Neubert
jonas.neub...@gmail.com wrote:
I just did a few successful scans! The patch does indeed make the
scanner work, with two caveats:
1) Only every other call to scanimage results in a successful scan,
the 2nd, 4th, 6th, etc scan fails the same way as before.
2) Even during successful scans the debug output contains an 'Error
during device I/O', although I'm not sure if this is even a problem.
Debug output from a successful scan (1st, 3rd, 5th, ... call to
scanimage): https://gist.github.com/jonemo/489414e8bc5590998890
Debug output from an unsuccessful scan (2nd, 4th, 6th, ... call to
scanimage): https://gist.github.com/jonemo/8a4cf7d13a50556b3c41
I also tried scanning at 600dpi and it worked successfully (every
other time).
-Jonas
--
well, I stand up next to a mountain- and I chop it down with the edge
of my hand
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject unsubscribe your_password
to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
Hmm- the scanner is upset that we tried to send window data. Perhaps it wants some other command to be sent first. I will look at your pcap again and come up with a patch allan On Mon, Mar 16, 2015 at 3:30 AM, Jonas Neubert jonas.neub...@gmail.com wrote: I believe all debug output I sent so far (both SANE and Windows) was with 300dpi setting, for scanimage it's the default value for the --resolution option in the output of 'scanimage -h'. Anyway, ran it again, this time with resolution and mode options explicitly set, still same behavior, see debug output below. Note that I already had SANE_DEBUG_EPJITSU=25 set before. Just in case you meant increasing it to 35: https://gist.github.com/jonemo/8e0b28f15e7e7431975a -Jonas jonas@sane-scanner:~$ sudo SANE_DEBUG_EPJITSU=25 scanimage --resolution=300 --mode=Color file.npm [sanei_debug] Setting debug level of epjitsu to 25. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.27, from sane-backends 1.0.25git [epjitsu] sane_init: finish [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: reading config file epjitsu.conf [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/60f_0A00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x10c7' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300M_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x117f' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/1300_0C26.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11ed' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/65f_0A01.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11bd' [epjitsu] attach_one: start 'libusb:001:007' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: finish [epjitsu] load_fw: start [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] load_fw: read firmware file /usr/share/sane/epjitsu/65f_0A01.nal ok [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 4 bytes, timeout 1 [epjitsu] cmd: wrote 4 bytes, retVal 0 [epjitsu] out: writing 65536 bytes, timeout 1 [epjitsu] out: wrote 65536 bytes, retVal 0 [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] get_ident: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 32 bytes [epjitsu] in: reading 32 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 32 bytes [epjitsu] do_cmd: finish [epjitsu] get_ident: finish [epjitsu] attach_one: Found FUJITSU scanner fi-65F 0A01 at libusb:001:007 [epjitsu] attach_one: Found fi-65F [epjitsu] attach_one: init options [epjitsu] attach_one: init settings [epjitsu] change_params: start [epjitsu] change_params:
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
I have attached a minor patch to the backend. The idea is to send commands in the same order as the windows driver, starting with get hardware status. If this does not fix it, I will move on to set window, which looks like it should be after the initial coarse calibration payload. allan On Mon, Mar 16, 2015 at 7:34 AM, m. allan noah kitno...@gmail.com wrote: Hmm- the scanner is upset that we tried to send window data. Perhaps it wants some other command to be sent first. I will look at your pcap again and come up with a patch allan On Mon, Mar 16, 2015 at 3:30 AM, Jonas Neubert jonas.neub...@gmail.com wrote: I believe all debug output I sent so far (both SANE and Windows) was with 300dpi setting, for scanimage it's the default value for the --resolution option in the output of 'scanimage -h'. Anyway, ran it again, this time with resolution and mode options explicitly set, still same behavior, see debug output below. Note that I already had SANE_DEBUG_EPJITSU=25 set before. Just in case you meant increasing it to 35: https://gist.github.com/jonemo/8e0b28f15e7e7431975a -Jonas jonas@sane-scanner:~$ sudo SANE_DEBUG_EPJITSU=25 scanimage --resolution=300 --mode=Color file.npm [sanei_debug] Setting debug level of epjitsu to 25. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.27, from sane-backends 1.0.25git [epjitsu] sane_init: finish [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: reading config file epjitsu.conf [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/60f_0A00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x10c7' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300M_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x117f' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/1300_0C26.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11ed' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/65f_0A01.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11bd' [epjitsu] attach_one: start 'libusb:001:007' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: finish [epjitsu] load_fw: start [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] load_fw: read firmware file /usr/share/sane/epjitsu/65f_0A01.nal ok [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 4 bytes, timeout 1 [epjitsu] cmd: wrote 4 bytes, retVal 0 [epjitsu] out: writing 65536 bytes, timeout 1 [epjitsu] out: wrote 65536 bytes, retVal 0 [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] get_ident: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 32 bytes [epjitsu] in: reading 32 bytes, timeout 1 [epjitsu] in:
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
I just did a few successful scans! The patch does indeed make the scanner work, with two caveats: 1) Only every other call to scanimage results in a successful scan, the 2nd, 4th, 6th, etc scan fails the same way as before. 2) Even during successful scans the debug output contains an 'Error during device I/O', although I'm not sure if this is even a problem. Debug output from a successful scan (1st, 3rd, 5th, ... call to scanimage): https://gist.github.com/jonemo/489414e8bc5590998890 Debug output from an unsuccessful scan (2nd, 4th, 6th, ... call to scanimage): https://gist.github.com/jonemo/8a4cf7d13a50556b3c41 I also tried scanning at 600dpi and it worked successfully (every other time). -Jonas On Mon, 16 Mar 2015 05:26:04 -0700 m. allan noahkitno...@gmail.com wrote I have attached a minor patch to the backend. The idea is to send commands in the same order as the windows driver, starting with get hardware status. If this does not fix it, I will move on to set window, which looks like it should be after the initial coarse calibration payload. allan On Mon, Mar 16, 2015 at 7:34 AM, m. allan noah kitno...@gmail.com wrote: Hmm- the scanner is upset that we tried to send window data. Perhaps it wants some other command to be sent first. I will look at your pcap again and come up with a patch allan -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
I believe all debug output I sent so far (both SANE and Windows) was with 300dpi setting, for scanimage it's the default value for the --resolution option in the output of 'scanimage -h'. Anyway, ran it again, this time with resolution and mode options explicitly set, still same behavior, see debug output below. Note that I already had SANE_DEBUG_EPJITSU=25 set before. Just in case you meant increasing it to 35: https://gist.github.com/jonemo/8e0b28f15e7e7431975a -Jonas jonas@sane-scanner:~$ sudo SANE_DEBUG_EPJITSU=25 scanimage --resolution=300 --mode=Color file.npm [sanei_debug] Setting debug level of epjitsu to 25. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.27, from sane-backends 1.0.25git [epjitsu] sane_init: finish [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: reading config file epjitsu.conf [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/60f_0A00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x10c7' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300M_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x117f' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/1300_0C26.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11ed' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/65f_0A01.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11bd' [epjitsu] attach_one: start 'libusb:001:007' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: finish [epjitsu] load_fw: start [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] load_fw: read firmware file /usr/share/sane/epjitsu/65f_0A01.nal ok [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 4 bytes, timeout 1 [epjitsu] cmd: wrote 4 bytes, retVal 0 [epjitsu] out: writing 65536 bytes, timeout 1 [epjitsu] out: wrote 65536 bytes, retVal 0 [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] get_ident: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 32 bytes [epjitsu] in: reading 32 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 32 bytes [epjitsu] do_cmd: finish [epjitsu] get_ident: finish [epjitsu] attach_one: Found FUJITSU scanner fi-65F 0A01 at libusb:001:007 [epjitsu] attach_one: Found fi-65F [epjitsu] attach_one: init options [epjitsu] attach_one: init settings [epjitsu] change_params: start [epjitsu] change_params: finish [epjitsu] disconnect_fd: start [epjitsu] disconnecting usb device [epjitsu] disconnect_fd: finish [epjitsu] attach_one: finish [epjitsu] sane_get_devices: found scanner libusb:001:007 [epjitsu] sane_get_devices: found 1 scanner(s) [epjitsu] sane_get_devices: finish [epjitsu] sane_open: start [epjitsu] sane_open: searching
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
hmm- I have never actually seen an fi-65f, I only have user reports from my patches. However, the initial development was done with firmware 65f_0A01.nal Can you try to extract that version (or later) from the Fujitsu windows drivers? You might have to get the latest version from their website. Maybe there is a difference? Otherwise, you would need to get a log of the scanner in action under windows, so we could try to reproduce the commands. allan On Sat, Mar 14, 2015 at 11:37 PM, Jonas Neubert jonas.neub...@gmail.com wrote: Thanks Allan, my mind was so set on thinking of output as the scanner output, I didn't even consider that this error might about the program's output! When doing 'scanimage file.pnm' the first attempt at scanning an image now ends with the same scanimage: sane_start: Error during device I/O as scanimage -T. Full output: jonas@sane-scanner:~$ sudo SANE_DEBUG_DLL=256 SANE_DEBUG_EPJITSU=25 scanimage file.pnm [sanei_debug] Setting debug level of dll to 256. [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.25git [dll] sane_init/read_dlld: attempting to open directory `./dll.d' [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: done. [dll] sane_init/read_config: reading dll.conf [dll] add_backend: adding backend `epjitsu' [dll] sane_get_devices [dll] load: searching backend `epjitsu' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-epjitsu.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-epjitsu.so.1' [dll] init: initializing backend `epjitsu' [sanei_debug] Setting debug level of epjitsu to 25. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.27, from sane-backends 1.0.25git [epjitsu] sane_init: finish [dll] init: backend `epjitsu' is version 1.0.27 [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: reading config file epjitsu.conf [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/60f_0A00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x10c7' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300M_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x117f' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/1300_0C26.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11ed' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/65f_.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11bd' [epjitsu] attach_one: start 'libusb:001:004' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: finish [epjitsu] load_fw: start [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] load_fw: read firmware file /usr/share/sane/epjitsu/65f_.nal ok [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 4 bytes, timeout 1 [epjitsu] cmd: wrote 4 bytes, retVal 0 [epjitsu] out: writing 65536 bytes, timeout 1 [epjitsu] out: wrote 65536 bytes, retVal 0 [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu]
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
Wireshark is fine, but this log does not contain the calibration step, which is where sane seems to fail. Can you unplug and replug the device while wireshark is running, and get a log of the initialization process? I'm not sure if wireshark can do that. allan On Sun, Mar 15, 2015 at 6:01 PM, Jonas Neubert jonas.neub...@gmail.com wrote: I see, installing that driver on Windows adds both a 65f_.nal in C:\Windows and a 65f_0A01.nal in C:\Windows\twain_32\fjscan32. I had missed that latter last time. Unfortunately, still no change in behavior. The output remains effectively same, but just in case I'm missing something, below is the full output again. Not sure what exactly you mean by log of the scanner in action under windows, but [1] is a .pcap captured with USBPcap on Windows while scanning a full page at 300dpi. I'd be happy to collect more data or dig deeper into this myself, but I'll definitely need guidance. -Jonas [1] https://www.dropbox.com/s/1yny75ns4qq6i4u/fi65_2.pcap?dl=0 jonas@sane-scanner:~$ sudo SANE_DEBUG_DLL=256 SANE_DEBUG_EPJITSU=25 scanimage file.pnm [sanei_debug] Setting debug level of dll to 256. [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.25git [dll] sane_init/read_dlld: attempting to open directory `./dll.d' [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: done. [dll] sane_init/read_config: reading dll.conf [dll] add_backend: adding backend `epjitsu' [dll] sane_get_devices [dll] load: searching backend `epjitsu' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-epjitsu.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-epjitsu.so.1' [dll] init: initializing backend `epjitsu' [sanei_debug] Setting debug level of epjitsu to 25. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.27, from sane-backends 1.0.25git [epjitsu] sane_init: finish [dll] init: backend `epjitsu' is version 1.0.27 [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: reading config file epjitsu.conf [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/60f_0A00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x10c7' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300M_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x117f' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/1300_0C26.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11ed' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/65f_0A01.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11bd' [epjitsu] attach_one: start 'libusb:001:002' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: finish [epjitsu] load_fw: start [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] load_fw: read firmware file /usr/share/sane/epjitsu/65f_0A01.nal ok [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 4 bytes, timeout 1 [epjitsu] cmd: wrote 4 bytes, retVal 0 [epjitsu] out: writing 65536 bytes, timeout 1 [epjitsu] out: wrote 65536 bytes, retVal 0 [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
I think this should cover it, started capture before plugging in, then initialization and then a full page scan: https://www.dropbox.com/s/y0mz0by18r1uti5/fi65_3.pcap?dl=0 -Jonas On Sun, 15 Mar 2015 15:39:16 -0700 m. allan noahkitno...@gmail.com wrote Wireshark is fine, but this log does not contain the calibration step, which is where sane seems to fail. Can you unplug and replug the device while wireshark is running, and get a log of the initialization process? I'm not sure if wireshark can do that. allan -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
Hmm- perhaps you can try scanimage again, but at resolution 300? Also increase the epjitsu debug level to 25, and don't set the dll debug level, it is not helpful. I see a couple possible differences that have never been important with prior scanners, but perhaps are important with yours. allan On Sun, Mar 15, 2015 at 6:53 PM, Jonas Neubert jonas.neub...@gmail.com wrote: I think this should cover it, started capture before plugging in, then initialization and then a full page scan: https://www.dropbox.com/s/y0mz0by18r1uti5/fi65_3.pcap?dl=0 -Jonas On Sun, 15 Mar 2015 15:39:16 -0700 m. allan noahkitno...@gmail.com wrote Wireshark is fine, but this log does not contain the calibration step, which is where sane seems to fail. Can you unplug and replug the device while wireshark is running, and get a log of the initialization process? I'm not sure if wireshark can do that. allan -- well, I stand up next to a mountain- and I chop it down with the edge of my hand -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
I see, installing that driver on Windows adds both a 65f_.nal in C:\Windows and a 65f_0A01.nal in C:\Windows\twain_32\fjscan32. I had missed that latter last time. Unfortunately, still no change in behavior. The output remains effectively same, but just in case I'm missing something, below is the full output again. Not sure what exactly you mean by log of the scanner in action under windows, but [1] is a .pcap captured with USBPcap on Windows while scanning a full page at 300dpi. I'd be happy to collect more data or dig deeper into this myself, but I'll definitely need guidance. -Jonas [1] https://www.dropbox.com/s/1yny75ns4qq6i4u/fi65_2.pcap?dl=0 jonas@sane-scanner:~$ sudo SANE_DEBUG_DLL=256 SANE_DEBUG_EPJITSU=25 scanimage file.pnm [sanei_debug] Setting debug level of dll to 256. [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.25git [dll] sane_init/read_dlld: attempting to open directory `./dll.d' [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: done. [dll] sane_init/read_config: reading dll.conf [dll] add_backend: adding backend `epjitsu' [dll] sane_get_devices [dll] load: searching backend `epjitsu' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-epjitsu.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-epjitsu.so.1' [dll] init: initializing backend `epjitsu' [sanei_debug] Setting debug level of epjitsu to 25. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.27, from sane-backends 1.0.25git [epjitsu] sane_init: finish [dll] init: backend `epjitsu' is version 1.0.27 [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: reading config file epjitsu.conf [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/60f_0A00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x10c7' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300M_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x117f' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/1300_0C26.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11ed' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/65f_0A01.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11bd' [epjitsu] attach_one: start 'libusb:001:002' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: finish [epjitsu] load_fw: start [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] load_fw: read firmware file /usr/share/sane/epjitsu/65f_0A01.nal ok [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 4 bytes, timeout 1 [epjitsu] cmd: wrote 4 bytes, retVal 0 [epjitsu] out: writing 65536 bytes, timeout 1 [epjitsu] out: wrote 65536 bytes, retVal 0 [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd:
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
Thanks Allan, my mind was so set on thinking of output as the scanner output, I didn't even consider that this error might about the program's output! When doing 'scanimage file.pnm' the first attempt at scanning an image now ends with the same scanimage: sane_start: Error during device I/O as scanimage -T. Full output: jonas@sane-scanner:~$ sudo SANE_DEBUG_DLL=256 SANE_DEBUG_EPJITSU=25 scanimage file.pnm [sanei_debug] Setting debug level of dll to 256. [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.25git [dll] sane_init/read_dlld: attempting to open directory `./dll.d' [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: done. [dll] sane_init/read_config: reading dll.conf [dll] add_backend: adding backend `epjitsu' [dll] sane_get_devices [dll] load: searching backend `epjitsu' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-epjitsu.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-epjitsu.so.1' [dll] init: initializing backend `epjitsu' [sanei_debug] Setting debug level of epjitsu to 25. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.27, from sane-backends 1.0.25git [epjitsu] sane_init: finish [dll] init: backend `epjitsu' is version 1.0.27 [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: reading config file epjitsu.conf [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/60f_0A00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x10c7' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300M_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x117f' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/1300_0C26.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11ed' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/65f_.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11bd' [epjitsu] attach_one: start 'libusb:001:004' [epjitsu] attach_one: init struct [epjitsu] attach_one: connect fd [epjitsu] connect_fd: start [epjitsu] connect_fd: opening USB device [epjitsu] connect_fd: finish [epjitsu] load_fw: start [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] load_fw: read firmware file /usr/share/sane/epjitsu/65f_.nal ok [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 4 bytes, timeout 1 [epjitsu] cmd: wrote 4 bytes, retVal 0 [epjitsu] out: writing 65536 bytes, timeout 1 [epjitsu] out: wrote 65536 bytes, retVal 0 [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] do_cmd: start [epjitsu] cmd: writing 1 bytes, timeout 1 [epjitsu] cmd: wrote 1 bytes, retVal 0 [epjitsu] in: memset 1 bytes [epjitsu] in: reading 1 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 1 bytes [epjitsu] do_cmd: finish [epjitsu] get_stat: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 2 bytes [epjitsu] in: reading 2 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 2 bytes [epjitsu] do_cmd: finish [epjitsu] get_ident: start [epjitsu] do_cmd: start [epjitsu] cmd: writing 2 bytes, timeout 1 [epjitsu] cmd: wrote 2 bytes, retVal 0 [epjitsu] in: memset 32 bytes [epjitsu] in: reading 32 bytes, timeout 1 [epjitsu] in: retVal 0 [epjitsu] in: read 32 bytes [epjitsu] do_cmd: finish [epjitsu]
Re: [sane-devel] Error during device I/O with Fujitsu fi65-F (epjitsu backend)
Well- 'output is not a file' is your first clue. You need to redirect the output of scanimage somewhere: scanimage [your options] file.pnm see if repeated invocations of that will work for you. allan On Sat, Mar 14, 2015 at 7:42 PM, Jonas Neubert jonas.neub...@gmail.com wrote: Hi, The Fujitsu fi65-F has recently showed up on the supported device list for the epjitsu backend, but I'm struggling to get it to scan an image using Ubuntu 14.04. Below are all the details but the gist is: * sane-find-scanner finds the scanner * scanimage -L recognizes the scanner * scanimage makes the scanner move back and forth (homing?) a little but then prints scanimage: output is not a file, exiting * repeated use of scanimage fails and prints scanimage: no SANE devices found * scanimage -T shows similar behavior and prints scanimage: sane_start: Error during device I/O * I'm using the latest sane-backends from the Git repo Did anyone else get this scanner working? Or maybe has seen similar behavior with a different device? This is my first time using SANE and I'm not quite sure if this is user error or not, and if it isn't what my next steps for debugging should be. Below are my setup steps and outputs of scanimage with debug flags set. Starting from a plain Ubuntu 14.04 box with basic tooling (gcc, vi, and so on), here are my setup steps: sudo apt-get install libusb-dev git clone git://git.debian.org/sane/sane-backends.git cd sane-backends ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var BACKENDS=epjitsu make sudo make install # copy /usr/share/sane/epjitsu/65f_.nal extracted from Windows driver echo # Fujitsu fi-65F /etc/sane.d/epjitsu.conf echo firmware /usr/share/sane/epjitsu/65f_.nal /etc/sane.d/epjitsu.conf echo usb 0x04c5 0x11bd /etc/sane.d/epjitsu.conf # comment out everything but epjitsu in /etc/sane.d/dll.conf sane-find-scanner: jonas@sane-scanner:~$ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04c5, product=0x11bd) at libusb:001:003 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. First use of scanimage: jonas@sane-scanner:~$ sudo SANE_DEBUG_DLL=128 SANE_DEBUG_EPJITSU=25 scanimage [sanei_debug] Setting debug level of dll to 128. [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.25git [dll] sane_init/read_dlld: attempting to open directory `./dll.d' [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: done. [dll] sane_init/read_config: reading dll.conf [dll] add_backend: adding backend `epjitsu' [dll] sane_get_devices [dll] load: searching backend `epjitsu' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-epjitsu.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-epjitsu.so.1' [dll] init: initializing backend `epjitsu' [sanei_debug] Setting debug level of epjitsu to 25. [epjitsu] sane_init: start [epjitsu] sane_init: epjitsu backend 1.0.27, from sane-backends 1.0.25git [epjitsu] sane_init: finish [dll] init: backend `epjitsu' is version 1.0.27 [epjitsu] sane_get_devices: start [epjitsu] sane_get_devices: reading config file epjitsu.conf [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/60f_0A00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x10c7' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x1156' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/300M_0C00.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x117f' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/1300_0C26.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11ed' [epjitsu] sane_get_devices: firmware '/usr/share/sane/epjitsu/65f_.nal' [epjitsu] sane_get_devices: looking for 'usb 0x04c5 0x11bd'
[sane-devel] Error during device I/O
# on Debian testing client sane version 1.0.14-9
scanadf --device-name net:192.168.24.11:fujitsu:ScanSnap S1500:14033
--scan-script /usr/lib/pct-scanner-scripts/pct-scanner-script-process
--output-file /home/jelle/scanscript/input/image-%04d.pbm --source ADF
Duplex --resolution 600 --mode Color -x 210 -y 295 --page-width 210
--page-height 297 --start-count 1 2/dev/null
returns Error during device I/O during or after scanning
# on Debian stable server sane-utils version 1.0.21-9
with /etc/xinetd.d/saned
# default: off
# description: The sane server accepts requests
# for network access to a local scanner via the
# network.
service sane-port
{
port= 6566
socket_type = stream
wait= no
user= saned
group = saned
groups = yes
server = /usr/sbin/saned
}
Duplex color scanning used to work with this scanner, I don't remember
when... duplex lineart works without issues...
Could somebody do some duplex color netscanning tests with there systems?
Kind regards,
Jelle de Jong
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: OpenPGP digital signature
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110406/77f91e7c/attachment.pgp
[sane-devel] Error during device I/O
On 06-04-11 21:34, m. allan noah wrote: Known bug in 1.0.21. Duplex is broken on smaller scanners if the scan is too large. Very low resolution color probably works. Upgrade to 1.0.22. # on the server side apt-get install sane-utils/testing # 1.0.22-2 Apr 6 21:40:31 finley saned[9632]: saned (AF-indep+IPv6) from sane-backends 1.0.22 starting up # on client scanadf: sane_read: Error during device I/O Error during device I/O I even rebootend the server... Issue is still there... Kind regards, Jelle de Jong -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 316 bytes Desc: OpenPGP digital signature URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110406/457e4f82/attachment.pgp
[sane-devel] Error during device I/O
On the server: SANE_DEBUG_FUJITSU=15 scanimage -b --source=ADF Duplex --resolution 600 --mode Color -x 210 -y 295 --page-width 210 --page-height 297 2s1500.log hopefully there will be something useful in that log. Oh- and you might need to send the images to /dev/null if you don't have enough disk. allan On Wed, Apr 6, 2011 at 3:48 PM, Jelle de Jong jelledejong at powercraft.nl wrote: On 06-04-11 21:34, m. allan noah wrote: Known bug in 1.0.21. Duplex is broken on smaller scanners if the scan is too large. Very low resolution color probably works. Upgrade to 1.0.22. # on the server side apt-get install sane-utils/testing # 1.0.22-2 Apr ?6 21:40:31 finley saned[9632]: saned (AF-indep+IPv6) from sane-backends 1.0.22 starting up # on client scanadf: sane_read: Error during device I/O Error during device I/O I even rebootend the server... Issue is still there... Kind regards, Jelle de Jong -- The truth is an offense, but not a sin
[sane-devel] Error during device I/O
On 06-04-11 21:53, m. allan noah wrote: On the server: SANE_DEBUG_FUJITSU=15 scanimage -b --source=ADF Duplex --resolution 600 --mode Color -x 210 -y 295 --page-width 210 --page-height 297 2s1500.log hopefully there will be something useful in that log. Oh- and you might need to send the images to /dev/null if you don't have enough disk. See attachment with the log. Thanks in advance, Kind regards, Jelle de Jong -- next part -- A non-text attachment was scrubbed... Name: s1500.log.bz2 Type: application/octet-stream Size: 11707 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110406/be79c57b/attachment-0001.obj -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 316 bytes Desc: OpenPGP digital signature URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110406/be79c57b/attachment-0001.pgp
[sane-devel] Error during device I/O
On 06-04-11 22:04, Jelle de Jong wrote: On 06-04-11 21:53, m. allan noah wrote: On the server: SANE_DEBUG_FUJITSU=15 scanimage -b --source=ADF Duplex --resolution 600 --mode Color -x 210 -y 295 --page-width 210 --page-height 297 2s1500.log hopefully there will be something useful in that log. Oh- and you might need to send the images to /dev/null if you don't have enough disk. See attachment with the log. /me is installing .../libsane-extras_1.0.22.1_amd64.deb :) !!! Kind regards, Jelle de Jong -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 316 bytes Desc: OpenPGP digital signature URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110406/e0a96d24/attachment.pgp
[sane-devel] Error during device I/O
this is still sane 1.0.21 allan On Wed, Apr 6, 2011 at 4:04 PM, Jelle de Jong jelledejong at powercraft.nl wrote: On 06-04-11 21:53, m. allan noah wrote: On the server: SANE_DEBUG_FUJITSU=15 scanimage -b --source=ADF Duplex --resolution 600 --mode Color -x 210 -y 295 --page-width 210 --page-height 297 2s1500.log hopefully there will be something useful in that log. Oh- and you might need to send the images to /dev/null if you don't have enough disk. See attachment with the log. Thanks in advance, Kind regards, Jelle de Jong -- The truth is an offense, but not a sin
[sane-devel] Error during device I/O
On 06-04-11 22:06, Jelle de Jong wrote: On 06-04-11 22:04, Jelle de Jong wrote: On 06-04-11 21:53, m. allan noah wrote: On the server: SANE_DEBUG_FUJITSU=15 scanimage -b --source=ADF Duplex --resolution 600 --mode Color -x 210 -y 295 --page-width 210 --page-height 297 2s1500.log hopefully there will be something useful in that log. Oh- and you might need to send the images to /dev/null if you don't have enough disk. See attachment with the log. /me is installing .../libsane-extras_1.0.22.1_amd64.deb :) !!! aptitude install sane-utils/testing libsane-extras/testing libsane/testing That did the trick! No more Error during device I/O Would love to see those packages in sqeeze-backports! There are some nasty dependencies... (mixed now with stable) Thank you allan! Kind regards, Jelle de Jong -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 316 bytes Desc: OpenPGP digital signature URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110406/16bee385/attachment.pgp
[sane-devel] Error during device I/O running saned on WL-500GP under OpenWRT using libusb
Changing to Kernel 2.6 could only be done, to do a test on it, if it is a problem that has to do with the kernel, cause I don't know what to test else... Under Kernel 2.6 the Broadcom device, that is used in the WL-500GP for W-LAN is not supported. So I could test it by using the LAN Interface only. Stingbyte
[sane-devel] Error during device I/O running saned on WL-500GP under OpenWRT using libusb
Hello @ all. I am running latest sane-backends for OpenWRT Kamikaze Kernel 2.4 using libusb (also from the OpenWRT package). The scanner gets detected successfully by sane-scanner-find. But when I try to run scanimage -d pixma it gives me the following: [full log @ http://stingbyte.com/sane_debug.txt] [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [...] scanimage: sane_read: Error during device I/O I have seen, that there was a similiar problem reported: http://lists.alioth.debian.org/pipermail/sane-devel/2007-March/018818.html There was the tip, to add a line in backend/pixma_mp150.c like this: pixma_sleep(100); /* == INSERT THIS LINE */ I did this, now the scanner runs the full initialization process, means it scans the whole bed one time and then adjusts and remains in waiting position. Here the log output after editing pixma_mp150.c: [...] [pixma] IN T=4.455 len=8 [pixma] :06 06 00 00 00 00 00 00 [pixma] [sanei_usb] sanei_usb_write_bulk: trying to write 16 bytes [sanei_usb] : F3 20 00 00 00 00 00 00 00 00 00 00 00 00 00 0C . .. [sanei_usb] sanei_usb_write_bulk: wanted 16 bytes, wrote 16 bytes [pixma] OUT T=4.457 len=16 [pixma] :f3 20 00 00 00 00 00 00 00 00 00 00 00 00 00 0c [pixma] [sanei_usb] sanei_usb_read_bulk: trying to read 20 bytes [sanei_usb] : 06 06 00 00 00 00 00 00 01 00 00 00 03 00 02 00 [sanei_usb] 0010: 00 21 00 D9 .!.. [sanei_usb] sanei_usb_read_bulk: wanted 20 bytes, got 20 bytes [pixma] IN T=4.485 len=20 [pixma] :06 06 00 00 00 00 00 00 01 00 00 00 03 00 02 00 [pixma] 0010:00 21 00 d9 [pixma] [pixma] Current status: paper=0 cal=0 lamp=0 busy=33 [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes [...] [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [pixma] WARNING:Timed out in wait_until_ready() [sanei_usb] sanei_usb_write_bulk: trying to write 16 bytes [sanei_usb] : EF 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 . .. [sanei_usb] sanei_usb_write_bulk: wanted 16 bytes, wrote 16 bytes [pixma] OUT T=35.139 len=16 [pixma] :ef 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] [sanei_usb] sanei_usb_read_bulk: trying to read 8 bytes [sanei_usb] : 06 06 00 00 00 00 00 00 [sanei_usb] sanei_usb_read_bulk: wanted 8 bytes, got 8 bytes [pixma] IN T=35.141 len=8 [pixma] :06 06 00 00 00 00 00 00 [pixma] [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [pixma] Reader task terminated: Connection timed out [pixma] read_image():reader task closed the pipe:0 bytes received, 1683840 bytes expected scanimage: sane_read: Error during device I/O [dll] sane_cancel(handle=0x16a0) [dll] sane_close(handle=0x16a0) [pixma] pixma_close(): Canon PIXMA MP150 [sanei_usb] sanei_usb_close: closing device 0 [dll] sane_exit: exiting [dll] sane_exit: calling backend `pixma's exit function [dll] sane_exit: finished So, compiling and testing would be no problem, but I don't know really what to do next... If somebody could help me? Thanks in advance Stingbyte
[sane-devel] Error during device I/O running saned on WL-500GP under OpenWRT using libusb
are interrupt usb endpoints supported under 2.4 with the chip that is in this box? allan On 12/17/07, fireandy fireandy at covers.de wrote: Hello @ all. I am running latest sane-backends for OpenWRT Kamikaze Kernel 2.4 using libusb (also from the OpenWRT package). The scanner gets detected successfully by sane-scanner-find. But when I try to run scanimage -d pixma it gives me the following: [full log @ http://stingbyte.com/sane_debug.txt] [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [...] scanimage: sane_read: Error during device I/O I have seen, that there was a similiar problem reported: http://lists.alioth.debian.org/pipermail/sane-devel/2007-March/018818.html There was the tip, to add a line in backend/pixma_mp150.c like this: pixma_sleep(100); /* == INSERT THIS LINE */ I did this, now the scanner runs the full initialization process, means it scans the whole bed one time and then adjusts and remains in waiting position. Here the log output after editing pixma_mp150.c: [...] [pixma] IN T=4.455 len=8 [pixma] :06 06 00 00 00 00 00 00 [pixma] [sanei_usb] sanei_usb_write_bulk: trying to write 16 bytes [sanei_usb] : F3 20 00 00 00 00 00 00 00 00 00 00 00 00 00 0C . .. [sanei_usb] sanei_usb_write_bulk: wanted 16 bytes, wrote 16 bytes [pixma] OUT T=4.457 len=16 [pixma] :f3 20 00 00 00 00 00 00 00 00 00 00 00 00 00 0c [pixma] [sanei_usb] sanei_usb_read_bulk: trying to read 20 bytes [sanei_usb] : 06 06 00 00 00 00 00 00 01 00 00 00 03 00 02 00 [sanei_usb] 0010: 00 21 00 D9 .!.. [sanei_usb] sanei_usb_read_bulk: wanted 20 bytes, got 20 bytes [pixma] IN T=4.485 len=20 [pixma] :06 06 00 00 00 00 00 00 01 00 00 00 03 00 02 00 [pixma] 0010:00 21 00 d9 [pixma] [pixma] Current status: paper=0 cal=0 lamp=0 busy=33 [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes [...] [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [pixma] WARNING:Timed out in wait_until_ready() [sanei_usb] sanei_usb_write_bulk: trying to write 16 bytes [sanei_usb] : EF 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 . .. [sanei_usb] sanei_usb_write_bulk: wanted 16 bytes, wrote 16 bytes [pixma] OUT T=35.139 len=16 [pixma] :ef 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] [sanei_usb] sanei_usb_read_bulk: trying to read 8 bytes [sanei_usb] : 06 06 00 00 00 00 00 00 [sanei_usb] sanei_usb_read_bulk: wanted 8 bytes, got 8 bytes [pixma] IN T=35.141 len=8 [pixma] :06 06 00 00 00 00 00 00 [pixma] [sanei_usb] sanei_usb_read_int: trying to read 16 bytes USB error: error submitting URB: Invalid argument [sanei_usb] sanei_usb_read_int: read failed: Invalid argument [pixma] Reader task terminated: Connection timed out [pixma] read_image():reader task closed the pipe:0 bytes received, 1683840 bytes expected scanimage: sane_read: Error during device I/O [dll] sane_cancel(handle=0x16a0) [dll] sane_close(handle=0x16a0) [pixma] pixma_close(): Canon PIXMA MP150 [sanei_usb] sanei_usb_close: closing device 0 [dll] sane_exit: exiting [dll] sane_exit: calling backend `pixma's exit function [dll] sane_exit: finished So, compiling and testing would be no problem, but I don't know really what to do next... If somebody could help me? Thanks in advance Stingbyte -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] Error during device I/O running saned on WL-500GP under OpenWRT using libusb
Sorry, but what are interrupt usb endpoints? Is it the way, the device is read / written by using libusb? The USB-Chip in the Box is a VIA 6212. Kernel is 2.4.34 used libusb is 0.1.12-1 By searching I found the following: http://www.nabble.com/usb_interrupt_read-with-libusb-0.1.12-and-kernel-2.4.2 7-to4452928.html Also a discussion about libusb with interrupt endpoints, where the person, that states it is not working, receives the same returncode -22 (invalid argument) as I see, when I do a dmesg. So I would have to give it a try with Kernel 2.6.x? Cause I can't find no scanner Kernel module for 2.4.34 for OpenWRT that I could use as an alternative way of getting data from / to the device. I mean..there was not nothing - scanner gets detected and moves around... Stingbyte
[sane-devel] Error during device I/O running saned on WL-500GP under OpenWRT using libusb
if you have the option to use 2.6 kernel, i think you should. allan On 12/17/07, fireandy fireandy at covers.de wrote: Sorry, but what are interrupt usb endpoints? Is it the way, the device is read / written by using libusb? The USB-Chip in the Box is a VIA 6212. Kernel is 2.4.34 used libusb is 0.1.12-1 By searching I found the following: http://www.nabble.com/usb_interrupt_read-with-libusb-0.1.12-and-kernel-2.4.2 7-to4452928.html Also a discussion about libusb with interrupt endpoints, where the person, that states it is not working, receives the same returncode -22 (invalid argument) as I see, when I do a dmesg. So I would have to give it a try with Kernel 2.6.x? Cause I can't find no scanner Kernel module for 2.4.34 for OpenWRT that I could use as an alternative way of getting data from / to the device. I mean..there was not nothing - scanner gets detected and moves around... Stingbyte -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] Error during device I/O with network attached HP
Hello, On May 29 10:29 Steven Legowik wrote (shortened): I am trying to access the scanning function of a network attache HP LaserJet 4100MFP, but I keep getting Error during device I/O from xsane. Using scanimage I get the following: [legowik at tahiti ~/proj]$ scanimage -L device `hpaio:/net/HP_LaserJet_4100_MFP?ip=192.168.1.152' is a Hewlett-Packard HP_LaserJet_4100_MFP all-in-one [legowik at tahiti ~/proj]$ scanimage -d hpaio:/net/HP_LaserJet_4100_MFP?ip=192.168.1.152 scanimage: open of device hpaio:/net/HP_LaserJet_4100_MFP?ip=192.168.1.152 failed: Error during device I/O The hpaio driver is not part of the SANE software but a so called external backend, which comes directly from HP, see http://hplip.sourceforge.net/ See http://hplip.sourceforge.net/troubleshooting/network.html But http://hplip.sourceforge.net/supported_devices/mono_laser_mfp.html indicates that there is No network support for the LaserJet 4100mfp so that you may have to connect it only directly via USB. For details you may ask on the HPLIP mailing list: http://hplip.sourceforge.net/mailing_lists.html Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] Error during device I/O with network attached HP
Thanks Johannes, I'll see what information I can get through the HPLIP mailing list. I saw the listing on the support page that claims that the 4100 doesn't have network support, and I am confused what that means. I can ping the printer on the network. I can print to it over the network. I've been doing that for months now. Where does scanimage -L get its information from? Does reply indicate that it is connecting to the printer, or just that the driver is installed? I guess it must be the latter since I get the same response with the printer turned off. -steve On Wednesday 30 May 2007, sane-devel-request at lists.alioth.debian.org wrote: Hello, On May 29 10:29 Steven Legowik wrote (shortened): I am trying to access the scanning function of a network attache HP LaserJet 4100MFP, but I keep getting Error during device I/O from xsane. Using scanimage I get the following: [legowik at tahiti ~/proj]$ scanimage -L device `hpaio:/net/HP_LaserJet_4100_MFP?ip=192.168.1.152' is a Hewlett-Packard HP_LaserJet_4100_MFP all-in-one [legowik at tahiti ~/proj]$ scanimage -d hpaio:/net/HP_LaserJet_4100_MFP?ip=192.168.1.152 scanimage: open of device hpaio:/net/HP_LaserJet_4100_MFP?ip=192.168.1.152 failed: Error during device I/O The hpaio driver is not part of the SANE software but a so called external backend, which comes directly from HP, see http://hplip.sourceforge.net/ See http://hplip.sourceforge.net/troubleshooting/network.html But http://hplip.sourceforge.net/supported_devices/mono_laser_mfp.html indicates that there is No network support for the LaserJet 4100mfp so that you may have to connect it only directly via USB. For details you may ask on the HPLIP mailing list: http://hplip.sourceforge.net/mailing_lists.html Kind Regards Johannes Meixner
[sane-devel] Error during device I/O with ehternet attached HP LJ 3052
Hi,
I have a HP Laserjet 3052 that is connected to my computer via ethernet.
Printing with the laserjet works fine. But scanning doesn't.
The printer is found when calling scanimage with parameter -L:
$ scanimage -L
device `v4l:/dev/video0' is a Noname BT878 video (Hauppauge (bt878)) virtual
device
device `hpoj:hpjd:192.168.1.50' is a Hewlett-Packard HP LaserJet 3052
multi-function peripheral
But when I want to scan, it says:
$ scanimage --device=hpoj:hpjd:192.168.1.50
scanimage: sane_start: Error during device I/O
Now what can be the problem? I already put option dumb-read to
/etc/sane.d/hp.conf, but it didn't help. I tried to get more output from
scanimage by using -v and exported SANE_DEBUG_HPOJ=255, but scanimage says
nothing more than the error message above.
On each call of scanimage the ethernet port of the printer flashs, so obviously
the printer receives something.
So, what can I do to get near to the problem?
Regards
Marco
--
Marco Herrn _ ___ o ' (_) _ _
_(__'o 0 (_X %
(_` O o _; _;'7^'_ \;\ %
(GnuPG/PGP-encrypted mail preferred) _;\ _.\ _.';;) ;,;_/;
Key ID: 0x94620736 _ _'./_\('))_; );/\)}/`fsc
[sane-devel] Error during device I/O with ehternet attached HP LJ 3052
$ scanimage --device=hpoj:hpjd:192.168.1.50 scanimage: sane_start: Error during device I/O Now what can be the problem? I already put option dumb-read to /etc/sane.d/hp.conf, but it didn't help. I tried to get more output from scanimage by using -v and exported SANE_DEBUG_HPOJ=255, but scanimage says nothing more than the error message above. On each call of scanimage the ethernet port of the printer flashs, so obviously the printer receives something. So, what can I do to get near to the problem? hpoj seems to no longer be supported by its makers. you could upgrade to HPLIP? http://hplip.sourceforge.net/ allan -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera
[sane-devel] Error during device I/O with ehternet attached HP LJ 3052
Hi, On Mon, Oct 09, 2006 at 01:55:43PM -0400, m. allan noah wrote: $ scanimage --device=hpoj:hpjd:192.168.1.50 scanimage: sane_start: Error during device I/O [...] hpoj seems to no longer be supported by its makers. you could upgrade to HPLIP? http://hplip.sourceforge.net/ Thanks, calling hp-makeuri 192.168.1.50 now gives me the URI hpaio:/net/HP_LaserJet_3052?p=192.168.1.50. Giving to scanimage as device does work and I get a correct scan. However, scanimage -L does not list it as a device. Also xsane and xscanimage obviously try to scan from the bttv TV-Card and provides me with no possibility to select the device. How can I register this device to sane? (I am using Debian, if that helps.) Regards Marco
[sane-devel] Error during device I/O with ehternet attached HP LJ 3052
On Mon, 9 Oct 2006, Marco Herrn wrote: Hi, On Mon, Oct 09, 2006 at 01:55:43PM -0400, m. allan noah wrote: $ scanimage --device=hpoj:hpjd:192.168.1.50 scanimage: sane_start: Error during device I/O [...] hpoj seems to no longer be supported by its makers. you could upgrade to HPLIP? http://hplip.sourceforge.net/ Thanks, calling hp-makeuri 192.168.1.50 now gives me the URI hpaio:/net/HP_LaserJet_3052?p=192.168.1.50. Giving to scanimage as device does work and I get a correct scan. However, scanimage -L does not list it as a device. Also xsane and xscanimage obviously try to scan from the bttv TV-Card and provides me with no possibility to select the device. How can I register this device to sane? (I am using Debian, if that helps.) try asking the hplip folks, the makers of the backend. allan Regards Marco -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera From an...@pfeiffer.edu Mon Oct 9 20:25:19 2006 From: an...@pfeiffer.edu (m. allan noah) Date: Mon Oct 9 20:51:49 2006 Subject: [sane-devel] Error during device I/O with ehternet attached HP LJ 3052 In-Reply-To: 20061009191801.GA13160@lurkabove References: 20061008171850.GA12076@lurkabove pine.lnx.4.61.0610091353280.32...@limos.pfeiffer.edu 20061009191801.GA13160@lurkabove Message-ID: pine.lnx.4.61.0610091624170.32...@limos.pfeiffer.edu On Mon, 9 Oct 2006, Marco Herrn wrote: Hi, On Mon, Oct 09, 2006 at 01:55:43PM -0400, m. allan noah wrote: $ scanimage --device=hpoj:hpjd:192.168.1.50 scanimage: sane_start: Error during device I/O [...] hpoj seems to no longer be supported by its makers. you could upgrade to HPLIP? http://hplip.sourceforge.net/ Thanks, calling hp-makeuri 192.168.1.50 now gives me the URI hpaio:/net/HP_LaserJet_3052?p=192.168.1.50. Giving to scanimage as device does work and I get a correct scan. However, scanimage -L does not list it as a device. Also xsane and xscanimage obviously try to scan from the bttv TV-Card and provides me with no possibility to select the device. How can I register this device to sane? (I am using Debian, if that helps.) try asking the hplip folks, the makers of the backend. allan Regards Marco -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera From olaf.meeuwis...@avasys.jp Tue Oct 10 00:15:51 2006 From: olaf.meeuwis...@avasys.jp (Olaf Meeuwissen) Date: Tue Oct 10 00:18:08 2006 Subject: [sane-devel] Iscan install In-Reply-To: op.tg01lwgvibo...@linux.site (Wolfram Heider's message of Sat, 07 Oct 2006 03:11:46 +0200) References: 4526c656.9000...@cox.net 200610061638.00978.russbuc...@nwi.net op.tg01lwgvibo...@linux.site Message-ID: 87psd158lk@geek.avasys.jp Wolfram Heider wolframhei...@web.de writes: On Sat, 07 Oct 2006 01:38:00 +0200, Russbucket russbuc...@nwi.net wrote: On Fri October 6 2006 14:10, Gary Montalbine wrote: Tried to install iscan 2.3 and got the following errors: rpm -ivh iscan-2.3.0-1.c2.i386.rpm Preparing...### [100%] file /usr/lib/sane/libsane-epkowa.so.1.0.15 from install of iscan-2.3.0-1.c2 conflicts with file from package libsane1-1.0.18-7mdv2007.0 file /usr/share/locale/de/LC_MESSAGES/iscan.mo from install of iscan-2.3.0-1.c2 conflicts with file from package sane-backends-1.0.18-7mdv2007.0 [snip] Tried to install iscan 2.1 and got the following error: rpm -ivh iscan-2.1.0-1.c2.i386.rpm Preparing...### [100%] file /usr/lib/sane/libsane-epkowa.so.1.0.15 from install of iscan-2.1.0-1.c2 conflicts with file from package libsane1-1.0.18-7mdv2007.0 I have a Perfection 3490 photo scanner using a new installed mandriva 2007. [snip] There seem to be some flaws in the mdk SANE.rpm. Ich would recommend to uninstall and substitute it with the .tar.gz from the SANE-server. Yup! Seems mandriva decided to make iscan part of the SANE project ... and did a bad job at that (message catalogs for the frontend in the sane-backends package???). I'll be filing a bug report to get iscan removed from their packages. If they insist on providing iscan, they should do so in a separate package. In the mean time, you can --force the install (at the risk of getting more of these warnings when you try updating Mandriva's SANE packages). Hope this helps, -- Olaf Meeuwissen EPSON AVASYS Corporation, SE1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] Error during device I/O
t takahashi gambarim...@gmail.com wrote: Hi, The debugging output is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272304, which is (a href=http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272304;here/a) The logs you sent are not from the hpoj backend you're using, thus they show nothing useful to find out what the problem is. Please try again with SANE_DEBUG_HPOJ=255 and send the logs to both the Debian bug and the list. The message from the kernel log, if pertaining to the scanner, indicates a timeout while reading from the scanner. This usually indicates the scanner is stuck after it received something that confused it, for whatever reason. It could also be a bug in the USB layer, you could try to upgrade your kernel if it's not current. JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169
[sane-devel] Error during device I/O
Hi, On Mon, Nov 15, 2004 at 04:48:09PM -0700, t takahashi wrote: I'm stuck on this one. $ scanimage -v -y 279.4 --mode lineart --resolution 300 \ --batch-scan=yes --batch=aaa--%02d--line300.pnm Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 scanimage: sane_start: Error during device I/O scanimage: read 0 bytes in total Scanned page 1. (scanner status = 9) Any ideas on how I can fix this or figure out what's going on? Does it also happen if you scan single pages (no batch-scan)? Does it always happen after the first scan succeeded as your log shows? Bye, Henning
[sane-devel] Error during device I/O
I'm stuck on this one. $ scanimage -v -y 279.4 --mode lineart --resolution 300 \ --batch-scan=yes --batch=aaa--%02d--line300.pnm Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 scanimage: sane_start: Error during device I/O scanimage: read 0 bytes in total Scanned page 1. (scanner status = 9) The debugging output is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272304, which is (a href=http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272304;here/a). Any ideas on how I can fix this or figure out what's going on? This is completely stopping the single most important purpose of my computer, and my scanner has been idle for weeks. Thanks.
