View previous topic :: View next topic |
Author |
Message |
maalth Tux's lil' helper
Joined: 06 Jun 2003 Posts: 76 Location: Can't tell you...
|
Posted: Sat Dec 13, 2003 10:33 pm Post subject: IBM Thinkpads and lm_sensors |
|
|
If you have an IBM Thinkpad (any model), do NOT use lm_sensors under any circumstances. |
|
Back to top |
|
|
marshall_j Tux's lil' helper
Joined: 22 Jan 2003 Posts: 98 Location: NZ
|
Posted: Sun Dec 14, 2003 4:15 am Post subject: Re: IBM Thinkpads and lm_sensors |
|
|
maalth wrote: | If you have an IBM Thinkpad (any model), do NOT use lm_sensors under any circumstances. |
Why's that?! |
|
Back to top |
|
|
kaare n00b
Joined: 21 Sep 2003 Posts: 30
|
Posted: Sun Dec 14, 2003 11:38 pm Post subject: |
|
|
Hey!
This info is great!.
I'm wondering if there is a app out there that can output the sensors info to web?
The ones I found doesn't support my chip (amd756). |
|
Back to top |
|
|
rollinncoaster n00b
Joined: 10 Nov 2003 Posts: 13
|
Posted: Sat Jan 10, 2004 4:18 pm Post subject: For some via chipset motherboards (MS-6378X-L) |
|
|
If you get this error message:
#sensors-detect
#No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
Download the source, untar it. And run the mkdev.sh script to create the necessary device files in order to let sensors-detect do its job.
Perhaps a change in the ebuild??
Hope this helps.
RC _________________ 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 |
|
|
charlesnadeau Apprentice
Joined: 19 May 2003 Posts: 205 Location: Ottawa, Ontario, Canada
|
Posted: Tue Jan 13, 2004 3:25 am Post subject: Re: Monitor CPU Temperature with lm_sensors and gkrellm |
|
|
smokeslikeapoet wrote: |
Making It Work
When compilling your kernel in the Character Devices section enable I2C Support , I2C device interface, and I2C /proc interface, as modules. If you have a tvtuner card, like I do, you already have probably already enabled these options. If you haven't already enabled them all you have to do is:
Code: | # make modules && make modules_install |
After compilling your kernel do the following
Code: | emerge i2c lm-sensors gkrellm |
|
If I recompile my kernel, do I have to re-emerge i2c lm-sensors and gkrellm? If so it would be like for alsa-driver.
Thanks!
Charles _________________ Charles Nadeau
http://radio.weblogs.com/0111823/
http://charlesnadeau.blogspot.com/search/label/Gentoo |
|
Back to top |
|
|
bammbamm808 Guru
Joined: 08 Dec 2002 Posts: 548 Location: Hawaii
|
Posted: Tue Jan 13, 2004 8:27 am Post subject: Well I've gotten it working |
|
|
Followed your guide. 2.8.1 wouldn't give me any temperatures, so I unmerged and emerge 2.8.2 and there it was. Thanks. I've always installed from the vanilla sources rather than emerge, but for some reason the "make, make install..." method wouldn't work this time. At least portage was there to bail me out. _________________ 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 |
|
|
berus Guru
Joined: 28 Dec 2003 Posts: 347 Location: Italy
|
Posted: Sun Feb 15, 2004 5:36 pm Post subject: |
|
|
barlad wrote: | Hey guys,
- The module is in ~/lmsensors/prog/hotplug/ so do
Code: | cd ~/lmsensors/prog/hotplug |
- Let's fix the sources. Edit the p4b_smbus.c file.
Modify the line 263 that reads:
Code: | write_lock_irqsave(i801smbus_lock, i801smbus_lock_flags); |
with:
Code: | write_lock_irqsave(&i801smbus_lock, i801smbus_lock_flags); |
Modify the line 268 that reads:
Code: | write_unlock_irqrestore(i801smbus_lock, i801smbus_lock_flags); |
with: Code: | write_unlock_irqrestore(&i801smbus_lock, i801smbus_lock_flags); |
- We are ready to compile the module now.
Code: | make -f Makefile.p4B |
Now you should have a file called p4b_smbus.o.
|
Hi, sorry form my english!
A follow this instructions ma after Code: | make -f Makefile.p4B | I have this error Code: | p4b_smbus.c: At top level:
p4b_smbus.c:277: warning: type defaults to `int' in declaration of `EXPORT_NO_SYMBOLS'
p4b_smbus.c:277: warning: data definition has no type or storage class
make: *** [p4b_smbus.o] Error 1
|
Someone can help me? I have a ASUS P4G8X and "hot-pluggable devices" is build in the kernel.. |
|
Back to top |
|
|
berus Guru
Joined: 28 Dec 2003 Posts: 347 Location: Italy
|
Posted: Mon Feb 16, 2004 8:13 pm Post subject: |
|
|
Any idea? Can depends by the gcc version?
Quote: | gcc version 3.3.2 20040119 (Gentoo Linux 3.3.2-r7, propolice-3.3-7)
|
|
|
Back to top |
|
|
berus Guru
Joined: 28 Dec 2003 Posts: 347 Location: Italy
|
Posted: Mon Feb 16, 2004 8:33 pm Post subject: |
|
|
Here I read that p4b_smbus isn´t needed for kernels 2.6.x.. and now? |
|
Back to top |
|
|
tlaloctlaloc Apprentice
Joined: 11 Feb 2004 Posts: 198 Location: Europe-In the heart of the Alps
|
Posted: Mon Feb 23, 2004 5:41 pm Post subject: Finally lm-sensors works for my ASUS P4B533E MB |
|
|
Good news for you (and me), berus. It is right that you do not need the p4b_smbus module anymore. The Intel 801 (i2c-i801) option enabled in the kernel works for my Asus P4B533E mb with the ASB100 hardware monitoring chip which is supported in the 2.6.3 kernel (wasn`t so in the 2.6.1 kernel, had to upgrade).
All i did was enable:
the Intel 801 option in Device Drivers--> I2C support --> I2C Hardware Bus support;
the I2C device interface option in Device Drivers--> I2C support;
the Asus ASB100 Bach option in Device Drivers --> I2C support --> Hardware Sensors Chip support.
The modules i have to load are asb100, i2c_sensor, i2c_i801, i2c_dev and i2c_core, which i have also added to to my /etc/modules.autoload.d/kernel-2.6 file. If I also have to do the rc-update add lm-sensors default I do not know. But I get the right temperature out of the box.
Bye, Valentin. |
|
Back to top |
|
|
berus Guru
Joined: 28 Dec 2003 Posts: 347 Location: Italy
|
Posted: Mon Feb 23, 2004 8:35 pm Post subject: |
|
|
Thanks, Valentin. Now I try to re-compile kernel with the options enabled.. I hope that it works on my pc also!! |
|
Back to top |
|
|
KenTI n00b
Joined: 28 Jan 2004 Posts: 53 Location: Italy
|
Posted: Sun Mar 14, 2004 6:06 pm Post subject: Re: For some via chipset motherboards (MS-6378X-L) |
|
|
rollinncoaster wrote: | If you get this error message:
#sensors-detect
#No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
Download the source, untar it. And run the mkdev.sh script to create the necessary device files in order to let sensors-detect do its job. |
sorry where is the mkdev.sh script?
i tried also with
cd /dev
./MAKEDEV i2c
but it said
.devfsd presence implies active DevFS. Aborting MAKEDEV invocation.
i also unpacked the source and compiled i2c manually but i still can't find the mkdev.sh script.. |
|
Back to top |
|
|
eean Guru
Joined: 10 Jun 2002 Posts: 355 Location: Kirksville, MO USA
|
Posted: Mon Mar 29, 2004 7:23 am Post subject: Re: For some via chipset motherboards (MS-6378X-L) |
|
|
KenTI wrote: | rollinncoaster wrote: | If you get this error message:
#sensors-detect
#No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
Download the source, untar it. And run the mkdev.sh script to create the necessary device files in order to let sensors-detect do its job. |
sorry where is the mkdev.sh script?
i tried also with
cd /dev
./MAKEDEV i2c
but it said
.devfsd presence implies active DevFS. Aborting MAKEDEV invocation.
i also unpacked the source and compiled i2c manually but i still can't find the mkdev.sh script.. | I think rollinncoaster is wrong, at least in my case. When I get this message its because I haven't loaded i2c-dev yet. |
|
Back to top |
|
|
AugustineF n00b
Joined: 19 Dec 2003 Posts: 31
|
Posted: Mon Mar 29, 2004 6:49 pm Post subject: |
|
|
CPU fan speed is always zero.
I have a 3 pin connector to the CPU fan, as the document suggests, but the speed shown is always zero.
The system fan speed indicator is working though. |
|
Back to top |
|
|
ares Apprentice
Joined: 13 Oct 2003 Posts: 280 Location: Savigliano (CN)
|
Posted: Mon Mar 29, 2004 11:09 pm Post subject: |
|
|
I use sensors in my .bashrc
Capture Cpu/Temp
vim .bashrc
Code: |
# Sens
sens() {
sensors | sed -n '/+/p' | awk '{print $1}' | sed -e '/v/d' | tail -n 1
}
export sens
export PS1="`sens`/\w /"
|
My PS1
+46°C/~/temp/ _________________ My portage and homepage |
|
Back to top |
|
|
jessler Tux's lil' helper
Joined: 17 Jul 2002 Posts: 78 Location: 127.0.0.1
|
Posted: Thu May 27, 2004 9:31 pm Post subject: |
|
|
The sensors-detect utility identified that I need a module named bmcsensors.
Code: | #----cut here----
# I2C adapter drivers
modprobe i2c-piix4
modprobe i2c-isa
# I2C chip drivers
modprobe eeprom
modprobe bmcsensors
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----
|
When I tried to install the module I get this. Code: | modprobe: Can't locate module bmcsensors
|
I have searched the entire file system and cannot find an module named bmcsensors.o. All of the other modules installed and appear to work fine.
Here is what I get when I run sensors:
Code: |
eeprom-i2c-0-50
Adapter: SMBus PIIX4 adapter at 08a0
Algorithm: Non-I2C SMBus adapter
Memory type: SDR SDRAM DIMM
Memory size (MB): 1024
eeprom-i2c-0-51
Adapter: SMBus PIIX4 adapter at 08a0
Algorithm: Non-I2C SMBus adapter
Memory type: SDR SDRAM DIMM
Memory size (MB): 1024
|
Is there a workaround or solution for this? |
|
Back to top |
|
|
roshan n00b
Joined: 18 Nov 2003 Posts: 22 Location: London
|
Posted: Mon May 31, 2004 8:36 am Post subject: Re: IBM Thinkpads and lm_sensors |
|
|
marshall_j wrote: | maalth wrote: | If you have an IBM Thinkpad (any model), do NOT use lm_sensors under any circumstances. |
Why's that?! |
Because it can corrupt the eeprom on certain (most?) Thinkpads. _________________ Smile - it makes people wonder what you're up to.
http://roshan.info |
|
Back to top |
|
|
roshan n00b
Joined: 18 Nov 2003 Posts: 22 Location: London
|
Posted: Mon May 31, 2004 8:45 am Post subject: Re: For some via chipset motherboards (MS-6378X-L) |
|
|
KenTI wrote: | rollinncoaster wrote: | If you get this error message:
#sensors-detect
#No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
Download the source, untar it. And run the mkdev.sh script to create the necessary device files in order to let sensors-detect do its job. |
sorry where is the mkdev.sh script?
i tried also with
cd /dev
./MAKEDEV i2c
but it said
.devfsd presence implies active DevFS. Aborting MAKEDEV invocation.
i also unpacked the source and compiled i2c manually but i still can't find the mkdev.sh script.. |
Ensure that you have the source available again, by typing:
Code: | emerge -f lm-sensors |
Then, extract the mkdev.sh file from the archive by issuing the following command, while located for example in the /tmp directory:
Code: | tar zxvf /usr/portage/distfiles/lm_sensors-2.8.1.tar.gz lm_sensors-2.8.1/prog/mkdev/mkdev.sh |
You'll find mkdev.sh in /tmp/lm_sensors-2.8.1/prog/mkdev/mkdev.sh _________________ Smile - it makes people wonder what you're up to.
http://roshan.info |
|
Back to top |
|
|
H-Dragon Guru
Joined: 22 Oct 2002 Posts: 547
|
Posted: Fri Jun 11, 2004 10:28 am Post subject: |
|
|
hi all!
i am running a a-xp 2400+ on my gigabyte ga7dxr with a ekl-papst cooler.
this is what lm-sensors tells me:
Code: |
via686a-isa-6000
Adapter: ISA adapter
Algorithm: ISA algorithm
CPU core: +1.81 V (min = +1.79 V, max = +2.18 V)
+2.5V: +1.13 V (min = +2.24 V, max = +2.74 V) ALARM
I/O: +3.30 V (min = +2.95 V, max = +3.62 V)
+5V: +4.99 V (min = +4.47 V, max = +5.49 V)
+12V: +12.28 V (min = +10.79 V, max = +13.18 V)
CPU Fan: 0 RPM (min = 3000 RPM, div = 2)
P/S Fan: 0 RPM (min = 3000 RPM, div = 2)
SYS Temp: +61.0°C (limit = +60°C, hysteresis = +50°C) ALARM
CPU Temp: +37.4°C (limit = +60°C, hysteresis = +50°C)
SBr Temp: +25.3°C (limit = +60°C, hysteresis = +50°C)
|
1. why is there a error with the Voltage?????
2. the cpu temp is about 50° not 37 nor 61° !!!!!!! why is it so far off (and / or wrongly labeled?)
thanks! _________________ WEBSITE
Do not meddle with the affairs of Dragons, for you are crunchy and tasty with ketchup! |
|
Back to top |
|
|
salamander n00b
Joined: 19 Aug 2004 Posts: 1
|
Posted: Thu Aug 19, 2004 1:35 pm Post subject: solution to sensors-detect complaining about no i2c devices |
|
|
I've got a dual Xeon 2.4Ghz and I've unsuccesfully tried to make lm-sensors work a lot of times. I always arrived to the following message:
Code: |
# modprobe i2c-dev
# sensors-detect
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
|
And I had no clue on how to continue from here. (Using mkdev seemed a bit out of place). Every howto I've read proposes, as it is shown in the example, to just load the module i2c-dev prior to the execution of sensors-detect to solve this problem.
But, with my machine (or kernel configuration) this was not sufficient.
I've just found that I also needed to load the i2c-isa module prior to running sensors-detect (I've double-checked that this was the only aditional module needed). This solved the problem:
Code: |
# modprobe i2c-dev i2c-isa
# sensors-detect
[output of sensors-detect]
|
Perhaps it is usefull to add this information to the how-to.
Thank you very much for your effort. |
|
Back to top |
|
|
CarlUman Apprentice
Joined: 07 Jul 2004 Posts: 158 Location: SE Iowa
|
Posted: Fri Aug 27, 2004 2:37 am Post subject: |
|
|
Just thought I'd post this page that has a list of the hardware monitor chipsets for motherboards.
Hope it helps |
|
Back to top |
|
|
SAngeli l33t
Joined: 16 Apr 2004 Posts: 904 Location: Italy
|
Posted: Sat Feb 26, 2005 11:42 am Post subject: Unable to make lm-sensors work |
|
|
Hi,
it seems like many times it is easyer to read than to execute.
I am not able to enable lm-sensors.
This is what I get when I run sensors-detect
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
Moreover, I am not able to find in my kernel this entry: <M> I2C /proc interface Where is it???
Finally, if I run sensors I get: Code: | # sensors
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
|
Here is my configuration spec:
- 2.6.9-gentoo-r13
- Udev
- Kernel specs:
Code: | <M> I2C support
<M> I2C device interface
I2C Algorithms --->
I2C Hardware Bus support --->
Hardware Sensors Chip support --->
Other I2C Chip support --->
[ ] I2C Core debugging messages
[ ] I2C Algorithm debugging messages
[ ] I2C Bus debugging messages
[ ] I2C Chip debugging messages
I2C Algorithms --->
--- I2C bit-banging interfaces
<M> I2C PCF 8584 interfaces
<M> I2C PCA 9564 interfaces
I2C Hardware Bus support ---> (only the following selected)
<M> Intel 801
<M> Intel 810/815
Hardware Sensors Chip support ---> (none selected)
Other I2C Chip support ---> (none selected)
|
- Motherboard: Intel D865-GLC
- Software: Kde and GKrellM
Please help. I am tired reading here and there info and tips but not having mine working.
Thank you,
Spiro |
|
Back to top |
|
|
mdshort Apprentice
Joined: 06 Dec 2004 Posts: 157
|
Posted: Wed Jul 13, 2005 3:16 am Post subject: i2c /proc |
|
|
I don't see that entry either, its kinda frustrating.
Anyone? _________________ "With every rise, there is a fall." |
|
Back to top |
|
|
stahlsau Guru
Joined: 09 Jan 2004 Posts: 584 Location: WildWestwoods
|
Posted: Wed Jul 13, 2005 6:58 am Post subject: |
|
|
this guide is more than 2 years old, probably many things have changed since then.
I never could lmsensors get working, no matter what i did, so, for the moment, i li´ve with gkrellm2 which shows me CPU and GPU Temps out-of-the-box. |
|
Back to top |
|
|
mdshort Apprentice
Joined: 06 Dec 2004 Posts: 157
|
Posted: Wed Jul 13, 2005 11:49 pm Post subject: |
|
|
I got it to work, this is what you need to do:
(This tutorial was made using a 2.6.12 kernel, most recent versions of the 2.6 kernel have /proc support for I2C built in so enabling it is unnecissary.)
Step One - Kernel
First, configure your kernel with i2c and i2c-dev compiled as modules.
Quote: |
Device Drivers ---> I2C support ---> (M) I2C support
Device Drivers ---> I2C support ---> (M) I2C device interface
|
After enabling them as modules, enable your corresponding I2C Hardware Bus support.
Quote: |
Device Drivers ---> I2C support ---> I2C Hardware Bus support ---> (M) <coresponding module(s)>
|
Exit, saving your kernel config, then mount your /boot partition (if applicable) and compile your kernel.
Quote: |
# make && make modules modules_install install
|
Reboot to your new kernel.
Step Two - Detection
At this point, install the lm_sensors package.
Now use modprobe to load all of the modules you enabled in the kernel.
Quote: |
# modprobe i2c-core
# modprobe i2c-dev
# modprobe <corresponding hardware bus module(s)>
|
At this point its time to detect your heat sensors, run sensors-detect while answering "YES" to everything until you get to the summary question.
If this command fails, you either didn't follow this tutorial correctly, or chose the wrong I2C Hardware Bus support module.
Pressing enter, take note of all the modules listed that say "should be inserted" ignoring all other types. (You will use these later.)
Quote: |
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `w83781d' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83782D' (confidence:
Driver `via686a' (should be inserted):
Detects correctly:
* ISA bus, undetermined address (Busdriver `i2c-isa')
Chip `VIA Technologies VT82C686 Integrated Sensors' (confidence: 9)
|
Afterwards, allow the script to create the configuration file when it asks.
Using the notes you took enable the corresponding modules in your kernel.
Quote: |
Device Drivers ---> I2C support ---> Hardware Sensors Chip support ---> (M) <your noted module(s)>
|
Your almost done! Rebuild your kernel with the previous build command (# make && make modules modules_install install) after mouting your /boot partition (if applicable).
Then enable the lm_sensors module autoloader.
Quote: | # rc-update add lm_sensors default |
*Then reboot to your new kernel.*
Test your sensors with the "sensors" command in the console.
Step Three - Choose Your Favorite Monitor
If your using KDE, then there is a KSensors applet you can install.
Otherwise, if your using Gnome or other window systems, install gkrellm.
And if your a console only advocate, simply use the "sensors" command provided with the lm_sensors package.
_________________ "With every rise, there is a fall." |
|
Back to top |
|
|
|