fedora core 3 installation kernel panic - not syncing
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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I didn't used any boot loader yet, just the installation CD.
My disk was low level formated (just new from the store)
I now run Slackware (kernel 2.4.29) and it runs just fine with LILO in the MBR (first tried LILO in the boot partition, but that didn't do the trick --> "L 99 99 99 99...").
I now know that nor kernel 2.4.26, nor kernel 2.6.xx support my SATA disk (250 GB Maxtor) or my onboard LAN (Gigabyte). I hope that a newer release of kernel 2.6 will help me with these problems, but in the mean time, I'll continue using 2.4.29 with an extra LAN because the onboard LAN is still not supported... :-s
i have a similar problem. I have installed fedora within vmware 4.0 and it appeared that the fedora installation went successfully. upon reboot, i receive the kernel panic - not syning; attempting to kill init
FWIW: I have the same problem. I have tried every kernel command line parameter I can think of and still get the kernel panic. I regret the day I bought this MSI MB with the the 915P chipset. These MB's have got to be the most "linux" incompatible MB's I have ever seen.
I see that the last post on this topic is just a few days ago, but is there any chance you guys have found anything useful? I'll keep searching google and post back if I find anything, but hopefully one of you has already found a fix.
Ok, found the solutions, the article on this page: http://kerneltrap.org/node/4030
tipped me off to the obvious fix. As with most software manufacturers the fixes are often in the newer versions.
Upgrade to Vmware 4.5.2 and you're off to the races boys
Here's my solution (suggest you try the same especially if system is hanging when trying to install Fedora X).
My machine was running Fedora Core 1 just fine. I upgraded to Fedora Core 3. Then after running the Kernel update (up2date) every time I rebooted I had various Kernel Panics which was very very very annoying.
Thinking it was Fedora 3 clashing with my motherboard I downloaded and installed version 2 (same results) and also version 1 (also same annoying hang on install).
After trying the 3 versions of Fedora I was fairly sure it was hardware related so buy process of elimination I finally discovered it was my memory which was causing the headache. Wish I tried my memory before buying a new harddrive (such is life!).
So the moral of the story is if your getting Kernel panics then I strongly suggest testing your system memory. I used software called Amidiag (dos version). My memory was failing on the pattern test.