<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 13/03/2016 16:10, Gordan Bobic wrote:<br>
<blockquote cite="mid:56E590F7.2000100@redsleeve.org" type="cite">On
13/03/16 15:57, Michael Howard wrote:
<br>
<blockquote type="cite">On 13/03/2016 14:58, Gordan Bobic wrote:
<br>
<blockquote type="cite">On 13/03/16 14:20, Michael Howard wrote:
<br>
<blockquote type="cite">On 13/03/2016 07:34, Gordan Bobic
wrote:
<br>
<blockquote type="cite">Does anyone have any input on what
(if any) lm_sensors drivers can be
<br>
used? Probing tends to result in crashing the machine. Is
there
<br>
something other than ipmi available?
<br>
</blockquote>
You'll probably find it's the default kernel causing the
crash, it'll
<br>
likely work with your new kernel, it does here.
<br>
</blockquote>
<br>
No, still causes a crash:
<br>
Do you want to scan for Super I/O sensors? (YES/no):
<br>
Probing for Super-I/O at 0x2e/0x2f
<br>
Trying family `National Semiconductor/ITE'...
<br>
Message from syslogd@orcone at Mar 13 14:34:18 ...
<br>
kernel:Internal error: : 96000010 [#1] SMP
<br>
<br>
Some systems (mainly servers) implement IPMI, a set of common
interfaces
<br>
through which system health data may be retrieved, amongst
other things.
<br>
We first try to get the information from SMBIOS. If we don't
find it
<br>
there, we have to read from arbitrary I/O ports to probe for
such
<br>
interfaces. This is normally safe. Do you want to scan for
IPMI
<br>
interfaces? (YES/no):
<br>
# DMI data unavailable, please consider installing dmidecode
2.7
<br>
# or later for better results.
<br>
Probing for `IPMI BMC KCS' at 0xca0...
<br>
Message from syslogd@orcone at Mar 13 14:51:42 ...
<br>
kernel:Internal error: : 96000010 [#1] SMP
<br>
<br>
So it seems the sensors aren't there, and proving the various
I/O
<br>
ranges causes a crash.
<br>
<br>
Still it would be nice to get "ipmitool sensor" working
locally.
<br>
# ipmitool sensor
<br>
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or
/dev/ipmidev/0:
<br>
No such file or directory
<br>
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or
/dev/ipmidev/0:
<br>
No such file or directory
<br>
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or
/dev/ipmidev/0:
<br>
No such file or directory
<br>
Get Device ID command failed
<br>
Unable to open SDR for reading
<br>
<br>
Is there a driver that I missed?
<br>
</blockquote>
This may be a compatibility issue with ipmitools package, the
protocol
<br>
is clearly compatible though. I guess you can't load the ipmi_si
module?
<br>
I created /dev/ipmi0 manually but it made no difference to the
error
<br>
displayed.
<br>
</blockquote>
<br>
<br>
# modprobe ipmi_si
<br>
modprobe: ERROR: could not insert 'ipmi_si': No such device
<br>
<br>
So I'm wondering if a different driver is needed. Or a patch for
this one.
<br>
</blockquote>
Having gone into the scant manual and the Ubuntu image (along with
some Googling) it seems the board requires an SSIF driver (<code>ipmi_smb?)
which is not in mainline since 2.6 days.<br>
</code>
<pre class="moz-signature" cols="72">--
Mike Howard
</pre>
</body>
</html>