lm_sensors not working after kernel upgrade

Arrakis · 2006-08-04 08:43:03

as the title says going from stock kernel 2.6.16.20-1 to 2.6.17.7-1 and from beyond 2.6.16.beyond4-1 to 2.6.17.beyond2.2-1 broke something in lm_sensors

sensors-detect doesn't recognize my sensors anymore

when I upgraded the kernel lm_sensors version was 2.9.2-1, so I downloaded the PKGBUILD and modified it to compile version 2.10.0 (which wasn't in the repos at that time) and when I issued the command sensors-detect it didn't recognize anything but when I ran the command sensors it gave me:

Can't access procfs/sysfs file 
Unable to find i2c bus information; 
For 2.6 kernels, make sure you have mounted sysfs and libsensors 
was compiled with sysfs support! 
For older kernels, make sure you have done 'modprobe i2c-proc'!

this both with stock and beyond kernel

now I have to tell you that I keep an archck kernel on my box just in case something goes wrong with the upgrades of the other two and, on this kernel, lm_sensors is working flawlessly

Since I'm on topic I tell you that there's something wrong in the makefile for lm_sensors-2.10.0 (which is in the repos now) that the mantainer of our package and the devs themselves apparently didn't notice:
it includes, on line 297, several files that are not yet created and the lm_sensors devs solved it, in the svn, by changing that line to this line: "-include $(INCLUDEFILES)" (just added a minus at the beginning of the line)

as you might have guessed I went on and compiled the svn version that, again, doesn't work in neither stock nor beyond but works like a charm in archck

on a clean boot this is the result of "lsmod | grep i2c":

archck:

i2c_i801                7820  0
i2c_core               16256  3 eeprom,asb100,i2c_i801

beyond:

i2c_dev                 7428  0
i2c_i801                7820  0 
i2c_core               15872  4 i2c_dev,eeprom,asb100,i2c_i801

stock:

i2c_i801                8204  0
i2c_core               17408  3 eeprom,asb100,i2c_i801

any ideas about what's going wrong?

bampowwack · 2006-08-09 04:00:06

Did you find a resolution?

Arrakis · 2006-08-14 21:58:11

not yet, are you experiencing the same problem?

bampowwack · 2006-08-15 02:55:28

Yeah was having the same problem. Seems fine if you install it from source.

http://www.lm-sensors.org/wiki/Download

Arrakis · 2006-08-19 10:27:52

I just installed their svn version from source and that didn't solve my problem

bampowwack · 2006-08-19 18:22:21

And your following what is directed to do when you run sensors-detect as root? It should give you some modprobe.conf snippits and a list of modules other than i2c the load.
Can you post the output of sensors detect?

Also maybe since your having troubles why dont you try the latest stable release?

Arrakis · 2006-08-21 08:36:38

the problem is subtler than you think because, no matter what version of lm_sensors, in the "old" archck kernel everything still works as it should, and I'm sure it will work in the old 2.6.16.20-1 and 2.6.16.beyond4-1 too if I just bothered to downgrade

in all of these configurations mentioned above, when I run sensors-detect as root, following every instruction of the official lm_sensors page, I get the list of modules I should load at boot to make things work properly

on the other hand, with these new kernels, sensors-detect doesn't detect anything, and even if I'm already loading the modules that I need the only thing I got out of 'sensors' is:

No sensors found!

so, I think, that something in these new kernels conflicts with my hardware/software configuration and prevents lm_sensors to do its job and I don't have a clue about how to troubleshoot this

however, if you still want to see the output of sensors-detect, as root on 2.6.17.beyond3-1, here it is:

# sensors-detect revision 4092 (2006-08-11 14:42:52 +0200 (Fri, 11 Aug 2006))

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
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.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

 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...
Sorry, no PCI bus adapters found.

We will now try to load each adapter module in turn.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

 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 successfully.

 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. This is usually safe though.

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 W83627EHF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627DHG'
  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 `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. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (0x87)
Probing for `Winbond W83627HF Super IO Sensors'
  Failed! (0x87)
Probing for `Winbond W83627THF Super IO Sensors'
  Failed! (0x87)
Probing for `Winbond W83637HF Super IO Sensors'
  Failed! (0x87)
Probing for `Winbond W83687THF Super IO Sensors'
  Failed! (0x87)
Probing for `Winbond W83697HF Super IO Sensors'
  Failed! (0x87)
Probing for `Winbond W83697SF/UF Super IO PWM'
  Failed! (0x87)
Probing for `Winbond W83L517D Super IO'
  Failed! (0x87)
Probing for `Fintek F71805F/FG Super IO Sensors'
  Failed! (0x8708)
Probing for `Fintek F71872F/FG Super IO Sensors'
  Failed! (0x8708)
Probing for `Fintek F81218D Super IO'
  Failed! (0x8708)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
  Failed! (0x8708)
Probing for `Winbond W83627DHG Super IO Sensors'
  Failed! (0x8708)

Do you want to scan for secondary Super I/O sensors? (YES/no): Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
  Failed! (skipping family)

 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, and
 http://www.lm-sensors.org/wiki/FAQ
 (FAQ #4.24.3) for further information.
 If you find out what chips are on your board, see
 http://www.lm-sensors.org/wiki/NewDrivers for driver status.

Arrakis · 2006-12-28 23:49:17

I'm writing here in case someone has the same problem, I discovered why lm_sensors stopped working all of a sudden after that upgrade, it was because of this patch

explanation and solution from here:

Long story short, Asus is hiding the SMBus on many boards, Linux tries
to unhide them, but it is dangerous to do so when suspend/resume
support is enabled, so since 2.6.17 the quirk which unhides the SMBus
is disabled when suspend support is enabled.
If you want your sensors back, you'll need to disable suspend support
for now ("Sleep States" in the ACPI menu.) I know it is a regression for
some users, but that's the only safe way until the kernel is taught how
to replay PCI quirks on resume.
Alternatively you can go bug Asus and ask them why they hide the SMBus
in the first place.

so, if you disable suspend support and recompile your kernel your sensors should be back working (sort of, actually because my fan sensors only works for the first minutes of uptime and then goes 0rpm, and no, the fan isn't broken, it's ok)

Arch Linux

#1 2006-08-04 08:43:03

lm_sensors not working after kernel upgrade

#2 2006-08-09 04:00:06

Re: lm_sensors not working after kernel upgrade

#3 2006-08-14 21:58:11

Re: lm_sensors not working after kernel upgrade

#4 2006-08-15 02:55:28

Re: lm_sensors not working after kernel upgrade

#5 2006-08-19 10:27:52

Re: lm_sensors not working after kernel upgrade

#6 2006-08-19 18:22:21

Re: lm_sensors not working after kernel upgrade

#7 2006-08-21 08:36:38

Re: lm_sensors not working after kernel upgrade

#8 2006-12-28 23:49:17

Re: lm_sensors not working after kernel upgrade

Board footer