On Wed, Feb 27, 2002 at 03:20:12AM -0700, Roberto Mello wrote: > > Well, what do you know. I thought the problem was with the libsane that I > had (1.0.6) so I built a new debian package with 1.0.7. Still had the same > problem with xscanimage (which BTW, will never leave or stop, and won't > respond to kill -9 or kill -15 once it gets stuck). > > Then I installed xsane which worked flawlessly! I suspect it would have > worked with 1.0.6 as well.
It seems I'm still getting some problems (the day after!)... It looks like it's something that's happenning as the scanner warms up or something in the communication. xsane is able to scan the image most of the times, but sometimes during acquiring the preview or scanning the actual image, I get this: Feb 27 09:37:44 brasileiro kernel: hub.c: USB new device connect on bus1/1, assigned device number 2 Feb 27 09:37:44 brasileiro kernel: usb.c: USB device 2 (vend/prod 0x4b8/0x110) is not claimed by any active driver. Feb 27 09:37:47 brasileiro kernel: usb.c: registered new driver usbscanner Feb 27 09:37:47 brasileiro kernel: scanner.c: probe_scanner: User specified USB read timeout - 180 Feb 27 09:37:47 brasileiro kernel: scanner.c: 0.4.6:USB Scanner Driver Feb 27 09:38:43 brasileiro kernel: [ca48a0c0] link (0a48a092) element (0a48d1e0) Feb 27 09:38:43 brasileiro kernel: 0: [ca48d1e0] link (00000001) e3 IOC Feb 27 09:38:43 brasileiro kernel: Stalled Babble Length=3 MaxLen=3 DT1 EndPt=2 Dev=2, PID=69(IN) (buf=0e888000) Feb 27 09:38:43 brasileiro kernel: scanner.c: read_scanner(0): funky result:-75. Consult Documentation/usb/scanner.txt. -Roberto -- +----| http://fslc.usu.edu/ USU Free Software & GNU/Linux Club |------+ Roberto Mello - Computer Science, USU - http://www.brasileiro.net/ http://www.sdl.usu.edu/ - Space Dynamics Lab, Developer As easy as pi=3.14159265358979323846264338327950288419716939937511
