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

[Charles Mangles]

Hi,

like Mr Ibbotson, in his mail of Fri Aug 19 15:29:19 UTC 2005, I have
recently purchased a Mustek 2400 CU plus scanner, which i connected via
a Belkin F5U222 USB2.0 cardbus card to my Toshiba Tecra 8100, which is
too old to have a USB2.0 port. After various struggles to get
everything to work (it transpired that the scanner would kill the usb
functions unless the Belkin card was fed from its external power supply)
, I discovered I had the same problem as Mr Ibbotson, in that the
scanner would read only half the page, so that the resulting image was a
lengthways half of the A4 document in the scanner, stretched across the
page to fit an A4 sized image.

Following the advice given subsequently, i.e. downloading the latest
PS2Dfw2.usb firmware and renaming it to PS2Dfw.usb, resulted in the
following error message when I tried to run xsane "failed to open device
gt68xx:libusb:003:003". After unplugging the USB card and the scanner,
reinserting them and replacing the new PS2Dfw.usb file with the original
one, I tried again, only to get the error message "failed to start
scanner: Invalid argument" and a message in the kernel log.

"bayard kernel: usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd xsane rqt 64
rq 1 len 64 ret -110"

Every time the scanner fails to work, I have to unplug the usb card and
the scanner from the card, reinsert the card, wait for about two minutes
and reinsert the scanner usb plug, otherwise neither sane or scanimage
can detect the scanner.

A final, possibly related, mystery is that my scanner is detected as a
usb1.1 device (full-speed), not a usb 2.0.

Has anyone any idea what I am not doing/ doing wrong?

I am running Debian Sarge 2.6.11, xsane version:

xsane-0.97 (c) 1998-2005 Oliver Rauch
Email: ***@xsane.org
package xsane-0.97
compiled with GTK-2.6.1
with GIMP support, compiled with GIMP-2.2.3
XSane output formats: jpeg, png, pnm, ps, tiff, txt

and the output of "scanimage -L" is

device `gt68xx:libusb:003:002' is a Mustek BearPaw 2400 CU Plus flatbed
scanner

[Charles Mangles]

Just to say that I have discovered that the error "failed to start
scanner: Invalid argument" and the message in the kernel log "bayard
kernel: usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd xsane rqt 64 rq 1
len 64 ret -110" seem to have been caused by not having the external
power supply to the Belkin usb2.0 cardbus card plugged in. I'm still
only getting an image of half a page, though.

[Henning Meier-Geinitz]

Hi,

Post by Charles Mangles
Following the advice given subsequently, i.e. downloading the latest
PS2Dfw2.usb firmware and renaming it to PS2Dfw.usb, resulted in the
following error message when I tried to run xsane "failed to open device
gt68xx:libusb:003:003". After unplugging the USB card and the scanner,
reinserting them and replacing the new PS2Dfw.usb file with the original
one, I tried again, only to get the error message "failed to start
scanner: Invalid argument" and a message in the kernel log.

Please send a log file, e.g. like this:

SANE_DEBUG_GT68XX=255 scanimage >/dev/null 2>log.txt

Post by Charles Mangles
Every time the scanner fails to work, I have to unplug the usb card and
the scanner from the card, reinsert the card, wait for about two minutes
and reinsert the scanner usb plug, otherwise neither sane or scanimage
can detect the scanner.

In the (seldom) case that one of my gt68xx scanners gets locked due to
bad commands, it's sufficient to pull their USB plug and plug it in
again. Your description seems to indicate that there is either a hardware
problem with your card or with the driver of that card. It's not
related to the backend or SANE.

Post by Charles Mangles
A final, possibly related, mystery is that my scanner is detected as a
usb1.1 device (full-speed), not a usb 2.0.

As it's is a USB 1.1 device, that's quite normal :-)
The GT6801 and GT6816 chips are both USB 1.1 only.
The sane-backends version is important. As explained in the mail you
refer to, you need a current development version of SANE (or at least
a current gt68xx backend). SANE 1.0.16 is not recent enough.

Bye,
Henning

[Henning Meier-Geinitz]

Hi,

attached
[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
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
[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