Re: HELP: Kernel panic

--ncSAzJYg3Aa9+CRW
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, 2003-03-21 10:59:47 -0500, Yinsheng Li <[email protected]>
wrote in message <[email protected]>:
> Hello,
>=20
> I have a problem after I upgrade the kernel. While I try to boot from the=
=20
> new updated kernel, I got an error -- "Kernel panic. No init found, try=
=20
> init =3D option to kernel"
>=20
> What should I do now? I can still use old kernel, but I really need to us=
e=20
> new kernel.
>=20
> Some background: I installed the Redhat 7.2 through RAID card using Dell=
=20
> GX400 CPU, then I removed the harddrive to an Multi-CPU box. After moving=
,=20

Umh... Asking google for "Dell GX400" seems to indicate that this is
an Intel P4 based box. Sure this is on-topic on this list (we're talking
about Linux on Alpha-based hardware...)

> I found it still using the kernel for single CPU, therefore I have to=20
> change to use smp-kernel. I download one rpm from redhat website. After=
=20
> install, I got the above error. I have used the command lilo -v -v, but=
=20
> didn't help.

LILO is also only suitable for ia32 hardware. You cannot really boot an
Alpha with that:)

> Following is my lilo.conf:
>=20
> prompt
> timeout=3D50
> default=3Dlinux

You tell lilo to boot the "linux" image after a 5sec delay. However, I
can nowhere find a "label=3Dlinux" or "alias=3Dlinux" line below... So I
would guess that lilo would have _never_ accepted this config file at
all...

> boot=3D/dev/sda
> map=3D/boot/map
> install=3D/boot/boot.b
> message=3D/boot/message
> linear
>=20
> image=3D/boot/vmlinuz-2.4.7-10
> label=3Dlinux-smp
> initrd=3D/boot/initrd-2.4.7-10.img
> read-only
> root=3D/dev/sda1
> append=3D"hdc=3Dide-scsi"
[...]

You're using initrds for all those images. Is it possible that one of
those (actually the new one you want to boot) cannot do the correct
things to bring up your "real" root filesystem? ...or are those initrds
not used at all, because there's a root=3D/dev/sda1 line (and not
root=3D/dev/ram or whatever...)? If it's the later one, is it possible
that /dev/sda1 isn't the partition mounted on "/" ?  Personally, I
almost _always_ have my first partition of my first HDD in a machine
containing /boot (because of BIOS issues, you know...).

After all - what's your old kernel version, what's your new kernel
version, what's their .config file looking like and how does the screen
look like (what can you read there?) when the panic occures? Not only
the last line, but the whole screen?!

And, most important, how is this related to DEC Alphas?

MfG, JBG

--=20
   Jan-Benedict Glaw       [email protected]    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier B=FCrger" | im Internet! |   im Ira=
k!
      ret =3D do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

--ncSAzJYg3Aa9+CRW
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+e1UVHb1edYOZ4bsRAiEPAJ0b7/lvKUmexE5SDAHLoeRRXFPcLwCgiZcq
6Iuf+7W8ngpBV6Nu/YmP6gk=
=zDND
-----END PGP SIGNATURE-----

--ncSAzJYg3Aa9+CRW--