[lm-sensors] i2c-i801 on Intel Server Board se7525gp2?

[lm-sensors] i2c-i801 on Intel Server Board se7525gp2?

[Nick Ellson]

I am hoping to get some help understanding why lm_sensors is not finding 
what it need on my two servers. I am trying to follow the Identifying your 
Hardware process and this is what I get:



Next adapter: SMBus I801 adapter at 0400
Do you want to scan it? (YES/no/selectively):
Client found at address 0x30
Client found at address 0x42
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
     (confidence 8, driver `eeprom')
Client found at address 0x55
Probing for `SPD EEPROM'... Success!
     (confidence 8, driver `eeprom')
Client found at address 0x69
Client found at address 0x6e

gubbie ~ # modprobe i2c-i801
gubbie ~ # modprobe eeprom
gubbie ~ # /usr/bin/sensors -s
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!
gubbie ~ # dmesg
[17179569.184000] Linux version 2.6.17-gentoo (root at gubbie) (gcc version 
3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)) #2 SMP PREEMPT Mon Jun 
26 09:33:18 PDT 2006

<snip>

[17179640.696000] IA-32 Microcode Update Driver: v1.14 
<tigran at veritas.com>
[17179646.016000] Installing knfsd (copyright (C) 1996 okir at monad.swb.de).
[17179939.952000] i2c /dev entries driver
gubbie ~ #

gubbie ~ #  lsmod
Module                  Size  Used by
eeprom                  8080  0
i2c_dev                10244  0
nfsd                  105192  13
snd_seq_midi            9600  0
snd_emu10k1_synth       8320  0
snd_emux_synth         37120  1 snd_emu10k1_synth
snd_seq_virmidi         8960  1 snd_emux_synth
snd_seq_midi_emul       8320  1 snd_emux_synth
evbug                   3968  0
hw_random               6808  0
snd_emu10k1           118916  1 snd_emu10k1_synth
snd_rawmidi            26624  3 snd_seq_midi,snd_seq_virmidi,snd_emu10k1
snd_ac97_codec         90528  1 snd_emu10k1
snd_ac97_bus            3328  1 snd_ac97_codec
snd_util_mem            5632  2 snd_emux_synth,snd_emu10k1
i2c_i801                9740  0
snd_hwdep              10884  2 snd_emux_synth,snd_emu10k1
e752x_edac             12932  0
edac_mc                15428  1 e752x_edac
raid10                 26112  0
raid6                 109840  0
raid5                  35968  0
xor                    16520  2 raid6,raid5
raid0                   9856  0
dm_bbr                 14368  0
dm_snapshot            18852  0
dm_mirror              24144  0
usb_storage            83520  0
usbhid                 43040  0



I have the I2C stuff and Hardware Monitoring sections in my Kernel all 
<M>odularized.


Have I over loked anything?


Nick


-- 
Nick Ellson
CCDA, CCNP, CCSP, CCAI,
MCSE 2000, Security+, Network+
Network Hobbyist, VFR Private Pilot.

[lm-sensors] i2c-i801 on Intel Server Board se7525gp2?

[Jim Cromie]

Nick Ellson wrote:
> I am hoping to get some help understanding why lm_sensors is not finding 
> what it need on my two servers. I am trying to follow the Identifying your 
> Hardware process and this is what I get:
>
> gubbie ~ # /usr/bin/sensors -s
> Can't access procfs/sysfs file
>   

This is where things have gone wrong.
Is this a kernel you configured and built ?
You have 2 identical boxes, I guess both fail the same way ?

I have noticed the absense of /sys/* directory exactly 2x,
both times it was transient (corrected on next boot, wo any other changes)
I dont recall finding any similar reports, but also dont recall how 
thoroughly I searched.

Esp if youve built your own kernel,
you should try a few of the live-CDs out there, and see if they are able 
to create a /sys dir.

> I have the I2C stuff and Hardware Monitoring sections in my Kernel all 
> <M>odularized.
>
>
> Have I over loked anything?
>
>
> Nick
>
>
>   

[lm-sensors] i2c-i801 on Intel Server Board se7525gp2?

[Nick Ellson]

Hi Jim,

It is my own Kernel in the sense that with Gentoo the install process I 
need to pick the features that match my system. The SMP stuff and drive 
controllers, network, the basics.

I do not add any odd patches to my kernel.

And yep, I bought two systems at the same time so that they would be 
identical so I could try software on one and work out the kinks before 
messing with my E-mail/DNS box.

What I have learned is that the E7525 chipset is known to not report any 
sensors. While I would love that not to be true, I have found no evidence 
that they can be read by lm-sensors. Intel's sensor observation drivers 
are for RedHat only as far as Linux goes, so I am not sure if they will 
work under Gentoo.

I am now looking at alternative solutions. I seem to have this kind of 
luck with systems, always picking one that Linux is shut out from the nice 
features on the hardware. :\

Nick

-- 
Nick Ellson
CCDA, CCNP, CCSP, CCAI,
MCSE 2000, Security+, Network+
Network Hobbyist, VFR Private Pilot.


On Tue, 27 Jun 2006, Jim Cromie wrote:

> Nick Ellson wrote:
>>  I am hoping to get some help understanding why lm_sensors is not finding
>>  what it need on my two servers. I am trying to follow the Identifying your
>>  Hardware process and this is what I get:
>>
>>  gubbie ~ # /usr/bin/sensors -s
>>  Can't access procfs/sysfs file
>> 
>
> This is where things have gone wrong.
> Is this a kernel you configured and built ?
> You have 2 identical boxes, I guess both fail the same way ?
>
> I have noticed the absense of /sys/* directory exactly 2x,
> both times it was transient (corrected on next boot, wo any other changes)
> I dont recall finding any similar reports, but also dont recall how 
> thoroughly I searched.
>
> Esp if youve built your own kernel,
> you should try a few of the live-CDs out there, and see if they are able to 
> create a /sys dir.
>
>>  I have the I2C stuff and Hardware Monitoring sections in my Kernel all
>>  <M>odularized.
>> 
>>
>>  Have I over loked anything?
>> 
>>
>>  Nick
>> 
>>
>> 
>

[lm-sensors] i2c-i801 on Intel Server Board se7525gp2?

[Jim Cromie]

Nick Ellson wrote:
>
>
> Hi Jim,
>
> It is my own Kernel in the sense that with Gentoo the install process 
> I need to pick the features that match my system. The SMP stuff and 
> drive controllers, network, the basics.
>
> I do not add any odd patches to my kernel.
>

I was thinking more of the possible mis-*configuration* of the build,
which is less likely for a 'distro' build than yours or mine.
 From what youve said, it sounds like you selected one of the prebuilt 
kernels.

I guess Im still dwelling on whether /sys exists or not, which you didnt 
respond to.
If /sys isnt there, for whatever reason, no sensors will work, no matter 
the chip.

That said, it might not matter, given what youve found about the chip.

What, if anything, does the BIOS tell you about sensors, etc.
What does the kernels ACPI tell you ?
Given that Intel was one of 2 or 3 players in ACPI development,
it would be worth a look into /proc/acpi/*

> And yep, I bought two systems at the same time so that they would be 
> identical so I could try software on one and work out the kinks before 
> messing with my E-mail/DNS box.
>
> What I have learned is that the E7525 chipset is known to not report 
> any sensors. While I would love that not to be true, I have found no 
> evidence that they can be read by lm-sensors. Intel's sensor 
> observation drivers are for RedHat only as far as Linux goes, so I am 
> not sure if they will work under Gentoo.
>
'Redhat *only*'  is more likely to be a 'certification' issue than a 
'just wont run' problem.

> I am now looking at alternative solutions. I seem to have this kind of 
> luck with systems, always picking one that Linux is shut out from the 
> nice features on the hardware. :\
>
> Nick
>

[lm-sensors] i2c-i801 on Intel Server Board se7525gp2?

[Nick Ellson]

Sorry about that Jim, I had intended on pasting this in.

gubbie ~ # ls /sys
block  bus  class  devices  firmware  fs  kernel  module  power
gubbie ~ # ls /sys/bus
ac97  i2c  ide  pci  pci_express  platform  pnp  scsi  serio  spi  usb
gubbie ~ # ls /sys/bus/i2c
devices  drivers
gubbie ~ # ls /sys/bus/i2c/drivers
dev_driver  eeprom  i2c_adapter
gubbie ~ # ls /sys/bus/i2c/devices
0-0051  0-0055
gubbie ~ #


And on acpi (not sure how to use this but here is a peek at my tree)

gubbie ~ # ls /proc/acpi
ac_adapter  battery  button  dsdt  embedded_controller  event  fadt  fan 
info  power_resource  processor  thermal_zone  video
gubbie ~ # ls /proc/acpi/processor/
CPU1  CPU2  CPU3  CPU4
gubbie ~ # ls /proc/acpi/processor/CPU1
info  limit  power  throttling
gubbie ~ # ls /proc/acpi/processor/CPU1/info
/proc/acpi/processor/CPU1/info
gubbie ~ # cat /proc/acpi/processor/CPU1/info
processor id:            0
acpi id:                 1
bus mastering control:   no
power management:        no
throttling control:      yes
limit interface:         yes
gubbie ~ # ls /proc/acpi/thermal_zone/
gubbie ~ # ls /proc/acpi/info
/proc/acpi/info
gubbie ~ # cat /proc/acpi/info
version:                 20060127
gubbie ~ #


-- 
Nick Ellson
CCDA, CCNP, CCSP, CCAI,
MCSE 2000, Security+, Network+
Network Hobbyist, VFR Private Pilot.


On Tue, 27 Jun 2006, Jim Cromie wrote:

> Nick Ellson wrote:
>> 
>>
>>  Hi Jim,
>>
>>  It is my own Kernel in the sense that with Gentoo the install process I
>>  need to pick the features that match my system. The SMP stuff and drive
>>  controllers, network, the basics.
>>
>>  I do not add any odd patches to my kernel.
>> 
>
> I was thinking more of the possible mis-*configuration* of the build,
> which is less likely for a 'distro' build than yours or mine.
> From what youve said, it sounds like you selected one of the prebuilt 
> kernels.
>
> I guess Im still dwelling on whether /sys exists or not, which you didnt 
> respond to.
> If /sys isnt there, for whatever reason, no sensors will work, no matter the 
> chip.
>
> That said, it might not matter, given what youve found about the chip.
>
> What, if anything, does the BIOS tell you about sensors, etc.
> What does the kernels ACPI tell you ?
> Given that Intel was one of 2 or 3 players in ACPI development,
> it would be worth a look into /proc/acpi/*
>
>>  And yep, I bought two systems at the same time so that they would be
>>  identical so I could try software on one and work out the kinks before
>>  messing with my E-mail/DNS box.
>>
>>  What I have learned is that the E7525 chipset is known to not report any
>>  sensors. While I would love that not to be true, I have found no evidence
>>  that they can be read by lm-sensors. Intel's sensor observation drivers
>>  are for RedHat only as far as Linux goes, so I am not sure if they will
>>  work under Gentoo.
>> 
> 'Redhat *only*'  is more likely to be a 'certification' issue than a 'just 
> wont run' problem.
>
>>  I am now looking at alternative solutions. I seem to have this kind of
>>  luck with systems, always picking one that Linux is shut out from the nice
>>  features on the hardware. :\
>>
>>  Nick
>> 
>
>

[lm-sensors] i2c-i801 on Intel Server Board se7525gp2?

[Nick Ellson]

I have dug a bit longer and talked a bit with Intel. The SE7525GP2 uses a 
National PC87431M Baseboard Management Controller

A thread I found give me some hope for lm-sensors

http://lists.lm-sensors.org/pipermail/lm-sensors/2005-June/012847.html

I am going to see if I can try to put this all together and get something 
working.. If anyone that knows this stuff (from an lm-sensors point of 
view) can lend a hand, I would appreciate it. I am getting close!

Nick

-- 
Nick Ellson
CCDA, CCNP, CCSP, CCAI,
MCSE 2000, Security+, Network+
Network Hobbyist, VFR Private Pilot.