modules

modules

Post by Kevin Hirs » Wed, 25 Mar 1998 04:00:00



    Where in Redhat 4.2 does it initialize your hardware modules?  I
upgraded the kernel to 2.0.32 and removed all traces of 2.0.30 (or so I
thought) and recompiled everything and I still can't get my SCSI card to
init at boot time because it says the module contains 2.0.30 symbols.
        Kevin

 
 
 

modules

Post by Henrik Storn » Mon, 30 Mar 1998 04:00:00



Quote:>    Where in Redhat 4.2 does it initialize your hardware modules?  I
>upgraded the kernel to 2.0.32 and removed all traces of 2.0.30 (or so I
>thought) and recompiled everything and I still can't get my SCSI card to
>init at boot time because it says the module contains 2.0.30 symbols.

Probably comes from the "initrd" file loaded by LILO in a default
RedHat setup. RedHat has all SCSI drivers as modules, so they need
an initial ram-disk to load the module from - it's /boot/initrd.
If you rebuild the kernel with the SCSI driver as a module, and
you need it for booting, then you must rebuild the initrd-file with
/sbin/mkinitrd (see "man mkinitrd"). If you don't need initrd, you
can simply remove the inird-setting from /etc/lilo.conf and re-run
lilo.

--
Henrik Storner                        "...Unix, MS-DOS, and Windows NT
                                       (also known as the Good, the Bad,
                                       and the Ugly)."    [Matt Welsh]

 
 
 

1. conf.modules vs. modules.conf & modules.dep??

Just upgraded my RH6.2 box to kernel 2.2.18 (in conjunction with
applying vpn masq patch).  Now I notice that it complains about
conf.modules, so I renamed this to conf.modules.old and made a copy as
modules.conf.  Now it complains that modules.conf is newer than
modules.dep.  And, in any case, it doesn't seem to load my modules
(specifically 3c509.o for ethernet).

My present workaround is just to manually invoke this module (modprobe
3c509) and restart /etc/rc.d/init.d/network (as well as dhcpd and
named), but I know there's gotta be a "Right Way" of doing this.

What's different between 2.2.18 and my old kernel (2.2.14-5.0) in
terms of handling these files?  And, more importantly, how do I
correct this situation?  Many thanks, in advance.

2. webmail

3. Linux "unresolved symbols in module /lib/modules/2.0.29..."

4. linux installing

5. Kernel upgrade: make modules -> nothing to do for 'modules' and complains afterwards ?

6. umask mayhem!!!!!!!

7. Module rewrite 9/20: x86 module support

8. Solaris 10 - NFS Server for volume management /vol not reponding

9. problem compiling modules from modules.tar.gz

10. apachectl /suse7.2/rcapache "unused" /php4 module / authldap module

11. *** Unresolved symbols in module /lib/modules/2.0.25/fs/ncpfs.o

12. no depepndency information for module /lib/modules/2.0.33/misc/hisax.o

13. apache: module post-process output of another module?