Kernel Panic??
 

I was booting into my RedHat partition just now, after attempting to install the Atmel drivers. I got the message "<o> Kernel Panic: Attempted to kill init!" What does this mean? Please help! I have kernel 2.4.18-14, i586.

When I reboot, I am greeted with a message telling my to "run fcsk manually without options". Then, I am dumped to a shell, I login as root, and I see the prompt "Repair File System # 1" The number changes for every time I press enter.

Please...so lost

:cry:

I think this thread has posted before, you can see at newbie forum with the same problem. It's probably the processor problem. Red hat Linux wont recognize certain processor.

Hope this help.

Linux will recognise and use a i586 with no problems

when dumped into the repair shell just run

fsck /dev/hdxy

where x is the drive you use eg hda/hdb and y is the partition number normally hda1

:)

Thanks, what exactly doe that do?

Ok, this just got a little more complicated...
I tied what you said, fsck /dev/hdb1 (A is my XP drive). It ran through some checks, and rebooted. Now, it gives me yet another kernel panic, "Aiee Killing interrupt handler!". So, I tried the same thing again. after I hit <enter>, after typing fsck /dev/hdb1, it just sits there, flashing a cursor at me. What can I do now?

lol @ aiiee killing interrupt handler (cant you tell that linux kernel hackers are all stoned) :)

rightyo

addressing your first question, fsck is like scandisk :)

right i need you to run yout eip number through this program

/usr/src/linux/scripts/ksymoops

eg.

Oops: 0000
CPU: 0
EIP: 0010:[<0015b132>] <=--- this number
EFLAGAS: 00010006

then post the results here, this *should* tell us where the error is occuring and how to fix it :), yep you may not know much about linux now but after this you'll know a hell of a lot more :)

sidey

Roger Cap'n, will do!

ok, problem, I tried to run the script, but it "has been removed from the kernel". Apparently, I have to re-download it from Kernel.org. But, I'll do that later and post the results here, sorry, and thanks.

do a locat for ksymoops, you may find a copy lurking in the /bin dir :)

Right, I found it there, BUT, when I tried to run it, it said that I hadn't specified enough information, and it showed me a list of - orptions ie. -V, which was the one that it recommend I use, so I did and the system hung up. What sould I try, just try it again?

are you actually getting into the linux box? or is it just sitting there on boot?

an alternate/easier way around, is to recompile your kernel :) plus you get the benefits of new drivers etc, but if you stil like to solve this problem you could install both kernels and keep working on the other problem.

try it with something like

/usr/bin/ksymoops -m /boot/System.map

i'll keep thinking for you :)

(but as i say if you really need your box up install a new kernel)

Ok, how do I install the kernel, I have the 2.4 source code, if that helps...I would like to keep working on this probelm, so can I install both?

yeah you can install both

to install new kernel you need to goto /usr/src/linux

make menuconfig

edit the variables

then make dep, make modules, make modules_install, make bzImage.

then copy the vmlinuz file to summet like /boot/vmlinuz2 then edit lilo.conf. copy the entry already in there, replacing vmlinuz with vmlinuz2 :)

thanks, ill try that!