Red Hat Bugzilla – Bug 509493
lm_sensors unable to load module it87
Last modified: 2015-03-04 20:20:31 EST
Description of problem:
i ran sensors-detect which told me i had to change /etc/sysconfig/lm_sensors. i let it do the change then it told me it couldnt find the sensor it had just found.
ran this like 3 times
Version-Release number of selected component (if applicable):
Steps to Reproduce:
it just works
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
* ISA bus, address 0x290
Chip `ITE IT8712F Super IO Sensors' (confidence: 9)
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Starting lm_sensors: loading module it87 No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
Unloading i2c-dev... OK
What are the last few lines of the output of dmesg after running sensors-detect ?
Are you using updates testing ? If you are then chances are that you are hitting
If you are not using updates-testing chances are your kernel is too old, try:
yum update --enablerepo=updates-testing
Eitherway the output of dmesg after running sensors-detect should help to determine the cause of this.
last few lines of dmesg:
i2c /dev entries driver
it87: Found IT8712F chip at 0x290, revision 6
ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region IP__ [0x295-0x296]
ACPI: Device needs an ACPI driver
updates testing: no
kernel too old:
18.104.22.168-191.fc11.x86_64 #1 SMP Tue Jun 16 23:23:21 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
i checked the link you posted and yes it looks like to be one and the same. so how do i fix this on my machine?
I asked about the old kernel because you indicated F-10 as version. As for how to fix this, the blog post I linked to gives a workaround (which can potentially be dangerous!). This is not a bug, you BIOS claims the IO resources used by the it87, so the native Linux driver cannot load.
first of all i m embarrassed if i had indicated f10.
secondly, lm_sensors was working in f10 but not f11. and no i dont want to do the workaround either.
in any case, the issue is now like beating a dead dog.