How to get memory speed when dmidecode says “Speed: Unknown” and lshw just hangs












1















I'd like to get memory speed information, but dmidecode -t memory says Speed: Unknown and lshw prints out string DMI and then does nothing until I kill it.



Is there other way to get this information? Or some magic parameters for lshw or dmidecode to force them to actualy do what they're supposed to?



root@server:~# dmidecode -t memory
# dmidecode 2.9
SMBIOS 2.5 present.

Handle 0x0027, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 2

Handle 0x0029, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0027
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 2048 MB
Form Factor: DIMM
Set: None
Locator: DIMM A1
Bank Locator: BANK0
Type: Other
Type Detail: Synchronous
Speed: Unknown
Manufacturer: Manufacturer0
Serial Number: SerNum0
Asset Tag: AssetTagNum0
Part Number: PartNum0

Handle 0x002B, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0027
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 4096 MB
Form Factor: DIMM
Set: None
Locator: DIMM B1
Bank Locator: BANK1
Type: Other
Type Detail: Synchronous
Speed: Unknown
Manufacturer: Manufacturer1
Serial Number: SerNum1
Asset Tag: AssetTagNum1
Part Number: PartNum1


.



root@server:~# lshw -version
B.02.14
root@server:~# lshw
DMI









share|improve this question



























    1















    I'd like to get memory speed information, but dmidecode -t memory says Speed: Unknown and lshw prints out string DMI and then does nothing until I kill it.



    Is there other way to get this information? Or some magic parameters for lshw or dmidecode to force them to actualy do what they're supposed to?



    root@server:~# dmidecode -t memory
    # dmidecode 2.9
    SMBIOS 2.5 present.

    Handle 0x0027, DMI type 16, 15 bytes
    Physical Memory Array
    Location: System Board Or Motherboard
    Use: System Memory
    Error Correction Type: None
    Maximum Capacity: 8 GB
    Error Information Handle: Not Provided
    Number Of Devices: 2

    Handle 0x0029, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x0027
    Error Information Handle: Not Provided
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 2048 MB
    Form Factor: DIMM
    Set: None
    Locator: DIMM A1
    Bank Locator: BANK0
    Type: Other
    Type Detail: Synchronous
    Speed: Unknown
    Manufacturer: Manufacturer0
    Serial Number: SerNum0
    Asset Tag: AssetTagNum0
    Part Number: PartNum0

    Handle 0x002B, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x0027
    Error Information Handle: Not Provided
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 4096 MB
    Form Factor: DIMM
    Set: None
    Locator: DIMM B1
    Bank Locator: BANK1
    Type: Other
    Type Detail: Synchronous
    Speed: Unknown
    Manufacturer: Manufacturer1
    Serial Number: SerNum1
    Asset Tag: AssetTagNum1
    Part Number: PartNum1


    .



    root@server:~# lshw -version
    B.02.14
    root@server:~# lshw
    DMI









    share|improve this question

























      1












      1








      1








      I'd like to get memory speed information, but dmidecode -t memory says Speed: Unknown and lshw prints out string DMI and then does nothing until I kill it.



      Is there other way to get this information? Or some magic parameters for lshw or dmidecode to force them to actualy do what they're supposed to?



      root@server:~# dmidecode -t memory
      # dmidecode 2.9
      SMBIOS 2.5 present.

      Handle 0x0027, DMI type 16, 15 bytes
      Physical Memory Array
      Location: System Board Or Motherboard
      Use: System Memory
      Error Correction Type: None
      Maximum Capacity: 8 GB
      Error Information Handle: Not Provided
      Number Of Devices: 2

      Handle 0x0029, DMI type 17, 27 bytes
      Memory Device
      Array Handle: 0x0027
      Error Information Handle: Not Provided
      Total Width: 64 bits
      Data Width: 64 bits
      Size: 2048 MB
      Form Factor: DIMM
      Set: None
      Locator: DIMM A1
      Bank Locator: BANK0
      Type: Other
      Type Detail: Synchronous
      Speed: Unknown
      Manufacturer: Manufacturer0
      Serial Number: SerNum0
      Asset Tag: AssetTagNum0
      Part Number: PartNum0

      Handle 0x002B, DMI type 17, 27 bytes
      Memory Device
      Array Handle: 0x0027
      Error Information Handle: Not Provided
      Total Width: 64 bits
      Data Width: 64 bits
      Size: 4096 MB
      Form Factor: DIMM
      Set: None
      Locator: DIMM B1
      Bank Locator: BANK1
      Type: Other
      Type Detail: Synchronous
      Speed: Unknown
      Manufacturer: Manufacturer1
      Serial Number: SerNum1
      Asset Tag: AssetTagNum1
      Part Number: PartNum1


      .



      root@server:~# lshw -version
      B.02.14
      root@server:~# lshw
      DMI









      share|improve this question














      I'd like to get memory speed information, but dmidecode -t memory says Speed: Unknown and lshw prints out string DMI and then does nothing until I kill it.



      Is there other way to get this information? Or some magic parameters for lshw or dmidecode to force them to actualy do what they're supposed to?



      root@server:~# dmidecode -t memory
      # dmidecode 2.9
      SMBIOS 2.5 present.

      Handle 0x0027, DMI type 16, 15 bytes
      Physical Memory Array
      Location: System Board Or Motherboard
      Use: System Memory
      Error Correction Type: None
      Maximum Capacity: 8 GB
      Error Information Handle: Not Provided
      Number Of Devices: 2

      Handle 0x0029, DMI type 17, 27 bytes
      Memory Device
      Array Handle: 0x0027
      Error Information Handle: Not Provided
      Total Width: 64 bits
      Data Width: 64 bits
      Size: 2048 MB
      Form Factor: DIMM
      Set: None
      Locator: DIMM A1
      Bank Locator: BANK0
      Type: Other
      Type Detail: Synchronous
      Speed: Unknown
      Manufacturer: Manufacturer0
      Serial Number: SerNum0
      Asset Tag: AssetTagNum0
      Part Number: PartNum0

      Handle 0x002B, DMI type 17, 27 bytes
      Memory Device
      Array Handle: 0x0027
      Error Information Handle: Not Provided
      Total Width: 64 bits
      Data Width: 64 bits
      Size: 4096 MB
      Form Factor: DIMM
      Set: None
      Locator: DIMM B1
      Bank Locator: BANK1
      Type: Other
      Type Detail: Synchronous
      Speed: Unknown
      Manufacturer: Manufacturer1
      Serial Number: SerNum1
      Asset Tag: AssetTagNum1
      Part Number: PartNum1


      .



      root@server:~# lshw -version
      B.02.14
      root@server:~# lshw
      DMI






      linux memory debian-squeeze






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Oct 20 '13 at 10:35









      monnefmonnef

      1401110




      1401110






















          1 Answer
          1






          active

          oldest

          votes


















          0














          you could use dmesg to pull this type of information from the kernel



          root@server ~]# dmesg |grep -i memory |grep core
          [ 1.518759] nouveau [ DRM] 0: core 208MHz shader 416MHz memory 100MHz voltage 1200mV fanspeed 100%
          [ 1.518762] nouveau [ DRM] 1: core 460MHz shader 920MHz memory 400MHz voltage 1200mV fanspeed 100%
          [ 1.518764] nouveau [ DRM] c: core 459MHz shader 918MHz memory 399MHz voltage 1200mV
          [ 2.141818] nouveau [ DRM] 0: core 208MHz shader 416MHz memory 100MHz voltage 1200mV fanspeed 100%
          [ 2.141821] nouveau [ DRM] 1: core 460MHz shader 920MHz memory 400MHz voltage 1200mV fanspeed 100%
          [ 2.141823] nouveau [ DRM] c: core 459MHz shader 918MHz memory 399MHz voltage 1200mV


          dmesg is good for pulling any device info;
          ie dmesg |grep -i scsi or dmesg |grep -i usb or just dmesg| more to see it all






          share|improve this answer





















          • 1





            I had no luck with dmesg. Also from your snippet it looks like info about graphic card, not main memory.

            – monnef
            Oct 20 '13 at 13:50











          • oops your right about dmesg snippet. for lshw try updating to 2.16+

            – user9909
            Oct 20 '13 at 15:04











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f662642%2fhow-to-get-memory-speed-when-dmidecode-says-speed-unknown-and-lshw-just-hangs%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          you could use dmesg to pull this type of information from the kernel



          root@server ~]# dmesg |grep -i memory |grep core
          [ 1.518759] nouveau [ DRM] 0: core 208MHz shader 416MHz memory 100MHz voltage 1200mV fanspeed 100%
          [ 1.518762] nouveau [ DRM] 1: core 460MHz shader 920MHz memory 400MHz voltage 1200mV fanspeed 100%
          [ 1.518764] nouveau [ DRM] c: core 459MHz shader 918MHz memory 399MHz voltage 1200mV
          [ 2.141818] nouveau [ DRM] 0: core 208MHz shader 416MHz memory 100MHz voltage 1200mV fanspeed 100%
          [ 2.141821] nouveau [ DRM] 1: core 460MHz shader 920MHz memory 400MHz voltage 1200mV fanspeed 100%
          [ 2.141823] nouveau [ DRM] c: core 459MHz shader 918MHz memory 399MHz voltage 1200mV


          dmesg is good for pulling any device info;
          ie dmesg |grep -i scsi or dmesg |grep -i usb or just dmesg| more to see it all






          share|improve this answer





















          • 1





            I had no luck with dmesg. Also from your snippet it looks like info about graphic card, not main memory.

            – monnef
            Oct 20 '13 at 13:50











          • oops your right about dmesg snippet. for lshw try updating to 2.16+

            – user9909
            Oct 20 '13 at 15:04
















          0














          you could use dmesg to pull this type of information from the kernel



          root@server ~]# dmesg |grep -i memory |grep core
          [ 1.518759] nouveau [ DRM] 0: core 208MHz shader 416MHz memory 100MHz voltage 1200mV fanspeed 100%
          [ 1.518762] nouveau [ DRM] 1: core 460MHz shader 920MHz memory 400MHz voltage 1200mV fanspeed 100%
          [ 1.518764] nouveau [ DRM] c: core 459MHz shader 918MHz memory 399MHz voltage 1200mV
          [ 2.141818] nouveau [ DRM] 0: core 208MHz shader 416MHz memory 100MHz voltage 1200mV fanspeed 100%
          [ 2.141821] nouveau [ DRM] 1: core 460MHz shader 920MHz memory 400MHz voltage 1200mV fanspeed 100%
          [ 2.141823] nouveau [ DRM] c: core 459MHz shader 918MHz memory 399MHz voltage 1200mV


          dmesg is good for pulling any device info;
          ie dmesg |grep -i scsi or dmesg |grep -i usb or just dmesg| more to see it all






          share|improve this answer





















          • 1





            I had no luck with dmesg. Also from your snippet it looks like info about graphic card, not main memory.

            – monnef
            Oct 20 '13 at 13:50











          • oops your right about dmesg snippet. for lshw try updating to 2.16+

            – user9909
            Oct 20 '13 at 15:04














          0












          0








          0







          you could use dmesg to pull this type of information from the kernel



          root@server ~]# dmesg |grep -i memory |grep core
          [ 1.518759] nouveau [ DRM] 0: core 208MHz shader 416MHz memory 100MHz voltage 1200mV fanspeed 100%
          [ 1.518762] nouveau [ DRM] 1: core 460MHz shader 920MHz memory 400MHz voltage 1200mV fanspeed 100%
          [ 1.518764] nouveau [ DRM] c: core 459MHz shader 918MHz memory 399MHz voltage 1200mV
          [ 2.141818] nouveau [ DRM] 0: core 208MHz shader 416MHz memory 100MHz voltage 1200mV fanspeed 100%
          [ 2.141821] nouveau [ DRM] 1: core 460MHz shader 920MHz memory 400MHz voltage 1200mV fanspeed 100%
          [ 2.141823] nouveau [ DRM] c: core 459MHz shader 918MHz memory 399MHz voltage 1200mV


          dmesg is good for pulling any device info;
          ie dmesg |grep -i scsi or dmesg |grep -i usb or just dmesg| more to see it all






          share|improve this answer















          you could use dmesg to pull this type of information from the kernel



          root@server ~]# dmesg |grep -i memory |grep core
          [ 1.518759] nouveau [ DRM] 0: core 208MHz shader 416MHz memory 100MHz voltage 1200mV fanspeed 100%
          [ 1.518762] nouveau [ DRM] 1: core 460MHz shader 920MHz memory 400MHz voltage 1200mV fanspeed 100%
          [ 1.518764] nouveau [ DRM] c: core 459MHz shader 918MHz memory 399MHz voltage 1200mV
          [ 2.141818] nouveau [ DRM] 0: core 208MHz shader 416MHz memory 100MHz voltage 1200mV fanspeed 100%
          [ 2.141821] nouveau [ DRM] 1: core 460MHz shader 920MHz memory 400MHz voltage 1200mV fanspeed 100%
          [ 2.141823] nouveau [ DRM] c: core 459MHz shader 918MHz memory 399MHz voltage 1200mV


          dmesg is good for pulling any device info;
          ie dmesg |grep -i scsi or dmesg |grep -i usb or just dmesg| more to see it all







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Oct 20 '13 at 14:07









          monnef

          1401110




          1401110










          answered Oct 20 '13 at 13:08









          user9909user9909

          1212




          1212








          • 1





            I had no luck with dmesg. Also from your snippet it looks like info about graphic card, not main memory.

            – monnef
            Oct 20 '13 at 13:50











          • oops your right about dmesg snippet. for lshw try updating to 2.16+

            – user9909
            Oct 20 '13 at 15:04














          • 1





            I had no luck with dmesg. Also from your snippet it looks like info about graphic card, not main memory.

            – monnef
            Oct 20 '13 at 13:50











          • oops your right about dmesg snippet. for lshw try updating to 2.16+

            – user9909
            Oct 20 '13 at 15:04








          1




          1





          I had no luck with dmesg. Also from your snippet it looks like info about graphic card, not main memory.

          – monnef
          Oct 20 '13 at 13:50





          I had no luck with dmesg. Also from your snippet it looks like info about graphic card, not main memory.

          – monnef
          Oct 20 '13 at 13:50













          oops your right about dmesg snippet. for lshw try updating to 2.16+

          – user9909
          Oct 20 '13 at 15:04





          oops your right about dmesg snippet. for lshw try updating to 2.16+

          – user9909
          Oct 20 '13 at 15:04


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f662642%2fhow-to-get-memory-speed-when-dmidecode-says-speed-unknown-and-lshw-just-hangs%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          How do I know what Microsoft account the skydrive app is syncing to?

          When does type information flow backwards in C++?

          Grease: Live!