Hi All,

I'm new to this site - so hello & more power to your mouse.
I'm running kernel version 2.4.20-8
At the moment I have to manually do:

modprobe aic7xxx

after reboot so that I can access my scsi DAT drive (without the 'modprobe' anything trying to use /dev/st0 just gets 'no such device or address'). From other threads I think it should be possible to get aic7xx loaded automatically on boot, but can't seem to make it work.

Here's my modules.conf:

alias eth0 e1000
alias eth1 e100
alias usb-controller ehci-hcd
alias usb-controller1 usb-uhci
alias scsi_hostadapter aic7xxx

Here's the output from 'lsmod' after boot but before 'modprobe aic7xxx':

Module Size Used by Tainted: PF
i830 74336 1
agpgart 47776 12 (autoclean)
vmnet 25000 8
vmmon 41644 5
lp 8996 0 (autoclean)
parport 37056 0 (autoclean) [lp]
nfsd 80176 8 (autoclean)
lockd 58704 1 (autoclean) [nfsd]
sunrpc 81564 1 (autoclean) [nfsd lockd]
autofs 13268 0 (autoclean) (unused)
e100 60644 1
e1000 50604 0 (unused)
sg 36524 0 (autoclean)
sr_mod 18136 2 (autoclean)
ide-scsi 12208 1
scsi_mod 107160 3 [sg sr_mod ide-scsi]
ide-cd 35708 0
cdrom 33728 0 [sr_mod ide-cd]
keybdev 2944 0 (unused)
mousedev 5492 1
hid 22148 0 (unused)
input 5856 0 [keybdev mousedev hid]
usb-uhci 26348 0 (unused)
ehci-hcd 19976 0 (unused)
usbcore 78784 1 [hid usb-uhci ehci-hcd]
ext3 70784 2
jbd 51892 2 [ext3]

Why no 'aic7xxx'? Have I got it wrong in 'modules.conf'?

Here's the output from 'lsmod' after 'modprobe aic7xxx':

aic7xxx 141300 0
st 31248 0 (autoclean)
i830 74336 1
agpgart 47776 12 (autoclean)
vmnet 25000 8
vmmon 41644 5
lp 8996 0 (autoclean)
parport 37056 0 (autoclean) [lp]
nfsd 80176 8 (autoclean)
lockd 58704 1 (autoclean) [nfsd]
sunrpc 81564 1 (autoclean) [nfsd lockd]
autofs 13268 0 (autoclean) (unused)
e100 60644 1
e1000 50604 0 (unused)
sg 36524 0 (autoclean)
sr_mod 18136 2 (autoclean)
ide-scsi 12208 1
scsi_mod 107160 5 [aic7xxx st sg sr_mod ide-scsi]
ide-cd 35708 0
cdrom 33728 0 [sr_mod ide-cd]
keybdev 2944 0 (unused)
mousedev 5492 1
hid 22148 0 (unused)
input 5856 0 [keybdev mousedev hid]
usb-uhci 26348 0 (unused)
ehci-hcd 19976 0 (unused)
usbcore 78784 1 [hid usb-uhci ehci-hcd]
ext3 70784 2
jbd 51892 2 [ext3]

I see an 'st' entry has magically appeared as well as 'aic7xx' and I can now use /dev/st0 ok.

Any ideas anyone?

Add the modprobe command to your /etc/rc.d/rc.local script, example below;

/sbin/modprobe aic7xxx


FYI: your kernel is really, really old, this was one of two orginal released kernels for Red Hat Linux 9 (which is out of date now). As a suggestion at least bring your system current. Visit http://www.fedoralegacy.org/ and learn how to download/install and use apt and/or yum.

Thanks Lenard,

I edited the 'rc.local' script as you suggested & st0 is now available immediately after boot.

I thought that 'module.conf' was supposed to enable this sort of stuff to be done without editing the 'rc' scripts.
Obviously, I'm wrong & this is just another item on my, almost infinite, list of things I don't understand.

Re: ancient kernel - yes it is - but I have to support users who don't or won't update their systems and I'm nervous about getting ahead of them in case something doesn't work when I ship them an update to my software.

If I were to update which do you think best: 'apt' or 'yum'?

Most prefer yum, I have used both and currently use yum. Nothing wrong with apt in a single mode environment, but I'm dual mode now and yum works better for this environment.

Dual mode == both 32-bit and 64-bit applications installed.

yum it shall be then!

Over & Out