On Wed, 2010-12-01 at 04:33 +0000, Ben Hutchings wrote: > On Tue, 2010-11-30 at 19:34 +0100, Marc Dequènes wrote: [...] > > dmidecode gives the following info on IPMI: > > Handle 0x003F, DMI type 38, 16 bytes > > IPMI Device Information > > Interface Type: KCS (Keyboard Control Style) > > Specification Version: 2.0 > > I2C Slave Address: 0x10 > > NV Storage Device Address: 0 > > Base Address: 0x0000000000000CA2 (I/O) > > > > Even if a hardware problem is perhaps the cause, the module should not > > block after not finding any device. Moreover, it looks at address 0x20, > > while the SMBIOS reports 0x10 (via dmidecode), so the problem perhaps > > lies here. > [...] > > I don't think so. For some reason, dmidecode divides the specified I2C > address by 2 before displaying it. This has no basis in the SMBIOS > specification and is probably a bug in dmidecode. Actually this is all correct. IPMI uses 8-bit addresses which may be either an I2C address multiplied by 2 (even number), or a software address (odd number). Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part