Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm a relative newbie with a seemingly old problem. I updated to Redhat 9 from 7.3 a couple of months ago. I'm running a twin xeon 2.2GHz machine. The SMP kernel booted fine with 7.3 but only the UP kernel supplied with RH9 (2.4.20-8) boots, the SMP kernel panics with the following message (snippet):
I've updated the kernel to 2.4.20-19.9, now neither the UP or SMP kernels boot (thankfully I can still use the 2.4.20-8 UP kernel to get into the system).
The lilo configuration file reads:
boot=/dev/sda
linear
prompt
timeout=50
message=/boot/message
root=/dev/sdb2
I've trawled through various forums and noticed that there were problems with the SMP kernel and ext3 in versions of the kernel released with RH7.3. Has anyone come across this problem with RH9 or can anyone help me out with it?
Hopefully by compiling the kernel you will resolve this issue. I have found that upgrades can corrupt the systems configuration resulting in that nasty message " kernel panic ". Use this HOWTO to compile your kernel. be sure to include the " ext3 " module.
Worryingly everything is now working fine. Not that I've knowingly done anything correctly. I successfully compiled the kernel and associated modules three times, and on each occasion the machine failed to boot. However, I retried the 2.4.20-19.9 smp kernel and it successfully booted for the first time, correctly recognising both processors and loading all modules correctly - no hint of a panic! I'm not sure I like this voodoo
Thanx for all your help in any case,
Cheers
G
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.