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 82801EB ICH5
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
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).

I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)?

To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.

Re: setup lm_sensors : im stuck

tested that but no different, but i think i have found where the problem is. There is a IO-conflict in the new kernel (2.6.10) with this winbond sensor and the ACPI plug and play so i will try to recompile the kernel without support for this and try again.

Re: setup lm_sensors : im stuck

Does your BIOS detect the CPU fan speed? If not, there's your problem: the fan has to be connected to a special fan header on your mainboard to enable RPM-readouts. In some cases, you may not want to connect the fan directly to your mainboard tho. If you have a powerful fan like a 50 dB Delta that can take your fingers off if you try to stop it, connecting it to the fan headers is a bad idea: the fan is very powerful so it drains a lot of power and mainboards simply can't deliver it (they'll die a lot faster). It's better to connect the fan to a molex (white powerplug on your PSU) and just do without the RPM reading. You could, however, connect it to a molex but disconnect the "RPM-reading cable" (one of the 3 cables in the fan) and attach a plug to it so you can connect it the fanheader. This way you won't kill your mainboard and still have the RPM readout. It takes a little craftsmanship and balls tho.

If you do get a readout in the BIOS, you'll have to fiddle around with lm_sensors' configfile: it might print the info on with the wrong title.
The same goes for your RAM-voltage: right down the figures and compare them to the readouts in the BIOS. This way you'll know which number means what.

A bus station is where a bus stops. A train station is where a train stops. On my desk I have a workstation.

Re: setup lm_sensors : im stuck

My BIOS is reading the cpu fan speed just fine. Even the Windoze application called AbitEQ displays the informations correctly. Maybe i'll run through sensors-detect again and actually read the weird questions it asks. Anyway, at the beggining it says that it's safe to answer 'YES' to all of the questions, unless you know what you're doing

As for the Vcore2 voltage, yes I think it stands for Vdimm becuase the value shown in BIOS is the same.