The error message is a standard one that simply means the kernel was not able to proceed loading. The not syncing bit means that it is not writing to your HD for your protection. The panic statement comes because the init process wants to die, but cannot ever (not allowed), so someone made up this cute panic statement.
This could be caused by anything that would prevent the kernel from loading. It could be hardware related where someone has messed around with the motherboard, drives, jumpers, cables or a faulty io controller. It could be caused by a process as well in which case you have to look at the processesthat happened immediately before the panic message. You need to scroll back and look at the processes before the kernel panic message.
You might also find a workaround. Sometimes the boot parameters can improve the situation.
Roy
On Sunday, May 4, 2014 9:25:12 PM, "ralph.bagwell@gmail.com" <ralph.bagwell@gmail.com> wrote:
I just set up a quad boot system including Puppy Lupu-520. All operating systems booted up just fine several time but now Puppy won't boot up. The screen displays normally 5 entries but after loading "lupu_528.sfs main file --- done - the next (last) entry is "kernal panic - notsyncing:Attempted to kill init! "
I've tried the options after hitting F2 and have loaded and run a little earlier Puppy version via booting from a cd - which worked well ( I did not save the session )
Can someone please suggest how I can fix this -
Thanks
Ralph
__._,_.___
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
To unsubscribe from this list, please email LINUX_Newbies-unsubscribe@yahoogroups.com & you will be removed.
.
__,_._,___
No comments:
Post a Comment