kernel panic - not syncing: attempted to kill init!
FedoraThis forum is for the discussion of the Fedora Project.
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.
kernel panic - not syncing: attempted to kill init!
I have been running fc2 server on my box. I tried upgrading to fc3, fc4, fc5 server. I was able to upgrade to fc5 server. Finally, I decided to give a shot at it. Now, I get an error when it boots up. I have backed up all my data already. Anyone can help me find a solution if possible. Your help is appreciated.
Quote:
kernel panic - not syncing: attempted to kill init!
The kernel panic message is not enough to determine what is causing the problem. Usually there are messages leading up to the panic message that give a clue about what is going on. Sometimes it has to do with incorrect mount information for your root or boot devices. Post more details when you can and perhaps we can figure out what is happening.
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=LABEL=/ rhgb quite
linux-bzimage, setup=0x1e00, size=0x16eb71,
initrd /initrd-2.6.15-1.2054_FC5.img
linux-initrd @ 0x17eff000, 0xe0baa bytes,
Uncompressing linux... OK, booting the kernel
agpgart: Unsupported SiS chipset (device id: 5600)
Red Hat nash version 5.0.32 starting
Kernel panic - not syncing: Attempted to kill init!
This is all i see on my monitor screen when it boots up and it halts.
I saw a few posts about agpgart: Unsupported SiS Chipset using google. Some those suggested adding agp_try_unsupported=1 to the kernel line in grub.conf. You would enter that right after root=LABEL=/.
However, I'm not certain that is the main culprit of the kernel panic. I would boot again, but remove rhgb and quiet from the kernel line so you can get more information on what the kernel is doing before the panic.
You can temporarily edit the kernel boot command through grub when grub first comes up. Hopefully either the addition of agp_try_unsupported or getting more info will lead to a solution.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.