I used 2.6.3-4mdk kernel with gkrellm showing temps allright

I've downloaded and succesfully compiled 2.6.5 kernel but i can't get any reading in gkrellm about my temps.I've read that i have 2 download and install lm sensors and i2c in their latest version. I did but when i try to compile them (make etc) i get an amazing amount of errors!!!
Has anyone had problems like that?What should i do?

PS1 When i 'sensors-detect' i get that no sensors r detected after the questions !

PS2 My cpu is overcloacked (from 2.4 ghz to 3.1 ghz) so temp reading is rather crucial 2 me!

Anyone?

You need the lastest version of lm_sensors http://www2.lm-sensors.nu/~lm78/download.html.
Just lm_sensors on i2c-it is already in the kernel.
I get cvs for the most up todate.
cd /usr/src then follow the direction for getting the latest lm_sensors
make user_tools
make user_install

Hmm. The url doesn't seem 2 work!

PS What directions?

Done a google search and downloaded lm sensors 2.8.6. Here is what i get when i do a make :
[george@localhost lm_sensors-2.8.6]$ make
Makefile:245: kernel/busses/i2c-nforce2.d: No such file or directory
Makefile:245: kernel/busses/i2c-ipmb.d: No such file or directory
Makefile:245: kernel/busses/i2c-ipmi.d: No such file or directory
Makefile:245: kernel/busses/i2c-ali1535.d: No such file or directory
Makefile:245: kernel/busses/i2c-ali15x3.d: No such file or directory
Makefile:245: kernel/busses/i2c-amd756.d: No such file or directory
Makefile:245: kernel/busses/i2c-amd8111.d: No such file or directory
Makefile:245: kernel/busses/i2c-hydra.d: No such file or directory
Makefile:245: kernel/busses/i2c-i801.d: No such file or directory
Makefile:245: kernel/busses/i2c-i810.d: No such file or directory
Makefile:245: kernel/busses/i2c-isa.d: No such file or directory
Makefile:245: kernel/busses/i2c-sis5595.d: No such file or directory
Makefile:245: kernel/busses/i2c-sis630.d: No such file or directory
Makefile:245: kernel/busses/i2c-sis645.d: No such file or directory
Makefile:245: kernel/busses/i2c-piix4.d: No such file or directory
Makefile:245: kernel/busses/dmi_scan.d: No such file or directory
Makefile:245: kernel/busses/i2c-savage4.d: No such file or directory
Makefile:245: kernel/busses/i2c-via.d: No such file or directory
Makefile:245: kernel/busses/i2c-viapro.d: No such file or directory
Makefile:245: kernel/busses/i2c-voodoo3.d: No such file or directory
Makefile:245: kernel/chips/bmcsensors.d: No such file or directory
Makefile:245: kernel/chips/ds1307.d: No such file or directory
Makefile:245: kernel/chips/lm83.d: No such file or directory
Makefile:245: kernel/chips/lm90.d: No such file or directory
Makefile:245: kernel/chips/max6650.d: No such file or directory
Makefile:245: kernel/chips/saa1064.d: No such file or directory
Makefile:245: kernel/chips/smartbatt.d: No such file or directory
Makefile:245: kernel/chips/smbus-arp.d: No such file or directory
Makefile:245: kernel/chips/vt8231.d: No such file or directory
Makefile:245: kernel/chips/w83627hf.d: No such file or directory
Makefile:245: kernel/chips/w83l785ts.d: No such file or directory
Makefile:245: kernel/chips/xeontemp.d: No such file or directory
Makefile:245: kernel/chips/adm1021.d: No such file or directory
Makefile:245: kernel/chips/adm1024.d: No such file or directory
Makefile:245: kernel/chips/adm1025.d: No such file or directory
Makefile:245: kernel/chips/adm1026.d: No such file or directory
Makefile:245: kernel/chips/adm9240.d: No such file or directory
Makefile:245: kernel/chips/asb100.d: No such file or directory
Makefile:245: kernel/chips/bt869.d: No such file or directory
Makefile:245: kernel/chips/ddcmon.d: No such file or directory
Makefile:245: kernel/chips/ds1621.d: No such file or directory
Makefile:245: kernel/chips/eeprom.d: No such file or directory
Makefile:245: kernel/chips/fscpos.d: No such file or directory
Makefile:245: kernel/chips/fscscy.d: No such file or directory
Makefile:245: kernel/chips/fscher.d: No such file or directory
Makefile:245: kernel/chips/gl518sm.d: No such file or directory
Makefile:245: kernel/chips/gl520sm.d: No such file or directory
Makefile:245: kernel/chips/it87.d: No such file or directory
Makefile:245: kernel/chips/lm75.d: No such file or directory
Makefile:245: kernel/chips/lm78.d: No such file or directory
Makefile:245: kernel/chips/lm80.d: No such file or directory
Makefile:245: kernel/chips/lm85.d: No such file or directory
Makefile:245: kernel/chips/lm87.d: No such file or directory
Makefile:245: kernel/chips/lm92.d: No such file or directory
Makefile:245: kernel/chips/ltc1710.d: No such file or directory
Makefile:245: kernel/chips/matorb.d: No such file or directory
Makefile:245: kernel/chips/maxilife.d: No such file or directory
Makefile:245: kernel/chips/mtp008.d: No such file or directory
Makefile:245: kernel/chips/pca9540.d: No such file or directory
Makefile:245: kernel/chips/pcf8574.d: No such file or directory
Makefile:245: kernel/chips/pcf8591.d: No such file or directory
Makefile:245: kernel/chips/sis5595.d: No such file or directory
Makefile:245: kernel/chips/smsc47m1.d: No such file or directory
Makefile:245: kernel/chips/pc87360-fan.d: No such file or directory
Makefile:245: kernel/chips/thmc50.d: No such file or directory
Makefile:245: kernel/chips/w83781d.d: No such file or directory
Makefile:245: kernel/chips/via686a.d: No such file or directory
Makefile:245: kernel/chips/vt1211.d: No such file or directory
Makefile:245: kernel/include/sensors.hd: No such file or directory
Makefile:245: lib/data.ld: No such file or directory
Makefile:245: lib/general.ld: No such file or directory
Makefile:245: lib/error.ld: No such file or directory
Makefile:245: lib/chips.ld: No such file or directory
Makefile:245: lib/proc.ld: No such file or directory
Makefile:245: lib/access.ld: No such file or directory
Makefile:245: lib/init.ld: No such file or directory
Makefile:245: lib/data.ad: No such file or directory
Makefile:245: lib/general.ad: No such file or directory
Makefile:245: lib/error.ad: No such file or directory
Makefile:245: lib/chips.ad: No such file or directory
Makefile:245: lib/proc.ad: No such file or directory
Makefile:245: lib/access.ad: No such file or directory
Makefile:245: lib/init.ad: No such file or directory
Makefile:245: prog/detect/i2cdetect.rd: No such file or directory
Makefile:245: prog/dump/i2cdump.rd: No such file or directory
Makefile:245: prog/dump/i2cset.rd: No such file or directory
Makefile:245: prog/dump/i2cbusses.rd: No such file or directory
Makefile:245: prog/dump/isadump.rd: No such file or directory
Makefile:245: prog/sensors/main.rd: No such file or directory
Makefile:245: prog/sensors/chips.rd: No such file or directory
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -Wall -O2 prog/sensors/c
hips.c | \
sed -e 's@^\(.*\)\.o:@prog/sensors/chips.rd prog/sensors/chips.ro: Make
file '`dirname prog/sensors/chips.rd`/Module.mk' @' > prog/sensors/chips.rd
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -Wall -O2 prog/sensors/m
ain.c | \
sed -e 's@^\(.*\)\.o:@prog/sensors/main.rd prog/sensors/main.ro: Makefi
le '`dirname prog/sensors/main.rd`/Module.mk' @' > prog/sensors/main.rd
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -Wall -O2 prog/dump/isad
ump.c | \
sed -e 's@^\(.*\)\.o:@prog/dump/isadump.rd prog/dump/isadump.ro: Makefi
le '`dirname prog/dump/isadump.rd`/Module.mk' @' > prog/dump/isadump.rd
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -Wall -O2 prog/dump/i2cb
usses.c | \
sed -e 's@^\(.*\)\.o:@prog/dump/i2cbusses.rd prog/dump/i2cbusses.ro: Ma
kefile '`dirname prog/dump/i2cbusses.rd`/Module.mk' @' > prog/dump/i2cbusses.rd
gcc -M -MG -I. -Ikernel/include -I/usr/local/include -Wall -O2 prog/dump/i2cs
et.c | \


and stuff like that.

What is goin wrong?

My mobo is asus p4g8x with intel's e7205 chipset and ich4 also from intel

Sorry http://www2.lm-sensors.nu/~lm78/download.html

Just lm_sensors not i2c-it is already in the kernel.
I get cvs for the most up todate.

cd /usr/src
cvs -d :pserver:anon@cvs.lm-sensors.nu:/home/cvs login
Log in using the password "anonymous".
cvs -d :pserver:anon@cvs.lm-sensors.nu:/home/cvs checkout lm_sensors2
cd /usr/src/lm_sensors2
make user_tools
make user_install

Walt

no make

sorry you are right. About the above question try to do the following.
First backup you .config file in /usr/src/liinux, ie cp .config ../conf26
then do a make mrproper. With that error you are getting it seem that you are not getting a clean compile?
Then copy your conf26 back into /usr/src/linux and then do make menuconfig and verify that you have everything you selected. I am not sure if you need i2c-isa selected? The do make to recompile your kernel.
If it any help I use the following on my debian system.

For building the 2.6 kernel

Take and read the following:

http://www.linux.org.uk/~davej/docs/...loween-2.6.txt
http://kerneltrap.org/node/view/799

You need to get the module-init-tools.

cp linux-2.6.2.tar.gz /usr/src
tar jfx linux-2.6.2.tar.gz
ln -sf linux-2.6.2 linux
cd linux

Use lspci -v to help select your hardware. This will be helpful for configuring the 2.6 kernel.

make mrproper
make menuconfig
make
make modules_install
make install

Then modify you lilo.conf or grub.txt

make install installs vmlinuz into the boot directory along with System.map
It creates a symbolic link to you old vmlinuz -> vmlinuz.old and System.old

All you need to do is add entry for the old vmlinuz. I use lilo.conf

This is mine....

image=/boot/vmlinuz
label=Linux2.6
read-only

** This would be you redhat config. **
image=/boot/vmlinuz.old
vga=791
append="hdc=scsi hdd=scsi apm=power-off nomce"
label=Linux2.4
read-only

If you are using lilo, issue lilo -v or modify you menu.lst for grub.

Hope this helps. The more people use 2.6 the better.

uh, ghostwalker, did you post in the wrong thread?

I did make user and make user_install and here's what i get

[root@localhost /]# sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c/*
files, for most things.
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.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

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
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):
Module loaded succesfully.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

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):
Module loaded succesfully.

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).

Next adapter: SMBus I801 adapter at e800 (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client at address 0x2d can not be probed - unload all client drivers first!
Client found at address 0x44
Client at address 0x48 can not be probed - unload all client drivers first!
Client at address 0x49 can not be probed - unload all client drivers first!
Client at address 0x50 can not be probed - unload all client drivers first!
Client at address 0x51 can not be probed - unload all client drivers first!

Next adapter: bt878 #0 [sw] (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively):
Client at address 0x50 can not be probed - unload all client drivers first!
Client at address 0x61 can not be probed - unload all client drivers first!

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no):
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no):
Probing for `ITE 8702F Super IO Sensors'
Failed!
Probing for `ITE 8705F Super IO Sensors'
Failed!
Probing for `ITE 8712F Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87365 Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87366 Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed!
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Failed!
Probing for `VT1211 Super IO Sensors'
Failed! (0x87)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0x87)
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0x87)
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0x87)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0x87)
Probing for `Winbond W83697UF Super IO PWM'
Failed! (0x87)

Do you want to scan for secondary Super I/O sensors? (YES/no):
Probing for `ITE 8702F Super IO Sensors'
Failed!
Probing for `ITE 8705F Super IO Sensors'
Failed!
Probing for `ITE 8712F Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed!
Probing for `Nat. Semi. PC87365 Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87366 Super IO Sensors'
Failed!
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed!
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed!
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Failed!
Probing for `VT1211 Super IO Sensors'
Failed!
Probing for `Winbond W83627HF Super IO Sensors'
Failed!
Probing for `Winbond W83627THF Super IO Sensors'
Failed!
Probing for `Winbond W83637HF Super IO Sensors'
Failed!
Probing for `Winbond W83697HF Super IO Sensors'
Failed!
Probing for `Winbond W83697UF Super IO PWM'
Failed!

Sorry, no chips were detected.
Either your sensors are not supported, or they are
connected to an I2C bus adapter that we do not support.
See doc/FAQ, doc/lm_sensors-FAQ.html, or
http://www2.lm-sensors.nu/~lm78/cvs/...nsors-FAQ.html
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, see
http://secure.netroedge.com/~lm78/newdrivers.html for driver status.


Why?

I just fixed this! I've downloaded the latest version of gkrellm (2.1.28) and i get temp readings !