Re: Memory Problems on Compaq Prosignia w/Potato
Ian Smith wrote: > > Hi, > > I've just recently installed Potato on a Compaq Prosignia 300 > Server with 64M of RAM. Checking free, however, shows only > 13M. The Bios reports the correct amount on startup, and the > previous OS (NT) also had no problems with the memory. I tried > adding an append="mem=64M" line to Lilo.conf, but that has not > helped. I had the same problem with SuSe on my Prosignia an found that there is a special program on Compaq's site, it's called the Compaq Siystems Cofiguration Utillity. You have to run this from a dos partition to upgrade your Bios with the new mem amound. http://www5.compaq.com/support/files/server/us/locate/8_1138.html#System ROMPaqs/BIOS good luck Mark Lamers I thought that the kernel was supposed to autodetect up to > 64M anyway. Should I just do a clean reinstall, or does anyone > have an idea of how to fix this? > > thanks, > > -Ian > Ian W. Smith > Systems Engineer > Systems Integration Group > Fourth Phase New Jersey > Westside Ave. > North Bergen, NJ 07047 > (201) 758-4315 > [EMAIL PROTECTED] > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Memory Problems on Compaq Prosignia w/Potato
On Wed, Feb 07, 2001 at 01:33:17PM -0500, Ian Smith wrote:
> Hi,
>
> I've just recently installed Potato on a Compaq Prosignia 300
> Server with 64M of RAM. Checking free, however, shows only
> 13M. The Bios reports the correct amount on startup, and the
> previous OS (NT) also had no problems with the memory. I tried
> adding an append="mem=64M" line to Lilo.conf, but that has not
> helped. I thought that the kernel was supposed to autodetect up to
> 64M anyway. Should I just do a clean reinstall, or does anyone
> have an idea of how to fix this?
Check your BIOS configuration for something like 'Memory hole at 15M' or
similar. This was needed for some old ISA cards that needed to fit
their memory mapped addresses in without conflicting with system memory.
It's highly unlikely you actually have such cards in your system, so you
should disable that setting.
That, of course, assumes that what you're taking about on 'free' is the
'Mem: total' value. That should be equal to the size of the kernel +
ram in the system. If you're taking about 'Mem: free', well, that
depends entirely on what you've been running lately and will usually
work its way down to only a few megs regardless of how much RAM you
have.
--
CueCat decoder .signature by Larry Wall:
#!/usr/bin/perl -n
printf "Serial: %s Type: %s Code: %s\n", map { tr/a-zA-Z0-9+-/ -_/; $_ = unpack
'u', chr(32 + length()*3/4) . $_; s/\0+$//; $_ ^= "C" x length; } /\.([^.]+)/g;
Re: Memory Problems on Compaq Prosignia w/Potato
On Wed, Feb 07, 2001 at 01:33:17PM -0500, Ian Smith wrote: > Hi, > > I've just recently installed Potato on a Compaq Prosignia 300 > Server with 64M of RAM. Checking free, however, shows only > 13M. The Bios reports the correct amount on startup, and the > previous OS (NT) also had no problems with the memory. I tried > adding an append="mem=64M" line to Lilo.conf, but that has not > helped. I thought that the kernel was supposed to autodetect up to > 64M anyway. Should I just do a clean reinstall, or does anyone > have an idea of how to fix this? > The append line should work. Just to make sure did you run lilo after making the changes in /etc/lilo.conf? That is the only thing I can think of. What does dmesg or /proc/meminfo say in terms of memory? Maybe there is some possibility of "free" not reporting correctly? hth, kent -- >From seeing and seeing the seeing has become so exhausted First line of "The Panther" - R. M. Rilke
Memory Problems on Compaq Prosignia w/Potato
Hi, I've just recently installed Potato on a Compaq Prosignia 300 Server with 64M of RAM. Checking free, however, shows only 13M. The Bios reports the correct amount on startup, and the previous OS (NT) also had no problems with the memory. I tried adding an append="mem=64M" line to Lilo.conf, but that has not helped. I thought that the kernel was supposed to autodetect up to 64M anyway. Should I just do a clean reinstall, or does anyone have an idea of how to fix this? thanks, -Ian Ian W. Smith Systems Engineer Systems Integration Group Fourth Phase New Jersey Westside Ave. North Bergen, NJ 07047 (201) 758-4315 [EMAIL PROTECTED]
