Has this issue been resolved? I also am seeing this problem on a 16MB 486
box with a D-Link DFE-538TX using a floppy image from ROM-O-MATIC. The
server is RH 7.2 .
The full amount of system memory is being detected. However, the first sign
of trouble is:
"initrd extends beyond end of memory"
Cheers,
Robert
---------------------------------------------------
Cicero,
My first thought is probably not enough ram in
the workstation, but that's just a guess, because
I have no clue how much ram there is.
You can hit the Shift-PageUp keys and scroll backwards
through the boot messages. Go all the way back
to where Etherboot hands control over to the kernel.
You should see some information about the initrd, and
whether the kernel had a problem with the initrd.
Jim McQuillan
[EMAIL PROTECTED]
Cicero Mota wrote:
> Hi,
>
> I'm running a ltsp v3.0 server. The provided ltsp kernel
> (vmlinuz-2.4.9-ltsp-5) boots without any problems for pentia (i586), and
amd
> machines but fails for i486 when it 's trying to mount ram0. These are
the
> last lines shown during boot proccess:
>
> NET4: Unix domain socktes 1.0/SMP for Linux NET4.0.
> VFS: Cannot open root device "ram0" or 01:00
> Please append a correct "root=" boot option
> Kernel panic: VFS: unable to mount root fson 01:00
>
> Does anyone know how to correct this?
>
> Thanks.
>
> Cicero
>
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
