Re: initrd does not boot in 2.6.3, working in 2.4.25

[William Lee Irwin III]

On Fri, Mar 05, 2004 at 12:38:53PM +0200, vda wrote:
> I am using initrd in order to configure ethernet and
> mount NFS root. It works with 2.4.25 kernel, like this:
> linld image=2425 initrd=image.gz vga=4 "cl=root=/dev/ram init=/linuxrc.nfs.vda devfs=mount"
> that is, it unpacks image.gz into ramdisk #0, mounts it,
> mounts devfs on /dev and execs /linuxrc.nfs.vda.
> When I tried to boot 2.6.3 with
> linld image=263 initrd=image.gz vga=4 "cl=root=/dev/ram init=/linuxrc.nfs.vda devfs=mount"
> it unpacks image.gz into ramdisk #0, mounts it,
> mounts devfs on /dev and ... complains about NFS server.
> Wow. I did not say /dev/nfs, what NFS?
> ...
> VFS: Mounted root (ext2 filesystem)
> Mounted devfs on /dev
> 	(here 2.4.25 would say "Freed unused kernel mem..." and exec init)
> Root-NFS: No NFS server available, giving up
> VFS: Unable to mount root fs via NFS, trying floppy
> VFS: Insert root floppy and press ENTER
> Omitting devfs=mount does not help.
> root=/dev/ram0, root=/dev/rd/0 does not help.
> Config attached.

nfsroot works in 2.6.3 and above here. I'm not sure you need it per se
for initrd's; I think the way it's intended to work with that is for
the scripts to configure network interfaces, mount the nfsroot, and then
pivot_root(). Can you try without initrd?
Also, try passing ip= for these things.


-- wli

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/