Hey Christian, Thanks for the traces. I noticed something peculiar in the ipmi-locate output.
Probing SSIF device using DMIDECODE... done IPMI Version: 1.5 IPMI locate driver: DMIDECODE IPMI interface: SSIF BMC driver device: /dev/i2c-0 BMC SMBUS slave address: 0x42 Register spacing: 1 Probing SSIF device using SMBIOS... done IPMI Version: 1.5 IPMI locate driver: SMBIOS IPMI interface: SSIF BMC driver device: /dev/i2c-0 BMC SMBUS slave address: 0x84 Register spacing: 1 The probing finds 2 different slave addresses. I'm not sure why. Perhaps you could try setting the driver values manually to see if it changes things?? bmc-info -D ssif --disable-auto-probe --driver-address=0x84 --driver-device=/dev/i2c-0 --register-spacing=1 and also try 0x42 for the driver-address. Assuming the FreeIPMI ssif driver doesn't have bugs (I don't have a machine that uses SSIF, so I've never tried it, I can only assume the original writers did it without bugs), it's possible the OpenIPMI kernel driver probes for addresses in an alternate order to the way FreeIPMI does, and by happen chance gets the right values. That might explain things. Al On Wed, 2011-02-09 at 10:14 -0800, Christian Ruppert wrote: > Hey guys, > > take a look at the attachments for "impi-locate" and "bmc-info --debug" > with debug/trace enabled. > > The kernel driver is only available through OpenIPMI and the patches are > only available up to kernel 2.6.35. I didn't get to the OpenIPMI kernel > drivers yet to port them to .36 and above. So I'd like to use FreeIPMI > instead if it works without any kernel drivers at all. > -- Albert Chu [email protected] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/freeipmi-devel
