Advisory: Updated dmidecode package provides SMBIOS3 support. This update provides proper SMBIOS3 support for newer hardware. SRPMS: dmidecode-3.0-1.mga5.src.rpm i586: dmidecode-3.0-1.mga5.i586.rpm x86_64: dmidecode-3.0-1.mga5.x86_64.rpm How to test: with old dmidecode-2.12 as root: dmidecode >dmidecode.old install dmidecode-3.0 dmidecode >dmidecode.new Then use diff (form diffutils package) to see changes diff -u dmidecode.old dmidecode.new For example on older hw the only thing changed might be: --- dmidecode.old +++ dmidecode.new @@ -1,4 +1,5 @@ -# dmidecode 2.12 +# dmidecode 3.0 +Getting SMBIOS data from sysfs. SMBIOS 2.6 present. On newer SMBIOS3 hw, you might see something like: --- dmidecode.old +++ dmidecode.new @@ -1,9 +1,6 @@ -# dmidecode 2.12 -# SMBIOS entry point at 0x878d9000 -SMBIOS 3.0 present. -# SMBIOS implementations newer than version 2.7 are not -# fully supported by this version of dmidecode. -32 structures occupying 2738 bytes. +# dmidecode 3.0 +Getting SMBIOS data from sysfs. +SMBIOS 3.0.0 present. Table at 0x878D6000. Handle 0x0000, DMI type 0, 24 bytes @@ -472,18 +469,18 @@ Group Associations Name: Firmware Version Info Items: 6 - 0x0016 (<OUT OF SPEC>) - 0x001B (<OUT OF SPEC>) - 0x001C (<OUT OF SPEC>) - 0x001D (<OUT OF SPEC>) - 0x001E (<OUT OF SPEC>) - 0x001F (<OUT OF SPEC>) + 0x0016 (OEM-specific) + 0x001B (OEM-specific) + 0x001C (OEM-specific) + 0x001D (OEM-specific) + 0x001E (OEM-specific) + 0x001F (OEM-specific) On bigger SMBIOS3 hw (like an intel X99 based m/b) , dmidecode 2.12 would simply fail to run with some error like: /sys/firmware/dmi/tables/DMI: Unexpected end of file Table is unreachable, sorry. where as the new dmidecode 3.0 gets proper output
Testing mga5 64 Acer i3-4005u laptop # diff -u before.txt after.txt --- before.txt 2016-05-06 10:00:33.457484702 +0100 +++ after.txt 2016-05-06 10:29:16.721276971 +0100 @@ -1,8 +1,7 @@ -# dmidecode 2.12 +# dmidecode 3.0 # SMBIOS entry point at 0x9c742000 +Found SMBIOS entry point in EFI, reading table from /dev/mem. SMBIOS 2.8 present. -# SMBIOS implementations newer than version 2.7 are not -# fully supported by this version of dmidecode. 24 structures occupying 1353 bytes. Table at 0x9C741000. @@ -124,7 +123,7 @@ Max Speed: 1700 MHz Current Speed: 1700 MHz Status: Populated, Enabled - Upgrade: <OUT OF SPEC> + Upgrade: Socket BGA1168 L1 Cache Handle: 0x0008 L2 Cache Handle: 0x0009 L3 Cache Handle: 0x000A @@ -274,9 +273,9 @@ Part Number: Not Specified Rank: Unknown Configured Clock Speed: Unknown - Minimum voltage: Unknown - Maximum voltage: Unknown - Configured voltage: Unknown + Minimum Voltage: Unknown + Maximum Voltage: Unknown + Configured Voltage: Unknown Handle 0x0010, DMI type 17, 40 bytes Memory Device @@ -298,9 +297,9 @@ Part Number: HMT41GS6BFR8A-PB Rank: 2 Configured Clock Speed: 1600 MHz - Minimum voltage: 1.500 V - Maximum voltage: 1.500 V - Configured voltage: Unknown + Minimum Voltage: 1.5 V + Maximum Voltage: 1.5 V + Configured Voltage: Unknown Handle 0x0011, DMI type 19, 31 bytes Memory Array Mapped Address @@ -330,13 +329,17 @@ 65 31 00 00 26 00 00 00 76 50 72 6F 00 00 00 00 Handle 0x0014, DMI type 170, 78 bytes -OEM-specific Type - Header and Data: - AA 4E 14 00 01 08 00 00 7F 00 0F 00 0E 10 04 01 - 01 08 41 01 01 00 42 01 02 00 43 01 04 00 44 01 - 08 00 45 01 10 00 48 01 20 00 49 01 40 00 61 01 - 01 00 62 01 02 00 63 01 04 00 64 01 08 00 82 01 - 02 00 83 01 04 00 86 01 00 10 89 01 08 00 +Acer Hotkey Function + Function bitmap for Communication Button: 0x0801 + WiFi: Yes + 3G: No + WiMAX: No + Bluetooth: Yes + Function bitmap for Application Button: 0x0000 + Function bitmap for Media Button: 0x007f + Function bitmap for Display Button: 0x000f + Function bitmap for Others Button: 0x100e + Communication Function Key Number: 4 Handle 0x0015, DMI type 171, 49 bytes OEM-specific Type
Whiteboard: (none) => has_procedure
Intel Skylake i5-6500. I removed from the diff everything which was just whitespace or case-related. # diff -puN d.old d.new --- d.old 2016-05-09 20:23:27.824392619 +0200 +++ d.new 2016-05-09 20:24:11.263769449 +0200 @@ -1,7 +1,6 @@ -# dmidecode 2.12 +# dmidecode 3.0 +Getting SMBIOS data from sysfs. SMBIOS 3.0 present. -# SMBIOS implementations newer than version 2.7 are not -# fully supported by this version of dmidecode. 92 structures occupying 4324 bytes. Table at 0xBFED6000. @@ -778,7 +777,7 @@ Memory Device Set: None Locator: DIMM_A1 Bank Locator: BANK 0 - Type: <OUT OF SPEC> + Type: DDR4 Type Detail: Synchronous Speed: 2133 MHz Manufacturer: Kingston @@ -787,9 +786,9 @@ Memory Device Part Number: 9905625-030.A00G Rank: 2 Configured Clock Speed: 2133 MHz - Minimum voltage: Unknown - Maximum voltage: Unknown - Configured voltage: 1.200 V + Minimum Voltage: Unknown + Maximum Voltage: Unknown + Configured Voltage: 1.2 V Handle 0x0048, DMI type 17, 40 bytes Memory Device @@ -826,7 +825,7 @@ Memory Device Set: None Locator: DIMM_B1 Bank Locator: BANK 2 - Type: <OUT OF SPEC> + Type: DDR4 Type Detail: Synchronous Speed: 2133 MHz Manufacturer: Kingston @@ -835,9 +834,9 @@ Memory Device Part Number: 9905625-030.A00G Rank: 2 Configured Clock Speed: 2133 MHz - Minimum voltage: Unknown - Maximum voltage: Unknown - Configured voltage: 1.200 V + Minimum Voltage: Unknown + Maximum Voltage: Unknown + Configured Voltage: 1.2 V Handle 0x004A, DMI type 17, 40 bytes Memory Device @@ -1004,18 +1003,18 @@ Handle 0x0057, DMI type 14, 23 bytes Group Associations Name: Firmware Version Info Items: 6 - 0x004C (<OUT OF SPEC>) - 0x0051 (<OUT OF SPEC>) - 0x0052 (<OUT OF SPEC>) - 0x0053 (<OUT OF SPEC>) - 0x0054 (<OUT OF SPEC>) - 0x0055 (<OUT OF SPEC>) + 0x004C (OEM-specific) + 0x0051 (OEM-specific) + 0x0052 (OEM-specific) + 0x0053 (OEM-specific) + 0x0054 (OEM-specific) + 0x0055 (OEM-specific) Handle 0x0058, DMI type 14, 8 bytes Group Associations Name: $MEI Items: 1 - 0x0000 (<OUT OF SPEC>) + 0x0000 (OEM-specific) Handle 0x0059, DMI type 219, 81 bytes OEM-specific Type
Trying M5 x64 real AMD EFI hardware Having included this update: dmidecode-3.0-1.mga5 with an abortive kernel update (reverted the kernel from that), I failed to preserve the 'before' output. BTAIM The update output looks sensible: # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. 27 structures occupying 1431 bytes. ... BIOS Information Vendor: American Megatrends Inc. Version: P11-A0 Release Date: 08/09/2012 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 4096 kB Characteristics: ... Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Packard Bell Product Name: imedia S2110 Version: Serial Number: DTU7JMF004234063C19200 UUID: AC6BA8EC-FCC1-1220-0825-033147000000 Wake-up Type: Power Switch SKU Number: Family: Packard Bell Desktop Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Packard Bell Product Name: imedia S2110 Version: 1.0A Serial Number: Asset Tag: Features: Board is a hosting board Board is replaceable Location In Chassis: Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 etc. On a 'no bad effects' basis, this is OK for me. But can Claire or Frédéric OK it - their tests were more correct?
CC: (none) => lewyssmith
(In reply to Frédéric Buclin from comment #2) > - Configured voltage: 1.200 V > + Configured Voltage: 1.2 V Damn, you will no longer be able to power half of your district using your RAM :P
Adding 64bit OK. It would benefit from 32bit testing also.
Whiteboard: has_procedure => has_procedure mga5-64-ok
Validating.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Whiteboard: has_procedure mga5-64-ok => has_procedure advisory mga5-64-ok
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGAA-2016-0074.html
Status: NEW => RESOLVEDResolution: (none) => FIXED