[sane-devel] Xsane go.... -no go.... "Bugger!"

[Henning Meier-Geinitz]

Hi,

On Sun, Aug 03, 2003 at 06:20:20PM +1200, Frank wrote:
> Then I went and replaced my second USB2 connected camera with a USB2 hub. I 
> noticed almost immediately that Linux-Mandrake did not prefer to have the 
> "Self" power enabled and worked better without that feature running. I did 
> not change the (First) USB2 connector and left the scanner connected to it 
> directly.

Which kernel version do you use? What do you mean by Linux prefers
non-self power mode? Error messages?

So you have no problems if you unplug the hub? That's most probably a
problem in the Linux kernel drivers (or the hardware).

I don't know the details about your specific scanner, but here are
some general tips for USB trouble:

Disable apic and acpi in the kernel. Both seem to cause USB trouble in
some configurations. I think there are boo-time options, check google
for "noapic".

> 1. The scanner light stays on all the time, even after a "Halt" and 

That's probably because SANE hasn't detected it and so can't turn off
the lamp or set a timer to turn it off. What you see now, is the
standard behaviour of the scanner if no driver is loaded.
> 
> 2. Xsane [and other programs, eg. OOo1.1rc] can no longer access the 
> scanner.....
> 
> "Failed to open device 'snapscan:/dev/usb/scanner0'. Invalid argument."

Any error messages in syslog (/var/log/messages)? The scanner is
listed by scanimage -L correctly?

Try 

SANE_DEBUG_SNAPSCAN=255 scanimage >/tmp/image.pnm 2>log

and send us the file "log". It should contain debugging messages.

Bye,
  Henning