Dunno about /etc/modules -- do you mean modules.conf? That is one beastie I've never understood very well, mainly because I don't know what all the alias names are that might be used. But in general, it modifies the behavior of modprobe, for example specifying optional parameter values, or prerequisite modules.
I'm pretty sure there's a way to specify your SCSI driver in there, but usually I just put a modprobe command in the startup scripts. I'd love to hear more about what the Best Way is. :-) -- Rod http://www.sunsetsystems.com/ On Wednesday 16 October 2002 10:14 am, [EMAIL PROTECTED] wrote: > On Wed, Oct 16, 2002 at 10:07:13AM -0700, Tim Riley wrote: > > [EMAIL PROTECTED] wrote: > > > AIC7000 support > > > > > > Covers many of the 29xx series... the 29 (two digits) is the important > > > part, as the rest often described the bytespeed. Not sure if it still > > > does anymore though... > > > > > > 2940 (40MB/sec), 2980 (80MB/sec), 29160 (160MB/sec) > > > > > > I do have a 2980, 29160 and both use the AIC7xxx linux driver... > > > > It finally works. The lesson learned is that adding the driver > > didn't stick across rebooting. So following was added in > > /etc/rc.d/rc.local: modprobe aic7xxx > > I dont recall the status of /etc/modules in newer kernels and Debian, > but with the 2.2 series (and possibly later) /etc/modules can be > configured to specify what modules should be loaded at start. You may > want to examine this file. Modules just need to be specified by name, > one per line for loading on boot. > > You may want to see if your system includes an /etc/modules text file > and then add: > aix7xxx > to one line by itself, reboot and see if it is auto-loaded. > > > Thanks to all who responded and to [EMAIL PROTECTED] for > > supplying the SCSI Card and drive. > > HTH > -ME _______________________________________________ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
