when the driver is unloaded, it may say something. so you could go back=20 thru your /var/log/messages, and see where this happens. there may be some= =20 clue on the preceding lines about why this happened.
if the kernel is automatically booting the module (because it believes it= =20 is unused) then you may be able to add a parameter to modules.conf to tell= =20 the kernel not to do this. otherwise, you may have to do some silly magic like put your 'modprobe'=20 command in the file /etc/rc.d/rc.local, which is a shell script that is=20 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=20 > unloaded. >=20 > Meanwhile I rebooted the machine and of course, the driver was gone, so I= 'm=20 > now looking for a way to load - or reload - it automatically.=20 >=20 > Le Lundi 1 Mars 2004 00:41, Karl Heinz Kremer a =E9crit : > > 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. >=20 >=20 > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-requ...@lists.alioth.debian.org >=20 --=20 "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
