[sane-devel] Re: scanner not recognised part II

[m. allan noah]

when the driver is unloaded, it may say something. so you could go back 
thru your /var/log/messages, and see where this happens. there may be some 
clue on the preceding lines about why this happened.

if the kernel is automatically booting the module (because it believes it 
is unused) then you may be able to add a parameter to modules.conf to tell 
the kernel not to do this.

otherwise, you may have to do some silly magic like put your 'modprobe' 
command in the file /etc/rc.d/rc.local, which is a shell script that is 
run at the end of system init.

allan

On Mon, 1 Mar 2004, Paul Frisson wrote:

> Yes, I already checked, and the line is there indeed, so the driver must be 
> unloaded.
> 
> Meanwhile I rebooted the machine and of course, the driver was gone, so I'm 
> now looking for a way to load - or reload - it automatically. 
> 
> Le Lundi 1 Mars 2004 00:41, Karl Heinz Kremer a écrit :
> > According to your boot messages, it was loaded at boot time. Something
> > must have
> > unloaded it. I have no idea why this happens. Usually, the driver
> > should not get
> > unloaded automatically.
> >
> > Check to see if you have this entry in your /etc/modules.conf file:
> > alias scsi_hostadapter fdomain
> >
> > If not, try to add it and see if this makes a difference.
> 
> 
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>              to sane-devel-request at lists.alioth.debian.org
> 

-- 
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera