Hi,

I am running a dell server 1650 with Red Hat ES 3.0 which comes with 2.4.21 kernel. I installed 2.6.5. on the same machine which need differe modutils. I installed mod-init-tools3.0 and was able to build 2.6.5. kernel. When I tried to boot with 2.4.21 again. I get a kernel panic with a message saying "kernel needs old insmod:could not find /bin/insmod: no such file or directory"

I found a similar bug on the red hat site but they are talking about having a insmod.static.old and have provided a fix in the initrd which assumes the existence of insmod.static.old. My system does not have a insmod.static.old. I am not sure how I can get 2.4.21 to work.

I linked /sbin/insmod.old to /bin/insmod.old but the kernel still shows the same error and I still get the kernel panic.

Any help is greatly appreciated.

Thank you for your time.

Vish

Is insmod in /sbin? If so, you could try putting making a link /bin/insmod that links to /sbin/insmod.

lasindi

Hi,

I tried copying /sbin/insmod to /bin/insmod.old. The kernel still says insmod.old no such file or directory, eventhough there is a insmod.old under /bin

What should I do to get the kernel to realize that there is a file under /bin? Any ideas are greatly appreciated.

Thanks
Vish

I'm just not quite sure why you want a file that has a name *.old. Seems to me that the system wouldn't care if it exists. Have you tried making a plain old /bin/insmod link to plain old /sbin/insmod?

lasindi

Is installing a new kernel really a good idea? Red Hat will probably not support your installation now, although the people here will of course. But it kinda defeats the purpose of paying Red Hat for RHEL, you may as well run White Box or CentOS. Unless of course your support has run out, then it won't matter.

Or is Red Hat strict with this kind of stuff. I know even on SUSE Pro 9.0 that if I installed the beta 2.6 kernel included on the discs, it would void my support offering unless I reinstalled the OS. Is Red Hat like this?