"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "man/dmidecode.8" between
dmidecode-3.2.tar.xz and dmidecode-3.3.tar.xz

About: dmidecode is a tool for dumping a computers DMI (some say SMBIOS) table contents in a human-readable format.

dmidecode.8  (dmidecode-3.2.tar.xz):dmidecode.8  (dmidecode-3.3.tar.xz)
skipping to change at line 58 skipping to change at line 58
OPTIONS OPTIONS
-d, --dev-mem FILE -d, --dev-mem FILE
Read memory from device FILE (default: /dev/mem) Read memory from device FILE (default: /dev/mem)
-q, --quiet -q, --quiet
Be less verbose. Unknown, inactive and OEM-specific entries are n ot displayed. Meta-data and han- Be less verbose. Unknown, inactive and OEM-specific entries are n ot displayed. Meta-data and han-
dle references are hidden. dle references are hidden.
-s, --string KEYWORD -s, --string KEYWORD
Only display the value of the DMI string identified by KEYWORD. K EYWORD must be a keyword from Only display the value of the DMI string identified by KEYWORD. K EYWORD must be a keyword from
the following list: bios-vendor, bios-version, bios-release-da the following list: bios-vendor, bios-version, bios-release-dat
te, system-manufacturer, system- e, bios-revision, firmware-revi-
product-name, system-version, system-serial-number, system-uuid, s sion, system-manufacturer, system-product-name, system-version, sy
ystem-family, baseboard-manufac- stem-serial-number, system-uuid,
turer, baseboard-product-name, baseboard-version, baseboard-ser system-sku-number, system-family, baseboard-manufacturer, basebo
ial-number, baseboard-asset-tag, ard-product-name, baseboard-ver-
chassis-manufacturer, chassis-type, chassis-version, chassis-se sion, baseboard-serial-number, baseboard-asset-tag, chassis-manufa
rial-number, chassis-asset-tag, cturer, chassis-type, chassis-
processor-family, processor-manufacturer, processor-version, pr version, chassis-serial-number, chassis-asset-tag, processor-fami
ocessor-frequency. Each keyword ly, processor-manufacturer, pro-
corresponds to a given DMI type and a given offset within this ent cessor-version, processor-frequency. Each keyword corresponds to
ry type. Not all strings may be a given DMI type and a given
meaningful or even defined on all systems. Some keywords may ret offset within this entry type. Not all strings may be meaningful
urn more than one result on some or even defined on all systems.
systems (e.g. processor-version on a multi-processor system). If Some keywords may return more than one result on some systems (e.g
KEYWORD is not provided or not . processor-version on a multi-
valid, a list of all valid keywords is printed and dmidecode e processor system). If KEYWORD is not provided or not valid,
xits with an error. This option a list of all valid keywords is
cannot be used more than once. 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 d irectly from sysfs, typically Note: on Linux, most of these strings can alternatively be read d irectly from sysfs, typically
from files under /sys/devices/virtual/dmi/id. Most of these fi les are even readable by regular from files under /sys/devices/virtual/dmi/id. Most of these fi les are even readable by regular
users. users.
-t, --type TYPE -t, --type TYPE
Only display the entries of type TYPE. TYPE can be either a DMI ty pe number, or a comma-separated Only display the entries of type TYPE. TYPE can be either a DMI ty pe number, or a comma-separated
list of type numbers, or a keyword from the following list: bios, system, baseboard, chassis, pro- list of type numbers, or a keyword from the following list: bios, system, baseboard, chassis, pro-
cessor, memory, cache, connector, slot. Refer to the DMI TYPES sec tion below for details. If this cessor, memory, cache, connector, slot. Refer to the DMI TYPES sec tion below for details. If this
option is used more than once, the set of displayed entries wi ll be the union of all the given option is used more than once, the set of displayed entries wi ll be the union of all the given
skipping to change at line 126 skipping to change at line 126
DMI TYPES DMI TYPES
The SMBIOS specification defines the following DMI types: The SMBIOS specification defines the following DMI types:
Type Information Type Information
──────────────────────────────────────────── ────────────────────────────────────────────
0 BIOS 0 BIOS
1 System 1 System
2 Baseboard 2 Baseboard
3 Chassis 3 Chassis
4 Processor 4 Processor
5 Memory Controller 5 Memory Controller
6 Memory Module 6 Memory Module
7 Cache 7 Cache
8 Port Connector 8 Port Connector
9 System Slots 9 System Slots
10 On Board Devices 10 On Board Devices
11 OEM Strings 11 OEM Strings
12 System Configuration Options 12 System Configuration Options
13 BIOS Language 13 BIOS Language
14 Group Associations 14 Group Associations
15 System Event Log 15 System Event Log
16 Physical Memory Array 16 Physical Memory Array
17 Memory Device 17 Memory Device
18 32-bit Memory Error 18 32-bit Memory Error
skipping to change at line 203 skipping to change at line 203
· dmidecode --type BIOS · dmidecode --type BIOS
BINARY DUMP FILE FORMAT BINARY DUMP FILE FORMAT
The binary dump files generated by --dump-bin and read using --from-dump are formatted as follows: The 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 crafte d to hard-code the table address · The SMBIOS or DMI entry point is located at offset 0x00. It is crafte d to hard-code the table address
at offset 0x20. at offset 0x20.
· The DMI table is located at offset 0x20. · The DMI table is located at offset 0x20.
UUID FORMAT
There is some ambiguity about how to interpret the UUID fields prior to S
MBIOS specification version 2.6.
There was no mention of byte swapping, and RFC 4122 says that no by
te swapping should be applied by
default. However, SMBIOS specification version 2.6 (and later) explicitly
states that the first 3 fields
of the UUID should be read as little-endian numbers (byte-swapped).
Furthermore, it implies that the
same was already true for older versions of the specification, even thoug
h it was not mentioned. In prac-
tice, many hardware vendors were not byte-swapping the UUID. So, in ord
er to preserve compatibility, it
was decided to interpret the UUID fields according to RFC 4122 (no byte s
wapping) when the SMBIOS version
is older than 2.6, and to interpret the first 3 fields as little-endia
n (byte-swapped) when the SMBIOS
version is 2.6 or later. The Linux kernel follows the same logic.
FILES FILES
/dev/mem /sys/firmware/dmi/tables/smbios_entry_point (Linux only) /sys /dev/mem
/firmware/dmi/tables/DMI (Linux /sys/firmware/dmi/tables/smbios_entry_point (Linux only)
only) /sys/firmware/dmi/tables/DMI (Linux only)
BUGS BUGS
More often than not, information contained in the DMI tables is inaccurat e, incomplete or simply wrong. More often than not, information contained in the DMI tables is inaccurat e, incomplete or simply wrong.
AUTHORS AUTHORS
Alan Cox, Jean Delvare Alan Cox, Jean Delvare
SEE ALSO SEE ALSO
biosdecode(8), mem(4), ownership(8), vpddecode(8) biosdecode(8), mem(4), ownership(8), vpddecode(8)
dmidecode March 2012 DMIDECODE(8) dmidecode January 2019 DMIDECODE(8)
 End of changes. 6 change blocks. 
23 lines changed or deleted 43 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)