[SOLVED]Installing it87 driver for lm_sensors support

Question

Hello,
I've done much research on how to properly install an update it87 driver that could make 0x8620 work.
I ran sensors-detect and ran into this:
# sensors-detect revision 6209 (2014-01-14 22:51:58 +0100)
# System: Gigabyte Technology Co., Ltd. Z97X-Gaming 7
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... Yes
Found unknown chip with ID 0x8620
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): y
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Found unknown SMBus adapter 8086:8ca2 at 0000:00:1f.3.
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.
Next adapter: i915 gmbus ssc (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus vga (i2c-1)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus panel (i2c-2)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpb (i2c-4)
Do you want to scan it? (yes/NO/selectively): y
Next adapter: i915 gmbus dpd (i2c-5)
Do you want to scan it? (yes/NO/selectively): y
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)
Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):
Created symlink from /etc/systemd/system/multi-user.target.wants/lm_sensors.service to /usr/lib/systemd/system/lm_sensors.service.
Unloading i2c-dev... OK
Unloading cpuid... OK
So I did some research and found that this was updated and available as a potential driver for my MOBO:
http://www.lm-sensors.org/wiki/Devices
You will see the IT8620E which covers the unknown chip lm_sensors found.
I downloaded the file, extracted it and tried to do a
sudo make
but I ran into an error because it was looking for
KERNEL_BUILD := /usr/src/linux-headers-$(TARGET)
which is NOT in that directory. I installed the linux-headers and saw that it adds files to
/lib/modules/3.19.3-3-ARCH
. I modified the Makefile and it got past that part but it ran into another error during
make install
After much frustration I looked and saw 
usr/lib/modules/3.19.3-3-ARCH/kernel/drivers/hwmon/it87.ko.gz
so now I'm questioning if I even need to install this driver or if I need to update it. Is there a way to learn more about these drivers that come in the linux package?
I can't find anything concrete on how to make this work. I'm just trying to add my fan speeds and other junk to my conky!
Edit:
modinfo it87 gave me this result:
filename: /lib/modules/3.19.3-3-ARCH/kernel/drivers/hwmon/it87.ko.gz
license: GPL
description: IT8705F/IT871xF/IT872xF hardware monitoring driver
author: Chris Gauthron, Jean Delvare <[email protected]>
depends: hwmon-vid,hwmon
intree: Y
vermagic: 3.19.3-3-ARCH SMP preempt mod_unload modversions
parm: force_id:Override the detected device ID (ushort)
parm: update_vbat:Update vbat if set else return powerup value (bool)
parm: fix_pwm_polarity:Force PWM polarity to active high (DANGEROUS) (bool)
So, this tells me that this driver does not cover 8620.
Last edited by SirMyztiq (2015-04-10 06:23:31)

Answer 1

Update:
I believe after some researching and actually going for it that I managed to install the it87 test driver.
I modified the Makefile on this line:
KERNEL_BUILD := /lib/modules/$(TARGET)/build
And when it failed on this line:
SYSTEM_MAP := /boot/System.map-$(TARGET)
I did:
sudo cp /proc/kallsyms /boot/System.map-`uname -r`
Because Arch doesn't put this file there because it isn't needed to boot...I think.
Either way it finished and I was able to use the lm_sensors.