home.social

#dmidecode — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dmidecode, aggregated by home.social.

fetched live
  1. [How-To] Velocidad y tipo de RAM en Linux

    Pues muchas veces ha pasado, que no tenemos un destornillador o un multiusos a mano, para destapar un case y acceder a la memoria RAM, ya que no recuerdo sus especificaciones. Y ahora cómo puedo comprobar la velocidad y el tipo de la memoria RAM (DDR1 o DDR2 o DDR3 o DDR4 o DDR5) sin abrir mi computadora? Necesito comprar RAM y necesito saber la velocidad exacta y el tipo instalados...

    #dmidecode #lshw #cpu_x #linux #hardware

    h4ckseed.wordpress.com/2025/09

  2. [How-To] Velocidad y tipo de RAM en Linux

    Pues muchas veces ha pasado, que no tenemos un destornillador o un multiusos a mano, para destapar un case y acceder a la memoria RAM, ya que no recuerdo sus especificaciones. Y ahora cómo puedo comprobar la velocidad y el tipo de la memoria RAM (DDR1 o DDR2 o DDR3 o DDR4 o DDR5) sin abrir mi computadora? Necesito comprar RAM y necesito saber la velocidad exacta y el tipo instalados...

    #dmidecode #lshw #cpu_x #linux #hardware

    h4ckseed.wordpress.com/2025/09

  3. [How-To] Velocidad y tipo de RAM en Linux

    Pues muchas veces ha pasado, que no tenemos un destornillador o un multiusos a mano, para destapar un case y acceder a la memoria RAM, ya que no recuerdo sus especificaciones. Y ahora cómo puedo comprobar la velocidad y el tipo de la memoria RAM (DDR1 o DDR2 o DDR3 o DDR4 o DDR5) sin abrir mi computadora? Necesito comprar RAM y necesito saber la velocidad exacta y el tipo instalados...

    #dmidecode #lshw #cpu_x #linux #hardware

    h4ckseed.wordpress.com/2025/09

  4. [How-To] Velocidad y tipo de RAM en Linux

    Pues muchas veces ha pasado, que no tenemos un destornillador o un multiusos a mano, para destapar un case y acceder a la memoria RAM, ya que no recuerdo sus especificaciones. Y ahora cómo puedo comprobar la velocidad y el tipo de la memoria RAM (DDR1 o DDR2 o DDR3 o DDR4 o DDR5) sin abrir mi computadora? Necesito comprar RAM y necesito saber la velocidad exacta y el tipo instalados...

    #dmidecode #lshw #cpu_x #linux #hardware

    h4ckseed.wordpress.com/2025/09

  5. Beware that data have proven to be too unreliable to be blindly trusted. does not scan your hardware, it only reports what the BIOS told it to - - nongnu.org/dmidecode/

  6. The problem came when the ram/board memory array topology was more complicated than a laptop or some vms (big hint about the developers), for example, > 1 array on board. Like most servers have, and which handles correctly, usually, by assigning each array a handle, and linking each slot to that handle.

    Anyway, for at least some syntaxes, we found a workaround for this, but it's very fragile and depends on specific term in BANK_LOCATION, which never is robust, but good enough.

    2/

  7. Do not ask users to share the output of #dmidecode without strong need, as it contains data some people would prefer to keep privat (like serial numbers for board, chassis, …).

    Instead tell them to share the output of the following command, which usually suffices (for example to generate #kernel quirks):

    grep '' /sys/class/dmi/id/* 2>/dev/null

    #NoteToSelf #LinuxKernel

    [Edits: grep command updated after valid critique and good suggestions from @Aissen and @lkundrak]

  8. Do not ask users to share the output of without strong need, as it contains data some people would prefer to keep privat (like serial numbers for board, chassis, …).

    Instead tell them to share the output of the following command, which usually suffices (for example to generate quirks):

    grep '' /sys/class/dmi/id/* 2>/dev/null

    [Edits: grep command updated after valid critique and good suggestions from @Aissen and @[email protected]]

  9. Do not ask users to share the output of #dmidecode without strong need, as it contains data some people would prefer to keep privat (like serial numbers for board, chassis, …).

    Instead tell them to share the output of the following command, which usually suffices (for example to generate #kernel quirks):

    grep '' /sys/class/dmi/id/* 2>/dev/null

    #NoteToSelf #LinuxKernel

    [Edits: grep command updated after valid critique and good suggestions from @Aissen and @lkundrak]

  10. Do not ask users to share the output of #dmidecode without strong need, as it contains data some people would prefer to keep privat (like serial numbers for board, chassis, …).

    Instead tell them to share the output of the following command, which usually suffices (for example to generate #kernel quirks):

    grep '' /sys/class/dmi/id/* 2>/dev/null

    #NoteToSelf #LinuxKernel

    [Edits: grep command updated after valid critique and good suggestions from @Aissen and @lkundrak]

  11. Do not ask users to share the output of #dmidecode without strong need, as it contains data some people would prefer to keep privat (like serial numbers for board, chassis, …).

    Instead tell them to share the output of the following command, which usually suffices (for example to generate #kernel quirks):

    grep '' /sys/class/dmi/id/* 2>/dev/null

    #NoteToSelf #LinuxKernel

    [Edits: grep command updated after valid critique and good suggestions from @Aissen and @lkundrak]

  12. @RL_Dane @mjgardner @benjaminhollon Would be very unlikely to be any performance boost. Probably a decrease I'd guess. Things that take longest are most dynamic, usb, gfx, smartctl, the stuff that is static relatively for each boot are very fast programs, #lspci, #dmidecode, but adding boot testing... not fun, lol. It would just be more code. This why I focus a lot on realtime optimizations, removing subshell calls, that's the real speedups.

  13. @RL_Dane @mjgardner @benjaminhollon Would be very unlikely to be any performance boost. Probably a decrease I'd guess. Things that take longest are most dynamic, usb, gfx, smartctl, the stuff that is static relatively for each boot are very fast programs, , , but adding boot testing... not fun, lol. It would just be more code. This why I focus a lot on realtime optimizations, removing subshell calls, that's the real speedups.

  14. @RL_Dane @mjgardner @benjaminhollon Would be very unlikely to be any performance boost. Probably a decrease I'd guess. Things that take longest are most dynamic, usb, gfx, smartctl, the stuff that is static relatively for each boot are very fast programs, #lspci, #dmidecode, but adding boot testing... not fun, lol. It would just be more code. This why I focus a lot on realtime optimizations, removing subshell calls, that's the real speedups.

  15. @RL_Dane @mjgardner @benjaminhollon Would be very unlikely to be any performance boost. Probably a decrease I'd guess. Things that take longest are most dynamic, usb, gfx, smartctl, the stuff that is static relatively for each boot are very fast programs, #lspci, #dmidecode, but adding boot testing... not fun, lol. It would just be more code. This why I focus a lot on realtime optimizations, removing subshell calls, that's the real speedups.

  16. is a information extractor.

    dmidecode scans the BIOS's DMI information and prints everything it can find. Information that may be found includes installed CPUs, RAM, PCI cards/slots, miscellaneous IO ports, etc. dmidecode comes with several other tools which can print other standardized information or platform specific information.

    Website 🔗️: nongnu.org/dmidecode/

    apt 📦️: dmidecode

  17. #dmidecode is a #BIOS information extractor.

    dmidecode scans the BIOS's DMI information and prints everything it can find. Information that may be found includes installed CPUs, RAM, PCI cards/slots, miscellaneous IO ports, etc. dmidecode comes with several other tools which can print other standardized information or platform specific information.

    Website 🔗️: nongnu.org/dmidecode/

    apt 📦️: dmidecode

    #free #opensource #foss #fossmendations #sysadmin