Ok, thanks for the clarification, I discovered that there was a duplicate /etc/sane.d directory in /usr/etc. I ran the sane "make install" to overwrite my installed sane library, which probably explains it - I have now removed the original sane package completely, then reinstalled from CVS and my scanner still hangs up.<br>
<br>The steps I see are :<br><br>1 - Start scanimage -T<br>2 - Scan head moves to the "start scan" position<br>3 - Scan head cycles through colours (light on/off)<br>4 - Scan head starts scan pass, but then stops about 1/3 of the way accoss the page.<br>
5 - Scan head returns to "start scan" position<br>6 - Scanner is unresponsive (returns -ETIMEDOUT to everything) until USB cable is removed and replaced or scanner is power cycled.<br><br>I have taken usb sniffs from windows and I can't spot any significant differences, but comparing the usbsniff format with the usbmon capture is pretty difficult.<br>
<br>When I have more time I plan to hack the usbsniff code so it will output in a format that's diffable with usbmon, and put some more debug into scanimage to try and spot where the problem occurs.<br><br><br><br><br>
<div class="gmail_quote">2009/2/25 Gleb Baryshev <span dir="ltr"><<a href="mailto:gleb.baryshev@gmail.com">gleb.baryshev@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Steve Hardy wrote:<br>
> I have similar problems to this with the pixma backend and a Canon<br>
> MF4660 - only my MFP *always* returns the -ETIMEOUT response after<br>
> moving the scan head to the end of the panel in preparation for the scan.<br>
<br>
</div>I can't yet define exactly what actions hang up my scanner. At least,<br>
when I scan continuously, using the same program, all work well.<br>
By the way, successful scanning adds three lines like this to the kernel<br>
ring buffer:<br>
usb 1-1: usbfs: interface 1 claimed by usblp while 'xsane' sets config #1<br>
(or 'scanimage' instead of 'xsane')<br>
<div class="Ih2E3d"><br>
Dennis Lou wrote:<br>
> If you keep reading, Gleb solved his problem by manually removing his old version of sane prior to re-installing a fresh CVS version (apparently automated package removal wasn't doing a complete job). Perhaps that will also solve your problem being that you two are experiencing similar things?<br>
<br>
</div>Actually, removing of old files was aimed to solve a problem when<br>
scanimage and xsane could only be run from /usr/local/etc/sane.d (i.e.<br>
scanimage couldn't find the scanner, but after 'cd<br>
/usr/local/etc/sane.d' it could). At first it helped, but after reboot<br>
only xsane could run from anywhere. This isn't a big problem, but the<br>
fact remains.<br>
<div><div></div><div class="Wj3C7c"><br>
Gleb<br>
<br>
--<br>
sane-devel mailing list: <a href="mailto:sane-devel@lists.alioth.debian.org">sane-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/sane-devel" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/sane-devel</a><br>
Unsubscribe: Send mail with subject "unsubscribe your_password"<br>
to <a href="mailto:sane-devel-request@lists.alioth.debian.org">sane-devel-request@lists.alioth.debian.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Steve Hardy<br><br>Applied Realtime Systems Limited<br><a href="http://www.appliedrealtime.co.uk">www.appliedrealtime.co.uk</a><br>Tel : 0845 8678251<br>Fax : 0845 8678241<br>