Thanks for the reply. I found the problem. The first kernel
image doesn't probe multiple luns, while the second one does.
So the devno of the root filesystem changes. I built the driver
into the kernel, so I did not use the initrd.
There is another problem with loadLin for > 2.4.2 kernel.
It seems that I could not use dev names to specify root
filesystem. Say if the boot.bat is like:
loadlin.exe bzImage ro root=/dev/sdc1
The kernel fails to boot due to null ptr error.
From: Ignacio Vazquez-Abrams [mailto:firstname.lastname@example.org]
Sent: Monday, August 06, 2001 12:58 PM
Subject: Re: Problems in using loadLin
On Mon, 6 Aug 2001, chen, xiangping wrote:
> I am trying to use loadlin to boot up a machine. But after I
> replaced the bzImage, the kernel fails to boot up. It prints
> out error messages like:
> VFS: Mounted root (ext2 filesystem) readonly
> Freeing unused kernel memory : 96K freed
> Warning: unable to open an initial console
> Kernel panic: No init found. Try passing init= option to kernel.
> The boot.bat file is:
> loadlin.exe bzImage ro root=0x0821
0x0821 represents /dev/sdc1. Did you build the SCSI driver into the kernel,
do use an initrd?
-- Ignacio Vazquez-Abrams <email@example.com>
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/