Kernel 2.4 upgrade requirements

iccus · 09-23-2002, 01:08 AM

I'm trying to upgrade this RH 6.2 box I have up to a 2.4.x kernel.

I've went through and made sure I have all the requirements listed in ../Documents/Changes.txt in the kernel 2.4.x source.

But it seems every time I try and boot with this kernel, I get "Kernel panic: No init found". Now I can go back to my 2.2.x kernel and boot fine...

I have had this problem for well over a month now and I've tried all the basic manuvers already:
*making sure init exists in /sbin
*passing misc arguments to lilo using 'append'
*make sure my 'root= ' line in lilo.conf is right

But It will mount the filesytem and just drop to that error, which makes me wonder if kernels 2.4.x have a minimum version requirement for the SysVinit package?

If someone has any comments/solutions to this matter, please post them. Because I am really finding this frustrating.

Thanks,

Adam

JimH · 09-23-2002, 02:05 AM

Originally Posted by iccus

But it seems every time I try and boot with this kernel, I get "Kernel panic: No init found". Now I can go back to my 2.2.x kernel and boot fine...

But It will mount the filesytem and just drop to that error, which makes me wonder if kernels 2.4.x have a minimum version requirement for the SysVinit package?

Possible SysVinit might be a problem. The old version of Lilo that 6.2 uses might also be a problem.

The only other thing I can think of is the change from using change_root to pivot_root in the current 2.4 kernels. pivot_root requires the /initrd directory to exist. However, the error message you are seeing does not correspond to what you would see if this was the problem.

Been a long time since I ran 6.2 and I have never tried to upgrade it to a 2.4 kernel, so I don't know what problems you might encounter.

Jim H

iccus · 09-25-2002, 02:04 AM

Well JimH... thumbs up for me figuring out the problem... thumbs dumb, however, that I'm a tool and didnt even THINK of checking the most obvious thing first:

PERMISSIONS!

Do not tell me how this got done... but all the perm's in my /lib folder were set to 666. So I thought this was odd... and changed them to what they should be in the first place, 755.

So finally... my month long ulcer is GONE! and Kernel 2.4.19 upgrade on my RH 6.2 box works flawlessly now! But I'm still baffled how those perm's got changed...? Damn Lawn Gnomes again. :-)