Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
lm_sensors and gkrellm HOWTO Support thread
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3, 4  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
smokeslikeapoet
Tux's lil' helper
Tux's lil' helper


Joined: 03 Apr 2003
Posts: 96
Location: Cordova, TN USA

PostPosted: Sat May 17, 2003 5:03 am    Post subject: lm_sensors and gkrellm HOWTO Support thread Reply with quote

This is the support thread for my lm_sensors and gkrellm howto.
http://forums.gentoo.org/viewtopic.php?t=52815
Please post all of your specific problems here. Please, include your motherboard, chipset, and kernel information:
e.g. EpoX 8KHA+, Via KT266A, and gentoo-sources-2.4.20.
I will do my best to answer your questions and hopefully some hardware experts will help me out.
_________________
-SmokesLikeaPoet

Folding@Home
Back to top
View user's profile Send private message
jerome187
Guru
Guru


Joined: 29 Apr 2003
Posts: 584

PostPosted: Sat May 17, 2003 7:33 am    Post subject: Reply with quote

i've been trying to get this to work for awhile

i've done this with the i2c things compiled in the kernel as modules and as built in, i allways get this error when i do 'emerge ksensors' or 'emerge lm_sensors'

Code:
make: *** [kernel/busses/i2c-amd8111.o] Error 1
make: *** Waiting for unfinished jobs....

!!! ERROR: sys-apps/lm_sensors-2.7.0 failed.
!!! Function src_compile, Line 31, Exitcode 2
!!! lm_sensors requires the source of a compatible kernel\nversion installed in /usr/src/linux and >=i2c-2.7.0 support built as a modules this support is included in gentoo-sources as of 2.4.20-r1


i've never seen a module i2c-amd8111 or anything like it in make menuconfig.

heres my specs:

Mobo: Biostar U8668 Grand
Chipset: VIA VT8751A (P4M266A)/ VT8235
Kernel: vinalla-sources 2.4.20

let me know if you need any other info

TIA!
Back to top
View user's profile Send private message
barlad
l33t
l33t


Joined: 22 Feb 2003
Posts: 673

PostPosted: Sat May 17, 2003 1:45 pm    Post subject: Reply with quote

Hello,
like it says, you need kernel sources which include some files lm_sensors-2.7.0 needs. For example, latest gentoo-source kernels include those files, the ck-kernel serie does not.
You have two solutions:
- emerge lm_sensors-2.6.5
- emerge gentoo-sources (or any other compatible kernel), link the sources to /usr/src/linux, emerge lm_sensors-2.7.0. Re-link /usr/src/linux to your current kernel sources. Unmerge gentoo-sources if you want to.
Back to top
View user's profile Send private message
ctford0
l33t
l33t


Joined: 25 Oct 2002
Posts: 774
Location: Lexington, KY,USA

PostPosted: Sat May 17, 2003 2:10 pm    Post subject: Reply with quote

I'm getting this in my everything log. Does anyone know what it means?

Code:

[kernel] i2c-ali1535.o: Resetting entire SMB Bus to clear busy condition (08)


Thanks,

Chris
Back to top
View user's profile Send private message
barlad
l33t
l33t


Joined: 22 Feb 2003
Posts: 673

PostPosted: Sat May 17, 2003 4:20 pm    Post subject: Reply with quote

Yes, if lm_sensors works fine, it's nothing worrying. When the module is loaded, it sets up your SMBus so that it can be used by sensors, that's about it. The busy state is most likely due to the way the motherboard works or the bios is set-up. It is not an error.
Back to top
View user's profile Send private message
jerome187
Guru
Guru


Joined: 29 Apr 2003
Posts: 584

PostPosted: Sat May 17, 2003 6:19 pm    Post subject: Reply with quote

barlad wrote:
Hello,
like it says, you need kernel sources which include some files lm_sensors-2.7.0 needs. For example, latest gentoo-source kernels include those files, the ck-kernel serie does not.
You have two solutions:
- emerge lm_sensors-2.6.5
- emerge gentoo-sources (or any other compatible kernel), link the sources to /usr/src/linux, emerge lm_sensors-2.7.0. Re-link /usr/src/linux to your current kernel sources. Unmerge gentoo-sources if you want to.


It says

Code:
bash-2.05b# emerge lm_sensors-2.6.5
Calculating dependencies
emerge: there are no masked or unmasked ebuilds to satisfy "lm_sensors-2.6.5".

!!! Error calculating dependancies. Please correct.


did i type it wrong or something? i would like to try to get this to work, i really dont want to have to emerge gentoo-sources and do all that work unless i really need to.
Back to top
View user's profile Send private message
barlad
l33t
l33t


Joined: 22 Feb 2003
Posts: 673

PostPosted: Sat May 17, 2003 6:49 pm    Post subject: Reply with quote

Code:

cd /usr/portage/sys-apps/lm_sensors
emerge lm_sensors-2.6.5.ebuild


It should work
Back to top
View user's profile Send private message
jerome187
Guru
Guru


Joined: 29 Apr 2003
Posts: 584

PostPosted: Sat May 17, 2003 10:46 pm    Post subject: Reply with quote

thanks, i got it to work. i dont know if its working right tho, isnt 74.0C little hot for a CPU? and 16.0C a little low for the system temp?

also, is there a way to get the mem on a graph like the cpu graph?
Back to top
View user's profile Send private message
smokeslikeapoet
Tux's lil' helper
Tux's lil' helper


Joined: 03 Apr 2003
Posts: 96
Location: Cordova, TN USA

PostPosted: Sun May 18, 2003 3:32 am    Post subject: Reply with quote

jerome187 wrote:
thanks, i got it to work. i dont know if its working right tho, isnt 74.0C little hot for a CPU? and 16.0C a little low for the system temp?

also, is there a way to get the mem on a graph like the cpu graph?


It does seem like a high temp for your cpu, but without information on your system setup it's hard to tell. My father was having heat problems and I cleaned half a centimeter of dust from his HSF and replaced the thermal tape with Artic Silver and dropped his CPU temp about 15 degrees. Athlon T-Bird's are known for there heat output, while stock Pentium III's will run much cooler. As far as the 16.0C temp you might need to edit the sensors.conf file to get the correct temp. If you dual boot you can download "motherboard monitor" for Windows which seems to be calibrated out of the box, better than lm_sensors is. From MBM's output or you PC Health section of you bios you should be able to gather enough accurate infomation on how to edit your sensors.conf file.
http://mbm.livewiredev.com/
For more information on how to edit sensors.conf view the links on my howto.
_________________
-SmokesLikeaPoet

Folding@Home
Back to top
View user's profile Send private message
jerome187
Guru
Guru


Joined: 29 Apr 2003
Posts: 584

PostPosted: Sun May 18, 2003 3:42 am    Post subject: Reply with quote

i'll be able to get the correct temps from the bios when i feel like rebooting (if that happens anytime soon :P )
Back to top
View user's profile Send private message
iceburglar
n00b
n00b


Joined: 05 Feb 2003
Posts: 10
Location: Boston, MA (God's Country)

PostPosted: Sun Jun 15, 2003 11:55 am    Post subject: Negative number for CPU temp? Reply with quote

Sometimes running "sensors" shows my CPU temp to be a negative number (like -35'C, which then climbs to -28'C under load). Other times it shows a whacked out temp like 114'C.

Anybody calibrated a Shuttle SK41G XPC (Small Form Factor) in there /etc/sensors.conf ?

Also, when I run Windows on this box, it runs a little hot (40'-42'C idling), but running gentoo, it seems like the CPU temps soar (the fan speeds up at 52'C), and occasionally, the fan cuts out and my SSH sessions lock up for a few seconds (I think the CPU is being throttled due to temps).

In other threads, I've heard of other users having strange kernel panics which may be heat related as well. Does Gentoo do something to make CPU's run extra toasty? Or does anybody have any ideas/suggestions/etc.?
_________________
--
Iceburglar;
To the world, you may just be one person,
But to one person, you may just be the world. - Source Unknown.
Back to top
View user's profile Send private message
wrs4
Tux's lil' helper
Tux's lil' helper


Joined: 27 May 2003
Posts: 95
Location: Alexandria, VA

PostPosted: Sun Jun 15, 2003 2:00 pm    Post subject: Reply with quote

I'm running a dual Xeon @ 2 GHz on an Iwill DPL-533 board.


    does it support lm_sensors?
    what does 'emerge: there are no masked or unmasked ebuilds to satisfy "lm_sensors".' mean?
Back to top
View user's profile Send private message
iceburglar
n00b
n00b


Joined: 05 Feb 2003
Posts: 10
Location: Boston, MA (God's Country)

PostPosted: Sun Jun 15, 2003 2:10 pm    Post subject: Reply with quote

wrs4 wrote:
what does 'emerge: there are no masked or unmasked ebuilds to satisfy "lm_sensors".' mean?


It means try "emerge lm-sensors" instead (dash instead of underscore)
_________________
--
Iceburglar;
To the world, you may just be one person,
But to one person, you may just be the world. - Source Unknown.
Back to top
View user's profile Send private message
wrs4
Tux's lil' helper
Tux's lil' helper


Joined: 27 May 2003
Posts: 95
Location: Alexandria, VA

PostPosted: Sun Jun 15, 2003 2:28 pm    Post subject: Reply with quote

Thanks...what I get for entering the emerge command as it was posted in the forum when I couldn't find the package in the gentoo package list :wink:
Back to top
View user's profile Send private message
wrs4
Tux's lil' helper
Tux's lil' helper


Joined: 27 May 2003
Posts: 95
Location: Alexandria, VA

PostPosted: Sun Jun 15, 2003 3:24 pm    Post subject: Reply with quote

OK...I emerged lm-sensors, then configured the kernel:

Code:

Character devices --->
I2C support --->
<*> I2C support
<*> I2C device interface
<*> I2C /proc interface


make dep, etc. Next, I emerged i2c, lm-sensors (again), and gkrellm (again)...

then I ran the sensors-detect:

Code:

kenobi linux # sensors-detect
 This program will help you to determine which I2C/SMBus modules you need to
 load to use lm_sensors most effectively.
 You need to have done a `make install', issued a `depmod -a' and made sure
 `/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate
 module path before you can use some functions of this utility. Read
 doc/modules for more information.
 Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files
 for some things. You can use prog/mkdev/mkdev.sh to create these /dev files
 if you do not have them already.
 If you have patched your kernel and have some drivers built-in you can
 safely answer NO if asked to load some modules. In this case, things may
 seem a bit confusing, but they will still work.

dmi: read: Success
 IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW!
 IBM Thinkpads have a severely broken i2c/SMBus implementation, just scanning
 the bus will break your Thinkpad forever!
 If this is a non-Thinkpad IBM, we still suggest you press CTRL+C. We have
 had users reporting system breakage on other IBM systems as well.

 We can start with probing for (PCI) I2C or SMBus adapters.
 You do not need any special privileges for this.
 Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801DB ICH4
Use driver `i2c-matroxfb' for device 01:00.0: MGA G400 AGP
Probe succesfully concluded.

 We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no):
/lib/modules/2.4.20-gentoo-r5/misc/i2c-i801.o: unresolved symbol i2c_add_adapter_Rsmp_c4d35d8f
/lib/modules/2.4.20-gentoo-r5/misc/i2c-i801.o: unresolved symbol i2c_del_adapter_Rsmp_a2df1640
/lib/modules/2.4.20-gentoo-r5/misc/i2c-i801.o: insmod /lib/modules/2.4.20-gentoo-r5/misc/i2c-i801.o failed
/lib/modules/2.4.20-gentoo-r5/misc/i2c-i801.o: insmod i2c-i801 failed
Loading failed (Illegal seek)... skipping.
Load `i2c-matroxfb' (say NO if built into your kernel)? (YES/no):
modprobe: Can't locate module i2c-matroxfb
Loading failed (Illegal seek)... skipping.
 Do you now want to be prompted for non-detectable adapters? (yes/NO):
 To continue, we need module `i2c-dev' to be loaded.
 If it is built-in into your kernel, you can safely skip this.
 i2c-dev is not loaded. Do you want to load it now? (YES/no):
modprobe: Can't locate module i2c-dev
 Loading failed (Illegal seek), expect problems later on.

 We are now going to do the adapter probings. Some adapters may hang halfway
 through; we can't really help that. Also, some chips will be double detected;
 we choose the one with the highest confidence value in that case.
 If you found that the adapter hung after probing a certain address, you can
 specify that address to remain unprobed. That often
 includes address 0x69 (clock chip).
Couldn't open /proc/bus/i2c?!? at /usr/sbin/sensors-detect line 2970, <STDIN> line 5.


kernel is/was/has been linux-2.4.20-gentoo-r5.

What did I miss?
Back to top
View user's profile Send private message
iceburglar
n00b
n00b


Joined: 05 Feb 2003
Posts: 10
Location: Boston, MA (God's Country)

PostPosted: Sun Jun 15, 2003 3:56 pm    Post subject: Reply with quote

wrs4 wrote:

What did I miss?


Check the link given in the first message in this topic. It links to a howto for this.

I think you forgot to "emerge i2c"
_________________
--
Iceburglar;
To the world, you may just be one person,
But to one person, you may just be the world. - Source Unknown.
Back to top
View user's profile Send private message
wrs4
Tux's lil' helper
Tux's lil' helper


Joined: 27 May 2003
Posts: 95
Location: Alexandria, VA

PostPosted: Sun Jun 15, 2003 5:20 pm    Post subject: Reply with quote

Rereading, what I missed was compiling it in as modules. I went back and modularized the items I posted above, then followed the rest of the tutorial. Not having an ISA bus on this board (Iwill DPL-533), I wasn't surprised that all of the tests on the ISA bus failed. It detected an i2c-i801 and an eeprom module, which I duly modprobed. I also had to add the /etc/sysconfig directory so that I could write out the lm_sensors file....

I have the two modules above inserted and running. sensors reports memory but nothing else:

Code:

kenobi linux # sensors
eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 1100
Algorithm: Non-I2C SMBus adapter
Memory type:            DDR SDRAM DIMM SPD
SDRAM Size (MB):        512

eeprom-i2c-0-54
Adapter: SMBus I801 adapter at 1100
Algorithm: Non-I2C SMBus adapter
Memory type:            DDR SDRAM DIMM SPD
SDRAM Size (MB):        512



I know the board has temperature monitoring because I can see it in the bios, and because the page I linked to says it does :) but apparently that functionality got missed. Is this an lm_sensors limitation?
Back to top
View user's profile Send private message
magikomax
n00b
n00b


Joined: 16 Jun 2003
Posts: 10
Location: Italy

PostPosted: Mon Jun 16, 2003 4:58 pm    Post subject: variuos Reply with quote

Hi,

I unmerged lm-sensor becouse I couldn't find the files needed to configure it. So I downloaded i2c 2.7.0 and lm-sensors 2.7.0 from the official site. I installed it following the quick install guide.

Now it works fine.
I have an ASUS A7V333 (VIAKT333) with an AthlonXP 1800+

What modules should I load. Now lsmod says:

socrate root # lsmod
Module Size Used by Not tainted
w83781d 20368 0
i2c-proc 7504 1 [w83781d]
i2c-dev 4900 0
i2c-viapro 3984 0
i2c-core 17160 0 [w83781d i2c-proc i2c-dev i2c-viapro]

Is it necessary w83781d?

I used also gkrellm to display Mb and CPU temperature. Does it exist a program wich do the same but fit in the top bar of Gnome?

Which are the correct value of "offset" and "factor" of the temp sensors?? Now it's about 12 degree less than Win ASUSProbe. But maybe linux uses less CPU than winXP.

Why I have 3 temp sensor (and in WinXP only 2)?? The 3rd sensor indicates 14°C and in my room now there are 29°C :)

Thanks for your suggestion!

Max
Back to top
View user's profile Send private message
wrs4
Tux's lil' helper
Tux's lil' helper


Joined: 27 May 2003
Posts: 95
Location: Alexandria, VA

PostPosted: Mon Jun 16, 2003 9:20 pm    Post subject: Reply with quote

Yes, you need the w83781d module, since the i2c modules depend on it. From your output:

Code:

i2c-proc 7504 1 [w83781d]


I don't know about gnome panel applets that display the information; I'm sure you could check the gnome site and see. For the other questions, someone else will have to help :)
Back to top
View user's profile Send private message
iceburglar
n00b
n00b


Joined: 05 Feb 2003
Posts: 10
Location: Boston, MA (God's Country)

PostPosted: Tue Jun 17, 2003 1:46 am    Post subject: Shuttle SK41G (FX41 motherboard) and lm_sensors Reply with quote

For those using a Shuttle XPC (I have the SK41G with the FX41 motherboard), you may notice that as soon as insert the it87 module (either "modprobe it87" or have it loaded at boot through "/etc/modules.autoload" as I do) your fan will start to run at full speed, which is very noisy.

There is a solution posted as a "Self-Serve Support Ticket" at the lm_sensors website.

What is happening is that when the it87 module gets loaded, it sends a reset to the chip. For whatever reason, this reset sends the fan into overdrive, which is quite noisy. The fix is to comment out the section of source code in it87.c so that it does not send this reset along to the chip. I'm not sure if you can use "emerge" after editing a local copy of a file (I "make install"'d it by hand).

Anyhoo, here's a snippet of my "lm_sensors-2.7.0/kernel/chips/it87.c":
Code:
Starting at Line 571:

int it87_write_value(struct i2c_client *client, u8 reg, u8 value)
{
/* Commented out for Shuttle SK41G Fan Speed Problem
    This will always "return 0" now

    if (i2c_is_isa_client(client)) {
        down(&(((struct it87_data *) (client->data))->lock));
        outb_p(reg, client->addr + IT87_ADDR_REG_OFFSET);
        outb_p(value, client->addr + IT87_DATA_REG_OFFSET);
        up(&(((struct it87_data *) (client->data))->lock));
        return 0;
    } else
        return i2c_smbus_write_byte_data(client, reg, value);
    }    */

return 0; /* New "return 0" added (always returns 0) */
}

A future release may add an option to avoid resetting the chip when loaded, but this is working great for me know.

SK41G Fan Speed Problem

Similar discussion at SFFTech
_________________
--
Iceburglar;
To the world, you may just be one person,
But to one person, you may just be the world. - Source Unknown.
Back to top
View user's profile Send private message
Peach
Advocate
Advocate


Joined: 08 Mar 2003
Posts: 3676
Location: London, UK

PostPosted: Mon Jun 23, 2003 11:17 pm    Post subject: Reply with quote

after a system update I got this prompt at boot time:
Code:
 * /etc/conf.d/lm_sensors does not exist, try running sensors-detect


that's right, so I run sensors-detect again and what I had was:
Code:
...
Probing for PCI bus adapters...
Use driver `i2c-viapro' for device 00:11.0: VIA Technologies VT8233 VLink South Bridge
Use driver `i2c-riva' for device 01:00.0: GeForce2 GTS2
Probe succesfully concluded.
 
 We will now try to load each adapter module in turn.
Module `i2c-viapro' already loaded.
Load `i2c-riva' (say NO if built into your kernel)? (YES/no):
modprobe: Can't locate module i2c-riva
Loading failed... skipping.
** Note: i2c-riva module is available at
** http://drama.obuda.kando.hu/~fero/cgi-bin/rivatv.shtml
 Do you now want to be prompted for non-detectable adapters? (yes/NO):
 To continue, we need module `i2c-dev' to be loaded.
 If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.
...
Sorry, no chips were detected.
...
blablabla

strange... they were working since yesterday...
:?
ok, so I did:
Code:
# emerge rivatv

but I found that I should disable framebuffer support 'cause it conflicts somehow with this driver... now I'm waitin to find what's up... someone updated lm_sensors a bit too much? :(

mind this:
Code:
# /etc/init.d/lm_sensors start
 * /etc/conf.d/lm_sensors does not exist, try running sensors-detect
# sensors
as99127f-i2c-0-2d
Adapter: SMBus Via Pro adapter at e800
Algorithm: Non-I2C SMBus adapter
VCore 1:   +1.84 V  (min =  +1.76 V, max =  +2.14 V)
VCore 2:   +0.12 V  (min =  +1.76 V, max =  +2.14 V)       ALARM
+3.3V:     +3.39 V  (min =  +2.97 V, max =  +3.63 V)
+5V:       +4.94 V  (min =  +4.50 V, max =  +5.48 V)
+12V:     +12.62 V  (min = +10.79 V, max = +13.11 V)
-12V:     -13.79 V  (min = -15.06 V, max = -12.32 V)       ALARM
-5V:       -3.90 V  (min =  -5.48 V, max =  -4.50 V)       ALARM
fan1:     5113 RPM  (min = 3000 RPM, div = 2)
fan2:        0 RPM  (min = 3000 RPM, div = 2)              ALARM
fan3:        0 RPM  (min = 3000 RPM, div = 2)              ALARM
temp1:       +38°C  (limit =  +60°C)
temp2:     +64.0°C  (limit = +120°C, hysteresis = +100°C)        (beep)
temp3:    +224.4°C  (limit = +120°C, hysteresis = +100°C)
vid:      +1.950 V
alarms:
beep_enable:
          Sound alarm enabled

_________________
Gentoo user since 2004.
"It's all fun and games, until someone loses an eye" - mom
Back to top
View user's profile Send private message
wrs4
Tux's lil' helper
Tux's lil' helper


Joined: 27 May 2003
Posts: 95
Location: Alexandria, VA

PostPosted: Tue Jun 24, 2003 9:27 am    Post subject: Reply with quote

Do you have an /etc/sysconfig directory? I noticed that when I ran sensors the first time, it said something on the order of "writing lm_sensors to /etc/sysconfig...failed no such file or directory."

Ultimately, I had to lsmod to get a list of modules installed, rmmod the ones associated with lm_sensors, rc-update remove lm_sensors default, run sensors again, then rc-update add lm_sensors default.

That worked for me, but depending on your situation, may not for you. Good luck.
Back to top
View user's profile Send private message
Peach
Advocate
Advocate


Joined: 08 Mar 2003
Posts: 3676
Location: London, UK

PostPosted: Tue Jun 24, 2003 10:36 am    Post subject: Reply with quote

wrs4 wrote:
Do you have an /etc/sysconfig directory? I noticed that when I ran sensors the first time, it said something on the order of "writing lm_sensors to /etc/sysconfig...failed no such file or directory.


Code:
$ ls /etc/sysconfig/
lm_sensors


there is... apart from that, when I'll have a little time I'll try to recompile the kernel without fb support and see if modprobing rivatv will give me some result in running sensors-detect
_________________
Gentoo user since 2004.
"It's all fun and games, until someone loses an eye" - mom
Back to top
View user's profile Send private message
hatem
n00b
n00b


Joined: 05 Jun 2003
Posts: 72
Location: Florida

PostPosted: Mon Sep 01, 2003 7:08 pm    Post subject: Reply with quote

Hey,

For some reason sensors seams to give me totally messed up readings. I get -5 C one second and 119 C the next. I took a look at the /etc/sensors.conf but I have no idea what to edit.

I have an Nforce2 Gigabyte 7njs Zenith motherboard running gentoo sources 2.4.20.

Here's some output that may be of help to you:

Code:

$ sensors
it87-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1:   +1.63 V  (min =  +1.53 V, max =  +1.87 V)   
VCore 2:   +2.68 V  (min =  +2.25 V, max =  +2.75 V)   
+3.3V:     +6.26 V  (min =  +2.96 V, max =  +3.60 V)   ALARM
+5V:       +4.91 V  (min =  +4.50 V, max =  +5.48 V)   
+12V:     +12.00 V  (min = +11.36 V, max = +13.80 V)   
-12V:     -19.31 V  (min = -15.85 V, max = -13.40 V)   ALARM
-5V:       -1.95 V  (min = -10.13 V, max =  -9.44 V)   ALARM
Stdby:     +2.55 V  (min =  +4.50 V, max =  +5.48 V)   ALARM
VBat:      +4.04 V
fan1:     4354 RPM  (min = 3000 RPM, div = 2)         
fan2:        0 RPM  (min = 3000 RPM, div = 2)          ALARM
fan3:        0 RPM  (min = 3000 RPM, div = 2)          ALARM
Temp1/MB:    +10?C  (min =  +20?C, max =  +60?C)
Temp2/CPU:  +120?C  (min =  +20?C, max =  +60?C) ALARM
Temp3:       +48?C  (min =  +20?C, max =  +60?C)


In the above output it says my cpu is 120C (!!!) but I think it is incorrect because my system should shut down if the temp gets that high (i think i configured my bios that way).

In the output below, I caught it displaying negative tempatures:
Code:

$ sensors
it87-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1:   +1.63 V  (min =  +1.53 V, max =  +1.87 V)   
VCore 2:   +2.68 V  (min =  +2.25 V, max =  +2.75 V)   
+3.3V:     +6.26 V  (min =  +2.96 V, max =  +3.60 V)   ALARM
+5V:       +4.91 V  (min =  +4.50 V, max =  +5.48 V)   
+12V:     +12.00 V  (min = +11.36 V, max = +13.80 V)   
-12V:     -19.31 V  (min = -15.85 V, max = -13.40 V)   ALARM
-5V:       -1.95 V  (min = -10.13 V, max =  -9.44 V)   ALARM
Stdby:     +2.55 V  (min =  +4.50 V, max =  +5.48 V)   ALARM
VBat:      +4.04 V
fan1:     4326 RPM  (min = 3000 RPM, div = 2)         
fan2:        0 RPM  (min = 3000 RPM, div = 2)          ALARM
fan3:        0 RPM  (min = 3000 RPM, div = 2)          ALARM
Temp1/MB:     +3?C  (min =  +20?C, max =  +60?C)
Temp2/CPU:   -17?C  (min =  +20?C, max =  +60?C) ALARM
Temp3:        +5?C  (min =  +20?C, max =  +60?C)


Code:

$ lsmod
Module                  Size  Used by    Tainted: P 
it87                    7396   0
i2c-proc                7568   0 [it87]
i2c-isa                 1132   0 (unused)
i2c-dev                 4772   0 (unused)
i2c-core               16304   0 [it87 i2c-proc i2c-isa i2c-dev]
nvidia               1537216  13 (autoclean)
nvnet                  26656   1
cmpci                  26232   0
soundcore               4580   2 [cmpci]


If there is anything that you guys need me to post, please ask and I will do so: I am totally clueless as to what the problem is. Thanks in advance for any suggestions.

Edit:
I went into my bios and got some specs... but I still have no idea what to edit in my /etc/sensors.conf. Any help will be appreciated.

Code:

CPU VCore = 1.61V
+2.5V = 2.68V
+3.3V = 3.13
+5.0V = 4.83V
+12V = 12.22V
-12V = (-)11.78V


Edit 2:
I think I've found the incorrect values. When I run "sensors" these are the only things I can find that is not matching what my bios tells me.
Code:

+5V:       +4.91 V  (min =  +4.50 V, max =  +5.48 V)   
+12V:     +12.00 V  (min = +11.36 V, max = +13.80 V)   
-12V:     -19.31 V  (min = -15.85 V, max = -13.40 V)   ALARM

I'm still at a loss as to what I should edit in my sensors.conf to fix this.

Edit 3:
I found this comment in sensors.conf under the it87 section:
Quote:

# Important - if your temperature readings are completely whacky
# you probably need to change the sensor type. This must be done
# with 'modprobe it87 temp_type=0xXX', you can't fix it in this file.
# See ../doc/chips/it87 for details and valid 'XX' values!!!

Great! Only problem is I cannot find the ../doc/chips/it87 file :?.

Edit 4:
(Have I broken the record for number of edits yet? :lol: )
I untared the .gz file portage downloaded and found the file there.

Quote:

Legal values:
sensor1 sensor2 sensor3 value
------- ------- ------- -----
diode diode diode 0x07
diode diode thermistor 0x23
diode thermistor diode 0x15
diode thermistor thermistor 0x31
thermistor diode diode 0x0e
thermistor diode thermistor 0x2a ** default
thermistor thermistor diode 0x1c
thermistor thermistor thermistor 0x38

Now my remaining problem is figuring out what my sensors use. Chaintech 's website isn't too helpful... just says:

Quote:

* 8 external voltage inputs
* 2 temperature sensing for CPU and system
* 2 Fan speed (CPU and system) monitoring

Anyone know what the Chaintech 7NJS Zenith motherboard uses? I don't know how safe it is to just try all of the values untill i get something that works.


Last edited by hatem on Mon Sep 01, 2003 11:54 pm; edited 3 times in total
Back to top
View user's profile Send private message
Grilo
Tux's lil' helper
Tux's lil' helper


Joined: 22 Apr 2003
Posts: 114
Location: Canada

PostPosted: Mon Sep 01, 2003 10:07 pm    Post subject: Reply with quote

ok i have a gigayte 7vax-A kt400a chipset amd 1600xp pocessor i am running the mm 2.6 test4 kernel and you don't need lmsensors anymore. but my gkrellm cannot see the i2c stuff in the sys directory .

any ideas on how to get this to work?

Grilo
_________________
Knowledge is power but the drive to learn is harnessing wizdom
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page 1, 2, 3, 4  Next
Page 1 of 4

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum