All of lore.kernel.org
 help / color / mirror / Atom feed
From: m-dettling@gmx.de (Matthias Dettling)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Strange problem with lm-sensors and module eeprom
Date: Fri, 04 Aug 2006 10:30:50 +0000	[thread overview]
Message-ID: <44D321DA.2080808@gmx.de> (raw)
In-Reply-To: <44D31A26.3000103@gmx.de>

Jean Delvare schrieb:
> Hi Matthias,
> 
> 
>>i have a strange problem with lm-sensors and the eeprom module.
>>On my Tyan Mainboard (S5350) I get all values of the temperature and fan 
>>sensors, but the memory modules are not listed on the output of sensors.
>>
>>The problem is that in /sys/bus/i2c/drivers/eeprom for every memory 
>>module an entry exists and therefore the output of decode-dimms.pl 
>>delivers the correct informations about the memory.
>>
>>Thus I think there should be a problem with the sensors program or maybe 
>>with the config file.
> 
> 
> No, this is a change we made on purpose. There is a note about that in
> the CHANGES document for release 2.10.0:
> 
> Library: NOTE: libsensors(3) will no longer see eeprom (SPD) chips
>          This is intentional.  Use decode-dimms.pl if you still
>          need your memory SPD data.
> 
> The rationale is that EEPROMs are not sensors, so they didn't belong to
> libsensors in the first place.
> 

Hi Jean,

thank you, very much!

I only found old documentation on the net and was wondering, why I get 
no values about the memory. But I think it is a good idea to move the 
memory information out of the sensors output.

Best Regards
Matthias Dettling


      parent reply	other threads:[~2006-08-04 10:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04  9:57 [lm-sensors] Strange problem with lm-sensors and module eeprom Matthias Dettling
2006-08-04 10:11 ` Jean Delvare
2006-08-04 10:30 ` Matthias Dettling [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=44D321DA.2080808@gmx.de \
    --to=m-dettling@gmx.de \
    --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.