I just installed a new CPU, XP2500, and tried to boot up but couldn't go through. My MB Asus A7V8X-X, does support the CPU.

But it cannot pass init to kernel. A "no init found" error apppeared.

I have no idea what is causing it.

I tried to put back my old CPU, and it is still giving the same error.

Was working fine before.

Does anyone know what could be causing it?

This problem might be caused by changes in the bios. Look through your bios configuration and see if anything has changed. In particular look at your disk configuration and boot sequence.




___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Perhaps I'm a little slow here, but your comment brought a question to mind.

I'm rather new at GNU/Linux (some old RH5/RH8 experience, hardly worth mentioning). I've installed Slack 9.1 (everything). It looked like it went ok. When I tried to boot it gave me the dreaded;
"Kernel panic: no init found. try passing init=option to kernel"

It gives me the same error from the HD or from the boot floppy that Slack made. Your comment about BIOS options, why would they have anything to do with anything?

I've got a 2 HD, 2 CD-ROM set up. Windows 2000 is on hda, Slackware is on hdb, CD-ROMs are hdc and hdd. Normally I have the first boot device set to C: drive. When I'm installing/recovering I set the bios to boot either;

CD-ROM then Floppy, then C:
or
Floppy then CD-ROM, then C:
or
some other combination (LS120's, Zipdisks, etc.) It's a rather flexible bios.

When I am finished I reset it to boot from the C: drive only.

Windows doesn't have a problem, it'll boot up no matter what the bios says. Even now, when I select "Windows" from my LILO menu it brings me to the windows boot loader and into Windows.

Are you saying that LILO/Linux/or some combination thereof won't let me boot into Slackware 9.1 if the boot options are different from when I installed it?

If that's the case, why? and how do I fix it without leaving floppies and CD-ROM's as boot avenues? Seems like one heck f a security risk.

If it helps, hdb1 is /boot, hdb5 is /, hdb3 is /home (all formatted ext3), hdb2 is swap. and there is another partition that's formatted Fat32 and serves as a place to pass data between operating systems when I duel boot. At least that's what I think, trying to do this from memory as I'm not at the machine at the moment.


Just my $0.02 (Canadian, before taxes)
someone247356

" Your comment about BIOS options, why would they have anything to do with anything?"

My comment about the BIOS was based on this line of logic:

You had a working hardware/software combination. Then you changed CPUs. Then you changed back to the original CPU which now does not work. You made no software changes during either CPU swap. The initrd error usually is caused by the kernel not being able to access the / partition. So perhaps in the process of swapping CPUs the BIOS got reset to its default values and initrd is no longer able to work because it cannot access the disk. So check your BIOS parameters to see if the disk geometries are still correct in the BIOS.

"Normally I have the first boot device set to C: drive. When I'm installing/recovering I set the bios to boot either;

CD-ROM then Floppy, then C:
or
Floppy then CD-ROM, then C:
or
some other combination (LS120's, Zipdisks, etc.) It's a rather flexible bios.

When I am finished I reset it to boot from the C: drive only."

This is reasonable. But as a test try setting the BIOS to exactly the way that you used to run under normal conditions.

"Are you saying that LILO/Linux/or some combination thereof won't let me boot into Slackware 9.1 if the boot options are different from when I installed it?"

In my reply I assumed that you made no changes to the LILO software at all. If you did then try booting a rescue CD (I think that the Slackware install CD has one, but I'm not sure), using the rescue CD to boot into Slackwre, and then repairing LILO.


"Seems like one heck f a security risk."

Anyone who has physical access to your computer can get into your computer with a boot floppy or boot CD. The boot CD does not even have to be the same OS as your system as long as the boot CD has the logic to access your file systems. The only logic block to bootable CD's is to have a hardware password.


___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Um, I didn't change CPU's. Why would you have thought that?

Let me reiterate, I set the bios to boot CD-ROM -> floppy -> C:

I installed Slackware 9.1 to hdb, Windows 2000 is on hda.

I installed LILO to the MBR of hda.

I reset bios (the ONLY thing I am changing in the bios is the boot devices and order) back to C: only.

Windows still boots (LILO -> Win boot manager -> windows). Slackware on the other hand (LILO -> Slackware, run, run, run, kernel panic, no init found). dies.

I didn't change Slack or LILO or the bios (except for boot order).

I reset the bios to boot floppy -> C: insert the boot disk and same thing. Run, run, run, kernel panic, no init found.

Is LILO and or the Slackware dependent on a certain boot order? Why? and how do I correct that.


You said;
"Anyone who has physical access to your computer can get into your computer with a boot floppy or boot CD. The boot CD does not even have to be the same OS as your system as long as the boot CD has the logic to access your file systems. The only logic block to bootable CD's is to have a hardware password."

Actually, they can't if you disable CD-ROM or floppy booting in the bios. Password protect the bios settings and if the kids leave a bootable floppy or CD-ROM in the drive, it won't boot. Even if they wanted to boot off the floppy or CD-ROM they have to either reset the bios (opening up the case and moving the jumper), or crack the password. Unlike password protecting the computer itself, they can still use it to run Windows. Since I am more concerned with someone accidentally leaving a bootable floppy or CD-ROM in the drive, simply setting the bios to only boot C: is the most strait forward way to go about it. Unfortunately, it seems that LILO or Slackware isn't happy.

Any suggestions about where I can learn about correcting this problem?

someone24735

perhaps your issue lies in the fault of the default init script
try modifying /etc/inittab to an appropriate init level

# Default runlevel.
id:3:initdefault:

"Um, I didn't change CPU's. Why would you have thought that?"

Kiroshiya's first post says that he installed a new CPU. The new CPU wouldn't work on his motherboard. So he went back to your his CPU and now had problems on his previously working computer.

My answer pertains to that problem. When someone2473 posted to this thread I thought that he was asking for an explanation of my answer, so I amplified my answer.

Now, reading someone2473's questions carefully I see that they are completely unrelated to a CPU switch and my answers about the BIOS have nothing to do with someone2473's questions.

someone2473 has a problem that he cannot boot.
' When I tried to boot it gave me the dreaded;
"Kernel panic: no init found. try passing init=option to kernel"'

The usual cause of this problem is that the kernel cannot access the / partition. Perhaps the hardware configuration is set up wrong in the kernel. Perhaps the hardware configuration is set up wrong in the initrd. I don't know enough about Slackware to tell you how it sets up the hardware at install time. I suggest that someone2473 start a new thread and explain that he has a Slackware install problem and ask how to fix it.

majortool's answer is the only information in this thread that is actually relevant to someone2473's problem.


___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

output of /etc/lilo.conf?