Dear Henning,
Many thanks!
I had done everything you suggested already, including:
modprobe scanner vendor=0x04b8 product=0x0110
(which is suggested by various authors, guidance notes, etc), but I had not
done:
rmmod scanner
modprobe scanner vendor=0x04b8 product=0x0110
so I suspect the rmmod, removed something nasty, even though it fired back
the error message:
module scanner is not loaded
By the way, for those that follow after (I spent a few hours going through
the archived mails last night ;-)> ! ):
A RED entry in the UsbView left hand window seems
to mean (at least among other things) "no driver".
It is now black.
Regards,
Michael.
On Saturday 16 March 2002 11:32, Henning Meier-Geinitz wrote:
> Hi,
>
> On Sat, Mar 16, 2002 at 07:46:23AM +0000, Michael Chapman wrote:
> > <SANE_DEBUG_EPSON=128 scanimage --device epson:/dev/usbscanner>
> > returns
> > [epson] sane_start: /dev/usbscanner open (USB) failed: No such device
>
> /dev/usbscanner exists has correct permissions? Is the scanner found
> by the kernel? -> try sane-find-scanner and cat /proc/bus/usb/devices .
>
> > then /var/log/messages has "Unable to access minor data" for scanner.c
>
> That's ok. SANE tries to open all available /dev/scanner* devices and
> so you get this message for every device not connected to a scanner.
>
> > PS usbview shows the scanner there but in RED, and in the information
> > field has the line "Name: (none)", which I presume is also indicative of
> > the no driver problem ???
>
> I have no idea, my version of usbview doesn't show anything red (but I
> don't have any Epson scanner). Is there any indication that the kernel
> USB scanner driver ("usbscanner") has detected your device? Otherwise
> you must tell the scanner module the vendor and device ids:
>
> rmmod scanner
> modprobe scanner vendor=0x0001 product=0x0002
>
> Get the correct ids from usbview.
>
> Bye,
> Henning
> _______________________________________________
> Sane-devel mailing list
> [email protected]
> http://www.mostang.com/mailman/listinfo/sane-devel
