[sane-devel] Re: microtek slimscan C6 USB

[jrlannon1 at cox.net]

I don't think we are looking at a cable or H/W issue because the scanner 
works fine under OS 10.3.2 using Ed Hamrick's VueScan.

Haven't tried a more recent kernel, just used the Yellowdog 3.0.1 configured 
kernel right out of the box. 

You see the same error messages without the microtek module loaded.  If the 
Slimscan C6 USB is connected at boot-up, the messages appear.

In the yellowdoglinux lists, someone suggested adding the line 

usb /dev/usb/scanner0

into microtek2.conf.  The poster did a similar thing to the epson.conf file and 
it worked for him.  I'm going to try it and see what happens.

Thanks for your response.
 
> 
> From: Henning Meier-Geinitz <henning at meier-geinitz.de>
> Date: 2004/03/15 Mon PM 12:57:52 EST
> To: SANE Mailing List <sane-devel at lists.alioth.debian.org>
> Subject: Re: [sane-devel] microtek slimscan C6 USB
> 
> Hi,
> 
> On Thu, Mar 11, 2004 at 08:06:37PM -0500, jrlannon1 at cox.net wrote:
> > I'm trying to get my microtek slimscan C6 USB scanner working under 
> > YellowDog Linux 3.0.1 (2.4.22-2g Kernel) running on an eMac.  
> 
> Have you tried a more recent kernel?
> 
> Even without the microtel module, your scanner should be found by
> sane-find-scanner as a USB device and in /proc/bus/usb/devices.
> 
> > Finally I plug in the scanner:
> 
> Does it work if you don't load the microtek module?
> 
> > Mar 11 16:53:37 localhost kernel: hub.c: new USB device 10:18.0-2, 
assigned address 2
> > Mar 11 16:53:37 localhost kernel: usb.c: failed to set device 2 default 
configuration (error=-110)
> 
> That's "Connection timed out". The scanner didn't want to talk to us
> when the configuration was set. That's one of the first commands so it
> may be a hardware issue. Is the cable ok?
> 
> > Mar 11 16:53:37 localhost kernel: hub.c: new USB device 10:18.0-2, 
assigned address 3
> > Mar 11 16:53:37 localhost kernel: usb.c: failed to set device 3 default 
configuration (error=-110)
> 
> Two devices on the same scanner? Strange.
> 
> If this happens also with a current kernel, ask the linux-usb-devel
> mailing list. That's not a SANE issue but Linux kernel and/or
> hardware.
> 
> Bye,
>   Henning
> 
> --