[sane-devel] Mustek Bearpaw 2400 CU plus scanner and gt68xx backend

[Henning Meier-Geinitz]

Hi,

On Sun, Oct 09, 2005 at 08:55:57PM +0100, Charles Mangles wrote:
> attached

Ok, let's have a look:
> [sanei_debug] Setting debug level of gt68xx to 255.
> [gt68xx] SANE GT68xx backend version 1.0 build 67 from sane-backends 1.0.15

That's old :-)

> [gt68xx] >> 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00 41 01 00 00 00 00 00 00
> [gt68xx] gt68xx_device_generic_req: reading response failed: Invalid argument

This is what I expected. That firmware doesn't like the "stop scan"
command. So you need the current development version of the backend.

> I looked at the box it came in again and it doesn't actually say it's a
> usb 2.0 device.  I assumed it was because when I plug the scanner into
> the old 1.1 port in my computer and try and do anything I get this
> message in /var/log/syslog:
> 
> Oct  9 19:51:10 bayard kernel: usb 1-2: new full speed USB device using
> uhci_hcd and address 5

"full speed" means that it's slow (11 MBit/s). 480 MBit/s would be
named "high speed".

> Oct  9 19:53:30 bayard kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 192 rq 1 len 8 ret -84

I guess that's the error from the "stop scan" command.

> Oct  9 19:53:30 bayard kernel: hub 1-0:1.0: over-current change on port 1

When this happens when the scanner is connected, something is wrong
with the hardware. It can happen when you unplug the scanner, however.
It means that you hub thinks that the scanner needs too much power.
Usually this happens if an external hub's power supply is not
connected. If it's an internal hub /normal USB card or built-in), I
guess there is something wrong with the internal card's power supply
or measurement, the cabling or the scanner itsself.

> and after that, nothing plugged into that port is detected and I haven't
> found a way to reset it without rebooting, yet.

Have you tried to rmmod all usb-related kernel modules including
uhci/ohci-hcd?

> Perhaps that's an unrelated problem :-(

I think so. As mentioned before, trouble withe SANE should be solved
by replugging the scanner. In fact, any trouble with USB devices
should be reset when replugging is done.

> OK, I went to the SANE website and followed their recommendations for
> downloading the latest version of SANE.  Then I tried running xsane
> again with the same error message as before.  A new log is also attached
> (log2.txt).  The entries in /var/log/syslog were:

You still use the old version:
> [sanei_debug] Setting debug level of gt68xx to 255.
> [gt68xx] SANE GT68xx backend version 1.0 build 67 from sane-backends 1.0.15
                                                 ^^		       ^^^^^^^

Probably this is because you haven't unistalled the old one.
Ugly trick: use /usr/local/bin/scanimage or something like:
LD_PRELOAD=/usr/local/lib/libsane.so xsane
						 
> Oct  9 20:34:54 bayard kernel: usb 2-1: xsane timed out on ep0in
> Oct  9 20:34:54 bayard kernel: usb 2-1: usbfs: USBDEVFS_CONTROL failed  cmd xsane rqt 192 rq 1 len 8 ret -110

Same problem as above.

Bye,
  Henning