All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jürgen Fuchsberger" <juergen.fuchsberger@uni-graz.at>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Kernel errors for dme1737
Date: Tue, 18 Feb 2014 07:36:27 +0000	[thread overview]
Message-ID: <53030D7B.7010209@uni-graz.at> (raw)
In-Reply-To: <CADLDEKtzZeoOyyUGe7Rug8n-c0oZ_n8Cqd=HFpPZdZWgYmJARg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2362 bytes --]



On 02/18/2014 08:25 AM, Juerg Haefliger wrote:
> 
> 
> 
> On Mon, Feb 17, 2014 at 4:55 PM, Jean Delvare <jdelvare@suse.de
> <mailto:jdelvare@suse.de>> wrote:
>>
>> Hallo Jürgen,
>>
>> On Mon, 17 Feb 2014 15:33:18 +0100, Jürgen Fuchsberger wrote:
>> > On 02/13/2014 08:32 AM, Jean Delvare wrote:
>> > > In your case, the native drivers are i2c-nforce2, dme1737 and
> lm85, and
>> > > the native tool is "sensors". The IPMI driver would be ipmi-si if I
>> > > remember correctly, and its tool is "ipmitool" or equivalent
> (there are
>> > > several IPMI packages out there, I don't know which ones are available
>> > > to you.) If you have a BMC card in the machine, that card would be
>> > > accessing the monitoring chips over IPMI as well so it will happen
> even
>> > > without any driver loaded.
>> > >
>> > > If you want to use IPMI (and if you have a BMC this is the only safe
>> > > option), blacklist i2c-nforce2 and delete your lm_sensors
> configuration
>> > > file (typically /etc/sysconfig/lm_sensors on a sysconfig-based system,
>> > > might be different on your distributions, e.g. on Debian you'd just
>> > > delete the relevant modules from /etc/modules.) Then load ipmi-si and
>> > > use ipmitool or whatever IPMI tool you have installed.
>> >
>> > OK, where should I blacklist i2c-nforce2?
>>
>> Add the following statement to any .conf file under /etc/modprobe.d:
>>
>> blacklist i2c-nforce2
>>
>> > impitool does not work:
>> > wegc203094:/etc# ipmitool sensor
>> > 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
> 
> $ modprobe ipmi_si
> $ modprobe ipmi_devintf
> 
Thanks! This worked.

Juergen.
>> I can't help with that, sorry, I don't know much about IPMI.
> 
> 
>> --
>> Jean Delvare
>> Suse L3 Support
>>
>> _______________________________________________
>> lm-sensors mailing list
>> lm-sensors@lm-sensors.org <mailto:lm-sensors@lm-sensors.org>
>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

-- 
| Jürgen Fuchsberger, M.Sc.
| Wegener Center for Climate and Global Change
| University of Graz
| Brandhofgasse 5, A-8010 Graz, Austria
| phone: +43-316-380-8438
|   web: www.wegcenter.at/wegenernet
|        www.wegenernet.org


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      parent reply	other threads:[~2014-02-18  7:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11  7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
2014-02-11  9:54 ` Jürgen Fuchsberger
2014-02-11 19:24 ` Guenter Roeck
2014-02-12  8:52 ` Jürgen Fuchsberger
2014-02-12  9:37 ` Juerg Haefliger
2014-02-12 10:10 ` Jürgen Fuchsberger
2014-02-12 10:33 ` Juerg Haefliger
2014-02-12 11:07 ` Jürgen Fuchsberger
2014-02-12 11:54 ` Guenter Roeck
2014-02-12 12:05 ` Jean Delvare
2014-02-12 14:24 ` Guenter Roeck
2014-02-13  6:39 ` Jürgen Fuchsberger
2014-02-13  7:26 ` Guenter Roeck
2014-02-13  7:32 ` Jean Delvare
2014-02-17 14:33 ` Jürgen Fuchsberger
2014-02-17 14:42 ` Juerg Haefliger
2014-02-17 14:49 ` Jürgen Fuchsberger
2014-02-17 15:55 ` Jean Delvare
2014-02-18  7:25 ` Juerg Haefliger
2014-02-18  7:36 ` Jürgen Fuchsberger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53030D7B.7010209@uni-graz.at \
    --to=juergen.fuchsberger@uni-graz.at \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.