lm_sensors, be6, rh9?
- Thread starter Marcello
- Start date
- Status
- Joined
- Jun 6, 2003
- Messages
- 690
- Reaction score
- 0
On Mon, 21 Jul 2003 15:36:14 +0000, Marcello wrote:
I've got them installed on Mandrake on a couple of different boards, but i don't use Intel. Sometimes the sensors-detect returns the wrong info, as it does on my latest board, so it helps to know what sensor chip the board has. What kind of problem are you having? I'll try and help.
I've got them installed on Mandrake on a couple of different boards, but i don't use Intel. Sometimes the sensors-detect returns the wrong info, as it does on my latest board, so it helps to know what sensor chip the board has. What kind of problem are you having? I'll try and help.
Wes Newell ha scritto:
I have a be6 with celeron cpu, untill now I haven't any problem installing something. So I tried to install lm_sensors to let gkrellm show cpu temperature. I think I have well installed i2c-2.0.8 and then lm_sensors-2.8.0. So I have tried sensors-detect (and lsmod to see the changes) to set fine lines in /etc/modules.conf:
[root@localhost lm_sensors-2.8.0]$ lsmod
Module Size Used by Not tainted
ide-cd 35708 0 (autoclean)
cdrom 33728 0 (autoclean) [ide-cd]
emu10k1 69032 1 (autoclean)
ac97_codec 13640 0 (autoclean) [emu10k1]
sound 74228 0 (autoclean) [emu10k1]
soundcore 6404 7 (autoclean) [emu10k1 sound] radeon 116132 10 agpgart 47776 3 parport_pc 19076 1 (autoclean) lp 8996 0 (autoclean) parport 37056 1 (autoclean) [parport_pc lp] autofs 13268 0 (autoclean) (unused) 8139too 18088 1 mii 3976 0 [8139too] ipt_REJECT 3928 2 (autoclean) iptable_filter 2412 1 (autoclean) ip_tables 15096 2 [ipt_REJECT iptable_filter] microcode 4668 0 (autoclean) nls_cp437 5116 2 (autoclean) vfat 13004 2 (autoclean) fat 38808 0 (autoclean) [vfat] nls_iso8859-1 3516 3 (autoclean) ntfs 59008 1 (autoclean) loop 12152 0 (autoclean) lvm-mod 64000 0 keybdev 2944 0 (unused) mousedev 5492 1 hid 22148 0 (unused) input 5856 0 [keybdev mousedev hid] usb-uhci 26348 0 (unused) usbcore 78784 1 [hid usb-uhci]
[root@localhost lm_sensors-2.8.0]# prog/detect/sensors-detect This program will help you to determine which I2C/SMBus modules you need to load to use lm_sensors most effectively. You need to have done a `make install', issued a `depmod -a' and made sure `/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate module path before you can use some functions of this utility. Read doc/modules for more information. Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files for some things. You can use prog/mkdev/mkdev.sh to create these /dev files if you do not have them already. 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.
BIOS vendor (ACPI): ABIT
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-piix4' for device 00:07.3: Intel 82371AB PIIX4 ACPI Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-piix4' (say NO if built into your kernel)? (YES/no):
/lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o: unresolved symbol dmi_scan_mach /lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o: insmod /lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o failed /lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o: insmod i2c-piix4 failed Loading failed... skipping. 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. That often includes address 0x69 (clock chip).
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):
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. Do you want to scan for Super I/O sensors? (YES/no):
Probing for `SMSC 47M1xx 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 W83697HF Super IO Sensors'
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/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.
[root@localhost lm_sensors-2.8.0]# lsmod
Module Size Used by Not tainted
i2c-dev 4992 0 (unused)
i2c-core 19556 0 [i2c-dev]
ide-cd 35708 0 (autoclean)
cdrom 33728 0 (autoclean) [ide-cd]
emu10k1 69032 2 (autoclean)
ac97_codec 13640 0 (autoclean) [emu10k1] sound 74228 0 (autoclean) [emu10k1] soundcore 6404 7 (autoclean) [emu10k1 sound] radeon 116132 10 agpgart 47776 3 parport_pc 19076 1 (autoclean) lp 8996 0 (autoclean) parport 37056 1 (autoclean) [parport_pc lp] autofs 13268 0 (autoclean) (unused) 8139too 18088 1 mii 3976 0 [8139too] ipt_REJECT 3928 2 (autoclean) iptable_filter 2412 1 (autoclean) ip_tables 15096 2 [ipt_REJECT iptable_filter] microcode 4668 0 (autoclean) nls_cp437 5116 2 (autoclean) vfat 13004 2 (autoclean) fat 38808 0 (autoclean) [vfat] nls_iso8859-1 3516 3 (autoclean) ntfs 59008 1 (autoclean) loop 12152 0 (autoclean) lvm-mod 64000 0 keybdev 2944 0 (unused) mousedev 5492 1 hid 22148 0 (unused) input 5856 0 [keybdev mousedev hid] usb-uhci 26348 0 (unused) usbcore 78784 1 [hid usb-uhci]
As you can see two modules were loaded (i2c-dev and i2c-core) after detecting, but no chips were detected. So I have tried to see on http://mbm.livewiredev.com/ and my mb has W83783S chip, which is not supported on http://secure.netroedge.com/~lm78/newdrivers.html, even if they say one can force...
Thx Newell for trying!
I hope we can solve some way.
Bye Marcello.
I have a be6 with celeron cpu, untill now I haven't any problem installing something. So I tried to install lm_sensors to let gkrellm show cpu temperature. I think I have well installed i2c-2.0.8 and then lm_sensors-2.8.0. So I have tried sensors-detect (and lsmod to see the changes) to set fine lines in /etc/modules.conf:
[root@localhost lm_sensors-2.8.0]$ lsmod
Module Size Used by Not tainted
ide-cd 35708 0 (autoclean)
cdrom 33728 0 (autoclean) [ide-cd]
emu10k1 69032 1 (autoclean)
ac97_codec 13640 0 (autoclean) [emu10k1]
sound 74228 0 (autoclean) [emu10k1]
soundcore 6404 7 (autoclean) [emu10k1 sound] radeon 116132 10 agpgart 47776 3 parport_pc 19076 1 (autoclean) lp 8996 0 (autoclean) parport 37056 1 (autoclean) [parport_pc lp] autofs 13268 0 (autoclean) (unused) 8139too 18088 1 mii 3976 0 [8139too] ipt_REJECT 3928 2 (autoclean) iptable_filter 2412 1 (autoclean) ip_tables 15096 2 [ipt_REJECT iptable_filter] microcode 4668 0 (autoclean) nls_cp437 5116 2 (autoclean) vfat 13004 2 (autoclean) fat 38808 0 (autoclean) [vfat] nls_iso8859-1 3516 3 (autoclean) ntfs 59008 1 (autoclean) loop 12152 0 (autoclean) lvm-mod 64000 0 keybdev 2944 0 (unused) mousedev 5492 1 hid 22148 0 (unused) input 5856 0 [keybdev mousedev hid] usb-uhci 26348 0 (unused) usbcore 78784 1 [hid usb-uhci]
[root@localhost lm_sensors-2.8.0]# prog/detect/sensors-detect This program will help you to determine which I2C/SMBus modules you need to load to use lm_sensors most effectively. You need to have done a `make install', issued a `depmod -a' and made sure `/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate module path before you can use some functions of this utility. Read doc/modules for more information. Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files for some things. You can use prog/mkdev/mkdev.sh to create these /dev files if you do not have them already. 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.
BIOS vendor (ACPI): ABIT
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-piix4' for device 00:07.3: Intel 82371AB PIIX4 ACPI Probe succesfully concluded.
We will now try to load each adapter module in turn.
Load `i2c-piix4' (say NO if built into your kernel)? (YES/no):
/lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o: unresolved symbol dmi_scan_mach /lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o: insmod /lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o failed /lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o: insmod i2c-piix4 failed Loading failed... skipping. 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. That often includes address 0x69 (clock chip).
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):
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. Do you want to scan for Super I/O sensors? (YES/no):
Probing for `SMSC 47M1xx 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 W83697HF Super IO Sensors'
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/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.
[root@localhost lm_sensors-2.8.0]# lsmod
Module Size Used by Not tainted
i2c-dev 4992 0 (unused)
i2c-core 19556 0 [i2c-dev]
ide-cd 35708 0 (autoclean)
cdrom 33728 0 (autoclean) [ide-cd]
emu10k1 69032 2 (autoclean)
ac97_codec 13640 0 (autoclean) [emu10k1] sound 74228 0 (autoclean) [emu10k1] soundcore 6404 7 (autoclean) [emu10k1 sound] radeon 116132 10 agpgart 47776 3 parport_pc 19076 1 (autoclean) lp 8996 0 (autoclean) parport 37056 1 (autoclean) [parport_pc lp] autofs 13268 0 (autoclean) (unused) 8139too 18088 1 mii 3976 0 [8139too] ipt_REJECT 3928 2 (autoclean) iptable_filter 2412 1 (autoclean) ip_tables 15096 2 [ipt_REJECT iptable_filter] microcode 4668 0 (autoclean) nls_cp437 5116 2 (autoclean) vfat 13004 2 (autoclean) fat 38808 0 (autoclean) [vfat] nls_iso8859-1 3516 3 (autoclean) ntfs 59008 1 (autoclean) loop 12152 0 (autoclean) lvm-mod 64000 0 keybdev 2944 0 (unused) mousedev 5492 1 hid 22148 0 (unused) input 5856 0 [keybdev mousedev hid] usb-uhci 26348 0 (unused) usbcore 78784 1 [hid usb-uhci]
As you can see two modules were loaded (i2c-dev and i2c-core) after detecting, but no chips were detected. So I have tried to see on http://mbm.livewiredev.com/ and my mb has W83783S chip, which is not supported on http://secure.netroedge.com/~lm78/newdrivers.html, even if they say one can force...
Thx Newell for trying!
I hope we can solve some way.
Bye Marcello.
- Joined
- Jun 6, 2003
- Messages
- 690
- Reaction score
- 0
On Tue, 22 Jul 2003 09:05:57 +0000, Marcello wrote:
chip "w83782d-*" "w83783s-*" "w83627hf-*"
# Same as above for w83781d except that in5 and in6 are computed differently. # Rather than an internal inverting op amp, the 82d/83s use standard positive # inputs and the negative voltages are level shifted by a 3.6V reference. # The math is convoluted, so we hope that your motherboard # uses the recommended resistor values.
If it does, you should be able to manually insert what you need. Mandrakes rc.init calls rc.serial, so I put this in rc.serial;
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83781d
Change w83781d to w83783s for your MB.
Also needed this in modules.conf
# I2C module options
alias char-major-89 i2c-dev
That along with the sensors.conf file were all I needed to get mine going. I edited sensors.conf afterward for what I wanted to show and some of the calculations. You may need some of the others too. Load all that you think you might need, then weed them out 1 at a time. That's what I did. Here's relevent modules modules I have loaded.
w83781d 21872 0
i2c-proc 9104 0 [w83781d]
i2c-isa 1928 0 (unused)
i2c-core 21224 0 [w83781d i2c-proc i2c-isa]
Be sure and run sensors -s to set them. Here's what i get with sensors.
[wes@wes2 wes]$ sensors
w83697hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore: +1.61 V (min = +0.00 V, max = +0.00 V)
+3.3V: +3.28 V (min = +2.97 V, max = +3.63 V)
+5V: +5.04 V (min = +4.50 V, max = +5.48 V)
+12V: +12.30 V (min = +11.64 V, max = +14.14 V)
V5SB: +5.06 V (min = +4.34 V, max = +5.28 V)
VBat: +3.45 V (min = +2.70 V, max = +3.29 V)
fan1: 5357 RPM (min = 3000 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2)
CPU: +31�C (limit = +60�C) sensor = thermistor
MB: +30.5�C (limit = +60�C, hysteresis = +50�C) sensor = thermistor alarms:
beep_enable:
Sound alarm disabled
[wes@wes2 wes]$
They were more, but I got rid of the -minus voltages. Hmmm... I haven't set mine yet since last boot. Here's the diff.
[root@wes2 wes]# sensors -s
[root@wes2 wes]# sensors
w83697hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore: +1.60 V (min = +1.42 V, max = +1.93 V)
+3.3V: +3.29 V (min = +3.13 V, max = +3.45 V)
+5V: +5.11 V (min = +4.72 V, max = +5.24 V)
+12V: +12.14 V (min = +10.74 V, max = +13.16 V)
V5SB: +5.05 V (min = +4.73 V, max = +5.24 V)
VBat: +3.45 V (min = +2.40 V, max = +3.60 V)
fan1: 5400 RPM (min = 3000 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2)
CPU: +31�C (limit = +60�C, hysteresis = +55�C) sensor = thermistor
MB: +30.5�C (limit = +42�C, hysteresis = +40�C) sensor = thermistor alarms:
beep_enable:
Sound alarm disabled
[root@wes2 wes]#
Good luck. LM sensors was probably the hardest thing I dealt with in Linux. Every time I tried sensors-detect it spewed out the wrong info. It took me a week to get it working when I tfirst tried installing it on the Abit KT7 board. It was all greek to me. And the new sis746fx board sensors detect showed I needed to load a sis module. That was BS too, but I was wise to it this time.
It appears that it didn't even try and probe for your sensor chip. I'm using version 2.7.0 and it supports your chip in the config. Check your sensors.conf file and see if it has this in it.
chip "w83782d-*" "w83783s-*" "w83627hf-*"
# Same as above for w83781d except that in5 and in6 are computed differently. # Rather than an internal inverting op amp, the 82d/83s use standard positive # inputs and the negative voltages are level shifted by a 3.6V reference. # The math is convoluted, so we hope that your motherboard # uses the recommended resistor values.
If it does, you should be able to manually insert what you need. Mandrakes rc.init calls rc.serial, so I put this in rc.serial;
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83781d
Change w83781d to w83783s for your MB.
Also needed this in modules.conf
# I2C module options
alias char-major-89 i2c-dev
That along with the sensors.conf file were all I needed to get mine going. I edited sensors.conf afterward for what I wanted to show and some of the calculations. You may need some of the others too. Load all that you think you might need, then weed them out 1 at a time. That's what I did.
Here's relevent modules modules I have loaded.w83781d 21872 0
i2c-proc 9104 0 [w83781d]
i2c-isa 1928 0 (unused)
i2c-core 21224 0 [w83781d i2c-proc i2c-isa]
Be sure and run sensors -s to set them. Here's what i get with sensors.
[wes@wes2 wes]$ sensors
w83697hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore: +1.61 V (min = +0.00 V, max = +0.00 V)
+3.3V: +3.28 V (min = +2.97 V, max = +3.63 V)
+5V: +5.04 V (min = +4.50 V, max = +5.48 V)
+12V: +12.30 V (min = +11.64 V, max = +14.14 V)
V5SB: +5.06 V (min = +4.34 V, max = +5.28 V)
VBat: +3.45 V (min = +2.70 V, max = +3.29 V)
fan1: 5357 RPM (min = 3000 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2)
CPU: +31�C (limit = +60�C) sensor = thermistor
MB: +30.5�C (limit = +60�C, hysteresis = +50�C) sensor = thermistor alarms:
beep_enable:
Sound alarm disabled
[wes@wes2 wes]$
They were more, but I got rid of the -minus voltages. Hmmm... I haven't set mine yet since last boot. Here's the diff.
[root@wes2 wes]# sensors -s
[root@wes2 wes]# sensors
w83697hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore: +1.60 V (min = +1.42 V, max = +1.93 V)
+3.3V: +3.29 V (min = +3.13 V, max = +3.45 V)
+5V: +5.11 V (min = +4.72 V, max = +5.24 V)
+12V: +12.14 V (min = +10.74 V, max = +13.16 V)
V5SB: +5.05 V (min = +4.73 V, max = +5.24 V)
VBat: +3.45 V (min = +2.40 V, max = +3.60 V)
fan1: 5400 RPM (min = 3000 RPM, div = 2)
fan2: 0 RPM (min = 3000 RPM, div = 2)
CPU: +31�C (limit = +60�C, hysteresis = +55�C) sensor = thermistor
MB: +30.5�C (limit = +42�C, hysteresis = +40�C) sensor = thermistor alarms:
beep_enable:
Sound alarm disabled
[root@wes2 wes]#
Good luck. LM sensors was probably the hardest thing I dealt with in Linux. Every time I tried sensors-detect it spewed out the wrong info. It took me a week to get it working when I tfirst tried installing it on the Abit KT7 board. It was all greek to me. And the new sis746fx board sensors detect showed I needed to load a sis module. That was BS too, but I was wise to it this time.
Wes Newell ha scritto:
this is lsmod:
[root@localhost Marcello]# lsmod
Module Size Used by Not tainted
i2c-isa 1292 0
w83781d 24592 0 (unused)
i2c-proc 7988 0 [w83781d]
i2c-dev 4992 0
i2c-core 19556 0 [i2c-isa w83781d i2c-proc i2c-dev] ide-cd 35708 0 (autoclean) cdrom 33728 0 (autoclean) [ide-cd] emu10k1 69032 1 (autoclean) ac97_codec 13640 0 (autoclean) [emu10k1] sound 74228 0 (autoclean) [emu10k1] soundcore 6404 7 (autoclean) [emu10k1 sound] radeon 116132 11 agpgart 47776 3 parport_pc 19076 1 (autoclean) lp 8996 0 (autoclean) parport 37056 1 (autoclean) [parport_pc lp] autofs 13268 0 (autoclean) (unused) 8139too 18088 1 mii 3976 0 [8139too] ipt_REJECT 3928 2 (autoclean) iptable_filter 2412 1 (autoclean) ip_tables 15096 2 [ipt_REJECT iptable_filter] microcode 4668 0 (autoclean) nls_cp437 5116 2 (autoclean) vfat 13004 2 (autoclean) fat 38808 0 (autoclean) [vfat] nls_iso8859-1 3516 3 (autoclean) ntfs 59008 1 (autoclean) loop 12152 0 (autoclean) lvm-mod 64000 0 keybdev 2944 0 (unused) mousedev 5492 1 hid 22148 0 (unused) input 5856 0 [keybdev mousedev hid] usb-uhci 26348 0 (unused) usbcore 78784 1 [hid usb-uhci]
and now I can see something with this:
[root@localhost Marcello]# /usr/sbin/i2cdetect
Error: No i2c-bus specified!
Syntax: i2cdetect I2CBUS
I2CBUS is an integer
Installed I2C busses:
i2c-0 dummy ISA main adapter
ISA bus algorithm
but still nothing:
[root@localhost Marcello]# sensors -s
No sensors found!
[root@localhost Marcello]# sensors
No sensors found!
[root@localhost Marcello]#
So how go on?
Thx so much Newell!
Marcello.
I have added this line and rem that before
I have insert these two modules from terminal
and added this line
That along with the sensors.conf file were all I needed to get mine going. I edited sensors.conf afterward for what I wanted to show and some of the calculations. You may need some of the others too. Load all that you think you might need, then weed them out 1 at a time. That's what I did.
w83781d 21872 0
i2c-proc 9104 0 [w83781d]
i2c-isa 1928 0 (unused)
i2c-core 21224 0 [w83781d i2c-proc i2c-isa]
Be sure and run sensors -s to set them. Here's what i get with sensors.
this is lsmod:
[root@localhost Marcello]# lsmod
Module Size Used by Not tainted
i2c-isa 1292 0
w83781d 24592 0 (unused)
i2c-proc 7988 0 [w83781d]
i2c-dev 4992 0
i2c-core 19556 0 [i2c-isa w83781d i2c-proc i2c-dev] ide-cd 35708 0 (autoclean) cdrom 33728 0 (autoclean) [ide-cd] emu10k1 69032 1 (autoclean) ac97_codec 13640 0 (autoclean) [emu10k1] sound 74228 0 (autoclean) [emu10k1] soundcore 6404 7 (autoclean) [emu10k1 sound] radeon 116132 11 agpgart 47776 3 parport_pc 19076 1 (autoclean) lp 8996 0 (autoclean) parport 37056 1 (autoclean) [parport_pc lp] autofs 13268 0 (autoclean) (unused) 8139too 18088 1 mii 3976 0 [8139too] ipt_REJECT 3928 2 (autoclean) iptable_filter 2412 1 (autoclean) ip_tables 15096 2 [ipt_REJECT iptable_filter] microcode 4668 0 (autoclean) nls_cp437 5116 2 (autoclean) vfat 13004 2 (autoclean) fat 38808 0 (autoclean) [vfat] nls_iso8859-1 3516 3 (autoclean) ntfs 59008 1 (autoclean) loop 12152 0 (autoclean) lvm-mod 64000 0 keybdev 2944 0 (unused) mousedev 5492 1 hid 22148 0 (unused) input 5856 0 [keybdev mousedev hid] usb-uhci 26348 0 (unused) usbcore 78784 1 [hid usb-uhci]
and now I can see something with this:
[root@localhost Marcello]# /usr/sbin/i2cdetect
Error: No i2c-bus specified!
Syntax: i2cdetect I2CBUS
I2CBUS is an integer
Installed I2C busses:
i2c-0 dummy ISA main adapter
ISA bus algorithm
but still nothing:
[root@localhost Marcello]# sensors -s
No sensors found!
[root@localhost Marcello]# sensors
No sensors found!
[root@localhost Marcello]#
So how go on?
Thx so much Newell!
Marcello.
Marcello ha scritto:
[root@localhost Marcello]# depmod
depmod: *** Unresolved symbols in
/lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o [root@localhost Marcello]# depmod -a depmod: *** Unresolved symbols in /lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o [root@localhost Marcello]#
I add these lines (Idon't know if they are important):
[root@localhost Marcello]# depmod
depmod: *** Unresolved symbols in
/lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o [root@localhost Marcello]# depmod -a depmod: *** Unresolved symbols in /lib/modules/2.4.20-8/kernel/drivers/i2c/busses/i2c-piix4.o [root@localhost Marcello]#
- Joined
- Jun 6, 2003
- Messages
- 690
- Reaction score
- 0
On Tue, 22 Jul 2003 21:06:04 +0000, Marcello wrote:
Here's the rest of it;
label in0 "VCore 1"
label in1 "VCore 2"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
label in5 "-12V"
label in6 "-5V"
label in7 "V5SB"
label in8 "VBat"
compute in3 ((6.8/10)+1)*@ , @/((6.8/10)+1)
compute in4 ((28/10)+1)*@ , @/((28/10)+1)
compute in5 (5.14 * @) - 14.91 , (@ + 14.91) / 5.14 compute in6 (3.14 * @) - 7.71 , (@ + 7.71) / 3.14 compute in7 ((6.8/10)+1)*@ , @/((6.8/10)+1)
# adjust this if your vid is wrong; see doc/vid
# set vrm 9.0
# set limits to 5% for the critical voltages
# set limits to 10% for the non-critical voltages
# set limits to 20% for the battery voltage
set in0_min vid*0.95
set in0_max vid*1.05
set in1_min vid*0.95
set in1_max vid*1.05
set in2_min 3.3 * 0.95
set in2_max 3.3 * 1.05
set in3_min 5.0 * 0.95
set in3_max 5.0 * 1.05
set in4_min 12 * 0.90
set in4_max 12 * 1.10
set in5_max -12 * 0.90
set in5_min -12 * 1.10
set in6_max -5 * 0.95
set in6_min -5 * 1.05
set in7_min 5 * 0.95
set in7_max 5 * 1.05
set in8_min 3.0 * 0.80
set in8_max 3.0 * 1.20
# set up sensor types (thermistor is default)
# 1 = PII/Celeron Diode; 2 = 3904 transistor;
# 3435 = thermistor with Beta = 3435
# If temperature changes very little, try 1 or 2.
# set sensor1 1
# set sensor2 2
# set sensor3 3435
# examples for temperature limits
# set temp1_over 40
# set temp1_hyst 37
# set temp2_over 52
# set temp2_hyst 47
# set temp3_over 52
# set temp3_hyst 47
Add the above below the chip line and try again.
There's more than one line to it.
Here's the rest of it;
label in0 "VCore 1"
label in1 "VCore 2"
label in2 "+3.3V"
label in3 "+5V"
label in4 "+12V"
label in5 "-12V"
label in6 "-5V"
label in7 "V5SB"
label in8 "VBat"
compute in3 ((6.8/10)+1)*@ , @/((6.8/10)+1)
compute in4 ((28/10)+1)*@ , @/((28/10)+1)
compute in5 (5.14 * @) - 14.91 , (@ + 14.91) / 5.14 compute in6 (3.14 * @) - 7.71 , (@ + 7.71) / 3.14 compute in7 ((6.8/10)+1)*@ , @/((6.8/10)+1)
# adjust this if your vid is wrong; see doc/vid
# set vrm 9.0
# set limits to 5% for the critical voltages
# set limits to 10% for the non-critical voltages
# set limits to 20% for the battery voltage
set in0_min vid*0.95
set in0_max vid*1.05
set in1_min vid*0.95
set in1_max vid*1.05
set in2_min 3.3 * 0.95
set in2_max 3.3 * 1.05
set in3_min 5.0 * 0.95
set in3_max 5.0 * 1.05
set in4_min 12 * 0.90
set in4_max 12 * 1.10
set in5_max -12 * 0.90
set in5_min -12 * 1.10
set in6_max -5 * 0.95
set in6_min -5 * 1.05
set in7_min 5 * 0.95
set in7_max 5 * 1.05
set in8_min 3.0 * 0.80
set in8_max 3.0 * 1.20
# set up sensor types (thermistor is default)
# 1 = PII/Celeron Diode; 2 = 3904 transistor;
# 3435 = thermistor with Beta = 3435
# If temperature changes very little, try 1 or 2.
# set sensor1 1
# set sensor2 2
# set sensor3 3435
# examples for temperature limits
# set temp1_over 40
# set temp1_hyst 37
# set temp2_over 52
# set temp2_hyst 47
# set temp3_over 52
# set temp3_hyst 47
Add the above below the chip line and try again.
- Joined
- Jun 6, 2003
- Messages
- 690
- Reaction score
- 0
On Tue, 22 Jul 2003 21:08:16 +0000, Marcello wrote:
When it comes to depmod you're own your own. I haven't messed with it at all. This may have something to do with the config file not beling complete. i really don't know.
When it comes to depmod you're own your own. I haven't messed with it at all. This may have something to do with the config file not beling complete. i really don't know.
- Joined
- Jun 6, 2003
- Messages
- 690
- Reaction score
- 0
On Wed, 23 Jul 2003 13:25:06 +0000, Marcello wrote:
Try a google search. You might get lucky and find something for your board. Many people have problems configuring lm_sensors. Yep, over 300 searching sensors be6. One of those messages will surely help.
I've tried, but always the same message:
[root@localhost Marcello]# sensors -s No sensors found! [root@localhost Marcello]# sensors No sensors found!
Thx Newell!
Ciao,
Marcello.
Try a google search. You might get lucky and find something for your board. Many people have problems configuring lm_sensors. Yep, over 300 searching sensors be6. One of those messages will surely help.
- Status
Latest threads
-
What's the weirdest fix you ever found for a no POST?- Started by Shaggy
- Replies: 0
-
-
AM5 or Intel for a new build right now?
- Started by Shaggy
- Replies: 0
-
What motherboard is in your main rig right now?
- Started by Shaggy
- Replies: 0
-