-d

Read memory from device FILE (default: /dev/mem)

-q

Be less verbose. Unknown, inactive and OEM-specific entries are not displayed. Meta-data and handle references are hidden.

-s

Only display the value of the DMI string identified by KEYWORD. KEYWORD must be a keyword from the following list: bios-ven‐dor, bios-version, bios-release-date, system-manufacturer, system-product-name, system-version, system-serial-number, system-uuid, baseboard-manufacturer, baseboard-product-name, baseboard-version, baseboard-serial-number, baseboard-asset-tag, chas‐sis-manufacturer, chassis-type, chassis-version, chassis-serial-number, chassis-asset-tag, processor-family, processor-manu‐facturer, processor-version, processor-frequency. Each keyword corresponds to a given DMI type and a given offset within thisentry type. Not all strings may be meaningful or even defined on all systems. Some keywords may return more than one resulton some systems (e.g. processor-version on a multi-processor system). If KEYWORD is not provided or not valid, a list of allvalid keywords is printed and dmidecode exits with an error. This option cannot be used more than once.Note: on Linux, most of these strings can alternatively be read directly from sysfs, typically from files under/sys/devices/virtual/dmi/id. Most of these files are even readable by regular users.

-t

Only display the entries of type TYPE. TYPE can be either a DMI type number, or a comma-separated list of type numbers, or akeyword from the following list: bios, system, baseboard, chassis, processor, memory, cache, connector, slot. Refer to the DMITYPES section below for details. If this option is used more than once, the set of displayed entries will be the union of allthe given types. If TYPE is not provided or not valid, a list of all valid keywords is printed and dmidecode exits with anerror.

-u

Do not decode the entries, dump their contents as hexadecimal instead. Note that this is still a text output, no binary datawill be thrown upon you. The strings attached to each entry are displayed as both hexadecimal and ASCII. This option is mainlyuseful for debugging.

--dump-bin

Do not decode the entries, instead dump the DMI data to a file in binary form. The generated file is suitable to pass to

--from-dump

Read the DMI data from a binary file previously generated using --dump-bin.

--no-sysfs

Do not attempt to read DMI data from sysfs files. This is mainly useful for debugging.

--oem-string

Only display the value of the OEM string number N. The first OEM string has number 1. With special value "count", return thenumber of OEM strings instead.

-h

Display usage information and exit

-V

Display the version and exitOptions --string, --type, --dump-bin and --oem-string determine the output format and are mutually exclusive.Please note in case of dmidecode is run on a system with BIOS that boasts new SMBIOS specification, which is not supported by thetool yet, it will print out relevant message in addition to requested data on the very top of the output. Thus informs the outputdata is not reliable.DMI TYPESThe SMBIOS specification defines the following DMI types:Type Information────────────────────────────────────────────0 BIOS1 System2 Baseboard3 Chassis4 Processor5 Memory Controller6 Memory Module7 Cache8 Port Connector9 System Slots10 On Board Devices11 OEM Strings12 System Configuration Options13 BIOS Language14 Group Associations15 System Event Log16 Physical Memory Array17 Memory Device18 32-bit Memory Error19 Memory Array Mapped Address20 Memory Device Mapped Address21 Built-in Pointing Device22 Portable Battery23 System Reset24 Hardware Security25 System Power Controls26 Voltage Probe27 Cooling Device28 Temperature Probe29 Electrical Current Probe30 Out-of-band Remote Access31 Boot Integrity Services32 System Boot33 64-bit Memory Error34 Management Device35 Management Device Component36 Management Device Threshold Data37 Memory Channel38 IPMI Device39 Power Supply40 Additional Information41 Onboard Devices Extended Information42 Management Controller Host InterfaceAdditionally, type 126 is used for disabled entries and type 127 is an end-of-table marker. Types 128 to 255 are for OEM-specificdata. dmidecode will display these entries by default, but it can only decode them when the vendors have contributed documentationor code for them.Keywords can be used instead of type numbers with --type. Each keyword is equivalent to a list of type numbers:Keyword Types──────────────────────────────bios 0, 13system 1, 12, 15, 23, 32baseboard 2, 10, 41chassis 3processor 4memory 5, 6, 16, 17cache 7connector 8slot 9Keywords are matched case-insensitively. The following command lines are equivalent:· dmidecode --type 0 --type 13· dmidecode --type 0,13· dmidecode --type bios· dmidecode --type BIOSBINARY DUMP FILE FORMATThe binary dump files generated by --dump-bin and read using --from-dump are formatted as follows:· The SMBIOS or DMI entry point is located at offset 0x00. It is crafted to hard-code the table address at offset 0x20.· The DMI table is located at offset 0x20.FILES/dev/mem /sys/firmware/dmi/tables/smbios_entry_point (Linux only) /sys/firmware/dmi/tables/DMI (Linux only)BUGSMore often than not, information contained in the DMI tables is inaccurate, incomplete or simply wrong.AUTHORSAlan Cox, Jean Delvare