SCIENTIFIC-LINUX-USERS Archives

May 2005

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Perret Yannick <[log in to unmask]>
Reply To:
Date:
Mon, 30 May 2005 17:27:10 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (44 lines)
Perret Yannick wrote:

> Jon Peatfield wrote:
>
>>
>> A long time ago we used to get exactly those symptoms with 386 
>> kernels iff
>> the machine had more than ~2G ram (I think), and it went away with an
>> upgrade to the pxelinux.bin to v2.06 (I think).
>>
>> The bug was that it was loading the kernel/initrd at some address beyond
>> what the boot-kernels could address (or my memory might have failed
>> again).
>>
>> There *might* be something similar at some higher memory threshold.  
>> Do all the boxes have the same amount of memory?
>>
>> Before the pxelinux update we used to tediously strip memory out of 
>> machines during installs...
>>
>>
>>  
>>
> Hello,
>
> I will try to see which pxelinux version I have...
> Most of our boxes have 2Go of RAM, but maybe
> this one is a 2.5Go one.
>
> I will investigate in this direction.
>
Hi,

so, this box is a 2Go one, but I installed the last
pxelinux.0 version and it corrects the problem.

By the way this box has a particular motherboard,
and it may be the reason of the bad memory support...

Thanks again.

--
Yannick

ATOM RSS1 RSS2