Is there anyway to find out what sticks of RAM is inside a specific machine aside from opening it? I saw this Windows application "CPU-Z" that gives you the number or sticks, the size, latency and stuff, aside from CPU type, AGP and some other things. A nifty little software actually. Is there anything like it under Linux? -- /Rikard ----------------------------------------------------------------------------- email : rikard.j@rikjoh.com web : http://www.rikjoh.com mob: : +46 (0)763 19 76 25 ------------------------ Public PGP fingerprint ---------------------------- < 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78 46 1C EE 56 >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-10-18 at 10:25 +0200, Rikard Johnels wrote:
Is there anything like it under Linux?
hwinfo --memory but it doesn't tell much. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFNfTStTMYHG2NR9URAnmKAJ4ugb8NBNE6Rb2jTqhNR1O8r4xtxwCeO3on Rc4Atsa87rHaAH5eh9h/Xk0= =3Fk5 -----END PGP SIGNATURE-----
On 10/18/06, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Wednesday 2006-10-18 at 10:25 +0200, Rikard Johnels wrote:
Is there anything like it under Linux?
hwinfo --memory
but it doesn't tell much.
- --
Does anybody know a software that can tell you the type of RAM mounted inside the CPU? I mean SD or DDR? I know that we can easily find it out by inspecting the physical structure of the RAM sticks..but is there are software that can do that? ..Just curious. :) --
Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Rikard Johnels wrote:
Is there anyway to find out what sticks of RAM is inside a specific machine aside from opening it? I saw this Windows application "CPU-Z" that gives you the number or sticks, the size, latency and stuff, aside from CPU type, AGP and some other things. A nifty little software actually.
Is there anything like it under Linux?
Some time ago i stumbled upon some "CPU-Z"-like application on kde-apps.org. I believe it was http://kde-apps.org/content/show.php?content=42435 but it does not show much info on the memory.
Rikard Johnels wrote:
Is there anyway to find out what sticks of RAM is inside a specific machine aside from opening it? I saw this Windows application "CPU-Z" that gives you the number or sticks, the size, latency and stuff, aside from CPU type, AGP and some other things. A nifty little software actually.
Is there anything like it under Linux?
Yes, it's part of the lm-sensors project - decode-dimms will help you. /Per Jessen, Zürich -- http://www.spamchek.com/ - managed email security. Starting at CHF5.00/month/user.
Per Jessen wrote:
Rikard Johnels wrote:
Is there anyway to find out what sticks of RAM is inside a specific machine aside from opening it? I saw this Windows application "CPU-Z" that gives you the number or sticks, the size, latency and stuff, aside from CPU type, AGP and some other things. A nifty little software actually.
Is there anything like it under Linux?
Yes, it's part of the lm-sensors project - decode-dimms will help you.
Couldn't locate it on my box, checked out what comes with sensors and noted there is a perl script: /usr/bin/decode-dimms.pl -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin
On Wednesday 18 October 2006 15:59, Geoffrey wrote:
Per Jessen wrote:
Rikard Johnels wrote:
Is there anyway to find out what sticks of RAM is inside a specific machine aside from opening it? I saw this Windows application "CPU-Z" that gives you the number or sticks, the size, latency and stuff, aside from CPU type, AGP and some other things. A nifty little software actually.
Is there anything like it under Linux?
Yes, it's part of the lm-sensors project - decode-dimms will help you.
Couldn't locate it on my box, checked out what comes with sensors and noted there is a perl script:
/usr/bin/decode-dimms.pl
-- Until later, Geoffrey
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
That didn't work as i wanted it too. Or shall i say "not at all"..? sparhawk:/home/rikjoh # decode-dimms.pl PC DIMM Serial Presence Detect Tester/Decoder By Philip Edelbrock, Christian Zuckschwerdt and others Version 2.6.6 ls: /proc/sys/dev/sensors/: No such file or directory Number of SDRAM DIMMs detected and decoded 0 Try '/usr/bin/decode-dimms.pl --format' for html output. But then i tried 'sensors' and it gave me (among other things) eeprom-i2c-0-52 Adapter: SMBus I801 adapter at 5000 Memory type: SDR SDRAM DIMM Memory size (MB): 256 eeprom-i2c-0-51 Adapter: SMBus I801 adapter at 5000 Memory type: SDR SDRAM DIMM Memory size (MB): 128 eeprom-i2c-0-50 Adapter: SMBus I801 adapter at 5000 Memory type: SDR SDRAM DIMM Memory size (MB): 256 So in my case the sollution was to use 'sensors' The question now becomes; What package provides the "/proc/sys/dev/sensors/" -- /Rikard ----------------------------------------------------------------------------- email : rikard.j@rikjoh.com web : http://www.rikjoh.com mob: : +46 (0)763 19 76 25 ------------------------ Public PGP fingerprint ---------------------------- < 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78 46 1C EE 56 >
Rikard Johnels wrote:
That didn't work as i wanted it too. Or shall i say "not at all"..?
sparhawk:/home/rikjoh # decode-dimms.pl
PC DIMM Serial Presence Detect Tester/Decoder By Philip Edelbrock, Christian Zuckschwerdt and others Version 2.6.6
ls: /proc/sys/dev/sensors/: No such file or directory Number of SDRAM DIMMs detected and decoded 0
I suspect you need to load the proper modules - i2c and eeprom, maybe more. Check out http://www.lm-sensors.org/ Per Jessen, Zurich -- http://www.spamchek.com/ - managed email security. Starting at SFr5/month/user.
On Wednesday 18 October 2006 16:57, Per Jessen wrote:
Rikard Johnels wrote:
That didn't work as i wanted it too. Or shall i say "not at all"..?
sparhawk:/home/rikjoh # decode-dimms.pl
PC DIMM Serial Presence Detect Tester/Decoder By Philip Edelbrock, Christian Zuckschwerdt and others Version 2.6.6
ls: /proc/sys/dev/sensors/: No such file or directory Number of SDRAM DIMMs detected and decoded 0
I suspect you need to load the proper modules - i2c and eeprom, maybe more. Check out http://www.lm-sensors.org/
Per Jessen, Zurich
-- http://www.spamchek.com/ - managed email security. Starting at SFr5/month/user.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
I have gkrellm and sensors running.. lsmod |grep i2c i2c_sensor 3584 2 w83627hf,eeprom i2c_isa 2176 0 i2c_i801 8844 0 i2c_core 20368 5 w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_i801 -- /Rikard ----------------------------------------------------------------------------- email : rikard.j@rikjoh.com web : http://www.rikjoh.com mob: : +46 (0)763 19 76 25 ------------------------ Public PGP fingerprint ---------------------------- < 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78 46 1C EE 56 >
Rikard Johnels wrote:
I have gkrellm and sensors running..
lsmod |grep i2c i2c_sensor 3584 2 w83627hf,eeprom i2c_isa 2176 0 i2c_i801 8844 0 i2c_core 20368 5 w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_i801
Hmm, here is my output from running decode-dimms on my mostly vanilla 10.1 system. http://jessen.ch/files/decode-dimms.txt Per Jessen, Zurich -- http://www.spamchek.com/ - managed email security. Starting at SFr5/month/user.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-10-18 at 18:28 +0200, Per Jessen wrote:
Rikard Johnels wrote:
I have gkrellm and sensors running..
lsmod |grep i2c i2c_sensor 3584 2 w83627hf,eeprom i2c_isa 2176 0 i2c_i801 8844 0 i2c_core 20368 5 w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_i801
Hmm, here is my output from running decode-dimms on my mostly vanilla 10.1 system.
Interesting. But I can not run it. My motherboard doesn't have sensors input, ie, not temperature readings. Thus, I can not install the sensors package, so decode-dimms doesn't run. But I don't understan why sensors is needed to check the ram. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFNnDNtTMYHG2NR9URAv5CAJ9BPuZvscFjRbA9xwTGbWcECgXlywCdEyRM qtwptyibZWolVG0Z0qXFC08= =hgdS -----END PGP SIGNATURE-----
Carlos E. R. wrote:
Interesting. But I can not run it. My motherboard doesn't have sensors input, ie, not temperature readings. Thus, I can not install the sensors package, so decode-dimms doesn't run. But I don't understan why sensors is needed to check the ram.
It's not about need, it's about ability. The lm-sensors software understand the i2c protocol, the SPD eeproms speak i2c, so .... Per Jessen, Zurich -- http://www.spamchek.com/ - managed email security. Starting at SFr5/month/user.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2006-10-20 at 23:01 +0200, Per Jessen wrote:
Interesting. But I can not run it. My motherboard doesn't have sensors input, ie, not temperature readings. Thus, I can not install the sensors package, so decode-dimms doesn't run. But I don't understan why sensors is needed to check the ram.
It's not about need, it's about ability. The lm-sensors software understand the i2c protocol, the SPD eeproms speak i2c, so ....
Ah! That makes sense, then. And another wire, I guess. It is a serial protocol. I do have an i2c internal to the TV card, I think, but the sensor setup program gets confused and tries to use it. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFOe/xtTMYHG2NR9URAvfuAJ99O5laZX1Vm2b3/HbCm3YHGyIZuQCff+6b ES03Z0hIiFCaPHPc3lYaDjE= =uP7Y -----END PGP SIGNATURE-----
participants (6)
-
Carlos E. R.
-
Duff Mckagan
-
Geoffrey
-
Per Jessen
-
Rikard Johnels
-
Sylvester Lykkehus