fan2 readout on Chaintech MB

fan2 readout on Chaintech MB

[Ljubomir Bozic Jr.]

Hello!

I have just installed i2c and lm_sensors from CVS because I thought that it 
might solve thr fan2 problem. I get only fan1 readout and not fan2, fan2 is 0 
and should be around 2300. BIOS shows fan1 and fan2 reading.

Fan2 readout is trough:
it87-isa-0290
Adapter: ISA adapter

Motherboard is:
CHAINTECH 7VJL Apogee DeLuxe 
Chipset: VIA KT400

Would you be so kind and check it out if it might be a bug or maybe it is a 
mobo issue.

Thanks!

Best regards, Ljubomir Bozic

P.S. lm90 sensor is working great, readings are accurate:-)

fan2 readout on Chaintech MB

[Jean Delvare]

> I have just installed i2c and lm_sensors from CVS because I thought
> that it might solve thr fan2 problem. I get only fan1 readout and not
> fan2, fan2 is 0 and should be around 2300. BIOS shows fan1 and fan2
> reading.
> 
> Fan2 readout is trough:
> it87-isa-0290
> Adapter: ISA adapter
> 
> Motherboard is:
> CHAINTECH 7VJL Apogee DeLuxe 
> Chipset: VIA KT400
> 
> Would you be so kind and check it out if it might be a bug or maybe it
> is a mobo issue.

It's a FAQ. You need to increase fan2_div (typically from 2 to 4) in
/etc/sensors.conf (it87-* section) and run "sensors -s" again, possibly
twice. Then "sensors" should report the correct reading. If not, try
increasing even more (8...).

> P.S. lm90 sensor is working great, readings are accurate:-)

Aha, you're using my driver. Great :) I had no feedback for it yet.
Could you please provide a sample sensors output, so that I can see how
it does look? Also, I'd be great if you could verify that limit
checkings are OK (simply set the limits in a way you know the readings
will be outside of them, and see is sensors reports alarms correctly.)
Thanks! If you find anything that would need fixing/tweaking in my
driver, please let me know and I'll take a look.

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

fan2 readout on Chaintech MB

[Ljubomir Bozic Jr.]

> It's a FAQ. You need to increase fan2_div (typically from 2 to 4) in
> /etc/sensors.conf (it87-* section) and run "sensors -s" again, possibly
> twice. Then "sensors" should report the correct reading. If not, try
> increasing even more (8...).
>

It works now! Thanks! Please forgive me , I did not read FAQ carefully.


> Aha, you're using my driver. Great :) I had no feedback for it yet.
> Could you please provide a sample sensors output, so that I can see how
> it does look? Also, I'd be great if you could verify that limit
> checkings are OK (simply set the limits in a way you know the readings
> will be outside of them, and see is sensors reports alarms correctly.)
> Thanks! If you find anything that would need fixing/tweaking in my
> driver, please let me know and I'll take a look.

I would like to test it a little bit further but it seems that I have some 
problems with my motherboard. It does not refresh sensor. I have tried it 
both in windows and Linux but same thing happens. I dont think that both MBM 
in windows and lm_sensors have same problems so it is motrerboard issue.
I will try to fix it somehow and then I will do some lm90 testing and give you 
all the feedback I can.

Thank you very much for your help.

Best regards, Ljubo

fan2 readout on Chaintech MB

[Jean Delvare]

> > Aha, you're using my driver. Great :) I had no feedback for it yet.
> > Could you please provide a sample sensors output, so that I can see
> > how it does look? Also, I'd be great if you could verify that limit
> > checkings are OK (simply set the limits in a way you know the
> > readings will be outside of them, and see is sensors reports alarms
> > correctly.) Thanks! If you find anything that would need
> > fixing/tweaking in my driver, please let me know and I'll take a
> > look.
> 
> I would like to test it a little bit further but it seems that I have
> some problems with my motherboard. It does not refresh sensor. I have
> tried it both in windows and Linux but same thing happens. I dont
> think that both MBM in windows and lm_sensors have same problems so it
> is motrerboard issue. I will try to fix it somehow and then I will do
> some lm90 testing and give you all the feedback I can.

Could be because both MBM and our code think its is a LM90 while it is
something else. If you can provide the output of "i2cdump 0 0x4c", I
could see if that's what's happening or not.

> Thank you very much for your help.

You're welcome.

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

fan2 readout on Chaintech MB

[Ljubomir Bozic Jr.]

> Could be because both MBM and our code think its is a LM90 while it is
> something else. If you can provide the output of "i2cdump 0 0x4c", I
> could see if that's what's happening or not.
>
I'm sending you output in attachment. I have also tried it87 sensors but I'm 
getting weird values, and I have also tried various temp_type values but I 
could not find the right value to get "normal" results, I will try it again 
and every combination.

I will see if my friend, that has EPOX nForce2 motherboard, has lm90 so that 
he can do some testing for you.

Thank you very, very much for your help. I have been thinking to RMA my board 
but now I will wait to see your results.

Best regards, Ljubo
-------------- next part --------------
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 22 2e 00 40 05 46 05 46 05 00 00 00 00 00 00 00    "..@?F?F?.......
10: 60 00 00 00 00 00 00 00 00 55 00 00 00 00 00 00    `........U......
20: 55 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00    U?..............
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: 66 20 43 b4 ad 00 05 00 00 4b 4b 00 00 00 00 00    f C??.?..KK.....
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 01 21    ..............?!

fan2 readout on Chaintech MB

[Ljubomir Bozic Jr.]

> My driver init code explicitely *stops* the chipset. No wonder you don't
> see the values changing... Stupid me. That's fixed in CVS, if you were
> kind enough to give it a try and tell me if it now works OK for you.
>

lm90 is working now:-))

Unfortunately I have new problems.
I cant execute sensors -s, I'm getting this:

[root@localhost etc]# sensors -s
it87-isa-0290: Can't access /proc file for writing;
Run as root?

I've never had problems with sensors -s before.

and the other possible problem is this:
sensors-detect advises to put adm1021 in modules, when I do that on boot it 
crashes my machine. Well, I exclude adm1021 from modules, it seems that I 
don't nedd it anyway but I wanted to report this because it did not hapenned 
before and I think I've had it before in my modules file.

If you need any other report from me I'm at your service.

Thank you very much for your work.

Best regards, Ljubo
Croatian LUG

fan2 readout on Chaintech MB

[Jean Delvare]

> > My driver init code explicitely *stops* the chipset. No wonder you don't
> > see the values changing... Stupid me. That's fixed in CVS, if you were
> > kind enough to give it a try and tell me if it now works OK for you.
> 
> lm90 is working now:-))

Great :) Could you try adjusting limits, and also provide a sample output?

> Unfortunately I have new problems.
> I cant execute sensors -s, I'm getting this:
> 
> [root@localhost etc]# sensors -s
> it87-isa-0290: Can't access /proc file for writing;
> Run as root?
> 
> I've never had problems with sensors -s before.

Oh no! :( Not that problem again. We thought it was solved once for all...

We'd need as much details as possible about the conditions in which the problem
occurs, and first occured. Did you update lm_sensors recently? Which version
were using before? Which version are you using now? (I'd guess "latest CVS" as
the answer to the third question, but maybe you only updated the lm90.c file?)
Does the problem show only when the lm90 module is loaded (or has been loaded
since bootup)? What if you "hide" (rename, move, delete, whatever)
/etc/sensors.conf from sensors?

> and the other possible problem is this:
> sensors-detect advises to put adm1021 in modules, when I do that on boot it 
> crashes my machine. Well, I exclude adm1021 from modules, it seems that I 
> don't nedd it anyway but I wanted to report this because it did not
> hapenned before and I think I've had it before in my modules file.

For which I2C address does sensors-detect pretends the adm1021 module is
required? (and for which chipset?) Do you mean that older versions of
sensors-detect never told you that, and than newer versions do?

Any log messages when the adm1021 driver crashes your machine?

Jean Delvare



-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

fan2 readout on Chaintech MB

[Jean Delvare]

> I have been trying to use recent CVS version. I update CVS whenever I 
> can with cvs update -d, I did not updated just lm90 or any file
> separately.
> 
> My install procedure goes like this(Mandrake 9.1):
> 1. vanilla 2.4.22 kernel
> 2. con kolivas 2.4.22-ck2 patch set
> 3. patching kernel with i2c and lm_sensors
> 4. loading my kernel config file
> 5. compiling and installing kernel
> 6. reboot
> 7. cd into lm_sensors, make and make install
> 8. /prog/detect/sensors-detect
> 9. then I edit modules and modules.conf as suggested
> 10. reboot
> 11. Gkrellm, KSensors or just sensors
> 
> I have used con kolivas ck1 patchset on previous lm_sensors config.

What's inside that patchset? Anything related to either ACL or GRSEC?

Can you remember all changes that occured between when "sensors -s" was
working OK, and when it wasn't anymore? I'd appreciate if you could take
all the steps back to a state where "sensors -s" works again. If we
could isolate the problem, we would have a chance to understand it.

> Unfortunately I have had some problems with 166MHz FSB jumper on my 
> motherboard and I have RMA the board. I thing that replacment/new
> board will arrive next week so I can't do more testing now :-((

No problem, I am busy myself and most of the lm_sensors developers also
are.

> As soone as I get it working again I will do more testing.

OK, thanks.

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

fan2 readout on Chaintech MB

[Jean Delvare]

Please ignore the duplicate reply, we have had network issues which confused my
webmail client.

Jean


-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

fan2 readout on Chaintech MB

[Jean Delvare]

> > My driver init code explicitely *stops* the chipset. No wonder you don't
> > see the values changing... Stupid me. That's fixed in CVS, if you were
> > kind enough to give it a try and tell me if it now works OK for you.
> 
> lm90 is working now:-))

Great :) Could you try adjusting limits, and also provide a sample output?

> Unfortunately I have new problems.
> I cant execute sensors -s, I'm getting this:
> 
> [root@localhost etc]# sensors -s
> it87-isa-0290: Can't access /proc file for writing;
> Run as root?
> 
> I've never had problems with sensors -s before.

Oh no! :( Not that problem again. We thought it was solved once for all...

We'd need as much details as possible about the conditions in which the problem
occurs, and first occured. Did you update lm_sensors recently? Which version
were using before? Which version are you using now? (I'd guess "latest CVS" as
the answer to the third question, but maybe you only updated the lm90.c file?)
Does the problem show only when the lm90 module is loaded (or has been loaded
since bootup)? What if you "hide" (rename, move, delete, whatever)
/etc/sensors.conf from sensors?

> and the other possible problem is this:
> sensors-detect advises to put adm1021 in modules, when I do that on boot it 
> crashes my machine. Well, I exclude adm1021 from modules, it seems that I 
> don't nedd it anyway but I wanted to report this because it did not
> hapenned before and I think I've had it before in my modules file.

For which I2C address does sensors-detect pretends the adm1021 module is
required? (and for which chipset?) Do you mean that older versions of
sensors-detect never told you that, and than newer versions do?

Any log messages when the adm1021 driver crashes your machine?

Jean Delvare



-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

fan2 readout on Chaintech MB

[Jean Delvare]

> I'm sending you output in attachment. I have also tried it87 sensors
> but I'm getting weird values, and I have also tried various temp_type
> values but I could not find the right value to get "normal" results, I
> will try it again and every combination.
> 
> I will see if my friend, that has EPOX nForce2 motherboard, has lm90
> so that he can do some testing for you.

Took a look at the output, this doubtlessly is a LM90.

(Reading through the datasheet, through the driver code, datasheet
again, driver again.)

Hm. How can I say that...

My driver init code explicitely *stops* the chipset. No wonder you don't
see the values changing... Stupid me. That's fixed in CVS, if you were
kind enough to give it a try and tell me if it now works OK for you.

> Thank you very, very much for your help. I have been thinking to RMA
> my board but now I will wait to see your results.

You're welcome.

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

fan2 readout on Chaintech MB

[Jean Delvare]

> Sorry that it took me so long to reply but I just received temporary 
> replacment for my board.
> Unfortunately it is not the same and it seems that it hasn't got lm90,
> this time I've got Soltek NForce2 motherboard. It has W83627HF
> hardware monitor. Readings are OK, but when I put set fan1_div line in
> sensors.conf and run sensors -s same thing happend.
> [root@localhost etc]# sensors -s
> w83627hf-isa-0290: Can't access /proc file for writing;
> Run as root?
> 
> I did not update cvs from time of your last mail, so it is about 2
> weeks old. Maybe I should try to do a test with updated drivers?

No need to update anything, we haven't changed anything serious these
last weeks.

This at least proves that the problem is driver independant, and lies
either in i2c-core, i2c-proc or libsensors.

> I will try with vanilla kernel and see what happends.

Yes, interesting test.

> I almost forgot to answer to your previous question:
> 
> > What's inside that patchset? Anything related to either ACL or
> > GRSEC?
> 
> GRSEC is inside the patchset but it is disabled.
> 
> You can find some more info on kon kolivas patches here:
> 
> http://members.optusnet.com.au/ckolivas/kernel/

I am offline now, will take a look later. What would be interesting to
see is which differences exit between ck1 and ck2 patches, because I
remember that it was working before you updated to ck2.

> I will have to wait and see if my old board will be back, with lm90 or
> maybe I will receive some other mobo. Until then I will see if my
> friend has board with lm90 so that he can do some lm90 testing.  

Thanks a lot for your help.

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