public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Kyle <kl-I2D4Bl1yN1BBDgjK7y7TUQ@public.gmane.org>
To: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: install functioning lm-sensors on CentOS 5 - Intel/Xeon combo. Help pls.
Date: Wed, 27 Aug 2008 00:11:58 +1000	[thread overview]
Message-ID: <48B40F2E.1090600@attitia.com> (raw)
In-Reply-To: <48B3AE8C.9090505-I2D4Bl1yN1BBDgjK7y7TUQ@public.gmane.org>


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

I'm not sure how this is the wrong mailing list.

I'm looking for assistance on getting lm-sensors installed on a 
particular OS / CPU combination.  My subject line didn't originally 
state "install lm-sensors on CentOS 5 - Intel/Xeon combo. Help pls." as 
I would expect that on the lm-sensors mailing list, that would be 
understood.

Is this not the mailing list to ask for assistance in installing 
lm-sensors? If not, pls do let me know to which mailing list I should 
post? If I knew which mailing list to ask, I would've posted there.

------------------------------------------------------------------------
Kind Regards

Kyle



Kyle wrote:
> Hi folks,
>
> I'm hoping someone can hep me out pls. I've installed lm-sensors in 
> the past in 2.4 kernels and it all just worked.
>
> But I cannot for the life of me understand what is happening with or 
> figure out what I need for my CentOS 5 / 2.6 kernel install.
>
> I have read snippets which "SEEM" to indicate all of the modules I 
> need are already compiled into or modularised with the base 2.6 Kernel 
> (CentOS is of course a downline from RedHat EL), but don't really make 
> it clear. When looking in 'make menuconfig', the modules listed as 
> required for lm-sensors don't seem to match up with what I read.
>
> I've read on the lm-sensors site that I "MAY" need a different driver 
> with the XEON CPU, but I can't figure out how to tell and don't want 
> to mess up a new install.
>
> When running sensors-detect, it appears to fail to find just about 
> everything. Basically, the abridged output of sensors-detect is as 
> follows;
>
> =========================================
> Probing for PCI bus adapters...
> Sorry, no PCI bus adapters found.
>
> i2c-dev is not loaded. Do you want to load it now? (YES/no):
> Module loaded succesfully.
>
> Next adapter: SMBus I801 adapter at 2000
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x08
> Client found at address 0x10
> Client found at address 0x30
> Client found at address 0x32
> Client found at address 0x44
> Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
> Client found at address 0x50
> Probing for `SPD EEPROM'... Success!
>    (confidence 8, driver `eeprom')
> Probing for `DDC monitor'... Failed!
> Probing for `Maxim MAX6900'... Failed!
> Client found at address 0x52
> Probing for `SPD EEPROM'... Success!
>    (confidence 8, driver `eeprom')
> Client found at address 0x69
>
> Do you want to scan the ISA bus? (YES/no):
> Probing for `IPMI BMC KCS'
>  Trying address 0x0ca0... Success!
>    (confidence 4, driver `bmcsensors')        [KL] ALL OTHERS FAILED.
>
> Do you want to scan for Super I/O sensors? (YES/no):
> [KL] ALL FAILED.
>
> Do you want to scan for secondary Super I/O sensors? (YES/no):
> [KL] ALL FAILED
>
>
> Driver `eeprom' (should be inserted):
>  Detects correctly:
>  * Bus `SMBus I801 adapter at 2000'
>    Busdriver `i2c-i801', I2C address 0x50
>    Chip `SPD EEPROM' (confidence: 8)
>  * Bus `SMBus I801 adapter at 2000'
>    Busdriver `i2c-i801', I2C address 0x52
>    Chip `SPD EEPROM' (confidence: 8)
>
> Driver `bmcsensors' (should be inserted):
>  Detects correctly:
>  * ISA bus address 0x0ca0 (Busdriver `i2c-isa')
>    Chip `IPMI BMC KCS' (confidence: 4)
>
> [KL] It then offers up the changes to rc.local and modprobe.conf. But 
> within that, there's
>
> # Warning: the required module bmcsensors is not currently installed 
> on your system.
> # For status of 2.6 kernel ports see 
> http://secure.netroedge.com/~lm78/supported.html
> # If driver is built-in to the kernel, or unavailable, comment out the 
> following line.
> modprobe bmcsensors
>
> [KL] How can it detect a driver if it's apparently NOT installed on 
> the system. Where do I get hold of the correct bmcsensors module?
> ===========================================
>
> Can I ask any one of you to help out pls and ask me the right 
> questions so I know/can figure out just what the hell I should be 
> looking for?
>
>

[-- Attachment #1.2: Type: text/html, Size: 5197 bytes --]

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

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

  parent reply	other threads:[~2008-08-26 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26  7:19 install CentOS 5 - Intel/Xeon combo. Help pls Kyle
     [not found] ` <48B3AE8C.9090505-I2D4Bl1yN1BBDgjK7y7TUQ@public.gmane.org>
2008-08-26  8:43   ` Jean Delvare
2008-08-26 14:11   ` Kyle [this message]
     [not found]     ` <48B40F2E.1090600-I2D4Bl1yN1BBDgjK7y7TUQ@public.gmane.org>
2008-08-26 14:22       ` install functioning lm-sensors on " Kyle
2008-08-26 14:51       ` Jean Delvare

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=48B40F2E.1090600@attitia.com \
    --to=kl-i2d4bl1yn1bbdgjk7y7tuq@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox