On Wed, May 07, 2008 at 09:39:25AM +0900, Olaf Meeuwissen wrote: > Phil Reynolds <phil-sane at tinsleyviaduct.com> writes: > Looks like that "meta"info never got to the backend, for whatever > reason. This is most likely a timing and/or a hardware problem. > > > [epson] scan_finish() > > [epson] send buf, size = 2 > > [epson] buf[0] 1b . > > [epson] buf[1] 66 f > > [epson] w_cmd_count = 45 > > [epson] r_cmd_count = 3804 > > [epson] send buf, size = 2 > > [epson] buf[0] 1b . > > [epson] buf[1] 66 f > > [epson] w_cmd_count = 46 > > [epson] r_cmd_count = 3804 > > [epson] w_cmd_count = 46 > > [epson] r_cmd_count = 3804 > > [epson] receive buf, expected = 4, got = 0 > > Ditto here. The expected reply is not making its way to the backend. > > > [snip] > > The preview stopped about 14 cm down the image area. > > Have you experienced other problems your desktop's USB port when using > large amounts of data? Something like not being able to reliably copy > large files to/from a USB stick for example.
I have had occasional failures with accessing hard disks over the USB, but I couldn't be sure the disks were supposed to be good. I may now have to retest the ones I've put for scrapping. > The fact that things work okay on your laptop (and assuming that you > use the same version of the same backend there) seem to point the > finger to your desktop's USB hardware (or the kernel support for it). I use the same version I was trying to use... I backported a newer one to my desktop in an attempt to see what was going on. I added a USB card from my spares, and the scanner works on that - within limits but then again it always did. It looks very like a motherboard fault. -- Phil Reynolds o ____ mail: phil-sane at tinsleyviaduct.com |L_ \ / Web: http://www.tinsleyviaduct.com/phil/ (_)- \/ Waltham 66, Emley Moor 69, Droitwich 79, Windows 95
