[Arm-dev] Gigabyte MP30-AR0

[Michael Howard]

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.

-- 
Mike Howard