koitsu
Support for Supermicro X7DBU (Winbond W83627HF/F/HG/G & Winbond W83793G)
I would love support for my Supermicro X7DBU (Super IO: Winbond W83627HF/F/HG/G, Hardware Monitor: Winbond W83793G). I don't have much useful information yet but I'm working on it and I'm willing to provide as much information as advised.
$ uname -a
FreeBSD irony 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #0: Tue May 8 05:21:56 UTC 2018 [email protected]:/usr/obj/usr/src/sys/GENERIC amd64
$ sudo superiotool
superiotool r4.0-2827-g1a00cf0
Found Winbond W83627HF/F/HG/G (id=0x52, rev=0x41) at 0x2e
$ sudo superiotool -de
superiotool r4.0-2827-g1a00cf0
Found Winbond W83627HF/F/HG/G (id=0x52, rev=0x41) at 0x2e
Register dump:
idx 02 20 21 22 23 24 25 26 28 29 2a 2b 2c 2e 2f
val ff 52 41 ff fe c4 00 00 00 50 fc 00 ff 00 ff
def 00 52 NA ff 00 MM 00 00 00 00 7c c0 00 00 00
LDN 0x00 (Floppy)
idx 30 60 61 70 74 f0 f1 f2 f4 f5
val 00 00 00 06 02 0e 00 ff 00 00
def 01 03 f0 06 02 0e 00 ff 00 00
LDN 0x01 (Parallel port)
idx 30 60 61 70 74 f0
val 00 00 00 07 03 3f
def 01 03 78 07 04 3f
LDN 0x02 (COM1)
idx 30 60 61 70 f0
val 01 03 f8 04 00
def 01 03 f8 04 00
LDN 0x03 (COM2)
idx 30 60 61 70 f0 f1
val 01 02 f8 03 00 40
def 01 02 f8 03 00 00
LDN 0x05 (Keyboard)
idx 30 60 61 62 63 70 72 f0
val 01 00 60 00 64 01 00 80
def 01 00 60 00 64 01 0c 80
LDN 0x06 (Consumer IR)
idx 30 60 61 70
val 00 00 00 00
def 00 00 00 00
LDN 0x07 (Game port, MIDI port, GPIO 1)
idx 30 60 61 62 63 70 f0 f1 f2
val 01 00 00 00 00 00 ff ff 00
def 00 02 01 03 30 09 ff 00 00
LDN 0x08 (GPIO 2, watchdog timer)
idx 30 f0 f1 f2 f3 f5 f6 f6 f7
val 00 ff ff ff 00 08 00 00 c0
def 00 ff 00 00 00 00 00 00 00
LDN 0x09 (GPIO 3)
idx 30 f0 f1 f2 f3
val 01 ff 14 00 40
def 00 ff 00 00 00
LDN 0x0a (ACPI)
idx 30 70 e0 e1 e2 e3 e4 e5 e6 e7 f0 f1 f3 f4 f6 f7 f9 fe ff
val 01 00 00 00 f2 00 40 00 00 00 00 af 32 00 00 00 00 00 00
def 00 00 00 00 NA NA 00 00 00 00 00 00 00 00 00 00 00 00 00
LDN 0x0b (Hardware monitor)
idx 30 60 61 70 f0
val 01 02 95 00 01
def 00 00 00 00 00
Hardware monitor (0x029a)
$ sudo dmidecode
# dmidecode 3.1
Scanning /dev/mem for entry point.
SMBIOS 2.4 present.
45 structures occupying 1406 bytes.
Table at 0xCFF6A000.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Phoenix Technologies LTD
Version: 1.3b2
Release Date: 02/06/2008
Address: 0xE54B0
Runtime Size: 109392 bytes
ROM Size: 1024 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
EDD is supported
3.5"/2.88 MB floppy services are supported (int 13h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Supermicro
Product Name: X7DBU
Version: 0123456789
Serial Number: 0123456789
UUID: 53D19F64-D663-A017-8922-003048C322A8
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Supermicro
Product Name: X7DBU
Version: PCB Version
Serial Number: 0123456789
Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
Manufacturer: Supermicro
Type: Other
Lock: Not Present
Version: 0123456789
Serial Number: 0123456789
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00001234
Handle 0x0004, DMI type 4, 35 bytes
Processor Information
Socket Designation: LGA771/CPU1
Type: Central Processor
Family: Xeon
Manufacturer: Intel
ID: FB 06 00 00 FF FB EB BF
Signature: Type 0, Family 6, Model 15, Stepping 11
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Xeon(R) CPU E5
Voltage: 1.4 V
External Clock: Unknown
Max Speed: 5000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Slot 1
L1 Cache Handle: 0x0006
L2 Cache Handle: 0x0007
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x0005, DMI type 4, 35 bytes
Processor Information
Socket Designation: LGA771/CPU2
Type: Central Processor
Family: Xeon
Manufacturer: Intel
ID: FB 06 00 00 FF FB EB BF
Signature: Type 0, Family 6, Model 15, Stepping 11
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Xeon(R)
Voltage: 1.4 V
External Clock: Unknown
Max Speed: 5000 MHz
Current Speed: 2000 MHz
Status: Populated, Enabled
Upgrade: Slot 1
L1 Cache Handle: 0x0008
L2 Cache Handle: 0x0009
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 16 kB
Maximum Size: 16 kB
Supported SRAM Types:
Burst
Pipeline Burst
Asynchronous
Installed SRAM Type: Asynchronous
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x0007, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2 Cache
Configuration: Enabled, Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 8192 kB
Maximum Size: 8192 kB
Supported SRAM Types:
Burst
Pipeline Burst
Asynchronous
Installed SRAM Type: Burst
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x0008, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 16 kB
Maximum Size: 16 kB
Supported SRAM Types:
Burst
Pipeline Burst
Asynchronous
Installed SRAM Type: Asynchronous
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x0009, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2 Cache
Configuration: Enabled, Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 8192 kB
Maximum Size: 8192 kB
Supported SRAM Types:
Burst
Pipeline Burst
Asynchronous
Installed SRAM Type: Burst
Speed: Unknown
Error Correction Type: Unknown
System Type: Unknown
Associativity: Unknown
Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: JCOM1
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
External Reference Designator: COM 1
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: JCOM2
Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
External Reference Designator: COM 2
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: JKM1
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: Circular DIN-8 male
Port Type: Keyboard Port
Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: JKM1
Internal Connector Type: None
External Reference Designator: PS/2 Mouse
External Connector Type: Circular DIN-8 male
Port Type: Keyboard Port
Handle 0x000E, DMI type 9, 13 bytes
System Slot Information
Designation: PCIE#1-x8
Type: Other
Current Usage: Available
Length: Other
Characteristics:
3.3 V is provided
Handle 0x000F, DMI type 9, 13 bytes
System Slot Information
Designation: PCI#2-133MHz
Type: 64-bit PCI-X
Current Usage: In Use
Length: Long
ID: 2
Characteristics:
3.3 V is provided
Handle 0x0010, DMI type 9, 13 bytes
System Slot Information
Designation: PCIE#3-x8
Type: Other
Current Usage: Available
Length: Other
Characteristics:
3.3 V is provided
Handle 0x0011, DMI type 9, 13 bytes
System Slot Information
Designation: PCIE#4-x8/x4
Type: Other
Current Usage: Available
Length: Other
Characteristics:
3.3 V is provided
Handle 0x0012, DMI type 9, 13 bytes
System Slot Information
Designation: PCIE#5-x4
Type: Other
Current Usage: Available
Length: Other
Characteristics:
3.3 V is provided
Handle 0x0013, DMI type 11, 5 bytes
OEM Strings
String 1: Intel Dempsey/Blackford/ESB2
String 2: Supermicro motherboard-X7DBU
Handle 0x0014, DMI type 12, 5 bytes
System Configuration Options
Option 1: Jumper settings can be described here.
Handle 0x0015, DMI type 15, 29 bytes
System Event Log
Area Length: 32 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: General-purpose non-volatile data functions
Access Address: 0x0000
Status: Valid, Not Full
Change Token: 0x000000F7
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: Single-bit ECC memory error
Data Format 2: Multiple-event
Descriptor 3: Multi-bit ECC memory error
Data Format 3: Multiple-event
Handle 0x0016, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 64 GB
Error Information Handle: Not Provided
Number Of Devices: 8
Handle 0x0017, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0016
Error Information Handle: No Error
Total Width: 72 bits
Data Width: 64 bits
Size: 4096 MB
Form Factor: DIMM
Set: 1
Locator: DIMM x 2
Bank Locator: Bank1
Type: DDR2
Type Detail: Synchronous
Speed: 667 MT/s
Manufacturer: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x0018, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0016
Error Information Handle: No Error
Total Width: 72 bits
Data Width: 64 bits
Size: 4096 MB
Form Factor: DIMM
Set: 1
Locator: DIMM x 2
Bank Locator: Bank2
Type: DDR2
Type Detail: Synchronous
Speed: 667 MT/s
Manufacturer: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x0019, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0016
Error Information Handle: No Error
Total Width: 72 bits
Data Width: 64 bits
Size: 4096 MB
Form Factor: DIMM
Set: 1
Locator: DIMM x 2
Bank Locator: Bank3
Type: DDR2
Type Detail: Synchronous
Speed: 667 MT/s
Manufacturer: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x001A, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x0016
Error Information Handle: No Error
Total Width: 72 bits
Data Width: 64 bits
Size: 4096 MB
Form Factor: DIMM
Set: 1
Locator: DIMM x 2
Bank Locator: Bank4
Type: DDR2
Type Detail: Synchronous
Speed: 667 MT/s
Manufacturer: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Handle 0x001B, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x003FFFFFFFF
Range Size: 16 GB
Physical Array Handle: 0x0016
Partition Width: 4
Handle 0x001C, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FFFFFFFF
Range Size: 4 GB
Physical Device Handle: 0x0017
Memory Array Mapped Address Handle: 0x001B
Partition Row Position: Unknown
Interleave Position: Unknown
Interleaved Data Depth: Unknown
Handle 0x001D, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00100000000
Ending Address: 0x001FFFFFFFF
Range Size: 4 GB
Physical Device Handle: 0x0018
Memory Array Mapped Address Handle: 0x001B
Partition Row Position: Unknown
Interleave Position: Unknown
Interleaved Data Depth: Unknown
Handle 0x001E, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00200000000
Ending Address: 0x002FFFFFFFF
Range Size: 4 GB
Physical Device Handle: 0x0019
Memory Array Mapped Address Handle: 0x001B
Partition Row Position: Unknown
Interleave Position: Unknown
Interleaved Data Depth: Unknown
Handle 0x001F, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00300000000
Ending Address: 0x003FFFFFFFF
Range Size: 4 GB
Physical Device Handle: 0x001A
Memory Array Mapped Address Handle: 0x001B
Partition Row Position: Unknown
Interleave Position: Unknown
Interleaved Data Depth: Unknown
Handle 0x0020, DMI type 23, 13 bytes
System Reset
Status: Enabled
Watchdog Timer: Present
Boot Option: Do Not Reboot
Boot Option On Limit: Do Not Reboot
Reset Count: Unknown
Reset Limit: Unknown
Timer Interval: Unknown
Timeout: Unknown
Handle 0x0021, DMI type 24, 5 bytes
Hardware Security
Power-On Password Status: Disabled
Keyboard Password Status: Unknown
Administrator Password Status: Disabled
Front Panel Reset Status: Unknown
Handle 0x0022, DMI type 25, 9 bytes
System Power Controls
Next Scheduled Power-on: 12-31 23:59:59
Handle 0x0023, DMI type 26, 20 bytes
Voltage Probe
Description: Voltage Probe
Location: Processor
Status: OK
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Handle 0x0024, DMI type 27, 12 bytes
Cooling Device
Temperature Probe Handle: 0x0025
Type: Fan
Status: OK
OEM-specific Information: 0x00000000
Handle 0x0025, DMI type 28, 20 bytes
Temperature Probe
Description: Temperature Probe
Location: Processor
Status: OK
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Handle 0x0026, DMI type 29, 20 bytes
Electrical Current Probe
Description: Electrical Current Probe
Location: Processor
Status: OK
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Handle 0x0027, DMI type 30, 6 bytes
Out-of-band Remote Access
Manufacturer Name: Intel
Inbound Connection: Enabled
Outbound Connection: Disabled
Handle 0x0028, DMI type 32, 19 bytes
System Boot Information
Status: No errors detected
Handle 0x0029, DMI type 38, 18 bytes
IPMI Device Information
Interface Type: Unknown
Specification Version: 1.0
I2C Slave Address: 0x00
NV Storage Device: Not Present
Base Address: 0x0000000000000000 (Memory-mapped)
Register Spacing: Successive Byte Boundaries
Handle 0x002A, DMI type 126, 4 bytes
Inactive
Handle 0x002B, DMI type 127, 4 bytes
End Of Table
Handle 0x002C, DMI type 127, 4 bytes
End Of Table
$ pciconf -vl
hostb0@pci0:0:0:0: class=0x060000 card=0x978015d9 chip=0x25d88086 rev=0xb1 hdr=0x00
vendor = 'Intel Corporation'
device = '5000P Chipset Memory Controller Hub'
class = bridge
subclass = HOST-PCI
pcib1@pci0:0:2:0: class=0x060400 card=0x00000000 chip=0x25f78086 rev=0xb1 hdr=0x01
vendor = 'Intel Corporation'
device = '5000 Series Chipset PCI Express x8 Port 2-3'
class = bridge
subclass = PCI-PCI
pcib7@pci0:0:4:0: class=0x060400 card=0x00000000 chip=0x25f88086 rev=0xb1 hdr=0x01
vendor = 'Intel Corporation'
device = '5000 Series Chipset PCI Express x8 Port 4-5'
class = bridge
subclass = PCI-PCI
pcib8@pci0:0:6:0: class=0x060400 card=0x00000000 chip=0x25f98086 rev=0xb1 hdr=0x01
vendor = 'Intel Corporation'
device = '5000 Series Chipset PCI Express x8 Port 6-7'
class = bridge
subclass = PCI-PCI
none0@pci0:0:8:0: class=0x088000 card=0x978015d9 chip=0x1a388086 rev=0xb1 hdr=0x00
vendor = 'Intel Corporation'
device = '5000 Series Chipset DMA Engine'
class = base peripheral
hostb1@pci0:0:16:0: class=0x060000 card=0x978015d9 chip=0x25f08086 rev=0xb1 hdr=0x00
vendor = 'Intel Corporation'
device = '5000 Series Chipset FSB Registers'
class = bridge
subclass = HOST-PCI
hostb2@pci0:0:16:1: class=0x060000 card=0x978015d9 chip=0x25f08086 rev=0xb1 hdr=0x00
vendor = 'Intel Corporation'
device = '5000 Series Chipset FSB Registers'
class = bridge
subclass = HOST-PCI
hostb3@pci0:0:16:2: class=0x060000 card=0x978015d9 chip=0x25f08086 rev=0xb1 hdr=0x00
vendor = 'Intel Corporation'
device = '5000 Series Chipset FSB Registers'
class = bridge
subclass = HOST-PCI
hostb4@pci0:0:17:0: class=0x060000 card=0x978015d9 chip=0x25f18086 rev=0xb1 hdr=0x00
vendor = 'Intel Corporation'
device = '5000 Series Chipset Reserved Registers'
class = bridge
subclass = HOST-PCI
hostb5@pci0:0:19:0: class=0x060000 card=0x978015d9 chip=0x25f38086 rev=0xb1 hdr=0x00
vendor = 'Intel Corporation'
device = '5000 Series Chipset Reserved Registers'
class = bridge
subclass = HOST-PCI
hostb6@pci0:0:21:0: class=0x060000 card=0x978015d9 chip=0x25f58086 rev=0xb1 hdr=0x00
vendor = 'Intel Corporation'
device = '5000 Series Chipset FBD Registers'
class = bridge
subclass = HOST-PCI
hostb7@pci0:0:22:0: class=0x060000 card=0x978015d9 chip=0x25f68086 rev=0xb1 hdr=0x00
vendor = 'Intel Corporation'
device = '5000 Series Chipset FBD Registers'
class = bridge
subclass = HOST-PCI
pcib11@pci0:0:30:0: class=0x060401 card=0x978015d9 chip=0x244e8086 rev=0xd9 hdr=0x01
vendor = 'Intel Corporation'
device = '82801 PCI Bridge'
class = bridge
subclass = PCI-PCI
isab0@pci0:0:31:0: class=0x060100 card=0x978015d9 chip=0x26708086 rev=0x09 hdr=0x00
vendor = 'Intel Corporation'
device = '631xESB/632xESB/3100 Chipset LPC Interface Controller'
class = bridge
subclass = PCI-ISA
none1@pci0:0:31:3: class=0x0c0500 card=0x978015d9 chip=0x269b8086 rev=0x09 hdr=0x00
vendor = 'Intel Corporation'
device = '631xESB/632xESB/3100 Chipset SMBus Controller'
class = serial bus
subclass = SMBus
pcib2@pci0:1:0:0: class=0x060400 card=0x978015d9 chip=0x35008086 rev=0x01 hdr=0x01
vendor = 'Intel Corporation'
device = '6311ESB/6321ESB PCI Express Upstream Port'
class = bridge
subclass = PCI-PCI
pcib6@pci0:1:0:3: class=0x060400 card=0x978015d9 chip=0x350c8086 rev=0x01 hdr=0x01
vendor = 'Intel Corporation'
device = '6311ESB/6321ESB PCI Express to PCI-X Bridge'
class = bridge
subclass = PCI-PCI
pcib3@pci0:2:0:0: class=0x060400 card=0x978015d9 chip=0x35108086 rev=0x01 hdr=0x01
vendor = 'Intel Corporation'
device = '6311ESB/6321ESB PCI Express Downstream Port E1'
class = bridge
subclass = PCI-PCI
pcib4@pci0:2:1:0: class=0x060400 card=0x978015d9 chip=0x35148086 rev=0x01 hdr=0x01
vendor = 'Intel Corporation'
device = '6311ESB/6321ESB PCI Express Downstream Port E2'
class = bridge
subclass = PCI-PCI
pcib5@pci0:2:2:0: class=0x060400 card=0x978015d9 chip=0x35188086 rev=0x01 hdr=0x01
vendor = 'Intel Corporation'
device = '6311ESB/6321ESB PCI Express Downstream Port E3'
class = bridge
subclass = PCI-PCI
em0@pci0:5:0:0: class=0x020000 card=0x109615d9 chip=0x10968086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = '80003ES2LAN Gigabit Ethernet Controller (Copper)'
class = network
subclass = ethernet
em1@pci0:5:0:1: class=0x020000 card=0x109615d9 chip=0x10968086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = '80003ES2LAN Gigabit Ethernet Controller (Copper)'
class = network
subclass = ethernet
pcib9@pci0:8:0:0: class=0x060400 card=0x00000000 chip=0x03298086 rev=0x09 hdr=0x01
vendor = 'Intel Corporation'
device = '6700PXH PCI Express-to-PCI Bridge A'
class = bridge
subclass = PCI-PCI
pcib10@pci0:8:0:2: class=0x060400 card=0x00000000 chip=0x032a8086 rev=0x09 hdr=0x01
vendor = 'Intel Corporation'
device = '6700PXH PCI Express-to-PCI Bridge B'
class = bridge
subclass = PCI-PCI
mpt0@pci0:9:1:0: class=0x010000 card=0x10001000 chip=0x00541000 rev=0x01 hdr=0x00
vendor = 'LSI Logic / Symbios Logic'
device = 'SAS1068 PCI-X Fusion-MPT SAS'
class = mass storage
subclass = SCSI
vgapci0@pci0:11:1:0: class=0x030000 card=0x978015d9 chip=0x515e1002 rev=0x02 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]'
device = 'ES1000'
class = display
subclass = VGA
superiotool output is not helpful here, sorry to say. It gives me "some ideas" (specifically that one of the chips does live on SMBus, as "0x2e" looks like a slave address), but this is not how I approach adding support for motherboards. As per README.md, I rely entirely on information provided by the board vendor, to ensure that there is no chance of mishap or need to "reverse-engineer" or take "guesses" at things.
A good example of why I rely on vendor information is in doc/board-technical.md for the X7SBL series, where there are two Winbond/Nuvoton chips on the board, but only one is used for hardware monitoring. Talking to the wrong chip could very likely cause system instability. Other times, there are multiple chips used for monitoring (due to large numbers of sensors/fans/etc. that exceed capabilities of a single chip), such as in doc/board-technical.md for the X6DVA series. As you can see, every board varies.
What would be helpful is:
-
kenv | grep smbiosoutput -- there is information here I use to key off of for proper board identification. I care specifically aboutsmbios.planar.makerandsmbios.planar.product, but sometimes the other information is helpful. -
Information from Supermicro directly. I should be able to get this information from them via Email, as I have in the past; they're excellent in providing this type of detail. This, combined with IC documentation, is usually the best way to go about it. Supermicro sometimes makes hardware changes to their boards (adding in-line resistors, etc.) that can affect readings (example: doc/), and sometimes they disclose this information in their Emails.
-
Having an available X7DBU system that can be tested on for development purposes. This means accepting the possibility that the system may crash, act "anomalous" (lock up), or possibly reboot, so having physical access to the system is important. Any other problems would be unrelated. I have seen (during development, incorrect index registers being read from, due to a bug) an older Supermicro board/system lock up requiring a full power-cycle (a hard reset did not work!). If I had SSH and root access to the system (I'd need both, though locking down sudo to only run the path to the binary, as well as
gdb(installed from pkg/ports), that would be fine), that makes the process significantly faster. But if that cannot be done (for security, personal concern, etc.), that's OK too! In that scenario I would give you binaries built for 11.1-RELEASE-p10 to try, or make a specific branch in GitHub and have you compile the source code (requires you be a little familiar withgit, but not difficult), but this can take time (Emails back and forth, etc.).
It should be noted that the X7DBU is officially EoL'd, per Supermicro's website, and as doc/board-technical.md states, I do not know what their retention policies are on documentation for EoL'd boards. In other words: they may come back and say "sorry we don't have this info due to EoL", in which case I cannot add support for this board (again: I don't take risks, I only rely on vendor information -- stability is important).
Let me know if you want me to proceed, and I can start conversations with Supermicro.
I am aware of the multiple Winbond/Nuvoton; I have provided some of that information as well as links to manuals/datasheets.
I am more than willing to help in any way that I can.
I do hae a remote networked PDU if the server needs to be rebooted and I have an IPMI card coming that should be here next week.
smbios.bios.reldate="02/06/2008"
smbios.bios.vendor="Phoenix Technologies LTD"
smbios.bios.version="1.3b2"
smbios.chassis.maker="Supermicro"
smbios.chassis.serial="0123456789"
smbios.chassis.tag=" "
smbios.chassis.version="0123456789"
smbios.memory.enabled="16777216"
smbios.planar.maker="Supermicro"
smbios.planar.product="X7DBU"
smbios.planar.serial="0123456789"
smbios.planar.version="PCB Version"
smbios.socket.enabled="2"
smbios.socket.populated="2"
smbios.system.maker="Supermicro"
smbios.system.product="X7DBU"
smbios.system.serial="0123456789"
smbios.system.uuid="53d19f64-d663-a017-8922-003048c322a8"
smbios.system.version="0123456789"
smbios.version="2.4"
It is up to you whether or not you would like to take this on as well.
If you run into problems with Supermicro, I may be able to get additional information for you. I used to work for a company who used these boards in their products and have designed a large number of custom solutions and interfaces specifically for these boards.
Great! I've put in a request to Supermicro. They usually take anywhere from 5 to 10 business days to respond to these type of requests. If I don't get a response within 2 weeks I'll send another. Historically they've been very forthcoming with all the necessary details, though this is the first time I've asked for details on an EoL'd product. Cross your fingers!
I forgot one additional item: in the case that they are able to provide said information, I'll also need from you photo(s) of the BIOS screen depicting voltages, fan RPMs, and temperatures of the system where the testing will be done from. I need this to ensure that the labels in bsdhwmon match that of the BIOS (and for general validation of data). Often the MB manual omits these, or describes them inaccurately (e.g. copy-pasted from another model). Likewise, data from IPMI also can't be used for this purpose as it varies per system, IPMI F/W revision, etc.; sometimes they choose to label the sensors simply by "sensor index number" rather than actual function. You can either Email me the photos at [email protected] or put them somewhere public (ex. imgur, Dropbox, your own web server, etc.) and provide links here.
Thanks!
Response from Support below.
From: Technical Support <[email protected]>
To: Jeremy Chadwick <[email protected]>
Date: Mon, 13 Aug 2018 16:59:43 +0000
Subject: RE: Request for H/W monitoring register details
Hi Jeremy,
Thank you for contacting Supermicro technical support. The X7DBU motherboard has been EOL for many years now and our engineering
team no longer provides support for this product. Unfortunately, we will need be able to get the requested information from our
engineering team.
Technical support,
BZ
From: Jeremy Chadwick <[email protected]>
To: Technical Support <[email protected]>
Date: Mon, 13 Aug 2018 11:29:15 -0700
Subject: Re: Request for H/W monitoring register details
Support,
I understand the product is EOL. However, I don't understand your 3rd
sentence ("Unfortunately, we will need be able to get the requested
information from our engineering team"). Does this mean you're going
to get the information?
From: Technical Support <[email protected]>
To: Jeremy Chadwick <[email protected]>
Date: Mon, 13 Aug 2018 18:37:01 +0000
Subject: RE: Request for H/W monitoring register details
Hi Jeremy,
Sorry, I meant to say we will not be able to get the requested information from our engineering team.
Technical support,
BZ
Supermicro is no longer providing technical information for boards that are EoL'd. This is different than how things were several years ago (I was able to ask for information from EoL'd boards on several occasions).
Therefore, I cannot add support for the Supermicro X7DBU to bsdhwmon.
Your only option would be to get IPMI modules, use whatever tools there are for IPMI (maybe openipmi or freeipmi ?), and hope sensor information is available through that. It is in most situations, but varies from board to board. Make sure you are running both the latest BIOS and IPMI firmware for your module.
It should also be noted here that on most newer (2013-present) boards, Supermicro has been pushing IPMI quite hard, and TMK no longer provide open documentation for sensor info, instead insisting you use IPMI. This, if the above is true, in effect means bsdhwmon is a project I should probably retire permanently. Sad news.
Fucking garbage
Clint Tyler http://www.cdtwebsolutions.com
On Tue, Feb 20, 2024 at 12:18 PM Jeremy Chadwick @.***> wrote:
Spammers have finally hit GitHub. Amazing.
— Reply to this email directly, view it on GitHub https://github.com/koitsu/bsdhwmon/issues/6#issuecomment-1954900196, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAIMOOZWHKLKP6WXRTZBF3YUTZI5AVCNFSM4FO6EOY2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJVGQ4TAMBRHE3A . You are receiving this because you were mentioned.Message ID: @.***>
