According to Akintayo Holder: While burning my CPU.
>
> I have recently compiled my kernel, for my scsi card. That is okay but I
> have a problem with my modules.
>
> 1. There is a symlik called module_info in the boot directory that
> points to a file <of the same stem e.g. module_info-2.0.36. The file
> seems to contain information about which mods to load.
> How do I create one of these for my new kernel?
When i used redhat i just deleted the symlink after recompiling the first
kernel.
>
> 2. in the /lib/modules directory there 'was' a link called preffered to
> the directory of the kernel version I was using. It disappeared after
> reboot, what does this and the file above do? And what else is involved
> in loading my modules
That link gets deleted at boottime check /etc/rc.d/rc.sysinit
>
> As it currently stands my system will not load the modules for my zip,
> which automounts in my fstab, what steps do I have to take to rectify
> this situation. I read the modules.txt, but that seemed more geared
> towards the manual loading of modules via insmod. I would appreciate if
> someone could help me with my predicament, preferably by pointing out
> the relevant docs.
>
> I use RH5.2, with the patches including 2.0.36-7 <prior to the upgrade>
Presuming you did make modules modules_install edit lilo.conf accordingly
copied the new image from /usr/src/linux/arch/i386/boot/ to /boot rerun lilo
if name conflicts are an issue in /boot delete the symlink to the old
kernel and System.map, you "may" also leave the new System.map in
/usr/src/linux as it will be searched for there.
The rc.sysinit file looks for the booted kernel name or number it uses
cat /proc/cmdline to obtain the full information then uses awk to pull out
the rest, this is possably where the problem lies.
I suggest you do 'cat /proc/cmdline' to establish which kernel you are
booting.
>
> --
> ..once again its on
> Ice Cube
> RH5.2 Personal 17728385
> http://www.bigfoot.com/~blakdogg
>
--
Regards Richard.
[EMAIL PROTECTED]
