| View previous topic :: View next topic |
| Author |
Message |
totoffe
Tux's lil' helper
Joined: 25 Sep 2003
Posts: 86
Location: Orange County, CA
|
 Posted: Sat Mar 06, 2004 7:55 pm Post subject: |
 |
|
I have this problem :
bash-2.05b$ sensors-detect
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
and I don't have any file called mkdev.sh.
Do you did I miss something??? |
|
| Back to top |
|
 |
totoffe
Tux's lil' helper
Joined: 25 Sep 2003
Posts: 86
Location: Orange County, CA
|
| Posted: Sat Mar 06, 2004 8:30 pm Post subject: |
|
|
Ok I've worked it out :
untar the source, then go in the directory freshly untared and you will find prog/mkdev/mkdev.sh
ciao |
|
| Back to top |
|
|
Joe23
n00b
Joined: 11 Jan 2004
Posts: 21
|
| Posted: Mon Mar 29, 2004 3:14 pm Post subject: wierd temp output |
|
|
I dunno.. I've read most of what's been written here, and I still can't understand what I'm doing wrong.
my stats:
Motherboard: GA-8KNXP (intel). this is the board's web page: http://tw.giga-byte.com/MotherBoard/Products/Products_Spec_GA-8KNXP.htm
kernel version is 2.6.4.
this is what I get:
it87-isa-0290
Adapter: ISA adapter
VCore 1: +1.52 V (min = +1.42 V, max = +1.56 V) ALARM
VCore 2: +2.60 V (min = +2.40 V, max = +2.60 V) ALARM
+3.3V: +6.72 V (min = +3.12 V, max = +3.44 V) ALARM
+5V: +4.22 V (min = +4.72 V, max = +5.24 V) ALARM
+12V: +12.32 V (min = +11.36 V, max = +12.60 V)
-12V: -16.09 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: -8.05 V (min = -5.28 V, max = -4.81 V) ALARM
Stdby: +4.67 V (min = +4.72 V, max = +5.24 V) ALARM
VBat: +4.08 V
fan1: 3139 RPM (min = 0 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2) ALARM
fan3: 0 RPM (min = 3000 RPM, div = 2) ALARM
M/B Temp: +25°C (low = +15°C, high = +40°C) sensor = thermistor
CPU Temp: +89°C (low = +15°C, high = +45°C) sensor = invalid
Temp3: +74°C (low = +15°C, high = +45°C) sensor = thermistor
somehow I don't think my CPU temp is 89°C ..
as you can see, it's being recognized as a "it87-isa-0290" chip, but I don't know if that's true, the motherboard manual says nothing about it.
what can I do? I want to be able to see the actual and real values.
thanks in advance,
Joe
EDIT: the motherboard's manual states that the I/O controller is IT8712F |
|
| Back to top |
|
|
srs5694
Guru
Joined: 08 Mar 2004
Posts: 434
Location: Woonsocket, RI
|
| Posted: Mon Mar 29, 2004 4:28 pm Post subject: |
|
|
There are scaling factors that must be applied to various sensor readings, and these can vary from one board to another, and even from each sensor to another. These are entered in the /etc/sensors.conf file. Do a search in that file for "scaling"; there's a comment that describes what to do. My hunch is you need to halve your CPU temperature, but you may want to see what Windows and/or your BIOS is saying about the readings, just to be sure.
My own board (an MSI K8T Neo-FSR) doesn't require scaling factors in /etc/sensors.conf, but when I ran GKrellM, I found it was reporting temperatures in the 400-degree range. Scaling factors are entered for it in a little dial entry called "Factor;" entering "0.100" works well for me. |
|
| Back to top |
|
|
Souperman
Guru
Joined: 14 Jul 2003
Posts: 449
Location: Cape Town, South Africa
|
| Posted: Mon Mar 29, 2004 8:58 pm Post subject: |
|
|
Got my sensors working, except one of my system fans is not detected. Motherboard is a Jetway N2PAP-LITE (nFORCE2). Both fans are detected in the PC health indicators in POST and in the winbond hwdoctor program (Windows) that shipped with the board. Any ideas?
_________________
moo |
|
| Back to top |
|
|
fvant
Guru
Joined: 08 Jun 2003
Posts: 328
Location: Leiden, The Netherlands
|
| Posted: Thu Apr 08, 2004 6:44 am Post subject: |
|
|
emerge i2c lm-sensors and making th kernel modukes worked without errors but when i run sensors-detect it complains with this message:
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
modprobe i2c-proc also works...what's missing here ? |
|
| Back to top |
|
|
curious_bob
l33t
Joined: 05 Dec 2003
Posts: 636
Location: San Francisco, CA
|
| Posted: Thu Apr 08, 2004 7:54 pm Post subject: |
|
|
| I am getting a kernel source compatiblilty error. Is this not compatible with linux-gaming-sources? |
|
| Back to top |
|
|
pens
Tux's lil' helper
Joined: 01 Jan 2003
Posts: 121
Location: Irvine, CA
|
| Posted: Fri Apr 09, 2004 11:33 pm Post subject: |
|
|
| Code: | 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): yes
Probing for PCI bus adapters...
Use driver `i2c-nforce2' for device 00:01.1: nVidia Corporation nForce2 SMBus (MCP)
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-nforce2' (say NO if built into your kernel)? (YES/no): no
Do you now want to be prompted for non-detectable adapters? (yes/NO): 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): no
Well, you will know best. We will just hope you edited `/etc/modules.conf'
for automatic loading of this module. If not,
you won't be able to open any /dev/i2c-* file (unless youhave it built-in
into your kernel)
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).
[b]Error: First argument not a number!
Syntax: i2cdetect I2CBUS
I2CBUS is an integer[/b]
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. Do you want to scan the ISA bus? (YES/no): no
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. Do you want to scan for Super I/O sensors? (YES/no): no
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/lm_sensors2/doc/lm_sensors-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. |
sensors-detect is not working all that great here. I have i2c-nforce and stuff built into my kernel, but the same error occurs when it's a module. |
|
| Back to top |
|
|
curious_bob
l33t
Joined: 05 Dec 2003
Posts: 636
Location: San Francisco, CA
|
| Posted: Mon Apr 12, 2004 5:45 pm Post subject: |
|
|
| totoffe wrote: |
untar the source, then go in the directory freshly untared and you will find prog/mkdev/mkdev.sh
|
untar which source? i2c or lm-sensors? |
|
| Back to top |
|
|
Flurp
n00b
Joined: 15 Apr 2004
Posts: 23
Location: Crewe, UK
|
| Posted: Thu Apr 15, 2004 7:58 pm Post subject: |
|
|
I had the same problem as totoffe and several others:
| Code: |
bash-2.05b$ sensors-detect
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
|
Since Gentoo uses devfs it doesn't make sense to manually add nodes!
Looking through the sensors-detect script I noticed that later versions of lm-sensors include extra code to detect whether devfs is being used. One way round the problem, given that you are using devfs is to comment out line 1582 of /usr/sbin/sensors-detect by adding a # at the beginning:
| Code: |
sub initialize_conf
{
if (-f '/etc/modules.conf') {
$modules_conf = '/etc/modules.conf';
} elsif (-f '/etc/conf.modules') {
$modules_conf = '/etc/conf.modules';
} else { # default
$modules_conf = '/etc/modules.conf';
}
if (-c '/dev/i2c-0') {
$dev_i2c = '/dev/i2c-';
} elsif (-c '/dev/i2c/0') {
$dev_i2c = '/dev/i2c/';
} elsif (-c '/dev/i2c0') {
$dev_i2c = '/dev/i2c';
} else { # default
print "No i2c device files found. Use prog/mkdev/mkdev.sh to create them.\n";
# exit -1;
}
}
|
With this modification the script still complains but doesn't drop out any more. I now have lm-sensors up and running with gkrellm displaying the results 
Now to get the scaling factors right... |
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Thu Apr 15, 2004 9:30 pm Post subject: |
|
|
| fvant wrote: | emerge i2c lm-sensors and making th kernel modukes worked without errors but when i run sensors-detect it complains with this message:
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
modprobe i2c-proc also works...what's missing here ? |
I had this at one stage . If I recall I found loading i2c-dev cleared it.
Device Drivers -> I2C support -> I2C device interface
HTH |
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Thu Apr 15, 2004 9:36 pm Post subject: |
|
|
PS I have this as module but kernel autoloading pulls it in.  |
|
| Back to top |
|
|
glimt
n00b
Joined: 29 Sep 2003
Posts: 15
Location: Washington
|
| Posted: Sun Apr 25, 2004 11:26 pm Post subject: |
|
|
IMHO, this is a bug, probably should be logged.
--g
| Flurp wrote: | I had the same problem as totoffe and several others:
| Code: |
bash-2.05b$ sensors-detect
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
|
Since Gentoo uses devfs it doesn't make sense to manually add nodes!
Looking through the sensors-detect script I noticed that later versions of lm-sensors include extra code to detect whether devfs is being used. One way round the problem, given that you are using devfs is to comment out line 1582 of /usr/sbin/sensors-detect by adding a # at the beginning:
| Code: |
sub initialize_conf
{
if (-f '/etc/modules.conf') {
$modules_conf = '/etc/modules.conf';
} elsif (-f '/etc/conf.modules') {
$modules_conf = '/etc/conf.modules';
} else { # default
$modules_conf = '/etc/modules.conf';
}
if (-c '/dev/i2c-0') {
$dev_i2c = '/dev/i2c-';
} elsif (-c '/dev/i2c/0') {
$dev_i2c = '/dev/i2c/';
} elsif (-c '/dev/i2c0') {
$dev_i2c = '/dev/i2c';
} else { # default
print "No i2c device files found. Use prog/mkdev/mkdev.sh to create them.\n";
# exit -1;
}
}
|
With this modification the script still complains but doesn't drop out any more. I now have lm-sensors up and running with gkrellm displaying the results
Now to get the scaling factors right... |
|
|
| Back to top |
|
|
Gentree
Watchman
Joined: 01 Jul 2003
Posts: 5350
Location: France, Old Europe
|
| Posted: Thu Apr 29, 2004 11:38 am Post subject: |
|
|
I dont see this as a bug,
if i2c-dev is not loaded there are no devices and the msg is correct.
The suggested fault msg may not be the most helpful, maybe it should suggest checking i2c-dev. |
|
| Back to top |
|
|
arkane
l33t
Joined: 30 Apr 2002
Posts: 918
Location: Phoenix, AZ
|
| Posted: Mon May 03, 2004 6:13 am Post subject: |
|
|
| Gentree wrote: | I dont see this as a bug,
if i2c-dev is not loaded there are no devices and the msg is correct.
The suggested fault msg may not be the most helpful, maybe it should suggest checking i2c-dev. |
Or a patch applied that makes it check, and if it's not compiled in, to attempt to load the module. |
|
| Back to top |
|
|
suikka
n00b
Joined: 13 May 2004
Posts: 52
|
| Posted: Mon May 17, 2004 3:41 pm Post subject: |
|
|
i tried to install lm_sensors with not so good results..
| Code: | # emerge lm-sensors
Calculating dependencies ...done!
>>> emerge (1 of 2) sys-apps/i2c-2.8.1 to /
>>> md5 src_uri ;-) i2c-2.8.1.tar.gz
* *****************************************************************
*
* This ebuild assumes your *current* kernel is >=2.4.9 && < 2.5+
*
* For 2.5+ series kernels, use the support already in the kernel
* under 'Character devices' -> 'I2C support'.
*
* To cross-compile, 'export LINUX="/lib/modules/<version>/build"'
* or symlink /usr/src/linux to another kernel.
*
* *****************************************************************
* *****************************************************************
*
* WARNING: This i2c support is not recommended for things such as
* WARNING: BTTV
*
* *****************************************************************
*
* http://www2.lm-sensors.nu/~lm78/cvs/browse.cgi/lm_sensors2/README
*
* 35 ADDITIONALLY, i2c-2.8.1 is not API compatible to earlier i2c
* 36 releases due to struct changes; therefore you must NOT ENABLE
* 37 any other i2c drivers (e.g. bttv) in the kernel.
* 38 Do NOT use lm-sensors 2.8.0 or i2c-2.8.0 if you require bttv.
*
* Please try out http://www.ensicaen.ismra.fr/~delvare/devel/i2c/
* for a kernel patch which will fix this problem. Please note that
* nor the lm_sensors team nor the package maintainers will be able
* to support you if you encounter problems with I2C when using
* other modules with requirements on I2C...
*
* *****************************************************************
>>> Unpacking source...
>>> Unpacking i2c-2.8.1.tar.gz to /var/tmp/portage/i2c-2.8.1/work
>>> Source unpacked.
* You are running:- 2.6.6-rc1
* Using kernel in /usr/src/linux:- 2.6.6-rc1
* Kernel version in /usr/src/linux is not 2.4.x
* Please specify a 2.4.x kernel!
!!! ERROR: sys-apps/i2c-2.8.1 failed.
!!! Function src_compile, Line 71, Exitcode 0
!!! Incompatible Kernel |
what should i do ? |
|
| Back to top |
|
|
kallamej
Administrator
Joined: 27 Jun 2003
Posts: 4983
Location: Gothenburg, Sweden
|
| Posted: Mon May 17, 2004 6:55 pm Post subject: |
|
|
You should put | Code: | | =sys-apps/lm-sensors-2.8.6 -x86 |
in /etc/portage/package.keywords.
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat |
|
| Back to top |
|
|
appetitus
Apprentice
Joined: 28 Sep 2003
Posts: 210
|
| Posted: Thu May 20, 2004 5:49 am Post subject: |
|
|
He should also visit
http://www2.lm-sensors.nu/~lm78/kernel26.html
and follow the instructions there about kernel options. Then the FAQ and some thinking will allow you to finally get it working. If he has ISA sensors, be sure to add the kernel option (not mentioned on webpage and was hard to find -- so I edited .config).
The newest sensors, 2.8.6 and kernel 2.6.6-mm4 work here on a Supermicro with only about a dozen attempts 
_________________
Being a Gentoo user means living in a house inhabited by a family of crazed carpenters. When you wake up, the house is different. Maybe there is a new turret, or some walls have moved, or perhaps someone has removed the floor under your bed. |
|
| Back to top |
|
|
wads
n00b
Joined: 09 May 2004
Posts: 52
Location: NYC
|
| Posted: Fri Jun 04, 2004 6:33 am Post subject: |
|
|
| Quote: | So did anyone get it to work with 2.6 kernels?
You can't emerge lm-sensors anymore because of the kernel diffrence.
Help would be very much appreciated cuz I am trying to get it to work for ages now. |
I had the same problem. To emerge a version (2.8.6) of lm_sensors that worked with my 2.6 kernel, I did the following:
| Code: | Step 1: echo "sys-apps/lm-sensors -x86" >> /etc/portage/package.keywords
Step 2: echo "sys-apps/lm-sensors" >> /etc/portage/package.unmask |
From that point on, I just followed the excellent tutorial found here: https://forums.gentoo.org/viewtopic.php?t=52815&highlight=sensors
Good luck! |
|
| Back to top |
|
|
mentok
n00b
Joined: 02 Nov 2003
Posts: 22
Location: Ontario, Canada
|
| Posted: Thu Jun 17, 2004 1:05 am Post subject: |
|
|
I'm using kernel 2.6.5-mm6 and I've been trying to emerge a version of lm-sensors >2.8.1 but for some reason I can't. I've just done emerge sync and I have done
| Code: | Step 1: echo "sys-apps/lm-sensors -x86" >> /etc/portage/package.keywords
Step 2: echo "sys-apps/lm-sensors" >> /etc/portage/package.unmask |
But emerge -av lm-sensors only shows version 2.8.1.
I also tried putting | Code: | | =sys-apps/lm-sensors-2.8.6 -x86 |
in /etc/portage/package.keywords
I have also tried
| Code: | emerge -av =lm-sensors-2.8.2
emerge -av =lm-sensors-2.8.3
emerge -av =lm-sensors-2.8.4
emerge -av =lm-sensors-2.8.5
emerge -av =lm-sensors-2.8.6 |
But no luck.
I've also tried ACCEPT_KEYWORDS="~x86" but it doesn't work either.
Trying to emerge lm-sensors-2.8.1 just gives an error since it's for a 2.4 kernel.
I have ALL the options in the kernel under i2c compiled as modules but I can't modprobe i2c-proc
what am I missing??? |
|
| Back to top |
|
|
Stormmind
Tux's lil' helper
Joined: 11 Aug 2002
Posts: 112
Location: Sweden
|
| Posted: Sun Jun 20, 2004 5:42 pm Post subject: |
|
|
I've tryed following the guide, but when running "sensors-detect" i got the "no devices" error. Following a tip from above, I commented out the "exit 1" line in sensors-detect, and the script run through and did loading and stuff, but all of a sudden it stopped with:
| Code: | 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.
|
I have an Asus A7V333 motherboard and lspci gives me this:
| Code: |
00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
|
It is not the 82801 chipset that has a workaround so I am afraid to test that. What should I do? |
|
| Back to top |
|
|
kallamej
Administrator
Joined: 27 Jun 2003
Posts: 4983
Location: Gothenburg, Sweden
|
| Posted: Sun Jun 20, 2004 5:59 pm Post subject: |
|
|
| mentokthemindtaker wrote: | I'm using kernel 2.6.5-mm6 and I've been trying to emerge a version of lm-sensors >2.8.1 but for some reason I can't. I've just done emerge sync and I have done
--SNIP--
|
The package.unmask entry is not necessary, but otherwise it seems like it should work. Which portage version do you use? Can you post the exact error messages as well as the contents of /etc/portage/package.keywords (for sanity), please.
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat |
|
| Back to top |
|
|
Stormmind
Tux's lil' helper
Joined: 11 Aug 2002
Posts: 112
Location: Sweden
|
| Posted: Sun Jun 20, 2004 6:03 pm Post subject: |
|
|
I dunno what I did, but I reran sensors-detect and it's working better now =)
will report results in a minute. |
|
| Back to top |
|
|
mentok
n00b
Joined: 02 Nov 2003
Posts: 22
Location: Ontario, Canada
|
| Posted: Sun Jun 20, 2004 7:29 pm Post subject: |
|
|
Here is what I get when trying to emerge lm-sensors:
| Code: | pi root # emerge -av lm-sensors
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N ] sys-apps/lm-sensors-2.8.1 -debug 0 kB
Total size of downloads: 0 kB
Do you want me to merge these packages? [Yes/No] y
>>> emerge (1 of 1) sys-apps/lm-sensors-2.8.1 to /
>>> md5 src_uri ;-) lm_sensors-2.8.1.tar.gz
>>> Unpacking source...
>>> Unpacking lm_sensors-2.8.1.tar.gz to /var/tmp/portage/lm-sensors-2.8.1/work
* Applying lm-sensors-2.8.1-sensors-detect-gentoo.diff... [ ok ]
>>> Source unpacked.
* *****************************************************************
*
* This ebuild assumes your /usr/src/linux kernel is the one you
* used to build i2c-2.8.1. and is >=2.4.9 && < 2.5+
*
* For 2.5+ series kernels, use the support already in the kernel
* under 'Character devices' -> 'I2C support' and get lm-sensors
* 2.8.2.
*
* To cross-compile, 'export LINUX="/lib/modules/<version>/build"'
* or symlink /usr/src/linux to another kernel.
*
* *****************************************************************
* You are running:- 2.6.5-mm6
* Using kernel in /usr/src/linux/:- 2.6.5-mm6
* Kernel version in /usr/src/linux is not 2.4.x
* Please specify a 2.4.x kernel!
!!! ERROR: sys-apps/lm-sensors-2.8.1 failed.
!!! Function src_compile, Line 62, Exitcode 0
!!! Incompatible Kernel
|
Here is my /etc/portage/package.keywords:
| Code: | sys-apps/lm-sensors ~x86
app-office/gnucash ~x86
net-im/amsn ~x86
|
Trying to emerge lm-sensors-2.8.6:
| Code: | pi root # emerge -av =lm-sensors-2.8.6
These are the packages that I would merge, in order:
Calculating dependencies
!!! all ebuilds that could satisfy "=lm-sensors-2.8.6" have been masked.
!!! possible candidates are:
- sys-apps/lm-sensors-2.8.6 (masked by: -keyword)
!!! Error calculating dependencies. Please correct.
|
Using ACCEPT_KEYWORDS:
| Code: | pi root # ACCEPT_KEYWORDS="~x86" emerge -av lm-sensors
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N ] sys-apps/lm-sensors-2.8.1 -debug 0 kB
Total size of downloads: 0 kB
Do you want me to merge these packages? [Yes/No] n
Quitting.
|
Both:
| Code: | pi root # ACCEPT_KEYWORDS="~x86" emerge -av =lm-sensors-2.8.6
These are the packages that I would merge, in order:
Calculating dependencies
!!! all ebuilds that could satisfy "=lm-sensors-2.8.6" have been masked.
!!! possible candidates are:
- sys-apps/lm-sensors-2.8.6 (masked by: -keyword)
!!! Error calculating dependencies. Please correct.
|
|
|
| Back to top |
|
|
kallamej
Administrator
Joined: 27 Jun 2003
Posts: 4983
Location: Gothenburg, Sweden
|
| Posted: Sun Jun 20, 2004 7:41 pm Post subject: |
|
|
| mentokthemindtaker wrote: | Here is my /etc/portage/package.keywords:
| Code: | sys-apps/lm-sensors ~x86
app-office/gnucash ~x86
net-im/amsn ~x86
|
|
Ah yes, you have tilde x86, it should be minus x86. In cases like this you can always look in the ebuild to see what keyword is used and copy that to be sure to get it correct.
_________________
Please read our FAQ Forum, it answers many of your questions.
irc: #gentoo-forums on irc.libera.chat |
|
| Back to top |
|
|
|
Kernel & Hardware
