On 14-Oct-2000 Jonathan Wilson spoke something to the effect:
> I could be very wrong, but I thought the proper thing was mem="128M".
>
> Did you check the lilo docs?
>
> Other then that, I"d like to say that there's probably nothing worse then
> bad RAM. It very well may be bad - consider trying a new stick. Get PNY,
> Kensington or Corsair. And do /not/ get ram with tin teeth - only gold.
> Many makers are starting to use tin for cost efficiency, but it corrodes
> in about 2 years, and often corrodes the slot in the mobo along with it.
He had it righter (append="mem=128M") but, I didn't notice what may be a
problem when he wrote the original.
In 1. It appears as:
append = "mem=128M"
which has 2 spaces in it that may not work: one on either side of the
first equals (=) sign. This is usually the RIGHT(tm) way with unix. But
this may be an exception.
You might try again, Rob, without the spaces and see what happens.
I can't say for sure with this but, I used to use such an entry and it
worked without the extra spacing. I know the lilo.conf manpage shows it
that way. But, I know what worked for me and the manpages are sometimes
(shudder) in error.
Another possibility is that the video memory is taken from the ram (had one
once that did that) and it's leaving a hole in memory. 'Doze seems able to
handle it (after all, this was likely one of M$'s ways of getting things
"better" for everyone by making sure nobody else could use it). But, linux
stops looking after it finds an empty memory position. If the bios can't
let you remap it, the video section may have a jumper for memory mapping
which can push its theft of resources to the top of the heap. Otherwise,
the memory it's seeing is all you'll ever get.
If it's neither of these, I'm outta ideas.
> At 06:50 PM 10/13/2000 -0700, you wrote:
>
>>Hopefully someone here has seen something like the problem
>>I'm having.
>>
>>In a moment of weakness my employer bought a cheapo 450MHz PIII
>>system ( A Fry's special for those that might know what that means).
>>It ran NT until this week when I wiped it and installed Linux.
>>
>>Unfortunately Linux can see only 64 of the 128Megs of memory. I've
>>tried:
>>
>>1) variations of append = "mem=128M" in lilo.conf to no effect.
>>2) linux mem=128M at the LILO prompt. kernel panic on boot.
>>3) switch the DIMM from slot to slot. also no different.
>>4) try a known to be good DIMM from another system with 1-3 above.
>> no difference.
>>5) twiddling BIOS settings. also no effect.
>>
>>I can't find any marking on the motherboard to identify the maker.
>>( I wouldn't admit to making it either) It has a SiS chipset of
>>some sort, but nothing else identifiable.
>>
>>Any suggestions?
--
You will become rich and famous. Unless you don't.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
