hi, Eric,
I tried a few days ago, using etherboot 5.0.2, mknbi 1.2.6 with different
--rdbase options, but all failed. The kernel is 2.4.13, the initrd is around
64M.
The netbooted client is a 1.5G memory HP Vectra 420. It can successfully
netbooted with 512M memory. But can not boot when memory is added to 1024M
and 1.5G.
The error prompt is something like:
Kernel panic: VFS: Unable to mount root fs on 01:00
I'm using Official kernel 2.4.13, the base system is RedHat 7.1 on HP
vectra 420.
The commands I used to create the tagged images is:
/usr/bin/mknbi-linux --output=./kernel.test.0540 --ip=dhcp
--rdbase=0x5b000000 --rootdir=/dev/ram0 --append="idebus=66 ide0=ata66
ide1=ata66 ro" bzImage initrd
I also tried options, --rdbase=top/asis/0x00300000, all can failed with the
same above problem.
At last I use local hard disk boot, with the same kernel (4G high memory
option enabled), it can boot successfully, then I tried to see the memory
mapping, and get the following information:
arc251.alexa.com guolin 64% cat /proc/iomem
00000000-0009fbff : System RAM
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000c8800-000c9fff : Extension ROM
000ca000-000cdfff : reserved
000e0000-000effff : Extension ROM
000f0000-000fffff : System ROM
00100000-5ffeffff : System RAM
00100000-002794af : Kernel code
002794b0-002efd17 : Kernel data
5fff0000-5fff7fff : ACPI Tables
5fff8000-5fffffff : ACPI Non-volatile Storage
d7a00000-dfafffff : PCI Bus #01
d8000000-dbffffff : PCI device 1002:5446 (ATI Technologies Inc)
dfb00000-dfbfffff : PCI Bus #02
dfd00000-dfdfffff : PCI Bus #01
dfdfc000-dfdfffff : PCI device 1002:5446 (ATI Technologies Inc)
dfe00000-dfefffff : PCI Bus #02
dfeff000-dfefffff : Intel Corporation 82820 (ICH2) Chipset Ethernet
Controller
dfeff000-dfefffff : eepro100
e0000000-e3ffffff : Intel Corporation 82845 845 (Brookdale) Chipset Host
Bridge
fff00000-ffffffff : reserved
Please suggest which method, I can try to netboot the machine. Thanks a
lot.
Yours sincerely,
Guolin Cheng
-----Original Message-----
From: Guolin Cheng
Sent: Thursday, November 08, 2001 1:32 PM
To: Ops
Subject: FW: [Etherboot-users] 1G memory limit and Etherboot
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Thursday, November 08, 2001 11:17 AM
To: Christopher Fowler
Cc: Etherboot-users
Subject: Re: [Etherboot-users] 1G memory limit and Etherboot
"Christopher Fowler" <[email protected]> writes:
> How do I specify that at boot?
It depends on what you are doing. With mnknbi --rdbase.
With other bootloaders it varies. The easy solution is to get
a newer kernel.
Eric
_______________________________________________
Etherboot-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/etherboot-users
Guolin Cheng <[email protected]> writes:
> hi, Eric,
>
> I tried a few days ago, using etherboot 5.0.2, mknbi 1.2.6 with different
> --rdbase options, but all failed. The kernel is 2.4.13, the initrd is around
> 64M.
Unless something regressed 2.4.13 should be fairly robust in this
regard.
> The netbooted client is a 1.5G memory HP Vectra 420. It can successfully
> netbooted with 512M memory. But can not boot when memory is added to 1024M
> and 1.5G.
>
> The error prompt is something like:
>
> Kernel panic: VFS: Unable to mount root fs on 01:00
Which just means it couldn't find your ramdisk. If you could please
report all of your kernel messages. A serial console is ideal for that
purpose. Without more information I cannot even guess why you are having
problems.
> I'm using Official kernel 2.4.13, the base system is RedHat 7.1 on HP
> vectra 420.
>
> The commands I used to create the tagged images is:
>
> /usr/bin/mknbi-linux --output=./kernel.test.0540 --ip=dhcp
> --rdbase=0x5b000000 --rootdir=/dev/ram0 --append="idebus=66 ide0=ata66
> ide1=ata66 ro" bzImage initrd
>
> I also tried options, --rdbase=top/asis/0x00300000, all can failed with the
> same above problem.
>
> At last I use local hard disk boot, with the same kernel (4G high memory
> option enabled), it can boot successfully, then I tried to see the memory
> mapping, and get the following information:
>
[snip]
>
> Please suggest which method, I can try to netboot the machine. Thanks a
> lot.
Eric