Intel D845GEBV2 with lm85: config is locked

Intel D845GEBV2 with lm85: config is locked

[Dimitri Puzin]

Hello,

I've got an Intel mainboard D845GEBV2 as replacement for my Asus P4B-266SE
(that ASB100 mess). I've mounted it, gone through the configs and
sensors-detect said I should use the lm85 driver. With lm85 it seem to work
well, except I cannot change anything in the proc interface. The values
reported seem correct but all changes (e.g. echoing values to the pwm#
registers) are ignored... As far as I can see from the BIOS, that board has
settings for fan control and speed. I guess that the BIOS initializes the
sensors during POST but as far as I could see, there was no change to the
problem even I deactivate the settings from the BIOS. I've took a look at
the board and found following devices I could think of being attached to the
bus: LM 85 BIMQ, ICS 950227 AF, FW 82801 DB, PC 87382 IBU/VLA and the eeprom
from the RAM. Intel claims there is an SMSC LPC47M172 on board. Here is the
output of what I could get from my system.

Output of syslog
-----------------------
Oct  1 20:33:18 elexis kernel: i2c-core.o: i2c core module version 2.8.0
(20030714)
Oct  1 20:33:18 elexis kernel: i2c-proc.o version 2.8.0 (20030714)
Oct  1 20:33:26 elexis kernel: i2c-dev.o: i2c /dev entries driver module
version 2.8.0 (20030714)
Oct  1 20:33:38 elexis kernel: i2c-i801 version 2.8.0 (20030714)
Oct  1 20:33:38 elexis kernel: i2c-dev.o: Registered 'SMBus I801 adapter at
e000' as minor 0
Oct  1 20:34:24 elexis kernel: lm85: Version 2.8.0 (20030714)
Oct  1 20:34:24 elexis kernel: lm85: See
http://www.penguincomputing.com/lm_sensors for more info.
Oct  1 20:34:24 elexis kernel: lm85: Assigning ID 0 to National LM85-B at
0,0x2e
Oct  1 20:34:24 elexis kernel: lm85(0): Client (0,0x2e) config is locked.

Output from sensors-detect
---------------------------
elexis:~# sensors-detect
Use driver `i2c-i801' for device 00:1f.3: Intel 82801DB ICH4

Driver `lm85' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at e000' (Non-I2C SMBus adapter)
    Busdriver `i2c-i801', I2C address 0x2e
    Chip `National Semiconductor LM85' (confidence: 7)

Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at e000' (Non-I2C SMBus adapter)
    Busdriver `i2c-i801', I2C address 0x50
    Chip `Serial EEPROM' (confidence: 8)

elexis:~# i2cdetect 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: XX XX XX XX XX XX XX XX 08 XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX 2e XX
30: 30 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX 44 XX XX XX XX XX XX XX XX XX XX XX
50: 50 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX

elexis:~# i2cdump 0 0x2e
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
20: 76 94 c0 c5 c2 1f 20 1f a7 06 ff ff 73 12 33 11    v????? ???..s?3?
30: ff ff 4d 00 00 00 00 00 00 00 00 00 00 00 01 62    ..M...........?b
40: 07 8b 01 04 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f    ????..........??
50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 42 c4    ????........bbB?
60: c4 c4 e0 00 80 80 4d 5a 5a 25 64 64 2f 44 40 00    ???.??MZZ%dd/D@.
70: 1f 20 1f 32 00 07 00 00 00 00 00 40 28 31 6c 57    ? ?2.?.....@(1lW
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
elexis:~# i2cdump 0 0x44
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 0f 04 00 00 00 00 00 00 00 00 00 00 00 00    ..??............
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
elexis:~# i2cdump 0 0x50
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 80 08 07 0d 0a 01 40 00 04 75 75 00 82 08 00 01    ??????@.?uu.??.?
10: 0e 04 0c 01 02 20 00 a0 75 00 00 50 3c 50 2d 40    ????? .?u..P<P-@
20: 90 90 50 50 00 00 00 00 00 00 00 00 00 00 00 00    ??PP............
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bf    ...............?
40: ce 00 00 00 00 00 00 00 01 4d 33 20 36 38 4c 33    ?.......?M3 68L3
50: 32 32 33 44 54 4c 2d 43 42 30 20 4c 44 02 32 f2    223DTL-CB0 LD?2?
60: 03 f5 de 00 43 42 42 30 45 30 35 00 00 00 00 00    ???.CBB0E05.....
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
elexis:~# i2cdump 0 0x69
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
10: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
20: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
30: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
40: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
50: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
60: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
70: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
80: d9 87 7e c5 3f 00 ff 01 0f 0a 80 8d 9b fe 17 44    ??~??..????????D
90: 95 09 04 03 40 aa aa 20 00 00 00 00 00 d3 XX XX    ????@?? .....?XX

I had to do a cold reset after the use of i2cdetect/dump. I tried to exclude
all except 0x2e but without success.
Do you have an idea how to solve that problem?

Regards,
-Dimitri

PS: sorry if I sent it multiple - my posts didn't appear on the list.

Intel D845GEBV2 with lm85: config is locked

[Philip Pokorny]

The LM85 driver is telling you that the BIOS has locked the config. 
When the LM85 config is locked, you can't change any of the pwm settings 
or limits.

 > lm85: Assigning ID 0 to National LM85-B at 0,0x2e
 > lm85(0): Client (0,0x2e) config is locked.

You can clear the lock by completely resetting the chip, but then you 
loose whatever limits may have been set and any pin configuration 
options that have been programmed.

We have seen that Intel motherboards implement SMBUS interrupts.  That 
means that if an ALARM is generated by an i2c device, the BIOS can  (and 
will) shutdown your system.  Resetting the chip might trigger the BIOS 
to shutdown your system.

Does the BIOS allow you to control the automatic fan speed control 
features of the lm85?  If so, I would recommend that you set the values 
there and then use lm_sensors to view the values.

If you're interested in working on the driver, you could implement some 
code to reset the chip and then reprogram the configuration to match the 
Intel BIOS setup without locking the config.  Then you would be able to 
change the PWM values.  You can set the limits from user space using 
'sensors -s'  If it doesn't shut your system down, then you've got what 
you want.



Dimitri Puzin wrote:
> Hello,
> 
> I've got an Intel mainboard D845GEBV2 as replacement for my Asus P4B-266SE
> (that ASB100 mess). I've mounted it, gone through the configs and
> sensors-detect said I should use the lm85 driver. With lm85 it seem to work
> well, except I cannot change anything in the proc interface. The values
> reported seem correct but all changes (e.g. echoing values to the pwm#
> registers) are ignored... As far as I can see from the BIOS, that board has
> settings for fan control and speed. I guess that the BIOS initializes the
> sensors during POST but as far as I could see, there was no change to the
> problem even I deactivate the settings from the BIOS. I've took a look at
> the board and found following devices I could think of being attached to the
> bus: LM 85 BIMQ, ICS 950227 AF, FW 82801 DB, PC 87382 IBU/VLA and the eeprom
> from the RAM. Intel claims there is an SMSC LPC47M172 on board. Here is the
> output of what I could get from my system.
> 
> Output of syslog
> -----------------------
> Oct  1 20:33:18 elexis kernel: i2c-core.o: i2c core module version 2.8.0
> (20030714)
> Oct  1 20:33:18 elexis kernel: i2c-proc.o version 2.8.0 (20030714)
> Oct  1 20:33:26 elexis kernel: i2c-dev.o: i2c /dev entries driver module
> version 2.8.0 (20030714)
> Oct  1 20:33:38 elexis kernel: i2c-i801 version 2.8.0 (20030714)
> Oct  1 20:33:38 elexis kernel: i2c-dev.o: Registered 'SMBus I801 adapter at
> e000' as minor 0
> Oct  1 20:34:24 elexis kernel: lm85: Version 2.8.0 (20030714)
> Oct  1 20:34:24 elexis kernel: lm85: See
> http://www.penguincomputing.com/lm_sensors for more info.
> Oct  1 20:34:24 elexis kernel: lm85: Assigning ID 0 to National LM85-B at
> 0,0x2e
> Oct  1 20:34:24 elexis kernel: lm85(0): Client (0,0x2e) config is locked.




-- 
Philip Pokorny, Director of Engineering
Tel: 415-358-2635   Fax: 415-358-2646   Toll Free: 888-PENGUIN
PENGUIN COMPUTING, INC.
www.penguincomputing.com

Intel D845GEBV2 with lm85: config is locked

[Jean Delvare]

> I've got an Intel mainboard D845GEBV2 as replacement for my Asus
> P4B-266SE(that ASB100 mess). I've mounted it, gone through the configs
> and sensors-detect said I should use the lm85 driver. With lm85 it
> seem to work well, except I cannot change anything in the proc
> interface. The values reported seem correct but all changes (e.g.
> echoing values to the pwm# registers) are ignored...

This is a feature of the LM85. I remember I read that some times ago.
(reading again) Yes, here it is. Bit 1 of register 0x40 is lock. Once
set to 1, all limits are read only, and that bit itself becomes read
only. And yes, that bit it set to 1 on your chip. Blame your motherboard
manifacturer for that (I guess).

> Intel claims there is an SMSC LPC47M172 on board.

We don't have support for this one yet, but support some members of the
family in the smsc47m1 driver. Maybe you could give it a try (using CVS
version is recommended). They are ISA chips so they don't appear on the
I2C bus.

> Output of syslog
> -----------------------
> Oct  1 20:34:24 elexis kernel: lm85(0): Client (0,0x2e) config is
> locked.

See, that's what I said.

> elexis:~# i2cdetect 0
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: XX XX XX XX XX XX XX XX 08 XX XX XX XX XX XX XX
> 10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX 2e XX
> 30: 30 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 40: XX XX XX XX 44 XX XX XX XX XX XX XX XX XX XX XX
> 50: 50 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX
> 70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX

You did not dump address 0x08. Maybe there's something interesting
there? (Although I admit we don't know any chip living there yet).

> I had to do a cold reset after the use of i2cdetect/dump.

Yes, that happends, especially after dumping address 0x69 which is a
clock chip you should avoid playing with.

> Do you have an idea how to solve that problem?

I am afraid you can't do anything :(

> PS: sorry if I sent it multiple - my posts didn't appear on the list.

Got only one, so it's OK :)

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

Intel D845GEBV2 with lm85: config is locked

[Dimitri Puzin]

Hello, thanks much for your reply.
I've read through the data sheet for the lm85, also found the settings about
locking at 0x40h. That's sad...I'll try to ask at Intel if they know of a
hack to
disable that feature in the BIOS and use custom settings. Maybe experiment
more with the BIOS settings. If I  get an answer I'd also
(try) to volunteer and extend the code to support that. About the addr 0x08:
there is nothing useful there. The output is consists of a large array of
"XX".

Regards,
-Dimitri

PS: I believe there is a typo in the doc for the lm85. In the original
datasheet
they suggest to use LM85-B for new designs, not the -C rev (on page 2
bottom I have the datasheet from
http://www.national.com/ds/LM/LM85.pdf)

----- Original Message ----- 
From: "Jean Delvare" <khali@linux-fr.org>
To: "Dimitri Puzin" <tristan-777@t-online.de>
Cc: <sensors@stimpy.netroedge.com>
Sent: Thursday, October 02, 2003 10:49 PM
Subject: Re: Intel D845GEBV2 with lm85: config is locked


>
> > I've got an Intel mainboard D845GEBV2 as replacement for my Asus
> > P4B-266SE(that ASB100 mess). I've mounted it, gone through the configs
> > and sensors-detect said I should use the lm85 driver. With lm85 it
> > seem to work well, except I cannot change anything in the proc
> > interface. The values reported seem correct but all changes (e.g.
> > echoing values to the pwm# registers) are ignored...
>
> This is a feature of the LM85. I remember I read that some times ago.
> (reading again) Yes, here it is. Bit 1 of register 0x40 is lock. Once
> set to 1, all limits are read only, and that bit itself becomes read
> only. And yes, that bit it set to 1 on your chip. Blame your motherboard
> manifacturer for that (I guess).
>
> > Intel claims there is an SMSC LPC47M172 on board.
>
> We don't have support for this one yet, but support some members of the
> family in the smsc47m1 driver. Maybe you could give it a try (using CVS
> version is recommended). They are ISA chips so they don't appear on the
> I2C bus.
>
> > Output of syslog
> > -----------------------
> > Oct  1 20:34:24 elexis kernel: lm85(0): Client (0,0x2e) config is
> > locked.
>
> See, that's what I said.
>
> > elexis:~# i2cdetect 0
> >      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> > 00: XX XX XX XX XX XX XX XX 08 XX XX XX XX XX XX XX
> > 10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> > 20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX 2e XX
> > 30: 30 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> > 40: XX XX XX XX 44 XX XX XX XX XX XX XX XX XX XX XX
> > 50: 50 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> > 60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX
> > 70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
>
> You did not dump address 0x08. Maybe there's something interesting
> there? (Although I admit we don't know any chip living there yet).
>
> > I had to do a cold reset after the use of i2cdetect/dump.
>
> Yes, that happends, especially after dumping address 0x69 which is a
> clock chip you should avoid playing with.
>
> > Do you have an idea how to solve that problem?
>
> I am afraid you can't do anything :(
>
> > PS: sorry if I sent it multiple - my posts didn't appear on the list.
>
> Got only one, so it's OK :)
>
> -- 
> Jean Delvare
> http://www.ensicaen.ismra.fr/~delvare/
>
>

Intel D845GEBV2 with lm85: config is locked

[Philip Pokorny]

I think one of the other bits in LM85_REG_CONFIG is the reset bit.  If 
set, the chip resets to it's power-on defaults and clears the LOCK bit.

I don't have my documentation handy right now so I can't tell you for 
sure which bit it is.  I suppose I should have created #defines for each 
of the bits in REG_CONFIG.  Oops...

:v)

Dimitri Puzin wrote:
> Hello,
> 
> thank you for the fast reply. I have read the source code and also
> the docs for the chip. Unfortunately I couldn't find a reset function
> on the lm85 chip. National mentioned that only power-cycling
> can clear the locks set :(. It looks like the BIOS initialize the chip
> during the POST. I tried to play with the settings in the BIOS but
> even disabling the fan control function completely didn't prevent
> the LOCK bit at 0x40 being set. I'm not a great specialist, maybe
> you know of another way? a function the i2c-i801 or a register which
> must be set in the bridge? I tried the original tool which is suggested
> by Intel but they also don't allow the setting. Only the alarm
> levels for voltage (max/min) and the thresholds for zones can be
> adjusted. If there is any way to make it work I would add the needed
> code to the sources.
> 
> I think this fact about a possible lock on the chip
> should be added to the docs of lm85 driver. In the source I read
> that the init function checks for the setting but it's not mentioned
> in the docs.
> 
> ----- Original Message ----- 
> From: "Philip Pokorny" <ppokorny@penguincomputing.com>
> To: "Dimitri Puzin" <tristan-777@t-online.de>
> Cc: <lm78@Stimpy.netroedge.com>
> Sent: Thursday, October 02, 2003 9:56 PM
> Subject: Re: Intel D845GEBV2 with lm85: config is locked
> 
> 
> 
>>The LM85 driver is telling you that the BIOS has locked the config.
>>When the LM85 config is locked, you can't change any of the pwm settings
>>or limits.
>>
>> > lm85: Assigning ID 0 to National LM85-B at 0,0x2e
>> > lm85(0): Client (0,0x2e) config is locked.
>>
>>You can clear the lock by completely resetting the chip, but then you
>>loose whatever limits may have been set and any pin configuration
>>options that have been programmed.
>>
>>We have seen that Intel motherboards implement SMBUS interrupts.  That
>>means that if an ALARM is generated by an i2c device, the BIOS can  (and
>>will) shutdown your system.  Resetting the chip might trigger the BIOS
>>to shutdown your system.
>>
>>Does the BIOS allow you to control the automatic fan speed control
>>features of the lm85?  If so, I would recommend that you set the values
>>there and then use lm_sensors to view the values.
>>
>>If you're interested in working on the driver, you could implement some
>>code to reset the chip and then reprogram the configuration to match the
>>Intel BIOS setup without locking the config.  Then you would be able to
>>change the PWM values.  You can set the limits from user space using
>>'sensors -s'  If it doesn't shut your system down, then you've got what
>>you want.
>>
>>
>>
>>Dimitri Puzin wrote:
>>
>>>Hello,
>>>
>>>I've got an Intel mainboard D845GEBV2 as replacement for my Asus
>>
> P4B-266SE
> 
>>>(that ASB100 mess). I've mounted it, gone through the configs and
>>>sensors-detect said I should use the lm85 driver. With lm85 it seem to
>>
> work
> 
>>>well, except I cannot change anything in the proc interface. The values
>>>reported seem correct but all changes (e.g. echoing values to the pwm#
>>>registers) are ignored... As far as I can see from the BIOS, that board
>>
> has
> 
>>>settings for fan control and speed. I guess that the BIOS initializes
>>
> the
> 
>>>sensors during POST but as far as I could see, there was no change to
>>
> the
> 
>>>problem even I deactivate the settings from the BIOS. I've took a look
>>
> at
> 
>>>the board and found following devices I could think of being attached to
>>
> the
> 
>>>bus: LM 85 BIMQ, ICS 950227 AF, FW 82801 DB, PC 87382 IBU/VLA and the
>>
> eeprom
> 
>>>from the RAM. Intel claims there is an SMSC LPC47M172 on board. Here is
>>
> the
> 
>>>output of what I could get from my system.
>>>
>>>Output of syslog
>>>-----------------------
>>>Oct  1 20:33:18 elexis kernel: i2c-core.o: i2c core module version 2.8.0
>>>(20030714)
>>>Oct  1 20:33:18 elexis kernel: i2c-proc.o version 2.8.0 (20030714)
>>>Oct  1 20:33:26 elexis kernel: i2c-dev.o: i2c /dev entries driver module
>>>version 2.8.0 (20030714)
>>>Oct  1 20:33:38 elexis kernel: i2c-i801 version 2.8.0 (20030714)
>>>Oct  1 20:33:38 elexis kernel: i2c-dev.o: Registered 'SMBus I801 adapter
>>
> at
> 
>>>e000' as minor 0
>>>Oct  1 20:34:24 elexis kernel: lm85: Version 2.8.0 (20030714)
>>>Oct  1 20:34:24 elexis kernel: lm85: See
>>>http://www.penguincomputing.com/lm_sensors for more info.
>>>Oct  1 20:34:24 elexis kernel: lm85: Assigning ID 0 to National LM85-B
>>
> at
> 
>>>0,0x2e
>>>Oct  1 20:34:24 elexis kernel: lm85(0): Client (0,0x2e) config is
>>
> locked.
> 
>>
>>
>>
>>-- 
>>Philip Pokorny, Director of Engineering
>>Tel: 415-358-2635   Fax: 415-358-2646   Toll Free: 888-PENGUIN
>>PENGUIN COMPUTING, INC.
>>www.penguincomputing.com
>>
>>
> 
> 
> 



-- 
Philip Pokorny, Director of Engineering
Tel: 415-358-2635   Fax: 415-358-2646   Toll Free: 888-PENGUIN
PENGUIN COMPUTING, INC.
www.penguincomputing.com

Intel D845GEBV2 with lm85: config is locked

[Philip Pokorny]

By the way, I wrote the lm85 driver...

I must have this confused with one of the other chips I've written 
drivers for.  You're right it doesn't look like there is a way to reset 
the chip.

Here's a patch to fix the documentation regarding recommended version...

Index: lm_sensors2/doc/chips/lm85
=================================RCS file: /home/cvs/lm_sensors2/doc/chips/lm85,v
retrieving revision 1.2
diff -u -r1.2 lm85
--- lm_sensors2/doc/chips/lm85  31 May 2003 00:24:07 -0000      1.2
+++ lm_sensors2/doc/chips/lm85  4 Oct 2003 06:15:32 -0000
@@ -168,7 +168,7 @@
 The lm85 driver detects both LM85B and LM85C revisions of the chip.
 See the datasheet for a complete description of the differences.
 Other than identifying the chip, the driver behaves no differently
-with regard to these two chips.  The LM85C is recommended for new
+with regard to these two chips.  The LM85B is recommended for new
 designs.
 
 The ADM1027 and ADT7463 chips have an optional SMBALERT output that


Dimitri Puzin wrote:

>Hi,
>
>I've gone through the datasheet. There seem to be no "undo" function
>after setting the LOCK bit at 0x40h. There would be a possibility to
>have a working state if intel wouldn't set that LOCK bit at 0x40h
>during POST. The settings in the BIOS have only influence on the
>config written into the chip before locking. Even disabling the fan
>control feature in the BIOS doesn't change this behavior.
>
>According to the data the other bits at the register 0x40h are without
>an assigned function.
>
>I had a look at the lm85.c. The lm85 itself doesn't have other bits
>set/defined. In the init function there is a code part which initializes
>the chip (setting the START bit).
>
>I have the datasheet from http://www.national.com/ds/LM/LM85.pdf
>
>I had setup another OS on that board, but neither Intel's own tool
>(Active monitor) or a third-party tool (Fanspeed, MBM5) did allow
>me any settings.
>
>I'd talk to intel, maybe they will change their BIOS and stop the
>setup of the chip after setting the START bit at 0x40h. At least in
>conjunction with the [DISABLED] setting in the BIOS. I think
>there is too much setup - they should allow other tools to set
>user-defined limits, at least when the intel's setup is in disabled
>state.
>
>
>  
>
>>I think one of the other bits in LM85_REG_CONFIG is the reset bit.  If
>>set, the chip resets to it's power-on defaults and clears the LOCK bit.
>>
>>I don't have my documentation handy right now so I can't tell you for
>>sure which bit it is.  I suppose I should have created #defines for each
>>of the bits in REG_CONFIG.  Oops...
>>
>>:v)
>>
>>Dimitri Puzin wrote:
>>    
>>
>>>Hello,
>>>
>>>thank you for the fast reply. I have read the source code and also
>>>the docs for the chip. Unfortunately I couldn't find a reset function
>>>on the lm85 chip. National mentioned that only power-cycling
>>>can clear the locks set :(. It looks like the BIOS initialize the chip
>>>during the POST. I tried to play with the settings in the BIOS but
>>>even disabling the fan control function completely didn't prevent
>>>the LOCK bit at 0x40 being set. I'm not a great specialist, maybe
>>>you know of another way? a function the i2c-i801 or a register which
>>>must be set in the bridge? I tried the original tool which is suggested
>>>by Intel but they also don't allow the setting. Only the alarm
>>>levels for voltage (max/min) and the thresholds for zones can be
>>>adjusted. If there is any way to make it work I would add the needed
>>>code to the sources.
>>>
>>>I think this fact about a possible lock on the chip
>>>should be added to the docs of lm85 driver. In the source I read
>>>that the init function checks for the setting but it's not mentioned
>>>in the docs.
>>>
>>>----- Original Message ----- 
>>>From: "Philip Pokorny" <ppokorny@penguincomputing.com>
>>>To: "Dimitri Puzin" <tristan-777@t-online.de>
>>>Cc: <lm78@Stimpy.netroedge.com>
>>>Sent: Thursday, October 02, 2003 9:56 PM
>>>Subject: Re: Intel D845GEBV2 with lm85: config is locked
>>>
>>>
>>>
>>>      
>>>
>>>>The LM85 driver is telling you that the BIOS has locked the config.
>>>>When the LM85 config is locked, you can't change any of the pwm settings
>>>>or limits.
>>>>
>>>>        
>>>>
>>>>>lm85: Assigning ID 0 to National LM85-B at 0,0x2e
>>>>>lm85(0): Client (0,0x2e) config is locked.
>>>>>          
>>>>>
>>>>You can clear the lock by completely resetting the chip, but then you
>>>>loose whatever limits may have been set and any pin configuration
>>>>options that have been programmed.
>>>>
>>>>We have seen that Intel motherboards implement SMBUS interrupts.  That
>>>>means that if an ALARM is generated by an i2c device, the BIOS can  (and
>>>>will) shutdown your system.  Resetting the chip might trigger the BIOS
>>>>to shutdown your system.
>>>>
>>>>Does the BIOS allow you to control the automatic fan speed control
>>>>features of the lm85?  If so, I would recommend that you set the values
>>>>there and then use lm_sensors to view the values.
>>>>
>>>>If you're interested in working on the driver, you could implement some
>>>>code to reset the chip and then reprogram the configuration to match the
>>>>Intel BIOS setup without locking the config.  Then you would be able to
>>>>change the PWM values.  You can set the limits from user space using
>>>>'sensors -s'  If it doesn't shut your system down, then you've got what
>>>>you want.
>>>>
>>>>
>>>>
>>>>Dimitri Puzin wrote:
>>>>
>>>>        
>>>>
>>>>>Hello,
>>>>>
>>>>>I've got an Intel mainboard D845GEBV2 as replacement for my Asus
>>>>>          
>>>>>
>>>P4B-266SE
>>>
>>>      
>>>
>>>>>(that ASB100 mess). I've mounted it, gone through the configs and
>>>>>sensors-detect said I should use the lm85 driver. With lm85 it seem to
>>>>>          
>>>>>
>>>work
>>>
>>>      
>>>
>>>>>well, except I cannot change anything in the proc interface. The values
>>>>>reported seem correct but all changes (e.g. echoing values to the pwm#
>>>>>registers) are ignored... As far as I can see from the BIOS, that board
>>>>>          
>>>>>
>>>has
>>>
>>>      
>>>
>>>>>settings for fan control and speed. I guess that the BIOS initializes
>>>>>          
>>>>>
>>>the
>>>
>>>      
>>>
>>>>>sensors during POST but as far as I could see, there was no change to
>>>>>          
>>>>>
>>>the
>>>
>>>      
>>>
>>>>>problem even I deactivate the settings from the BIOS. I've took a look
>>>>>          
>>>>>
>>>at
>>>
>>>      
>>>
>>>>>the board and found following devices I could think of being attached
>>>>>          
>>>>>
>to
>  
>
>>>the
>>>
>>>      
>>>
>>>>>bus: LM 85 BIMQ, ICS 950227 AF, FW 82801 DB, PC 87382 IBU/VLA and the
>>>>>          
>>>>>
>>>eeprom
>>>
>>>      
>>>
>>>>>from the RAM. Intel claims there is an SMSC LPC47M172 on board. Here is
>>>>
>>>>        
>>>>
>>>the
>>>
>>>      
>>>
>>>>>output of what I could get from my system.
>>>>>
>>>>>Output of syslog
>>>>>-----------------------
>>>>>Oct  1 20:33:18 elexis kernel: i2c-core.o: i2c core module version
>>>>>          
>>>>>
>2.8.0
>  
>
>>>>>(20030714)
>>>>>Oct  1 20:33:18 elexis kernel: i2c-proc.o version 2.8.0 (20030714)
>>>>>Oct  1 20:33:26 elexis kernel: i2c-dev.o: i2c /dev entries driver
>>>>>          
>>>>>
>module
>  
>
>>>>>version 2.8.0 (20030714)
>>>>>Oct  1 20:33:38 elexis kernel: i2c-i801 version 2.8.0 (20030714)
>>>>>Oct  1 20:33:38 elexis kernel: i2c-dev.o: Registered 'SMBus I801
>>>>>          
>>>>>
>adapter
>  
>
>>>at
>>>
>>>      
>>>
>>>>>e000' as minor 0
>>>>>Oct  1 20:34:24 elexis kernel: lm85: Version 2.8.0 (20030714)
>>>>>Oct  1 20:34:24 elexis kernel: lm85: See
>>>>>http://www.penguincomputing.com/lm_sensors for more info.
>>>>>Oct  1 20:34:24 elexis kernel: lm85: Assigning ID 0 to National LM85-B
>>>>>          
>>>>>
>>>at
>>>
>>>      
>>>
>>>>>0,0x2e
>>>>>Oct  1 20:34:24 elexis kernel: lm85(0): Client (0,0x2e) config is
>>>>>          
>>>>>
>>>locked.
>>>
>>>      
>>>

Intel D845GEBV2 with lm85: config is locked

[Jean Delvare]

> Here's a patch to fix the documentation regarding recommended
> version...

Thanks, commited.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/