plustek@linuxhacker.org

plustek@linuxhacker.org


Subject: load scanner-module for EPSON Perfection 1260 automatically at boot-time with SuSE 8.1?
From: Christoph Haas
Date: 18 Jan 2003 09:28:42 +0100

Hi Gerhard,

sorry, that my response is delayed ... but I'm weekdays abroad (with
Internet-access, but without Scanner ;-)

On Mon, 2003-01-13 at 08.17 Gerhard Jaeger wrote:
> Hi,
> 
> On Sonntag, 12. Januar 2003 19:19, Christoph Haas wrote:
> [SNIPSNAP]
> > I guess this should load the scanner module automatically at boot-time
> > ... _only_ if I make a modprobe scanner, then sane-find-scanner finds
> > the two devices:
> > found USB scanner (vendor=0x04b8, product=0x011d) at /dev/usb/scanner0
> > found USB scanner (vendor=0x04b8, product=0x011d) at /dev/usbscanner
> > and the scanner is accessable to xsane 0.90 or kooka.
> >
> > What else then the above entry in /etc/modules.conf do I have to do,
> > that the scanner-module is loaded automatically at boot-time?
> >
> 
> At least your scanner module has to be loaded, when the scanner is detected.
> This will be done with the hotplug tools under SuSE8.
> AFAIK it should be enough to edit the file /etc/hotplug/usb.distmap:
> Look for the first line starting with "scanner", copy this line and
> edit the vendor and product ID to 0x04b8 0x011d (should be column 3 and 4)
> After that replug your scanner and the scanner module should have been
> loaded automatically...
> 
> Gerhard

the scanner module for my EPSON Perfection 1260 on my SuSE 8.1-system,
still doesn't load automatically at boot-time. 

Hotplugging is activated! I tried the following things (besides the
existing entry in /etc/modules.conf):
- made the entry in /etc/hotplug/usb.distmap
scanner	0x0003	0x04b8	0x011d	0x0000	0x0000	0x00	0x00	0x00	\
0x00	0x00	0x00 0x00000000
- made the entry in /etc/hotplug/usb.usermap

but in /var/log/messages there it still keeps on saying "kusterdingen01
kernel: usb.c: USB device 2 (vend/prod 0x4b8/0x11d) is not claimed by
any active driver." at boot-time :-<<

I even tried make the entry in /lib/modules/2.4.19-4GB but this caused
an error at boot-time when loading the modules and was corrected by the
system itself!

If I do a insmod scanner vendor=0x04b8 product=0x011d or a modprobe
scanner, all works perfectly - but it should be automatically ...

What do I else have to do? Lost .-<<
Christoph.


--
Mit freundlichen Gruessen / Yours sincerely
Christoph Haas
Linux User #99546



plustek@linuxhacker.org