how to deal with

[root@cook xsensors-0.10]# modprobe i2c-proc
FATAL: Module i2c_proc not found.
[root@cook xsensors-0.10]#

[root@cook xsensors-0.10]# sensors -s
Can't access /proc file
/proc/sys/dev/sensors/chips or /proc/bus/i2c unreadable;
Make sure you have done 'modprobe i2c-proc'!
[root@cook xsensors-0.10]#

sensors-detect:

Probing for PCI bus adapters...
Sorry, no PCI bus adapters found.

We will now try to load each adapter module in turn.
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):
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. If you have a PIIX4, that often
includes addresses 0x69 and/or 0x6a.
Couldn't open /proc/bus/i2c?!? at /usr/sbin/sensors-detect line 2494, <STDIN> line 3.
[root@cook xsensors-0.10]#

[root@cook xsensors-0.10]# rpm -q i2c
i2c-2.9.0-1.1.rhfc3.at
[root@cook xsensors-0.10]# rpm -q lm_sensors
lm_sensors-2.6.1-1
[root@cook xsensors-0.10]#

Make sure that you are mounting the proc filesystem in your /etc/fstab. You should have an entry that looks like:

none /proc proc defaults 0 0

You can confirm that it's there by displaying one of the standard "files", like:

cat /proc/cpuinfo

I made it work but can't figure out which sensor exactly is for my board since I got very strange output from sensors like -5V detected current= -8.11V... and so on...