Finding Memory

View: New views
3 Messages — Rating Filter:   Alert me  

Finding Memory

by olcarman@cableone.net :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


An easier way is to type cat /proc/meminfo in a terminal window.
Ken


---- Msg sent via CableONE.net MyMail - http://www.cableone.net

Re: Finding Memory

by Kenneth Marcy :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Saturday 29 August 2009 10:10:28 olcarman@... wrote:
> An easier way is to type cat /proc/meminfo in a terminal window.
> Ken

If this message, despite the fact that it is posted to the Mandriva Expert
list rather than the Mandriva Newbie list, is in fact about a recent thread
on the Newbie list in the last couple of days within which I suggested to
someone that she use lshw to determine the memory content of her machine
rather than any of several other suggested memory reporting utilities, there
is a reason I suggested lshw over the simpler alternatives.

The reason is that lshw reports not only the total amount of RAM, but also the
size of the physical packages in which it is installed. This laptop, for
example, has 2 GiB total RAM installed in 1 GiB modules in bank 0 and bank 1.

By asking the original poster with the installation problem how much memory
she has installed in her machine, and using lshw to find the answer to that
question, one would be able to make more specific recommendations about
whether, and if so, how to upgrade the memory for better machine performance.

So, to you and the other posters who suggested "easier" alternatives, I
respond that yes, they are easier to execute than creating a text file from
lshw, but they are also less informative for useful upgrade decision-making.


Ken

Re: Finding Memory

by Anne Wilson-5 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sunday 30 August 2009 00:28:42 Kenneth Marcy wrote:

> By asking the original poster with the installation problem how much memory
> she has installed in her machine, and using lshw to find the answer to that
> question, one would be able to make more specific recommendations about
> whether, and if so, how to upgrade the memory for better machine
> performance.
>
> So, to you and the other posters who suggested "easier" alternatives, I
> respond that yes, they are easier to execute than creating a text file from
> lshw, but they are also less informative for useful upgrade
> decision-making.
lshw and dmidecode are wonderful tools, but do output a huge amount of
information.  You have to be both confident and patient enough to find the bit
that you actually want.  The person on the newbie list doesn't have that kind
of confidence.  As long as she reports that she has at least 1 GB RAM, that
isn't the cause of her problem, so why worry her with extraneous information?

Anne
--
New to KDE4? - get help from http://userbase.kde.org
Just found a cool new feature?  Add it to UserBase


signature.asc (205 bytes) Download Attachment