| View previous topic :: View next topic |
| Author |
Message |
Inside
n00b
Joined: 21 Oct 2002
Posts: 39
Location: Afro-Eurasia
|
 Posted: Mon Sep 01, 2003 10:58 pm Post subject: |
 |
|
Hi,
i get the same Error as jerome187 got.
I am using the vanilla-sources 2.4.22 and the i2c 2.8.0 patch.
Any clue why this happens and how to fix it?
| 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
|
[/url] |
|
| Back to top |
|
 |
eisforian
n00b
Joined: 19 Apr 2003
Posts: 11
Location: Boston, MA
|
| Posted: Fri Sep 19, 2003 3:12 am Post subject: |
|
|
You don't seem to be using version 2.8.0 of lm_sensors and i2c. I did this by adding the following to my /etc/portage/package.unmask:
| Code: | sys-apps/lm-sensors
sys-apps/i2c |
_________________
The Asus A7V8X Deluxe: The Motherboard of Copious Intrigue.
Check out my fun-filled Gentoo notes & todo list! It's fun! Well, it at least looks good. |
|
| Back to top |
|
|
staed
n00b
Joined: 22 Sep 2003
Posts: 6
Location: Umeå, Sweden
|
| Posted: Tue Sep 23, 2003 11:35 pm Post subject: |
|
|
Hi.
I have a Gigabyte 7VRXP with a Via KT333 / Via 8233A chipset on a 2.4.20-gentoo-r7 kernel.
I've followed the instructions in the installation thread, but when i try to run 'sensors' i only get this:
# sensors
flex scanner jammed
tried to ask google, but he didn't know :(
_________________
The Internet? Is that thing still around? |
|
| Back to top |
|
|
defunk
n00b
Joined: 30 Mar 2003
Posts: 3
Location: Canada
|
| Posted: Sat Sep 27, 2003 4:22 pm Post subject: i2c-amd756 seems to hang after ltime |
|
|
Not sure if anyone can help me out with this one. My only machine out of four Gentoo boxes that seems to hate lm_senesors. This is an older settup. I am using a Gigabyte GA-7IXE motherboard with an Athlon 800 cpu. The chipset on this board; AMD 750, consisting of AMD 751 PCI/AGP and AMD 756 PCI ISA IDE Controller. Now after running sensors detect. The program returns with modules to load. i2c-amd756, w83781d and eeprom. I load these modules into the kernel with i2c-dev.o and everything seems to run good for a while. But eventually things go South and wacky. A quick look at the kern log tells me
kernel: i2c-amd756.o: SMBus collision!]
kernel: i2c-amd756.o: Busy wait timeout! (0800)
kernel: i2c-amd756.o: Sending abort.
Once this starts it will just stay this way until I reboot the machine. (and spams my log all up)
If anyone has some sort of resolution to this problem it would be much appreciated. It is driving me nuts! |
|
| Back to top |
|
|
viperlin
Veteran
Joined: 15 Apr 2003
Posts: 1319
Location: UK
|
| Posted: Sun Sep 28, 2003 9:10 am Post subject: |
|
|
i have a Gigabyte GA-7VT600 with a VIA KT600 chipset.
i have tryed all of these settings for it87
| Code: |
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 0x3
|
then wrote the temps down & rebooted, none even came close to the temperatures my bios was saying. that or the temperature seriously jumped or dropped during reboot.
the ones that seemed most possible (no negative ones) were these:
| Code: |
diode thermistor diode 0x15
diode thermistor thermistor 0x31
thermistor thermistor diode 0x1c
|
but again were about 20 degree's C off in temperature
according to my bios my system temp is 33 degree's C and my CPU is at 58 degree's C.
these three told me that my CPU was either at 30 something or 70 something.
anyone know what the setting is for my exact mobo (and yes i've searched but i'm gonna continue after posting , but without hope) |
|
| Back to top |
|
|
netboyiam
n00b
Joined: 01 Nov 2003
Posts: 2
|
| Posted: Sun Nov 02, 2003 7:20 pm Post subject: shuttle SN41G2 lm-sensors settings (it87) |
|
|
Hi:
Here's the arg's required to insmod it87 to avoid getting bogus/negative values on a shuttle SN41G2:
insmod it87 temp_type=0x38
Cheers,
k |
|
| Back to top |
|
|
kermitjunior
Apprentice
Joined: 04 Aug 2002
Posts: 167
|
| Posted: Sun Nov 02, 2003 10:01 pm Post subject: |
|
|
Just wanted to say THANK YOU. Excellent threads... both of them. First time I've managed to get it all working properly.
KJ
_________________
-----
Toshiba Satellite A15-S157, 2.2 Celery, 40GB, 512MB
AMD Athlon XP 1900+, 640MB PC2100, ABIT KG-7R
IBM 120GB (Linux), WD 30GB (WinDoze), ATI All-In-Wonder 128 Pro PCI |
|
| Back to top |
|
|
Merlin-TC
l33t
Joined: 16 May 2003
Posts: 603
Location: Germany
|
| Posted: Sun Nov 02, 2003 10:42 pm Post subject: |
|
|
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. |
|
| Back to top |
|
|
shakti
Guru
Joined: 15 May 2002
Posts: 358
Location: omnipresent
|
| Posted: Tue Nov 04, 2003 8:24 pm Post subject: |
|
|
| Merlin-TC wrote: | 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. |
all i can say is that it did work...dont know what i did but after first install of 2.6.0 i got cpu temp in gkrellm, but i recopiled with a config from scratch and puff..gone it was 
_________________
Using Gentoo since 2002. |
|
| Back to top |
|
|
bammbamm808
Guru
Joined: 08 Dec 2002
Posts: 548
Location: Hawaii
|
| Posted: Tue Jan 13, 2004 5:56 am Post subject: Maybe you can help me with my difficulty: |
|
|
2.4.24, but doing it the same way I have for the last few kernels. No i2c stuff is builtin to kernel, some as modules. Made sure no i2c modules were loaded, then from freshly untarred i2c-2.8.2:
make all
make install
depmod -a
Seems to go fine
Then from fresh lm_sensors-2.8.2:
make all
make install
depmod -a
ldconfig
modprobe i2c-core
modprobe i2c-dev
modprobe i2c-nforce2
prog/detect/sensors-detect
When asked to probe for non-detectable adapter, I answer no and get the following for my trouble.
Can't exec "i2cdetect": No such file or directory at prog/detect/sensors-detect line 4061, <STDIN> line 3.
Couldn't find i2cdetect program!! at prog/detect/sensors-detect line 4061, <STDIN> line 3.
i2cdetect is, of course in the same dir as sensors-detect script. Here's the referenced line from sensors-detect (in bold):
# i2cdetect -l either cats /proc/bus/i2c or scans sysfs for the same information
open INPUTFILE,"i2cdetect -l |" or die "Couldn't find i2cdetect program!!";
while (<INPUTFILE>) {
Here's /cat/proc/bus/i2c:
mark@hnllhi1-ar6-4-7-247-127 mark $ cat /proc/bus/i2c
i2c-0 smbus SMBus nForce2 adapter at 5000 Non-I2C SMBus adapter
i2c-1 smbus SMBus nForce2 adapter at 5040 Non-I2C SMBus adapter
What am I missing?
i2c-cvs and lm_sensors-cvs also behave identically
_________________
MSI MAG B550 Tomahawk
Ryzen 3900x
32Gb Samsung B-die (16GB dual rank x2) DDR4 @ 3200MHz, cl14
Geforce RTX 2070S 8GB
Samsung m.2 NVME pcie-3.0
Etc.... |
|
| Back to top |
|
|
andrea_ferraris
n00b
Joined: 06 Jan 2004
Posts: 19
|
| Posted: Wed Jan 21, 2004 6:26 pm Post subject: gs-sources kernel with ECS K7s5a Pro troubles |
|
|
Hi,
Mobo: ECS K7S5A Pro with Athlon XP 2000+, 512 MB RAM
kernel: gs-sources : 2.4.23_pre8
lm-sensors: I don't know because I don't have the PC here. I know that is the last stable, because I updated this morning the system with
emerge sync
emerge system
emerge world
ic2: the same
The problem: I can modprobe and I do
i2c-core
i2c-dev
i2c-proc
then I get an empty dir either under /dev/i2c , either under /proc/i2c
If I run sensors-detect I get a no /dev error with the suggestion of trying
to run some prog/mkdev.sh script, that I can't find on my hd.
I tried also to modprobe it81 that could be the sensor of my mobo and it
load, but there are no improvement in the previous behaviours.
sensors can't find any sensors.
I tried also to load manually all the modules under
/lib/modules/linux-2.4.23_pre8/kernel/drivers/i2c/bus.
After that sensors-detect works, but I get some nice kernel oops.
What can I try? Also a ponter to the right docs is really welcome.
Best regards,
Andrea |
|
| Back to top |
|
|
Braempje
l33t
Joined: 31 Jan 2003
Posts: 748
|
| Posted: Tue Jan 27, 2004 4:01 pm Post subject: Re: gs-sources kernel with ECS K7s5a Pro troubles |
|
|
I had to change mobo due to hardware problems, and now I have exactly same problem as andrea. I did a fresh install, put those modules there, but sensors-detect doesn't find a thing. There isn't even a /proc/i2c directory! There is a /dev/i2c directory, but that's empty.
My motherboard is an Intel D875PBZ.
_________________
Dictionary of the Flemish Sign Language - Woordenboek Vlaamse Gebarentaal |
|
| Back to top |
|
|
andrea_ferraris
n00b
Joined: 06 Jan 2004
Posts: 19
|
| Posted: Tue Jan 27, 2004 9:04 pm Post subject: Re: gs-sources kernel with ECS K7s5a Pro troubles |
|
|
| Braempje wrote: | I had to change mobo due to hardware problems, and now I have exactly same problem as andrea. I did a fresh install, put those modules there, but sensors-detect doesn't find a thing. There isn't even a /proc/i2c directory! There is a /dev/i2c directory, but that's empty.
My motherboard is an Intel D875PBZ. |
I'll have to read the lm-sensors docs, as suggested by the package install.
If you do lsmod what do you see? Are i2c-core, i2c-proc and i2c-dev loaded. I don't know, but I think that they are neede to have lm-sensors working. Anyway I have they loaded, but sensors-detect doesn't work, neither sensors. Now I installed the new kernel for gss-sources, I'll have to try again to installa lm-sensors.
Andrea |
|
| Back to top |
|
|
HermanR
Apprentice
Joined: 08 Jan 2004
Posts: 293
Location: The Netherlands
|
| Posted: Sat Jan 31, 2004 4:00 pm Post subject: can't access /proc file for writing |
|
|
I would like to access my sensors (CPU/MB temp etc.) through (Super)Karamba.
Thus far, I have lm_sensors working to the point that I get (apparently correct) readings when I run the 'sensors' program.
However, when I try to run 'sensors -s', as recommended everywhere, I get the following error messages:
| Code: |
as99127f-i2c-0-2d: Can't access /proc file for writing;
Run as root?
via686a-isa-e200: Can't access /proc file for writing;
Run as root?
|
And yes, I ran this as root! The /proc filesystem is available and there are relevant entries in /proc/sys/dev/sensors. There is no /proc/sensors, however.
As far as I understand it, Karamba uses the 'sensors' program to fetch it's readings. But 'sensors -s' is necessary to make labels such as 'temp1', etc., isn't it?
When I run 'sensors', I get the following output:
| Code: |
as99127f-i2c-0-2d
Adapter: SMBus Via Pro adapter at e800
Algorithm: Non-I2C SMBus adapter
VCore 1: +1.82 V (min = +1.66 V, max = +2.03 V)
VCore 2: +0.14 V (min = +1.66 V, max = +2.03 V) ALARM
+3.3V: +3.50 V (min = +2.98 V, max = +3.63 V)
+5V: +5.07 V (min = +4.52 V, max = +5.48 V)
+12V: +12.58 V (min = +10.83 V, max = +13.15 V)
-12V: -12.16 V (min = -15.06 V, max = -12.32 V) ALARM
-5V: -5.22 V (min = -5.49 V, max = -4.50 V)
fan1: 0 RPM (min = 3000 RPM, div = 2) ALARM
fan2: 4655 RPM (min = 3000 RPM, div = 2)
fan3: 0 RPM (min = 3000 RPM, div = 2) ALARM
M/B Temp: +44°C (limit = +60°C)
CPU Temp: +57.4°C (limit = +120°C, hysteresis = +100°C) (beep)
temp3: +224.4°C (limit = +120°C, hysteresis = +100°C)
vid: +1.850 V
alarms:
beep_enable:
Sound alarm enabled
via686a-isa-e200
Adapter: ISA adapter
Algorithm: ISA algorithm
CPU core: +3.02 V (min = +1.79 V, max = +2.18 V) ALARM
+2.5V: +3.02 V (min = +2.24 V, max = +2.74 V) ALARM
I/O: +3.35 V (min = +2.95 V, max = +3.62 V)
+5V: +6.28 V (min = +4.47 V, max = +5.49 V) ALARM
+12V: +15.22 V (min = +10.79 V, max = +13.18 V) ALARM
CPU Fan: 0 RPM (min = 3000 RPM, div = 2)
P/S Fan: 0 RPM (min = 3000 RPM, div = 2)
SYS Temp: -68.8°C (limit = +60°C, hysteresis = +50°C)
CPU Temp: -68.8°C (limit = +60°C, hysteresis = +50°C)
SBr Temp: +28.4°C (limit = +60°C, hysteresis = +50°C)
|
How do I get from here to correct readings in my Karamba theme? |
|
| Back to top |
|
|
snakattak3
Guru
Joined: 11 Dec 2002
Posts: 468
Location: Seattle
|
| Posted: Thu Feb 05, 2004 3:25 am Post subject: |
|
|
Ok...Got sensors almost working with 2.6.2 kernel. Here's the deal though, my sensors output is this | Code: | arusnak@Otto arusnak $ sensors
it87-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1: +1.53 V (min = +1.53 V, max = +1.87 V) ALARM
VCore 2: +1.61 V (min = +2.25 V, max = +2.75 V) ALARM
+3.3V: +6.10 V (min = +2.96 V, max = +3.60 V) ALARM
+5V: +5.04 V (min = +4.50 V, max = +5.48 V)
+12V: +0.00 V (min = +11.36 V, max = +13.80 V) ALARM
-12V: -27.36 V (min = -15.86 V, max = -13.40 V) ALARM
-5V: -13.64 V (min = -10.13 V, max = -9.44 V) ALARM
Stdby: +0.00 V (min = +4.50 V, max = +5.48 V) ALARM
VBat: +3.29 V
fan1: 0 RPM (min = 3000 RPM, div = 2) ALARM
fan2: 0 RPM (min = 3000 RPM, div = 2) ALARM
fan3: 0 RPM (min = 3000 RPM, div = 2) ALARM
ERROR: Can't get TEMP1 data!
ERROR: Can't get TEMP2 data!
ERROR: Can't get TEMP3 data! |
My temps aren't registering, and neither are my fans. I have these modules loaded | Code: | it87 20872 0
i2c_sensor 2560 1 it87
i2c_sis96x 4484 0
i2c_isa 1920 0
i2c_core 18692 4 it87,i2c_sensor,i2c_sis96x,i2c_isa |
Dmesg shows this... | Code: | i2c-sis96x version 1.0.0
sis96x smbus 0000:00:02.1: SiS96x SMBus base address: 0xe600 |
My motherboard is an Asus P4S533-VM. I can provide more info if needed, but I think thats about all. If you have a suggestion, don't hesitate. Thanks.
_________________
Ban Reality TV!
Adopt an Unanswered Post |
|
| Back to top |
|
|
wood
n00b
Joined: 06 Nov 2003
Posts: 30
|
| Posted: Thu Feb 05, 2004 3:12 pm Post subject: Some mobos... |
|
|
| That weird 200ºC to -200ºC sensor is wrong. It is probably not even a sensor but something your mb thinks is a temp sensor. Your cpu is very probably one of the others. Generaly there's one wacked, one hot (your cpu at 30-60), and one less hot (your mb chipset at 30-50)[/b] |
|
| Back to top |
|
|
Sp4rky
n00b
Joined: 10 Jul 2002
Posts: 15
|
| Posted: Fri Feb 06, 2004 5:44 pm Post subject: |
|
|
Very strange, sensors seems to be working oke:
| Code: |
s99127f-i2c-0-2d
Adapter: SMBus AMD75x adapter at e4e0
Algorithm: Non-I2C SMBus adapter
VCore 1: +1.70 V (min = +1.49 V, max = +1.81 V)
VCore 2: +1.68 V (min = +1.49 V, max = +1.81 V)
+3.3V: +3.38 V (min = +2.98 V, max = +3.63 V)
+5V: +5.07 V (min = +4.52 V, max = +5.48 V)
+12V: +12.27 V (min = +10.83 V, max = +13.15 V)
-12V: -3.26 V (min = -15.06 V, max = -12.32 V)
-5V: -0.57 V (min = -5.49 V, max = -4.50 V)
fan1: 4821 RPM (min = 3000 RPM, div = 2)
fan2: 4655 RPM (min = 3000 RPM, div = 2)
fan3: 3183 RPM (min = 3000 RPM, div = 2)
M/B Temp: +35°C (limit = +60°C)
CPU Temp: +44.4°C (limit = +120°C, hysteresis = +100°C) (beep)
temp3: +43.0°C (limit = +120°C, hysteresis = +100°C)
vid: +1.650 V
alarms:
beep_enable:
Sound alarm enabled
|
However, I cannot get gkrellm2 or ksensor or karamba to use the reading. For instance, gkrellm2 just has the options for sensors "gray" and cannot be chosen
Any ideas?
_________________
| Asus A7M266-D | dual XP2400+ t-bred | 1024Mb PC2100 REG ECC | Geforce4 Ti4600 |
| 3Ware 7006-2 | 2x WD800JB | LiteOn LTR-48125w | HEC-425VD-PT power | |
|
| Back to top |
|
|
HermanR
Apprentice
Joined: 08 Jan 2004
Posts: 293
Location: The Netherlands
|
| Posted: Sat Feb 07, 2004 9:08 pm Post subject: |
|
|
| Quote: | Very strange, sensors seems to be working oke:
...
However, I cannot get gkrellm2 or ksensor or karamba to use the reading. For instance, gkrellm2 just has the options for sensors "gray" and cannot be chosen
Any ideas? |
That sounds like the same problems I'm having. There is no /proc/sensors here, but the readings are okay in /proc/sys/dev/sensors. I cannot do 'sensors -s'.
I have not yet been able to solve this, but I have a workaround to get the readings into Karamba. Instead of 'sensor=sensor etc.', I use:
| Code: | | sensor=program program="echo `awk ' { print ($3) } ' /proc/sys/dev/sensors/as99127f-i2c-0-2d/temp1` °C" |
This works fine for me. But you'll have to adjust the raw readings yourself (for me, CPU temp is 2*temp2), for example.
Maybe this can help you. |
|
| Back to top |
|
|
Sp4rky
n00b
Joined: 10 Jul 2002
Posts: 15
|
| Posted: Tue Feb 10, 2004 5:40 pm Post subject: |
|
|
| HermanR wrote: |
That sounds like the same problems I'm having. There is no /proc/sensors here, but the readings are okay in /proc/sys/dev/sensors. I cannot do 'sensors -s'.
I have not yet been able to solve this, but I have a workaround to get the readings into Karamba. |
for some reason, ksensor DOES give me readings now, but gkrellm2 two does not. (Super)karamba now can show one temp (out of 3) en the 3 fans
not sure what is the problem. I cannot do sensors -s either.
Thinking maybe the labels aren't set correctly because of that?
_________________
| Asus A7M266-D | dual XP2400+ t-bred | 1024Mb PC2100 REG ECC | Geforce4 Ti4600 |
| 3Ware 7006-2 | 2x WD800JB | LiteOn LTR-48125w | HEC-425VD-PT power | |
|
| Back to top |
|
|
PaoloP
n00b
Joined: 03 Feb 2004
Posts: 14
|
| Posted: Thu Feb 12, 2004 4:32 pm Post subject: Re: can't access /proc file for writing |
|
|
| HermanR wrote: |
However, when I try to run 'sensors -s', as recommended everywhere, I get the following error messages:
| Code: |
as99127f-i2c-0-2d: Can't access /proc file for writing;
Run as root?
via686a-isa-e200: Can't access /proc file for writing;
Run as root?
|
And yes, I ran this as root! The /proc filesystem is available and there are relevant entries in /proc/sys/dev/sensors. There is no /proc/sensors, however. |
Has anyone looked into this yet? I have the same problem (kernel 2.4.22-gentoo-r5, latest stable i2c and lm_sensors, Gigabyte GA-7N400-L motherboard).
_________________
--
Paolo Pedroni |
|
| Back to top |
|
|
rollinncoaster
n00b
Joined: 10 Nov 2003
Posts: 13
|
| Posted: Fri Feb 20, 2004 3:53 pm Post subject: Voltage not detected... (SOLVED partially at least) |
|
|
Hi Folks,
I have a couple of question that I was unable to answer after reading this and several other posts.
I have an nforce2 motherboard (Soltek FRN2-L) with 1GB of OCZ-3200 performance series RAM.
I've installed lm_sensors following the directions on the installation thread and everything went ok, the only problem it that lm_sensors does not detect my voltage nor it does not scan the memory slots.
The output of 'sensors' is the following:
| Code: | lm90-i2c-0-4c
Adapter: SMBus nForce2 adapter at 5000
Algorithm: Non-I2C SMBus adapter
M/B Temp: +37°C (low = +5°C, high = +70°C)
CPU Temp: +39.8°C (low = +5.0°C, high = +70.0°C)
tcrit1: +85°C
tcrit2: +85°C
hyst: +10°C
pcf8591-i2c-0-4e
Adapter: SMBus nForce2 adapter at 5000
Algorithm: Non-I2C SMBus adapter
Chan. 0: 30
Chan. 1: 30
Chan. 2: 30
Chan. 3: 30
Output: 0 (enabled)
eeprom-i2c-0-50
Adapter: SMBus nForce2 adapter at 5000
Algorithm: Non-I2C SMBus adapter
Unknown EEPROM type (10)
eeprom-i2c-0-51
Adapter: SMBus nForce2 adapter at 5000
Algorithm: Non-I2C SMBus adapter
Unknown EEPROM type (10)
eeprom-i2c-0-52
Adapter: SMBus nForce2 adapter at 5000
Algorithm: Non-I2C SMBus adapter
Unknown EEPROM type (10) |
Also, 'sensors-detect' instructed me to load the following modules:
| Code: | MODULE_0=i2c-nforce2
MODULE_1=i2c-isa
MODULE_2=lm90
MODULE_3=pcf8591
MODULE_4=eeprom
MODULE_5=w83781d |
After looking the documentation for each of the sensors, I have no idea why the voltage sensors are not being detected. One thing that caught my attention is the fact that lm90 sensor only reports two temperatures. If that is the case 'w83791d' is supposed to handle the rest of the readings. However when looking at the /proc/sys//dev/sensors/ directory, I only have entries for the lm90, 3 eeprom's (3 memory slots), but no 'w83791d'. This one is not being recognized.
This is the directory listing:
| Code: | valentina sensors # pwd
/proc/sys/dev/sensors
valentina sensors # ls
chips eeprom-i2c-0-50 eeprom-i2c-0-51 eeprom-i2c-0-52 lm90-i2c-0-4c pcf8591-i2c-0-4e
valentina sensors # cd lm90-i2c-0-4c/
valentina lm90-i2c-0-4c # ls
alarms hyst tcrit1 tcrit2 temp1 temp2 |
My questions are:
Does anybody know why the memory probes are unsuccesful?
Why my voltage sensors are not being detected?
Any insight will be greatly appreciated.
If anybody wants to see the contentes of /proc/bus/*, here it is:
| Code: |
valentina bus # ls
i2c i2c-0 i2c-1 i2c-2 pci usb
valentina bus # cat i2c
i2c-0 smbus SMBus nForce2 adapter at 5000 Non-I2C SMBus adapter
i2c-1 smbus SMBus nForce2 adapter at 5100 Non-I2C SMBus adapter
i2c-2 dummy ISA main adapter ISA bus algorithm
valentina bus # cat i2c-0
4c LM90 chip LM90 sensor driver
4e PCF8591 chip PCF8591 sensor chip driver
50 EEPROM chip EEPROM READER
51 EEPROM chip EEPROM READER
52 EEPROM chip EEPROM READER
valentina bus # cat i2c-1
valentina bus # cat i2c-2
valentina bus #
|
Also, here is lsmod:
| Code: | valentina bus # lsmod
Module Size Used by Tainted: P
w83781d 23700 0 (unused)
eeprom 3572 0 (unused)
pcf8591 3172 0 (unused)
lm90 4472 0 (unused)
i2c-isa 716 0
i2c-nforce2 3368 0
i2c-dev 4640 0
floppy 47420 0 (autoclean)
i2c-proc 7060 0 [w83781d eeprom pcf8591 lm90]
i2c-core 15460 0 [w83781d eeprom pcf8591 lm90 i2c-isa i2c-nforce2 i2c-dev i2c-proc]
serial 48964 0 (autoclean)
isa-pnp 27824 0 (autoclean) [serial]
parport_pc 24552 1 (autoclean)
lp 6400 0 (autoclean)
parport 22728 1 (autoclean) [parport_pc lp]
usb-ohci 17416 0 (unused)
ehci-hcd 16108 0 (unused)
tulip 38304 1
snd-pcm-oss 34500 0 (unused)
snd-mixer-oss 10896 0 [snd-pcm-oss]
snd-intel8x0 16516 0 (autoclean)
snd-ac97-codec 35384 0 (autoclean) [snd-intel8x0]
snd-pcm 53028 0 (autoclean) [snd-pcm-oss snd-intel8x0]
snd-page-alloc 5620 0 (autoclean) [snd-intel8x0 snd-pcm]
snd-mpu401-uart 2704 0 (autoclean) [snd-intel8x0]
snd-rawmidi 12416 0 (autoclean) [snd-mpu401-uart]
snd-seq-oss 24096 0 (unused)
snd-seq-midi-event 3232 0 [snd-seq-oss]
snd-seq 30032 2 [snd-seq-oss snd-seq-midi-event]
snd-timer 12612 0 [snd-pcm snd-seq]
snd-seq-device 3728 0 [snd-rawmidi snd-seq-oss snd-seq]
snd 27908 0 [snd-pcm-oss snd-mixer-oss snd-intel8x0 snd-ac97-codec snd-pcm snd-mpu401-uart snd-rawmidi snd-seq-oss snd-seq-midi-event snd-seq snd-timer snd-seq-device]
soundcore 3364 6 [snd]
usbcore 56012 1 [usb-ohci ehci-hcd]
nvidia 1626496 11
valentina bus # |
If you need me to post any more info let me know, I'll post it.
Thanks.
----------------------------------
UPDATE:
Going back to the specs of my MB the chips that are supported are the
'lm90' and the 'w83627hf' not the 'w83781d' as detected by 'sensors-detect'.
It is on the FAQ for the lm_sensors package:
| Quote: | 4.17.5 Bad readings from a w8378[12]d!
Do you own an ASUS motherboard? Perhaps your chip is being misidentified. Look on the motherboard (or at http://mbm.livewiredev.com) for a 'Winbond' or Asus chip. Often the real device is an Asus as99127f. If so, the driver can be forced to recognize the as99127f with force_as99127f=BUS,0x2d where BUS is your i2c bus number. Cat /proc/bus/i2c to see a list of bus numbers. Read the w83781d module documentation (doc/chips/w83781d) for more details. |
All I had to do is remove the unneeded module and insert the appropiate one. Now 'sensors' shows:
| Code: |
same as before and ...
w83627hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1: +1.64 V (min = +1.48 V, max = +1.80 V)
VCore 2: +4.08 V (min = +1.48 V, max = +1.80 V)
+3.3V: +3.23 V (min = +2.97 V, max = +3.63 V)
+5V: +5.07 V (min = +4.50 V, max = +5.48 V)
+12V: +12.01 V (min = +10.79 V, max = +13.11 V)
-12V: -12.24 V (min = -13.21 V, max = -10.90 V)
-5V: -5.07 V (min = -5.51 V, max = -4.51 V)
V5SB: +5.58 V (min = +4.50 V, max = +5.48 V)
VBat: +1.50 V (min = +2.70 V, max = +3.29 V)
fan1: 0 RPM (min = 3000 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2)
fan3: 2191 RPM (min = 750 RPM, div = 8)
temp1: +39°C (limit = +60°C) sensor = thermistor
temp2: +40.0°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
temp3: +36.0°C (limit = +60°C, hysteresis = +50°C) sensor = thermistor
vid: +1.650 V
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled |
However, my memory is still not recognized. ANy ideas?
_________________
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." Rich Cook |
|
| Back to top |
|
|
lilvalo
n00b
Joined: 04 Jun 2003
Posts: 6
|
| Posted: Sun Feb 22, 2004 10:55 pm Post subject: lm-sensor dual p3 |
|
|
l440gx+ with p3 750mhz
mylex dac960 raid
it refuses to work
I did what I was supposed to:
| Code: | kernel/chips/max6650.c:115: error: initializer element is not constant
kernel/chips/max6650.c:115: error: (near initialization for `max6650_driver.id')
make: *** [kernel/chips/max6650.o] Error 1
make: *** Waiting for unfinished jobs....
!!! ERROR: sys-apps/lm-sensors-2.8.1 failed.
!!! Function src_compile, Line 84, Exitcode 2
!!! lm_sensors requires the source of a compatible kernel version in /usr/src/linux or specified in $LINUX and >=i2c-2.8.1 support built as modules. |
this is what i have in my kernel:
| Code: |
<*> I2C support
[*] I2C mainboard interfaces
<*> Intel 82801AA, AB, BA, DB
<*> Intel 82371AB PIIX4(E), 443MX, ServerWorks OSB4/CSB5, SMSC Vict
<*> Pseudo ISA adapter (for some hardware sensors)
<M> I2C device interface
<M> I2C /proc interface (required for hardware sensors)
|
yea i figured i had an intel board so i should have that in it.... thanks
valmiki |
|
| Back to top |
|
|
lilvalo
n00b
Joined: 04 Jun 2003
Posts: 6
|
| Posted: Mon Feb 23, 2004 1:20 pm Post subject: l440gx cont'd |
|
|
Well I actually got something to work. The modules get loaded and dmesg shows it detecting some stuff. but i can't get bmcsensors, eeprom, ds1621 to work, well the modules don't load.. So i had somehow gotten lm-sensors to compile before, so running the old sensors-detect generates the file with those, but I tried recompiling and it gives me the same error as in my post above.. Any help any one?
Thanks
Valmiki |
|
| Back to top |
|
|
ronmon
Veteran
Joined: 15 Apr 2002
Posts: 1043
Location: Key West, FL
|
| Posted: Mon Feb 23, 2004 5:17 pm Post subject: |
|
|
Hey Sp4rky,
I didn't see you mention what motherboard you are using, but the chipset seems to be the same as my A7M266-D. Like yours, using the stock /etc/sensors.conf, the -12v and -5v readings were hosed.
A while back, I found this file by googling and have tweaked a bit to suit my setup. It works much better now:
| Code: |
as99127f-i2c-0-2d
Adapter: SMBus AMD756 adapter at e4e0
VCore1: +1.78 V (min = +1.60 V, max = +1.86 V)
VCore2: +1.73 V (min = +1.60 V, max = +1.86 V)
+3.3V: +3.39 V (min = +3.14 V, max = +3.46 V)
+5V: +5.05 V (min = +4.73 V, max = +5.24 V)
+12V: +12.34 V (min = +11.37 V, max = +12.59 V)
CPU0 Fan: 3629 RPM (min = 1997 RPM, div = 4)
CPU1 Fan: 3479 RPM (min = 1997 RPM, div = 4)
PSU Fan: 2934 RPM (min = 1500 RPM, div = 4)
M/B Temp: +37°C (high = +45°C, hyst = +42°C)
CPU0 Temp: +52.0°C (high = +60°C, hyst = +57°C)
CPU1 Temp: +54.0°C (high = +60°C, hyst = +57°C)
VID: +1.750 V
|
Though 'sensors' reports correctly, as above, a few kernel versions back it became necessary to set the temperature divisor to 1/10th of its normal value in my gkrellm2 configuration. I'm pretty sure it is kernel related and not lm-sensors. My current version is lm-sensors-2.8.4. |
|
| Back to top |
|
|
Death Barrel
n00b
Joined: 12 Feb 2004
Posts: 65
|
| Posted: Mon Feb 23, 2004 9:30 pm Post subject: |
|
|
hi
gigabyte ga7vt600-l , VIA KT600, gentoo-sources 2.4.22 >> and gentoo-dev-sources-2.6.2
i compiled my kernel just like you said adding the ic2 supports as modules
then i emerged i2c lm-sensors gkrellm
then i did a sensors-detect and this is what i got:
| Code: | root # sensors-detect
No i2c device files found. Use prog/mkdev/mkdev.sh to create them. |
i then tried prog/mkdev/mkdev.sh but really don't know where that is or if that is what i need to do... any help would be nice 
DB |
|
| Back to top |
|
|
|
|
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
|
|
Kernel & Hardware
