Hi Phong, I stumbled across this in my SPAM folder. The message from Gmail: "Why is this message in Spam? It has a from address in apm.com but has failed apm.com's required tests for authentication. Learn more". "Learn more" is linked to https://support.google.com/mail/answer/1366858?hl=en&expand=5. (Sending to the list in case others are missing the reply). Jeff On Mon, Mar 14, 2016 at 10:29 AM, Phong Vo <pvo at apm.com> wrote: > Hi folks, > > > > X-Gene kernel does not support ipmitools, which relies on OpenIPMI driver > (using /dev/ipmi). > > Instead, communications to the BMC is via SSIF over /dev/i2c. > > > > You can either use ipmitools with the BMC LAN interface directly (out of > band), or freeipmi (inband). > > I don’t have the information handy at this time – will follow up tomorrow. > > > > -Phong > > > > From: arm-dev-bounces at centos.org [mailto:arm-dev-bounces at centos.org] On > Behalf Of Michael Howard > Sent: Monday, March 14, 2016 6:48 PM > To: arm-dev at centos.org > Subject: Re: [Arm-dev] Gigabyte MP30-AR0 > > > > On 13/03/2016 16:10, Gordan Bobic wrote: > > On 13/03/16 15:57, Michael Howard wrote: > > On 13/03/2016 14:58, Gordan Bobic wrote: > > On 13/03/16 14:20, Michael Howard wrote: > > On 13/03/2016 07:34, Gordan Bobic wrote: > > Does anyone have any input on what (if any) lm_sensors drivers can be > used? Probing tends to result in crashing the machine. Is there > something other than ipmi available? > > You'll probably find it's the default kernel causing the crash, it'll > likely work with your new kernel, it does here. > > > No, still causes a crash: > Do you want to scan for Super I/O sensors? (YES/no): > Probing for Super-I/O at 0x2e/0x2f > Trying family `National Semiconductor/ITE'... > Message from syslogd at orcone at Mar 13 14:34:18 ... > kernel:Internal error: : 96000010 [#1] SMP > > Some systems (mainly servers) implement IPMI, a set of common interfaces > through which system health data may be retrieved, amongst other things. > We first try to get the information from SMBIOS. If we don't find it > there, we have to read from arbitrary I/O ports to probe for such > interfaces. This is normally safe. Do you want to scan for IPMI > interfaces? (YES/no): > # DMI data unavailable, please consider installing dmidecode 2.7 > # or later for better results. > Probing for `IPMI BMC KCS' at 0xca0... > Message from syslogd at orcone at Mar 13 14:51:42 ... > kernel:Internal error: : 96000010 [#1] SMP > > So it seems the sensors aren't there, and proving the various I/O > ranges causes a crash. > > Still it would be nice to get "ipmitool sensor" working locally. > # ipmitool sensor > Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: > No such file or directory > Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: > No such file or directory > Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: > No such file or directory > Get Device ID command failed > Unable to open SDR for reading > > Is there a driver that I missed? > > This may be a compatibility issue with ipmitools package, the protocol > is clearly compatible though. I guess you can't load the ipmi_si module? > I created /dev/ipmi0 manually but it made no difference to the error > displayed. > > > > # modprobe ipmi_si > modprobe: ERROR: could not insert 'ipmi_si': No such device > > So I'm wondering if a different driver is needed. Or a patch for this one. > > Having gone into the scant manual and the Ubuntu image (along with some > Googling) it seems the board requires an SSIF driver (ipmi_smb?) which is > not in mainline since 2.6 days.