[sane-devel] HP 7450C libusb problems

[insane@piments.com]

Thanks Henning,

> That scanner is listed as "untested" so you were lucky if it worked.

True but it seems to be very close to the FB630U for which the backend was  
written. Anyway it has worked with sane at one stage, and pretty well.  
Hopefully I can soon provide some feedback and it will be classed as  
tested!

> SANE may trigger a bug in the
> kernel by accessing the scanner differently.

Fair point, vuescan does not prove anything more that the hardware is good  
and CAN work on Linux.

0000:00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1  
Controller (rev 23)
0000:00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1  
Controller (rev 23)

So I am on UHCI, seems like others having pbs are using this driver as  
well (I also compiled ehci as module but it did not change the bahaviour).

Here's an end snip of the USB debug output.

[sanei_usb] 0000: 01                                               
................
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132,  
index = 0, len = 1
[sanei_usb] 0000: 00                                               
................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 12, value = 131,  
index = 0, len = 1
[sanei_usb] 0000: 01                                               
................
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132,  
index = 0, len = 1
[sanei_usb] 0000: 00                                               
................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 12, value = 131,  
index = 0, len = 1
[sanei_usb] 0000: 01                                               
................
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132,  
index = 0, len = 1
[sanei_usb] 0000: 00                                               
................
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 12, value = 131,  
index = 0, len = 1
[sanei_usb] 0000: 01                                               
................
[sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132,  
index = 0, len = 1

This is the loop it gets stuck in and hangs sane. xsane xscanimage etc.  
all lock up. I Cntl-C out at this point.



Now here's the end of the Canon_bebug output:

[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */
[canon630u] read_byte(fd, 0x01, &result); /* got 00 */


I dont know if that enables you to see more of what is happening.

Regards, Peter.



On Sun, 6 Jun 2004 20:25:52 +0200, Henning Meier-Geinitz  
<henning@meier-geinitz.de> wrote:

> Hi,
>
> On Sun, Jun 06, 2004 at 08:12:51PM +0200, insane@piments.com wrote:
>> Yes this seems to be a pretty broad issue with sane/libusb and more  
>> recent
>> 2.6.x kernels
>>
>> I am getting very similar behaviour from my canoscan FB636U on
>> Athlon-XP/Gentoo/2.6.6 kernel.
>
> That scanner is listed as "untested" so you were lucky if it worked.
>
>> [ebuild   R   ] media-gfx/xsane-0.93
>> [ebuild   R   ] media-gfx/sane-backends-1.0.14-r2
>> [ebuild   R   ] dev-libs/libusb-0.1.8
>
> Some more data points: Linux 2.6.7rc2, ohci host controller, libusb 0.1.8
>
> The following scanners do work without any trouble:
>
> Mustek 1200 CU (mustek_usb)
> Mustek BearPaw 1200 CU (gt68xx)
> Mustek BearPaw 2400 CU Plus (gt68xx)
> Plustek OpticPro U16B (gt68xx)
> Plustek Opticpro UT16 (plustek)
>
>> It was scanning briefly at one stage and I think I was running early 2.6
>> kernels at that time although I can not be precise.
>>
>> I does not appear to be a problem in the kernel itself since vuescan  
>> works
>> perfectly on this system.
>
> That may be a hint, but needn't as SANE may trigger a bug in the
> kernel by accessing the scanner differently.
>
>> If sane is going to continue to be an option it appears some dev work is
>> needed to resolve this issue.
>
> First, we need to find out when this bug happens and in which part of
> SANE or the kernel it is.
>
>> Could someone remind me what the debug line is for this scanner so I can
>> get more detailed output.
>
> export SANE_DEBUG_CANON630U=255
>
> For USB debug messages try also:
>
> export SANE_DEBUG_SANEI_USB=255
>
> Bye,
>   Henning
>



-- 
Using M2, Opera's e-mail client: on Gentoo Linux