Could we include the f71882fg sensor module in the kernel? Would be nice not to have to compile it myself after each unraid update

 

Hope I posted this in the right place. Saw similar requests here so went ahead.

Actually, the right place for this would be in the v6 Roadmap.  However ...

 

I requested it myself a little while ago, and Tom kindly added it!  Don't remember which beta.  Unfortunately for me, something about my motherboard rejects it, and I get the following errors -

Jun  9 09:56:22 JacoBack kernel: f71882fg: Found f71882fg chip at 0x290, revision 32

Jun  9 09:56:22 JacoBack kernel: ACPI Warning: SystemIO range 0x0000000000000290-0x0000000000000297 conflicts with OpRegion 0x0000000000000295-0x0000000000000296 (\IP__) (20150204/utaddress-254)

Jun  9 09:56:22 JacoBack kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

---and---

root@JacoBack:~# modprobe f71882fg

modprobe: ERROR: could not insert 'f71882fg': Device or resource busy

 

You might try the modprobe on yours, see if it works for you.  If it does, should be detected and added in System Temp plugin.

I'll admit I actually haven't tested on the recent betas/rc for this machine. I was looking something up and remembered I had wanted to request this module a while ago. Thanks for the response.

 

Looks like you have another module taking up that device and holding it as busy. Are any other "sensors" modules loaded before f71882fg on your machine?

Jun  9 15:16:46 JacoBack kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)

Jun  9 15:16:46 JacoBack kernel: system 00:01: [io  0x04d0-0x04d1] has been reserved

Jun  9 15:16:46 JacoBack kernel: system 00:01: [io  0x0800-0x0805] has been reserved

Jun  9 15:16:46 JacoBack kernel: system 00:01: [io  0x0295-0x0296] has been reserved

 

I found the f71882fg datasheet, and located the base address of the hardware monitor for the f71882, and it's 0x0295-0x0296, so it sure looks like it's there.  The only other sensor chip I'm aware of is the standard k8temp for AMD's, and I see no evidence of a conflict.  Manufacturer is gone now, and wouldn't surprise me if they set something up wrong.

 

I can't find anything else using that address range.

 

When I have a chance, I'll experiment further, try manually running sensors-detect after trying to remove any built-in f71882 module, and other experiments too.

I have a MB with the same chip (f71882fg). I also see similar output from the dmesg:

f71882fg: Found f71808a chip at 0x290, revision 33
ACPI Warning: SystemIO range 0x0000000000000290-0x0000000000000297 conflicts with OpRegion 0x0000000000000295-0x0000000000000296 (\_TZ_.IP__) (20150204/utaddress-254)
ACPI Warning: SystemIO range 0x0000000000000290-0x0000000000000297 conflicts with OpRegion 0x0000000000000295-0x0000000000000296 (\_GPE.IP__) (20150204/utaddress-254)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

 

Any update for the issue?