SMBIOS 2.6 规范详解

需积分: 10 197 浏览量更新于2024-08-01 收藏 716KB PDF 举报

"SMBIOS SPEC v2.6是System Management BIOS (SMBIOS)的版本2.6规范，由Distributed Management Task Force (DMTF)发布。该文档于2008年9月4日最终确定，版权归属于DMTF。DMTF是一个非营利性的行业联盟，致力于推动企业级和系统管理的互操作性。此规范允许成员和非成员在符合规定目的下复制和使用，但需正确引用来源。由于规格可能会更新，因此应始终注意特定版本和发布日期。实施该标准或提议标准的某些元素可能涉及到第三方专利权。DMTF不对用户关于此类权利的存在、所有者或声称者的识别和披露承担责任，也不对任何不完整或不准确的专利权识别或披露负责。" 正文： SMBIOS（System Management BIOS）是一种标准接口，用于在个人计算机系统中提供硬件配置和状态信息。这个接口被设计用来支持系统管理和监控软件，比如远程管理工具、操作系统安装程序和诊断程序。SMBIOS规范v2.6是这一系列标准的一个里程碑，它定义了在BIOS固件中存储和传递系统信息的标准数据结构。 SMBIOS v2.6包含了多个结构类型，这些结构类型定义了不同种类的系统信息，如系统制造商、产品名称、序列号、系统UUID、BIOS版本、系统配置选项等。每个结构类型都有其特定的数据字段，使得管理软件能够解析这些信息来识别和管理硬件。例如，结构类型1（System Information）包含了基本的系统标识信息，而结构类型2（Base Board Information）则提供了主板的详细信息。此规范的版本2.6是一个成熟的版本，相较于早期版本，可能包含了更多的优化、增强和新结构类型，以适应不断发展的硬件环境。例如，随着新硬件组件的引入，可能有新的结构类型被添加来报告这些组件的信息，或者现有结构类型可能已经进行了扩展以包含更多的数据字段。在实现SMBIOS v2.6时，开发者需要注意的是，可能存在与标准中某些元素相关的第三方专利权。这意味着在实际应用中，可能需要获得专利持有者的授权才能合法地使用这些元素。DMTF明确表示，他们不对识别或披露这些专利权的责任负责，这也提醒了业界在实施标准时需要进行充分的专利审查。 SMBIOS SPEC v2.6是系统管理和硬件信息交换的核心标准，它定义了标准的数据格式和交换机制，促进了跨平台的硬件识别和管理。这一规范的实施对于系统集成商、操作系统开发商和硬件制造商来说至关重要，因为它确保了兼容性和互操作性，减少了与硬件管理相关的复杂性。同时，对潜在的专利问题的关注也是开发者在实现此规范时必须考虑的因素。

System Management BIOS Reference Specification Version 2.6 (Final)

DMTF Specification DSP0134 16 of 96 September 4, 2008

references), the formatted section of the structure is followed by two null (00h) BYTES. See 3.1.1 Structure

Evolution and Usage Guidelines on page 14 for a string-containing example.

Note: Each

text string is limited to 64 significant characters due to system MIF limitations.

3.2 Required Structures and Data

Beginning with SMBIOS v2.3, compliant SMBIOS implementations include the following base set of required

structures and data within those structures. For a detailed list of conformance guidelines, refer to Appendix A

Conformance Guidelines on page 79.

Not

e that DIG64-compliant systems are only required to provide a type 1 structure (which includes the UUID); see

section 4.6.2 of DIG64 for details.

Note: as of version 2.5, structure type 20 is optional.

Structure Name and Type Data Requirements

BIOS Information (Type 0) One and only one structure is present in the structure-table. BIOS Version and

BIOS Release Date strings are non-null; the date field uses a 4-digit year (e.g.

1999). All other fields reflect full BIOS support information

System Information (Type 1) Manufacturer and Product Name strings are non-null. UUID field identifies the

system’s non-zero UUID value. Wake-up Type field identifies the wake-up source

and cannot be Unknown

. One and only one structure is present in the structure-

table.

System Enclosure (Type 3) Manufacturer string is non-null; the Type field identifies the type of enclosure

(Unknown

is disallowed).

Processor Information (Type 4) One structure is required for each system processor. The presence of two

structures with the Processor Type field set to Central Processor, for instance,

identifies that the system is capable of dual-processor operations.

Socket Designation string is non-null. Processor Type, Max Speed, and Processor

Upgrade fields are all set to “known” values — i.e. the Unknown

value is disallowed

for each field.

If the associated processor is present (i.e. the CPU Socket Populated sub-field of

the Status field indicates that the socket is populated), the Processor Manufacturer

string is non-null and the Processor Family, Current Speed, and CPU Status sub-

field of the Status field are all set to “known” values.

Each of the Lx

Cache Handle fields is either set to 0xFFFF (no further cache

description) or references a valid Cache Information Structure.

Cache Information (Type 7) One structure is required for each external-to-the-processor cache.

Socket Designation string is non-null if the cache is external to the processor. If the

cache is present (i.e. the Installed Size is non-zero), the Cache Configuration field is

set to a “known” value — i.e. the Unknown

value is disallowed.

System Slots (Type 9) One structure is required for each upgradeable system slot. A structure is not

required if the slot must be populated for proper system operation (e.g. the system

contains a single memory-card slot).

Slot Designation string is non-null. Slot Type, Slot Data Bus Width, Slot ID, and

Slot Characteristics 1 & 2 are all set to “known” values.

If device presence is detectable within the slot (e.g. PCI), the Current Usage field

must be set to either Available or In-use. Otherwise (e.g. ISA), the Unknown

value

for the field is also allowed.

Physical Memory Array (Type 16) One structure is required for the system memory.

Location, Use, Memory Error Correction, and Maximum Capacity are all set to

“known” values. Number of Memory Devices is non-zero and identifies the number

of Memory Device structures that are associated with this Physical Memory Array.

System Management BIOS Reference Specification Version 2.6 (Final)

DMTF Specification DSP0134 17 of 96 September 4, 2008

Memory Device (Type 17) One structure is required for each socketed system-memory device, whether or not

the socket is currently populated; if the system includes soldered system-memory,

one additional structure is required to identify that memory device.

Device Locator string is set to a non-null value. Memory Array Handle contains the

handle associated with the Physical Memory Array structure to which this device

belongs. Data Width, Size, Form Factor, and Device Set are all set to “known”

values. If the device is present (i.e. Size is non-zero), the Total Width field is not set

to 0xFFFF (Unknown).

Memory Array Mapped Address (Type 19) One structure is required for each contiguous block of memory addresses mapped

to a Physical Memory Array.

Ending Address is larger than Starting Address. Each structure’s address range is

unique and non-overlapping. Memory Array Handle references a Physical Memory

Array structure. Partition Width is non-zero.

System Boot Information (Type 32) The structure’s length is at least 0x0B, i.e. at least one byte of System Boot Status

is provided

3.3 Structure Definitions

Many of the enumerated values are shared between SMBIOS fields and Common Information Model (CIM) MOF

properties. The table that follows identifies the relationships; any additions to these enumerated lists should be

reflected in both documents by submitting change requests to mailto:wg-cimcore@dmtf.org

and mailto:wg-

pos@dmtf.org for the CIM-related and SMBIOS-related updates, respectively. Any other enumerated value

identified in this specification is controlled by this specification; change requests should be sent to mailto:wg-

pos@dmtf.org.

See the SMBIOS CR Guide

for details on change request submission.

Name Section MOF Class.Property

Baseboard 3.3.3.1 Originally, the base board feature flags mapped to CIM properties

CIM_PhysicalPackage.HotSwappable,

CIM_PhysicalPackage.Replaceable,

CIM_PhysicalPackage.Removable. These properties are deprecated

and replaced with CIM_PhysicalPackage.RemovalConditions.

CIM_Card. RequiresDaughterCard

CIM_Card.HostingBoard

Enclosure or Chassis Type 3.3.4.1 CIM_Chassis.ChassisPackageType

Processor Type 3.3.5.1 CIM defines a CIM_Processor.Role property, which is a free-form

string.

Processor Family 3.3.5.2 CIM_Processor.Family

CIM_ArchitectureCheck.ArchitectureType

Processor Upgrade 3.3.5.5 CIM_Processor.UpgradeMethod

System Cache Type 3.3.8.4 CIM_AssociatedCacheMemory.CacheType

Cache Associativity 3.3.8.5 CIM_AssociatedCacheMemory.Associativity

Slot Data Bus Width 3.3.10.2 CIM_Slot.MaxDataWidth

Slot Current Usage 3.3.10.3 CIM handles slot population more explicitly than SMBIOS or DMI, by

using a CIM_CardInSlot class to associate the card (CIM_Card) with

the slot (CIM_Slot) into which it is inserted.

Memory Array Location 3.3.17.1 CIM handles memory location more specifically than SMBIOS or DMI,

by using a CIM_AssociatedMemory class to associate the memory

(CIM_Memory) with the device on which it is installed.

Memory Array Use 3.3.17.2 CIM handles memory array use more specifically than SMBIOS or DMI,

by defining classes that inherit from CIM_Memory to define the specific

use — e.g. CIM_CacheMemory or CIM_NonVolatileStorage.

Memory Array Error

Correction Types

3.3.17.3 CIM_Memory.ErrorMethodology CIM maps memory error correction

types into string values rather than enumerations.

Memory Device Form Factor 3.3.18.1 CIM_PhysicalMemory.FormFactor is inherited from

CIM_Chip.FormFactor, and uses a different enumeration than SMBIOS.

Memory Device Type 3.3.18.2 CIM_PhysicalMemory.MemoryType uses a different enumeration than

SMBIOS.

Memory Error Type 3.3.19.1 CIM_MemoryError.ErrorInfo Values 0Ch-0Eh have no match in the

CIM_MemoryError.ErrorInfo property, instead they are reported via

CIM_MemoryError.CorrectableError (Boolean).

System Management BIOS Reference Specification Version 2.6 (Final)

DMTF Specification DSP0134 18 of 96 September 4, 2008

Name Section MOF Class.Property

Memory Error Operation 3.3.19.3 CIM_MemoryError.Access

Pointing Device Type 3.3.22.1 CIM_PointingDevice. PointingType

Portable Battery Device

Chemistry

3.3.23.1 CIM_Battery.Chemistry

Power Supply Type 3.3.40.1 Linear/switching is reported via CIM_PowerSupply.IsSwitchingSupply

(Boolean).

Power Supply Input Voltage

Range Switching

3.3.40.1 CIM_PowerSupply.TypeOfRangeSwitching

3.3.1 BIOS Information (Type 0)

Offset Name Length Value Description

00h Type BYTE 0 BIOS Information Indicator

01h Length BYTE Varies 12h + number of BIOS Characteristics Extension Bytes. If no

Extension Bytes are used the Length will be 12h. For v2.1

and v2.2 implementations, the length is 13h since one

extension byte is defined. For v2.3 and later

implementations, the length is at least 14h since two

extension bytes are defined. For v2.4 and later

implementations, the length is at least 18h since bytes 14-

17h are defined.

02h Handle WORD Varies

04h Vendor BYTE STRING String number of the BIOS Vendor’s Name

05h BIOS Version BYTE STRING String number of the BIOS Version. This is a free form string

that may contain Core and OEM version information.

06h BIOS Starting

Address Segment

WORD Varies Segment location of BIOS starting address, e.g.0E800h.

Note: The size of the runtime BIOS image can be computed

by subtracting the Starting Address Segment from 10000h

and multiplying the result by 16.

08h BIOS Release Date BYTE STRING String number of the BIOS release date. The date string, if

supplied, is in either mm/dd/yy or mm/dd/yyyy format. If the

year portion of the string is two digits, the year is assumed to

be 19yy.

Note: The mm/dd/yyyy format is required

for SMBIOS

version 2.3 and later.

09h BIOS ROM Size BYTE Varies (n) Size (n) where 64K * (n+1) is the size of the physical device

containing the BIOS, in bytes

0Ah BIOS Characteristics QWORD Bit Field Defines which functions the BIOS supports.

PCI, PCMCIA, Flash, etc. See 3.3.1.1.

12h BIOS Characteristics

Extension Bytes

Zero or more

BYTEs

Bit Field Optional space reserved for future supported functions. The

number of Extension Bytes that are present is indicated by

the Length in offset 1 minus 12h. See 3.3.1.2 for extensions

defined for v2.1 and later implementations. For version 2.4

and later implementations, tw

o BIOS Characteristics

Extension Bytes are defined (12-13h) and bytes 14-17h are

also defined.

14h System BIOS Major

Release

BYTE Varies Identifies the major release of the System BIOS; for example,

the value will be 0Ah for revision 10.22 and 02h for revision

2.1.

This field and/or the System BIOS Minor Release field will be

updated each time a System BIOS update for a given system

is released.

If the system does not support the use of this field, the value

will be 0FFh for both this field and the System BIOS Minor

Release field.

15h System BIOS Minor

Release

BYTE Varies Identifies the minor release of the System BIOS; for example,

the value will be 16h for revision 10.22 and 01h for revision

2.1.

System Management BIOS Reference Specification Version 2.6 (Final)

DMTF Specification DSP0134 19 of 96 September 4, 2008

Offset Name Length Value Description

16h Embedded

Controller Firmware

Major Release

BYTE Varies Identifies the major release of the embedded controller

firmware; for example, the value will be 0Ah for revision

10.22 and 02h for revision 2.1.

This field and/or the Embedded Controller Firmware Minor

Release field will be updated each time an embedded

controller firmware update for a given system is released.

If the system does not have field upgradeable embedded

controller firmware, the value will be 0FFh.

17h Embedded

Controller Firmware

Minor Release

BYTE Varies Identifies the minor release of the embedded controller

firmware; for example, the value will be 16h for revision

10.22 and 01h for revision 2.1.

If the system does not have field upgradeable embedded

controller firmware, the value will be 0FFh.

3.3.1.1 BIOS Characteristics

QWORD Bit

Position

Meaning if Set

Bit 0 Reserved

Bit 1 Reserved

Bit 2 Unknown

Bit 3 BIOS Characteristics Not Supported

Bit 4 ISA is supported

Bit 5 MCA is supported

Bit 6 EISA is supported

Bit 7 PCI is supported

Bit 8 PC Card (PCMCIA) is supported

Bit 9 Plug and Play is supported

Bit 10 APM is supported

Bit 11 BIOS is Upgradeable (Flash)

Bit 12 BIOS shadowing is allowed

Bit 13 VL-VESA is supported

Bit 14 ESCD support is available

Bit 15 Boot from CD is supported

Bit 16 Selectable Boot is supported

Bit 17 BIOS ROM is socketed

Bit 18 Boot From PC Card (PCMCIA) is supported

Bit 19 EDD (Enhanced Disk Drive) Specification is supported

Bit 20 Int 13h - Japanese Floppy for NEC 9800 1.2mb (3.5”, 1k Bytes/Sector, 360 RPM) is supported

Bit 21 Int 13h - Japanese Floppy for Toshiba 1.2mb (3.5”, 360 RPM) is supported

Bit 22 Int 13h - 5.25” / 360 KB Floppy Services are supported

Bit 23 Int 13h - 5.25” /1.2MB Floppy Services are supported

Bit 24 Int 13h - 3.5” / 720 KB Floppy Services are supported

Bit 25 Int 13h - 3.5” / 2.88 MB Floppy Services are supported

Bit 26 Int 5h, Print Screen Service is supported

Bit 27 Int 9h, 8042 Keyboard services are supported

Bit 28 Int 14h, Serial Services are supported

Bit 29 Int 17h, Printer Services are supported

Bit 30 Int 10h, CGA/Mono Video Services are supported

Bit 31 NEC PC-98

Bits32:47 Reserved for BIOS Vendor

Bits 48:63 Reserved for System Vendor

3.3.1.2 BIOS Characteristics Extension Bytes

Note: All Characteristics Extension Bytes are reserved for assignment via this specification.

System Management BIOS Reference Specification Version 2.6 (Final)

DMTF Specification DSP0134 20 of 96 September 4, 2008

3.3.1.2.1 BIOS Characteristics Extension Byte 1

This information, available for SMBIOS version 2.1 and later, appears at offset 12h within the BIOS Information

structure.

Byte Bit Position Meaning if Set

Bit 0 ACPI supported

Bit 1 USB Legacy is supported

Bit 2 AGP is supported

Bit 3 I2O boot is supported

Bit 4 LS-120 boot is supported

Bit 5 ATAPI ZIP Drive boot is supported

Bit 6 1394 boot is supported

Bit 7 Smart Battery supported

3.3.1.2.2 BIOS Characteristics Extension Byte 2

This information, available for SMBIOS version 2.3 and later, appears at offset 13h within the BIOS Information

structure.

Byte Bit

Position

Meaning if Set

Bit 0 BIOS Boot Specification supported

Bit 1 Function key-initiated Network Service boot supported. When function key-uninitiated Network Service Boot is not

supported, a network adapter option ROM may choose to offer this functionality on its own, thus offering this

capability to legacy systems. When the function is supported, the network adapter option ROM shall not offer this

capability.

Bit 2 Enable Targeted Content Distribution. The manufacturer has ensured that the SMBIOS data is useful in identifying

the computer for targeted delivery of model-specific software and firmware content through third-party content

distribution services.

Bits 3:7 Reserved for future assignment via this specification.

3.3.2 System Information (Type 1)

The information in this structure defines attributes of the overall system and is intended to be associated with the

Component ID group of the system’s MIF. An SMBIOS implementation is associated with a single system instance

and contains one and only one System Information (Type 1) structure.

Offset Spec

Version

Name Length Value Description

00h 2.0+ Type BYTE 1 System Information Indicator

01h 2.0+ Length BYTE 08h or 19h Length dependent on version supported, 08h for 2.0

or 19h for 2.1-2.3.4, 1Bh for 2.4 and later.

02h 2.0+ Handle WORD Varies

04h 2.0+ Manufacturer BYTE STRING Number of Null terminated string

05h 2.0+ Product Name BYTE STRING Number of Null terminated string

06h 2.0+ Version BYTE STRING Number of Null terminated string

07h 2.0+ Serial Number BYTE STRING Number of Null terminated string

08h 2.1+ UUID 16 BYTEs Varies Universal Unique ID number, see 3.3.2.1 below.

18h 2.1+ Wake-up Type BYTE ENUM Identifies the event that caused the system to power

up. See 3.3.2.1.

19h 2.4+ SKU Number BYTE STRING Number of Null terminated string.

This text string is used to identify a particular

computer configuration for sale. It is sometimes also

called a product ID or purchase order number. This

number is frequently found in existing fields, but there

is no standard format. Typically for a given system

board from a given OEM, there are tens of unique

processor, memory, hard drive, and optical drive

configurations.

剩余95页未读，继续阅读

rong_jerry

粉丝: 1
资源: 4

SMBIOS 2.6 规范详解

SMBIOS spec 3.6

SMBIOS Spec2.6

SMBIOS Spec 2.7

SMBIOS SPEC 3.7

SMBIOS SPEC 3.5 版本

SMBIOS spec 3.5 2021

SMBIOS SPEC 3.5英文原版

SMBIOS Spec 3. 2 2018

smbios v2.3 spec

"SMBIOS SPEC 3.7发布：企业和系统管理参考规范

最新资源