public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] memory upgrade
Date: Tue, 01 Apr 2008 15:20:49 +0800	[thread overview]
Message-ID: <1207034450.21997.3.camel@bunyip.localdomain> (raw)
In-Reply-To: <47F1DBEB.1040704@bellsouth.net>


On Tue, 2008-04-01 at 01:53 -0500, Dale wrote:
> W.Kenworthy wrote:
> > bunyip ~ # esearch lshw
> > [ Results for search key : lshw ]
> > [ Applications found : 1 ]
> >
> > *  sys-apps/lshw
> >       Latest version available: 02.11.01b
> >       Latest version installed: 02.11.01b
> >       Size of downloaded files: [no/bad digest]
> >       Homepage:    http://ezix.org/project/wiki/HardwareLiSter
> >       Description: Hardware Lister
> >       License:     GPL-2
> >
> >
> >   
> 
> I tried that on mine to but didn't post it because it may not help 
> much.  This is the only thing that I see that may help with the 
> frequency of the memory:
> 
>      *-cpu
>           description: CPU
>           product: AMD Athlon(tm) XP 2500+
>           vendor: Advanced Micro Devices [AMD]
>           physical id: 4
>           bus info: cpu@0
>           version: 6.10.0
>           slot: Socket A
>           size: 1833MHz
>           capacity: 3GHz
>           width: 32 bits
>           *clock: 166MHz*
>           capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce 
> cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 
> 3dnowext 3dnow ts
> 
> 
> Since it says the clock is 166MHz then the memory should be the same.  
> Only thing is, my memory has to be 333MHz not 166Mhz.  Basically, 
> depending on a few things, that info may not help much unless he has a 
> idea what it takes.
> 
> My advice, find out the model of the computer if it is factory built or 
> the model of the mobo if it is custom built, then go to crucial.com or 
> something and look it up that way.  Once you get the info, you can look 
> it up at whatever site you choose.
> 
> Also, if you have windoze on the rig, some memory sites can look it up 
> for you too.  I'm not sure how they do that tho.  I guess they can scan 
> something on the mobo.  I dunno.  No windoze here.
> 
> Hope that helps.
> 
> Dale
> 
> :-)  :-)  :-)

Thats the cpu - try looking at the existing memory which is what he
wants to know.

BillK

        *-bank:1
             description: DIMM DDR Synchronous 400 MHz (2.5 ns)
             product: PartNum1
             vendor: Manufacturer1
             physical id: 1
             serial: SerNum1
             slot: DIMM1
             size: 1GB
             width: 64 bits
             clock: 400MHz (2.5ns)


-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-04-01  7:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01  6:02 [gentoo-user] memory upgrade Dani Crisan
2008-04-01  6:28 ` W.Kenworthy
2008-04-01  6:53   ` Dale
2008-04-01  7:20     ` W.Kenworthy [this message]
2008-04-01  7:43       ` Dale
2008-04-03 13:14         ` [gentoo-user] how accurate is 'lshw' (was memory upgrade) ? Philip Webb
2008-04-04  0:33           ` Dale
2008-04-01 15:02 ` [gentoo-user] memory upgrade Volker Armin Hemmann
  -- strict thread matches above, loose matches on Subject: below --
2008-04-02  1:36 Dani Crisan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1207034450.21997.3.camel@bunyip.localdomain \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox