* [lm-sensors] f71882fg not showing motherboard temps
@ 2012-10-31 22:37 Logan Freijo
2012-11-01 4:49 ` Guenter Roeck
` (13 more replies)
0 siblings, 14 replies; 15+ messages in thread
From: Logan Freijo @ 2012-10-31 22:37 UTC (permalink / raw)
To: lm-sensors
**Hello. I have a system running Ubuntu Server 12.04.1 on a Jetway
motherboard. Sensors-detect finds my AMD cpu temp and a chip for the
motherboard (f71882fg). However, after adding the suggested line to
/etc/modules and rebooting, only the cpu temp shows up using the sensors
command. I have tried acpi-enforce-resources=lax with no effect. I have
tried searching the internet for an answer and I find none. Below is the
information requested in the FAQ. I would like to note that this is not
a new problem, it has been ongoing since I bought the motherboard in Jan
2011.
Any help would be appreciated.
Logan
*
Motherboard vendor and model*
JetWay JHZ03-GT-LF
*Lm_sensors and kernel versions*
sensors version 3.3.1 with libsensors version 3.3.1
3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux
*The output of sensors*
k10temp-pci-00c3
Adapter: PCI adapter
CPU Temp: +26.0 C (high = +70.0 C)
*The dmesg or syslog output if applicable*
kernel: [ 8.795196] f71882fg: Found f71882fg chip at 0x220,
revision 32
kernel: [ 8.795228] f71882fg.544: failed to claim resource 0
kernel: [ 8.795233] f71882fg: Device addition failed
*The output of (as root) sensors-detect*
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: To Be Filled By O.E.M. To Be Filled By O.E.M.
# Board: JETWAY HZ03-GT
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):
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... Success!
(driver `k10temp')
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
Intel digital thermal sensor... No
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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
Found `Fintek F71882FG/F71883FG Super IO Sensors' Success!
(address 0x225, driver `f71882fg')
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):
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):
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):
Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc
SB600/SB700/SB800 SMBus
Module i2c-dev loaded successfully.
Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
Do you want to scan it? (YES/no/selectively):
Next adapter: Radeon i2c bit bus 0x14 (i2c-4)
Do you want to scan it? (YES/no/selectively):
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `k10temp' (autoloaded):
* Chip `AMD Family 10h thermal sensors' (confidence: 9)
Driver `f71882fg':
* ISA bus, address 0x225
Chip `Fintek F71882FG/F71883FG Super IO Sensors' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
f71882fg
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!
Do you want to add these lines automatically to /etc/modules? (yes/NO)n
Unloading i2c-dev... OK
Unloading cpuid... OK
*The output of lsmod*
Module Size Used by
cifs 287317 0
ext2 73795 1
dm_multipath 23230 0
psmouse 97443 0
edac_core 53746 0
radeon 804460 1
serio_raw 13211 0
k10temp 13166 0
edac_mce_amd 23709 0
ttm 76949 1 radeon
sp5100_tco 13791 0
drm_kms_helper 46978 1 radeon
joydev 17693 0
i2c_piix4 13301 0
drm 241921 3 radeon,ttm,drm_kms_helper
i2c_algo_bit 13423 1 radeon
mac_hid 13253 0
shpchp 37277 0
wmi 19256 0
lp 17799 0
parport 46562 1 lp
usbhid 47199 1
hid 99559 1 usbhid
r8169 62099 0
pata_atiixp 13204 4
dm_raid45 78155 0
xor 12894 1 dm_raid45
dm_mirror 22203 0
dm_region_hash 20918 1 dm_mirror
dm_log 18564 3 dm_raid45,dm_mirror,dm_region_hash
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
@ 2012-11-01 4:49 ` Guenter Roeck
2012-11-01 16:03 ` Logan Freijo
` (12 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Guenter Roeck @ 2012-11-01 4:49 UTC (permalink / raw)
To: lm-sensors
On Wed, Oct 31, 2012 at 06:37:01PM -0400, Logan Freijo wrote:
> **Hello. I have a system running Ubuntu Server 12.04.1 on a Jetway
> motherboard. Sensors-detect finds my AMD cpu temp and a chip for the
> motherboard (f71882fg). However, after adding the suggested line to
> /etc/modules and rebooting, only the cpu temp shows up using the
> sensors command. I have tried acpi-enforce-resources=lax with no
> effect. I have tried searching the internet for an answer and I find
> none. Below is the information requested in the FAQ. I would like
> to note that this is not a new problem, it has been ongoing since I
> bought the motherboard in Jan 2011.
>
> Any help would be appreciated.
>
> Logan
>
>
> *
>
> Motherboard vendor and model*
> JetWay JHZ03-GT-LF
>
> *Lm_sensors and kernel versions*
> sensors version 3.3.1 with libsensors version 3.3.1
> 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012
> x86_64 x86_64 x86_64 GNU/Linux
>
> *The output of sensors*
> k10temp-pci-00c3
> Adapter: PCI adapter
> CPU Temp: +26.0 C (high = +70.0 C)
>
> *The dmesg or syslog output if applicable*
> kernel: [ 8.795196] f71882fg: Found f71882fg chip at 0x220,
> revision 32
> kernel: [ 8.795228] f71882fg.544: failed to claim resource 0
> kernel: [ 8.795233] f71882fg: Device addition failed
>
Hi,
An old post suggests that you may be able to work around the problem by booting
with "pnpacpi=off", and that the problem might be due to a BIOS problem.
See http://lists.lm-sensors.org/pipermail/lm-sensors/2009-January/025175.html
and subsequent posts for additional details.
Might be worth a try.
Guenter
> *The output of (as root) sensors-detect*
> # sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
> # System: To Be Filled By O.E.M. To Be Filled By O.E.M.
> # Board: JETWAY HZ03-GT
>
> 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):
> 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... Success!
> (driver `k10temp')
> 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
> Intel digital thermal sensor... No
> 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):
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor/ITE'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
> Found `Fintek F71882FG/F71883FG Super IO Sensors' Success!
> (address 0x225, driver `f71882fg')
> 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):
> 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):
>
> 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):
> Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies
> Inc SB600/SB700/SB800 SMBus
> Module i2c-dev loaded successfully.
>
> Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x50
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... No
> Probing for `EDID EEPROM'... Yes
> (confidence 8, not a hardware monitoring chip)
>
> Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
> Do you want to scan it? (YES/no/selectively):
>
> Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
> Do you want to scan it? (YES/no/selectively):
>
> Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
> Do you want to scan it? (YES/no/selectively):
>
> Next adapter: Radeon i2c bit bus 0x14 (i2c-4)
> Do you want to scan it? (YES/no/selectively):
>
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
>
> Driver `k10temp' (autoloaded):
> * Chip `AMD Family 10h thermal sensors' (confidence: 9)
>
> Driver `f71882fg':
> * ISA bus, address 0x225
> Chip `Fintek F71882FG/F71883FG Super IO Sensors' (confidence: 9)
>
> To load everything that is needed, add this to /etc/modules:
> #----cut here----
> # Chip drivers
> f71882fg
> #----cut here----
> If you have some drivers built into your kernel, the list above will
> contain too many modules. Skip the appropriate ones!
>
> Do you want to add these lines automatically to /etc/modules? (yes/NO)n
>
> Unloading i2c-dev... OK
> Unloading cpuid... OK
>
> *The output of lsmod*
>
> Module Size Used by
> cifs 287317 0
> ext2 73795 1
> dm_multipath 23230 0
> psmouse 97443 0
> edac_core 53746 0
> radeon 804460 1
> serio_raw 13211 0
> k10temp 13166 0
> edac_mce_amd 23709 0
> ttm 76949 1 radeon
> sp5100_tco 13791 0
> drm_kms_helper 46978 1 radeon
> joydev 17693 0
> i2c_piix4 13301 0
> drm 241921 3 radeon,ttm,drm_kms_helper
> i2c_algo_bit 13423 1 radeon
> mac_hid 13253 0
> shpchp 37277 0
> wmi 19256 0
> lp 17799 0
> parport 46562 1 lp
> usbhid 47199 1
> hid 99559 1 usbhid
> r8169 62099 0
> pata_atiixp 13204 4
> dm_raid45 78155 0
> xor 12894 1 dm_raid45
> dm_mirror 22203 0
> dm_region_hash 20918 1 dm_mirror
> dm_log 18564 3 dm_raid45,dm_mirror,dm_region_hash
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
2012-11-01 4:49 ` Guenter Roeck
@ 2012-11-01 16:03 ` Logan Freijo
2012-11-01 16:19 ` Hans de Goede
` (11 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Logan Freijo @ 2012-11-01 16:03 UTC (permalink / raw)
To: lm-sensors
On 11/1/2012 12:49 AM, Guenter Roeck wrote:
> On Wed, Oct 31, 2012 at 06:37:01PM -0400, Logan Freijo wrote:
>> **Hello. I have a system running Ubuntu Server 12.04.1 on a Jetway
>> motherboard. Sensors-detect finds my AMD cpu temp and a chip for the
>> motherboard (f71882fg). However, after adding the suggested line to
>> /etc/modules and rebooting, only the cpu temp shows up using the
>> sensors command. I have tried acpi-enforce-resources=lax with no
>> effect. I have tried searching the internet for an answer and I find
>> none. Below is the information requested in the FAQ. I would like
>> to note that this is not a new problem, it has been ongoing since I
>> bought the motherboard in Jan 2011.
>>
>> Any help would be appreciated.
>>
>> Logan
>>
>>
>> *
>>
>> Motherboard vendor and model*
>> JetWay JHZ03-GT-LF
>>
>> *Lm_sensors and kernel versions*
>> sensors version 3.3.1 with libsensors version 3.3.1
>> 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012
>> x86_64 x86_64 x86_64 GNU/Linux
>>
>> *The output of sensors*
>> k10temp-pci-00c3
>> Adapter: PCI adapter
>> CPU Temp: +26.0 C (high = +70.0 C)
>>
>> *The dmesg or syslog output if applicable*
>> kernel: [ 8.795196] f71882fg: Found f71882fg chip at 0x220,
>> revision 32
>> kernel: [ 8.795228] f71882fg.544: failed to claim resource 0
>> kernel: [ 8.795233] f71882fg: Device addition failed
>>
> Hi,
>
> An old post suggests that you may be able to work around the problem by booting
> with "pnpacpi=off", and that the problem might be due to a BIOS problem.
> See http://lists.lm-sensors.org/pipermail/lm-sensors/2009-January/025175.html
> and subsequent posts for additional details.
>
> Might be worth a try.
>
> Guenter
>
>> *The output of (as root) sensors-detect*
>> # sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
>> # System: To Be Filled By O.E.M. To Be Filled By O.E.M.
>> # Board: JETWAY HZ03-GT
>>
>> 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):
>> 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... Success!
>> (driver `k10temp')
>> 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
>> Intel digital thermal sensor... No
>> 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):
>> Probing for Super-I/O at 0x2e/0x2f
>> Trying family `National Semiconductor/ITE'... No
>> Trying family `SMSC'... No
>> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
>> Found `Fintek F71882FG/F71883FG Super IO Sensors' Success!
>> (address 0x225, driver `f71882fg')
>> 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):
>> 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):
>>
>> 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):
>> Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies
>> Inc SB600/SB700/SB800 SMBus
>> Module i2c-dev loaded successfully.
>>
>> Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
>> Do you want to scan it? (YES/no/selectively):
>> Client found at address 0x50
>> Probing for `Analog Devices ADM1033'... No
>> Probing for `Analog Devices ADM1034'... No
>> Probing for `SPD EEPROM'... No
>> Probing for `EDID EEPROM'... Yes
>> (confidence 8, not a hardware monitoring chip)
>>
>> Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
>> Do you want to scan it? (YES/no/selectively):
>>
>> Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
>> Do you want to scan it? (YES/no/selectively):
>>
>> Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
>> Do you want to scan it? (YES/no/selectively):
>>
>> Next adapter: Radeon i2c bit bus 0x14 (i2c-4)
>> Do you want to scan it? (YES/no/selectively):
>>
>> Now follows a summary of the probes I have just done.
>> Just press ENTER to continue:
>>
>> Driver `k10temp' (autoloaded):
>> * Chip `AMD Family 10h thermal sensors' (confidence: 9)
>>
>> Driver `f71882fg':
>> * ISA bus, address 0x225
>> Chip `Fintek F71882FG/F71883FG Super IO Sensors' (confidence: 9)
>>
>> To load everything that is needed, add this to /etc/modules:
>> #----cut here----
>> # Chip drivers
>> f71882fg
>> #----cut here----
>> If you have some drivers built into your kernel, the list above will
>> contain too many modules. Skip the appropriate ones!
>>
>> Do you want to add these lines automatically to /etc/modules? (yes/NO)n
>>
>> Unloading i2c-dev... OK
>> Unloading cpuid... OK
>>
>> *The output of lsmod*
>>
>> Module Size Used by
>> cifs 287317 0
>> ext2 73795 1
>> dm_multipath 23230 0
>> psmouse 97443 0
>> edac_core 53746 0
>> radeon 804460 1
>> serio_raw 13211 0
>> k10temp 13166 0
>> edac_mce_amd 23709 0
>> ttm 76949 1 radeon
>> sp5100_tco 13791 0
>> drm_kms_helper 46978 1 radeon
>> joydev 17693 0
>> i2c_piix4 13301 0
>> drm 241921 3 radeon,ttm,drm_kms_helper
>> i2c_algo_bit 13423 1 radeon
>> mac_hid 13253 0
>> shpchp 37277 0
>> wmi 19256 0
>> lp 17799 0
>> parport 46562 1 lp
>> usbhid 47199 1
>> hid 99559 1 usbhid
>> r8169 62099 0
>> pata_atiixp 13204 4
>> dm_raid45 78155 0
>> xor 12894 1 dm_raid45
>> dm_mirror 22203 0
>> dm_region_hash 20918 1 dm_mirror
>> dm_log 18564 3 dm_raid45,dm_mirror,dm_region_hash
>>
>> _______________________________________________
>> lm-sensors mailing list
>> lm-sensors@lm-sensors.org
>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>>
Thanks for the suggestion Guenter. I did see that post. I added
pnpacpi=off to the boot options and it had no effect. I also tried
pnpbios=off and pnp_reserve_io with no effect. The temperatures and
voltages are displayed in bios and could also be read by several popular
windows 7 programs. I am not planing on switch back to windows, but I
would like to monitor the temps.
Logan
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
2012-11-01 4:49 ` Guenter Roeck
2012-11-01 16:03 ` Logan Freijo
@ 2012-11-01 16:19 ` Hans de Goede
2012-11-01 16:38 ` Logan Freijo
` (10 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Hans de Goede @ 2012-11-01 16:19 UTC (permalink / raw)
To: lm-sensors
Hi,
On 11/01/2012 05:03 PM, Logan Freijo wrote:
> On 11/1/2012 12:49 AM, Guenter Roeck wrote:
>> On Wed, Oct 31, 2012 at 06:37:01PM -0400, Logan Freijo wrote:
>>> **Hello. I have a system running Ubuntu Server 12.04.1 on a Jetway
>>> motherboard. Sensors-detect finds my AMD cpu temp and a chip for the
>>> motherboard (f71882fg). However, after adding the suggested line to
>>> /etc/modules and rebooting, only the cpu temp shows up using the
>>> sensors command. I have tried acpi-enforce-resources=lax with no
>>> effect. I have tried searching the internet for an answer and I find
>>> none. Below is the information requested in the FAQ. I would like
>>> to note that this is not a new problem, it has been ongoing since I
>>> bought the motherboard in Jan 2011.
>>>
>>> Any help would be appreciated.
>>>
>>> Logan
>>>
>>>
>>> *
>>>
>>> Motherboard vendor and model*
>>> JetWay JHZ03-GT-LF
>>>
>>> *Lm_sensors and kernel versions*
>>> sensors version 3.3.1 with libsensors version 3.3.1
>>> 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012
>>> x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> *The output of sensors*
>>> k10temp-pci-00c3
>>> Adapter: PCI adapter
>>> CPU Temp: +26.0 C (high = +70.0 C)
>>>
>>> *The dmesg or syslog output if applicable*
>>> kernel: [ 8.795196] f71882fg: Found f71882fg chip at 0x220,
>>> revision 32
>>> kernel: [ 8.795228] f71882fg.544: failed to claim resource 0
>>> kernel: [ 8.795233] f71882fg: Device addition failed
>>>
>> Hi,
>>
>> An old post suggests that you may be able to work around the problem by booting
>> with "pnpacpi=off", and that the problem might be due to a BIOS problem.
>> See http://lists.lm-sensors.org/pipermail/lm-sensors/2009-January/025175.html
>> and subsequent posts for additional details.
>>
>> Might be worth a try.
>>
>> Guenter
>>
>>> *The output of (as root) sensors-detect*
>>> # sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
>>> # System: To Be Filled By O.E.M. To Be Filled By O.E.M.
>>> # Board: JETWAY HZ03-GT
>>>
>>> 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):
>>> 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... Success!
>>> (driver `k10temp')
>>> 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
>>> Intel digital thermal sensor... No
>>> 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):
>>> Probing for Super-I/O at 0x2e/0x2f
>>> Trying family `National Semiconductor/ITE'... No
>>> Trying family `SMSC'... No
>>> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
>>> Found `Fintek F71882FG/F71883FG Super IO Sensors' Success!
>>> (address 0x225, driver `f71882fg')
>>> 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):
>>> 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):
>>>
>>> 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):
>>> Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies
>>> Inc SB600/SB700/SB800 SMBus
>>> Module i2c-dev loaded successfully.
>>>
>>> Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
>>> Do you want to scan it? (YES/no/selectively):
>>> Client found at address 0x50
>>> Probing for `Analog Devices ADM1033'... No
>>> Probing for `Analog Devices ADM1034'... No
>>> Probing for `SPD EEPROM'... No
>>> Probing for `EDID EEPROM'... Yes
>>> (confidence 8, not a hardware monitoring chip)
>>>
>>> Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
>>> Do you want to scan it? (YES/no/selectively):
>>>
>>> Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
>>> Do you want to scan it? (YES/no/selectively):
>>>
>>> Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
>>> Do you want to scan it? (YES/no/selectively):
>>>
>>> Next adapter: Radeon i2c bit bus 0x14 (i2c-4)
>>> Do you want to scan it? (YES/no/selectively):
>>>
>>> Now follows a summary of the probes I have just done.
>>> Just press ENTER to continue:
>>>
>>> Driver `k10temp' (autoloaded):
>>> * Chip `AMD Family 10h thermal sensors' (confidence: 9)
>>>
>>> Driver `f71882fg':
>>> * ISA bus, address 0x225
>>> Chip `Fintek F71882FG/F71883FG Super IO Sensors' (confidence: 9)
>>>
>>> To load everything that is needed, add this to /etc/modules:
>>> #----cut here----
>>> # Chip drivers
>>> f71882fg
>>> #----cut here----
>>> If you have some drivers built into your kernel, the list above will
>>> contain too many modules. Skip the appropriate ones!
>>>
>>> Do you want to add these lines automatically to /etc/modules? (yes/NO)n
>>>
>>> Unloading i2c-dev... OK
>>> Unloading cpuid... OK
>>>
>>> *The output of lsmod*
>>>
>>> Module Size Used by
>>> cifs 287317 0
>>> ext2 73795 1
>>> dm_multipath 23230 0
>>> psmouse 97443 0
>>> edac_core 53746 0
>>> radeon 804460 1
>>> serio_raw 13211 0
>>> k10temp 13166 0
>>> edac_mce_amd 23709 0
>>> ttm 76949 1 radeon
>>> sp5100_tco 13791 0
>>> drm_kms_helper 46978 1 radeon
>>> joydev 17693 0
>>> i2c_piix4 13301 0
>>> drm 241921 3 radeon,ttm,drm_kms_helper
>>> i2c_algo_bit 13423 1 radeon
>>> mac_hid 13253 0
>>> shpchp 37277 0
>>> wmi 19256 0
>>> lp 17799 0
>>> parport 46562 1 lp
>>> usbhid 47199 1
>>> hid 99559 1 usbhid
>>> r8169 62099 0
>>> pata_atiixp 13204 4
>>> dm_raid45 78155 0
>>> xor 12894 1 dm_raid45
>>> dm_mirror 22203 0
>>> dm_region_hash 20918 1 dm_mirror
>>> dm_log 18564 3 dm_raid45,dm_mirror,dm_region_hash
>>>
>>> _______________________________________________
>>> lm-sensors mailing list
>>> lm-sensors@lm-sensors.org
>>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>>>
> Thanks for the suggestion Guenter. I did see that post. I added pnpacpi=off to the boot options and it had no effect. I also tried pnpbios=off and pnp_reserve_io with no effect. The temperatures and voltages are displayed in bios and could also be read by several popular windows 7 programs. I am not planing on switch back to windows, but I would like to monitor the temps.
Can you do a "cat /proc/ioports" and send us the output?
That may help to figure out what is causing the io conflict.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
` (2 preceding siblings ...)
2012-11-01 16:19 ` Hans de Goede
@ 2012-11-01 16:38 ` Logan Freijo
2012-11-01 17:34 ` Logan Freijo
` (9 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Logan Freijo @ 2012-11-01 16:38 UTC (permalink / raw)
To: lm-sensors
On 11/1/2012 12:19 PM, Hans de Goede wrote:
> Hi,
>
> On 11/01/2012 05:03 PM, Logan Freijo wrote:
>> On 11/1/2012 12:49 AM, Guenter Roeck wrote:
>>> On Wed, Oct 31, 2012 at 06:37:01PM -0400, Logan Freijo wrote:
>>>> **Hello. I have a system running Ubuntu Server 12.04.1 on a Jetway
>>>> motherboard. Sensors-detect finds my AMD cpu temp and a chip for the
>>>> motherboard (f71882fg). However, after adding the suggested line to
>>>> /etc/modules and rebooting, only the cpu temp shows up using the
>>>> sensors command. I have tried acpi-enforce-resources=lax with no
>>>> effect. I have tried searching the internet for an answer and I find
>>>> none. Below is the information requested in the FAQ. I would like
>>>> to note that this is not a new problem, it has been ongoing since I
>>>> bought the motherboard in Jan 2011.
>>>>
>>>> Any help would be appreciated.
>>>>
>>>> Logan
>>>>
>>>>
>>>> *
>>>>
>>>> Motherboard vendor and model*
>>>> JetWay JHZ03-GT-LF
>>>>
>>>> *Lm_sensors and kernel versions*
>>>> sensors version 3.3.1 with libsensors version 3.3.1
>>>> 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012
>>>> x86_64 x86_64 x86_64 GNU/Linux
>>>>
>>>> *The output of sensors*
>>>> k10temp-pci-00c3
>>>> Adapter: PCI adapter
>>>> CPU Temp: +26.0 C (high = +70.0 C)
>>>>
>>>> *The dmesg or syslog output if applicable*
>>>> kernel: [ 8.795196] f71882fg: Found f71882fg chip at 0x220,
>>>> revision 32
>>>> kernel: [ 8.795228] f71882fg.544: failed to claim resource 0
>>>> kernel: [ 8.795233] f71882fg: Device addition failed
>>>>
>>> Hi,
>>>
>>> An old post suggests that you may be able to work around the problem
>>> by booting
>>> with "pnpacpi=off", and that the problem might be due to a BIOS
>>> problem.
>>> See
>>> http://lists.lm-sensors.org/pipermail/lm-sensors/2009-January/025175.html
>>> and subsequent posts for additional details.
>>>
>>> Might be worth a try.
>>>
>>> Guenter
>>>
>>>> *The output of (as root) sensors-detect*
>>>> # sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
>>>> # System: To Be Filled By O.E.M. To Be Filled By O.E.M.
>>>> # Board: JETWAY HZ03-GT
>>>>
>>>> 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):
>>>> 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... Success!
>>>> (driver `k10temp')
>>>> 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
>>>> Intel digital thermal sensor... No
>>>> 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):
>>>> Probing for Super-I/O at 0x2e/0x2f
>>>> Trying family `National Semiconductor/ITE'... No
>>>> Trying family `SMSC'... No
>>>> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
>>>> Found `Fintek F71882FG/F71883FG Super IO Sensors' Success!
>>>> (address 0x225, driver `f71882fg')
>>>> 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):
>>>> 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):
>>>>
>>>> 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):
>>>> Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies
>>>> Inc SB600/SB700/SB800 SMBus
>>>> Module i2c-dev loaded successfully.
>>>>
>>>> Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
>>>> Do you want to scan it? (YES/no/selectively):
>>>> Client found at address 0x50
>>>> Probing for `Analog Devices ADM1033'... No
>>>> Probing for `Analog Devices ADM1034'... No
>>>> Probing for `SPD EEPROM'... No
>>>> Probing for `EDID EEPROM'... Yes
>>>> (confidence 8, not a hardware monitoring chip)
>>>>
>>>> Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
>>>> Do you want to scan it? (YES/no/selectively):
>>>>
>>>> Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
>>>> Do you want to scan it? (YES/no/selectively):
>>>>
>>>> Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
>>>> Do you want to scan it? (YES/no/selectively):
>>>>
>>>> Next adapter: Radeon i2c bit bus 0x14 (i2c-4)
>>>> Do you want to scan it? (YES/no/selectively):
>>>>
>>>> Now follows a summary of the probes I have just done.
>>>> Just press ENTER to continue:
>>>>
>>>> Driver `k10temp' (autoloaded):
>>>> * Chip `AMD Family 10h thermal sensors' (confidence: 9)
>>>>
>>>> Driver `f71882fg':
>>>> * ISA bus, address 0x225
>>>> Chip `Fintek F71882FG/F71883FG Super IO Sensors' (confidence: 9)
>>>>
>>>> To load everything that is needed, add this to /etc/modules:
>>>> #----cut here----
>>>> # Chip drivers
>>>> f71882fg
>>>> #----cut here----
>>>> If you have some drivers built into your kernel, the list above will
>>>> contain too many modules. Skip the appropriate ones!
>>>>
>>>> Do you want to add these lines automatically to /etc/modules?
>>>> (yes/NO)n
>>>>
>>>> Unloading i2c-dev... OK
>>>> Unloading cpuid... OK
>>>>
>>>> *The output of lsmod*
>>>>
>>>> Module Size Used by
>>>> cifs 287317 0
>>>> ext2 73795 1
>>>> dm_multipath 23230 0
>>>> psmouse 97443 0
>>>> edac_core 53746 0
>>>> radeon 804460 1
>>>> serio_raw 13211 0
>>>> k10temp 13166 0
>>>> edac_mce_amd 23709 0
>>>> ttm 76949 1 radeon
>>>> sp5100_tco 13791 0
>>>> drm_kms_helper 46978 1 radeon
>>>> joydev 17693 0
>>>> i2c_piix4 13301 0
>>>> drm 241921 3 radeon,ttm,drm_kms_helper
>>>> i2c_algo_bit 13423 1 radeon
>>>> mac_hid 13253 0
>>>> shpchp 37277 0
>>>> wmi 19256 0
>>>> lp 17799 0
>>>> parport 46562 1 lp
>>>> usbhid 47199 1
>>>> hid 99559 1 usbhid
>>>> r8169 62099 0
>>>> pata_atiixp 13204 4
>>>> dm_raid45 78155 0
>>>> xor 12894 1 dm_raid45
>>>> dm_mirror 22203 0
>>>> dm_region_hash 20918 1 dm_mirror
>>>> dm_log 18564 3 dm_raid45,dm_mirror,dm_region_hash
>>>>
>>>> _______________________________________________
>>>> lm-sensors mailing list
>>>> lm-sensors@lm-sensors.org
>>>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>>>>
>> Thanks for the suggestion Guenter. I did see that post. I added
>> pnpacpi=off to the boot options and it had no effect. I also tried
>> pnpbios=off and pnp_reserve_io with no effect. The temperatures and
>> voltages are displayed in bios and could also be read by several
>> popular windows 7 programs. I am not planing on switch back to
>> windows, but I would like to monitor the temps.
>
> Can you do a "cat /proc/ioports" and send us the output?
>
> That may help to figure out what is causing the io conflict.
>
> Regards,
>
> Hans
>
Here you go:
0000-0cf7 : PCI Bus 0000:00
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-0060 : keyboard
0064-0064 : keyboard
0070-0071 : rtc0
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : 0000:00:14.1
0170-0177 : pata_atiixp
01f0-01f7 : 0000:00:14.1
01f0-01f7 : pata_atiixp
0225-0244 : pnp 00:09
0376-0376 : 0000:00:14.1
0376-0376 : pata_atiixp
03f6-03f6 : 0000:00:14.1
03f6-03f6 : pata_atiixp
040b-040b : pnp 00:08
04d0-04d1 : pnp 00:08
04d6-04d6 : pnp 00:08
0800-089f : pnp 00:08
0800-0803 : ACPI PM1a_EVT_BLK
0804-0805 : ACPI PM1a_CNT_BLK
0808-080b : ACPI PM_TMR
0810-0815 : ACPI CPU throttle
0820-0827 : ACPI GPE0_BLK
0900-090f : pnp 00:08
0910-091f : pnp 00:08
0ae0-0aef : pnp 00:09
0b00-0b0f : pnp 00:08
0b20-0b3f : pnp 00:08
0c00-0c01 : pnp 00:08
0c14-0c14 : pnp 00:08
0c50-0c51 : pnp 00:08
0c52-0c52 : pnp 00:08
0c6c-0c6c : pnp 00:08
0c6f-0c6f : pnp 00:08
0cd0-0cd1 : pnp 00:08
0cd2-0cd3 : pnp 00:08
0cd4-0cd5 : pnp 00:08
0cd6-0cd7 : pnp 00:08
0cd8-0cdf : pnp 00:08
0cf8-0cff : PCI conf1
0d00-ffff : PCI Bus 0000:00
8000-800f : 0000:00:11.0
8000-800f : ahci
9000-9003 : 0000:00:11.0
9000-9003 : ahci
a000-a007 : 0000:00:11.0
a000-a007 : ahci
b000-b003 : 0000:00:11.0
b000-b003 : ahci
c000-c007 : 0000:00:11.0
c000-c007 : ahci
d000-dfff : PCI Bus 0000:01
d000-d0ff : 0000:01:05.0
e000-efff : PCI Bus 0000:02
e800-e8ff : 0000:02:00.0
e800-e8ff : r8169
fe00-fefe : pnp 00:08
ff00-ff0f : 0000:00:14.1
ff00-ff0f : pata_atiixp
Thanks,
Logan
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
` (3 preceding siblings ...)
2012-11-01 16:38 ` Logan Freijo
@ 2012-11-01 17:34 ` Logan Freijo
2012-11-01 19:25 ` Hans de Goede
` (8 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Logan Freijo @ 2012-11-01 17:34 UTC (permalink / raw)
To: lm-sensors
On 11/1/2012 12:19 PM, Hans de Goede wrote:
> Hi,
>
> On 11/01/2012 05:03 PM, Logan Freijo wrote:
>> On 11/1/2012 12:49 AM, Guenter Roeck wrote:
>>> On Wed, Oct 31, 2012 at 06:37:01PM -0400, Logan Freijo wrote:
>>>> **Hello. I have a system running Ubuntu Server 12.04.1 on a Jetway
>>>> motherboard. Sensors-detect finds my AMD cpu temp and a chip for the
>>>> motherboard (f71882fg). However, after adding the suggested line to
>>>> /etc/modules and rebooting, only the cpu temp shows up using the
>>>> sensors command. I have tried acpi-enforce-resources=lax with no
>>>> effect. I have tried searching the internet for an answer and I find
>>>> none. Below is the information requested in the FAQ. I would like
>>>> to note that this is not a new problem, it has been ongoing since I
>>>> bought the motherboard in Jan 2011.
>>>>
>>>> Any help would be appreciated.
>>>>
>>>> Logan
>>>>
>>>>
>>>> *
>>>>
>>>> Motherboard vendor and model*
>>>> JetWay JHZ03-GT-LF
>>>>
>>>> *Lm_sensors and kernel versions*
>>>> sensors version 3.3.1 with libsensors version 3.3.1
>>>> 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012
>>>> x86_64 x86_64 x86_64 GNU/Linux
>>>>
>>>> *The output of sensors*
>>>> k10temp-pci-00c3
>>>> Adapter: PCI adapter
>>>> CPU Temp: +26.0 C (high = +70.0 C)
>>>>
>>>> *The dmesg or syslog output if applicable*
>>>> kernel: [ 8.795196] f71882fg: Found f71882fg chip at 0x220,
>>>> revision 32
>>>> kernel: [ 8.795228] f71882fg.544: failed to claim resource 0
>>>> kernel: [ 8.795233] f71882fg: Device addition failed
>>>>
>>> Hi,
>>>
>>> An old post suggests that you may be able to work around the problem
>>> by booting
>>> with "pnpacpi=off", and that the problem might be due to a BIOS
>>> problem.
>>> See
>>> http://lists.lm-sensors.org/pipermail/lm-sensors/2009-January/025175.html
>>> and subsequent posts for additional details.
>>>
>>> Might be worth a try.
>>>
>>> Guenter
>>>
>>>> *The output of (as root) sensors-detect*
>>>> # sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
>>>> # System: To Be Filled By O.E.M. To Be Filled By O.E.M.
>>>> # Board: JETWAY HZ03-GT
>>>>
>>>> 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):
>>>> 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... Success!
>>>> (driver `k10temp')
>>>> 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
>>>> Intel digital thermal sensor... No
>>>> 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):
>>>> Probing for Super-I/O at 0x2e/0x2f
>>>> Trying family `National Semiconductor/ITE'... No
>>>> Trying family `SMSC'... No
>>>> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
>>>> Found `Fintek F71882FG/F71883FG Super IO Sensors' Success!
>>>> (address 0x225, driver `f71882fg')
>>>> 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):
>>>> 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):
>>>>
>>>> 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):
>>>> Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies
>>>> Inc SB600/SB700/SB800 SMBus
>>>> Module i2c-dev loaded successfully.
>>>>
>>>> Next adapter: Radeon i2c bit bus 0x90 (i2c-0)
>>>> Do you want to scan it? (YES/no/selectively):
>>>> Client found at address 0x50
>>>> Probing for `Analog Devices ADM1033'... No
>>>> Probing for `Analog Devices ADM1034'... No
>>>> Probing for `SPD EEPROM'... No
>>>> Probing for `EDID EEPROM'... Yes
>>>> (confidence 8, not a hardware monitoring chip)
>>>>
>>>> Next adapter: Radeon i2c bit bus 0x91 (i2c-1)
>>>> Do you want to scan it? (YES/no/selectively):
>>>>
>>>> Next adapter: Radeon i2c bit bus 0x92 (i2c-2)
>>>> Do you want to scan it? (YES/no/selectively):
>>>>
>>>> Next adapter: Radeon i2c bit bus 0x93 (i2c-3)
>>>> Do you want to scan it? (YES/no/selectively):
>>>>
>>>> Next adapter: Radeon i2c bit bus 0x14 (i2c-4)
>>>> Do you want to scan it? (YES/no/selectively):
>>>>
>>>> Now follows a summary of the probes I have just done.
>>>> Just press ENTER to continue:
>>>>
>>>> Driver `k10temp' (autoloaded):
>>>> * Chip `AMD Family 10h thermal sensors' (confidence: 9)
>>>>
>>>> Driver `f71882fg':
>>>> * ISA bus, address 0x225
>>>> Chip `Fintek F71882FG/F71883FG Super IO Sensors' (confidence: 9)
>>>>
>>>> To load everything that is needed, add this to /etc/modules:
>>>> #----cut here----
>>>> # Chip drivers
>>>> f71882fg
>>>> #----cut here----
>>>> If you have some drivers built into your kernel, the list above will
>>>> contain too many modules. Skip the appropriate ones!
>>>>
>>>> Do you want to add these lines automatically to /etc/modules?
>>>> (yes/NO)n
>>>>
>>>> Unloading i2c-dev... OK
>>>> Unloading cpuid... OK
>>>>
>>>> *The output of lsmod*
>>>>
>>>> Module Size Used by
>>>> cifs 287317 0
>>>> ext2 73795 1
>>>> dm_multipath 23230 0
>>>> psmouse 97443 0
>>>> edac_core 53746 0
>>>> radeon 804460 1
>>>> serio_raw 13211 0
>>>> k10temp 13166 0
>>>> edac_mce_amd 23709 0
>>>> ttm 76949 1 radeon
>>>> sp5100_tco 13791 0
>>>> drm_kms_helper 46978 1 radeon
>>>> joydev 17693 0
>>>> i2c_piix4 13301 0
>>>> drm 241921 3 radeon,ttm,drm_kms_helper
>>>> i2c_algo_bit 13423 1 radeon
>>>> mac_hid 13253 0
>>>> shpchp 37277 0
>>>> wmi 19256 0
>>>> lp 17799 0
>>>> parport 46562 1 lp
>>>> usbhid 47199 1
>>>> hid 99559 1 usbhid
>>>> r8169 62099 0
>>>> pata_atiixp 13204 4
>>>> dm_raid45 78155 0
>>>> xor 12894 1 dm_raid45
>>>> dm_mirror 22203 0
>>>> dm_region_hash 20918 1 dm_mirror
>>>> dm_log 18564 3 dm_raid45,dm_mirror,dm_region_hash
>>>>
>>>> _______________________________________________
>>>> lm-sensors mailing list
>>>> lm-sensors@lm-sensors.org
>>>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>>>>
>> Thanks for the suggestion Guenter. I did see that post. I added
>> pnpacpi=off to the boot options and it had no effect. I also tried
>> pnpbios=off and pnp_reserve_io with no effect. The temperatures and
>> voltages are displayed in bios and could also be read by several
>> popular windows 7 programs. I am not planing on switch back to
>> windows, but I would like to monitor the temps.
>
> Can you do a "cat /proc/ioports" and send us the output?
>
> That may help to figure out what is causing the io conflict.
>
> Regards,
>
> Hans
>
After my last reply I searched the web again and noticed that some
places indicate "acpi-enforce-resources=lax" and others
"acpi_enforce_resources=lax". So I decided to try all options again. I
found after several reboots that "pnpacpi=off" did when I passed it by
itself. I now have a full range of sensor readings. Is there anyway to
determine which sensor is which? My output for sensors is below. in1 -
in6 seem to be reading incorrect values.
Thanks,
Logan
f71882fg-isa-0220
Adapter: ISA adapter
+3.3V: +3.50 V
in1: +1.06 V (max = +2.04 V)
in2: +0.42 V
in3: +0.98 V
in4: +1.13 V
in5: +0.96 V
in6: +0.75 V
3VSB: +3.31 V
Vbat: +3.33 V
fan1: 1492 RPM
fan2: 0 RPM ALARM
fan3: 1007 RPM
fan4: 0 RPM ALARM
temp1: +33.0 C (high = +85.0 C, hyst = +81.0 C)
(crit = +100.0 C, hyst = +96.0 C) sensor =
transistor
temp2: +32.0 C (high = +85.0 C, hyst = +81.0 C)
(crit = +100.0 C, hyst = +96.0 C) sensor =
transistor
temp3: +32.0 C (high = +70.0 C, hyst = +68.0 C)
(crit = +85.0 C, hyst = +83.0 C) sensor =
transistor
k10temp-pci-00c3
Adapter: PCI adapter
CPU Temp: +26.1 C (high = +70.0 C)
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
` (4 preceding siblings ...)
2012-11-01 17:34 ` Logan Freijo
@ 2012-11-01 19:25 ` Hans de Goede
2012-11-02 3:20 ` Guenter Roeck
` (7 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Hans de Goede @ 2012-11-01 19:25 UTC (permalink / raw)
To: lm-sensors
Hi,
On 11/01/2012 05:38 PM, Logan Freijo wrote:
> On 11/1/2012 12:19 PM, Hans de Goede wrote:
<snip>
>> Can you do a "cat /proc/ioports" and send us the output?
>>
>> That may help to figure out what is causing the io conflict.
>>
>> Regards,
>>
>> Hans
>>
> Here you go:
>
> 0000-0cf7 : PCI Bus 0000:00
> 0000-001f : dma1
> 0020-0021 : pic1
> 0040-0043 : timer0
> 0050-0053 : timer1
> 0060-0060 : keyboard
> 0064-0064 : keyboard
> 0070-0071 : rtc0
> 0080-008f : dma page reg
> 00a0-00a1 : pic2
> 00c0-00df : dma2
> 00f0-00ff : fpu
> 0170-0177 : 0000:00:14.1
> 0170-0177 : pata_atiixp
> 01f0-01f7 : 0000:00:14.1
> 01f0-01f7 : pata_atiixp
> 0225-0244 : pnp 00:09
> 0376-0376 : 0000:00:14.1
> 0376-0376 : pata_atiixp
> 03f6-03f6 : 0000:00:14.1
> 03f6-03f6 : pata_atiixp
> 040b-040b : pnp 00:08
> 04d0-04d1 : pnp 00:08
> 04d6-04d6 : pnp 00:08
> 0800-089f : pnp 00:08
> 0800-0803 : ACPI PM1a_EVT_BLK
> 0804-0805 : ACPI PM1a_CNT_BLK
> 0808-080b : ACPI PM_TMR
> 0810-0815 : ACPI CPU throttle
> 0820-0827 : ACPI GPE0_BLK
> 0900-090f : pnp 00:08
> 0910-091f : pnp 00:08
> 0ae0-0aef : pnp 00:09
> 0b00-0b0f : pnp 00:08
> 0b20-0b3f : pnp 00:08
> 0c00-0c01 : pnp 00:08
> 0c14-0c14 : pnp 00:08
> 0c50-0c51 : pnp 00:08
> 0c52-0c52 : pnp 00:08
> 0c6c-0c6c : pnp 00:08
> 0c6f-0c6f : pnp 00:08
> 0cd0-0cd1 : pnp 00:08
> 0cd2-0cd3 : pnp 00:08
> 0cd4-0cd5 : pnp 00:08
> 0cd6-0cd7 : pnp 00:08
> 0cd8-0cdf : pnp 00:08
> 0cf8-0cff : PCI conf1
> 0d00-ffff : PCI Bus 0000:00
> 8000-800f : 0000:00:11.0
> 8000-800f : ahci
> 9000-9003 : 0000:00:11.0
> 9000-9003 : ahci
> a000-a007 : 0000:00:11.0
> a000-a007 : ahci
> b000-b003 : 0000:00:11.0
> b000-b003 : ahci
> c000-c007 : 0000:00:11.0
> c000-c007 : ahci
> d000-dfff : PCI Bus 0000:01
> d000-d0ff : 0000:01:05.0
> e000-efff : PCI Bus 0000:02
> e800-e8ff : 0000:02:00.0
> e800-e8ff : r8169
> fe00-fefe : pnp 00:08
> ff00-ff0f : 0000:00:14.1
> ff00-ff0f : pata_atiixp
Hmm, it seems that your bios is claiming
the io-range for the hwmon part (and then some
more ports too ...)
Can you try adding "pnp_reserve_io=0x220,8" on the kernel
cmdline? That *might* help. Also to further debug this,
can you please do:
ls -lR /sys/bus/pnp/devices/00\:09/
And:
cat /sys/bus/pnp/devices/00\:09/id
And include the output in your next mail?
Thanks,
Hans
>
> Thanks,
>
> Logan
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
` (5 preceding siblings ...)
2012-11-01 19:25 ` Hans de Goede
@ 2012-11-02 3:20 ` Guenter Roeck
2012-11-02 5:29 ` Logan Freijo
` (6 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Guenter Roeck @ 2012-11-02 3:20 UTC (permalink / raw)
To: lm-sensors
Hi,
On Thu, Nov 01, 2012 at 01:34:35PM -0400, Logan Freijo wrote:
[ ... ]
> >
> After my last reply I searched the web again and noticed that some
> places indicate "acpi-enforce-resources=lax" and others
> "acpi_enforce_resources=lax". So I decided to try all options again.
> I found after several reboots that "pnpacpi=off" did when I passed
> it by itself. I now have a full range of sensor readings. Is there
Would be great if you can provide the logs Hans asked for.
> anyway to determine which sensor is which? My output for sensors is
> below. in1 - in6 seem to be reading incorrect values.
>
Not incorrect - simple reason is that there are voltage dividers on the board.
Tricky part now is to find out what the divider values are. A good starting point
is http://www.lm-sensors.org/wiki/VoltageLabelsAndScaling.
Thanks,
Guenter
> Thanks,
>
> Logan
>
> f71882fg-isa-0220
> Adapter: ISA adapter
> +3.3V: +3.50 V
> in1: +1.06 V (max = +2.04 V)
> in2: +0.42 V
> in3: +0.98 V
> in4: +1.13 V
> in5: +0.96 V
> in6: +0.75 V
> 3VSB: +3.31 V
> Vbat: +3.33 V
> fan1: 1492 RPM
> fan2: 0 RPM ALARM
> fan3: 1007 RPM
> fan4: 0 RPM ALARM
> temp1: +33.0 C (high = +85.0 C, hyst = +81.0 C)
> (crit = +100.0 C, hyst = +96.0 C) sensor > transistor
> temp2: +32.0 C (high = +85.0 C, hyst = +81.0 C)
> (crit = +100.0 C, hyst = +96.0 C) sensor > transistor
> temp3: +32.0 C (high = +70.0 C, hyst = +68.0 C)
> (crit = +85.0 C, hyst = +83.0 C) sensor > transistor
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> CPU Temp: +26.1 C (high = +70.0 C)
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
` (6 preceding siblings ...)
2012-11-02 3:20 ` Guenter Roeck
@ 2012-11-02 5:29 ` Logan Freijo
2012-11-02 9:09 ` Hans de Goede
` (5 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Logan Freijo @ 2012-11-02 5:29 UTC (permalink / raw)
To: lm-sensors
On 11/1/2012 11:20 PM, Guenter Roeck wrote:
> Hi,
>
> On Thu, Nov 01, 2012 at 01:34:35PM -0400, Logan Freijo wrote:
>
> [ ... ]
>
>> After my last reply I searched the web again and noticed that some
>> places indicate "acpi-enforce-resources=lax" and others
>> "acpi_enforce_resources=lax". So I decided to try all options again.
>> I found after several reboots that "pnpacpi=off" did when I passed
>> it by itself. I now have a full range of sensor readings. Is there
> Would be great if you can provide the logs Hans asked for.
>
>> anyway to determine which sensor is which? My output for sensors is
>> below. in1 - in6 seem to be reading incorrect values.
>>
> Not incorrect - simple reason is that there are voltage dividers on the board.
> Tricky part now is to find out what the divider values are. A good starting point
> is http://www.lm-sensors.org/wiki/VoltageLabelsAndScaling.
>
> Thanks,
> Guenter
>
>> Thanks,
>>
>> Logan
>>
>> f71882fg-isa-0220
>> Adapter: ISA adapter
>> +3.3V: +3.50 V
>> in1: +1.06 V (max = +2.04 V)
>> in2: +0.42 V
>> in3: +0.98 V
>> in4: +1.13 V
>> in5: +0.96 V
>> in6: +0.75 V
>> 3VSB: +3.31 V
>> Vbat: +3.33 V
>> fan1: 1492 RPM
>> fan2: 0 RPM ALARM
>> fan3: 1007 RPM
>> fan4: 0 RPM ALARM
>> temp1: +33.0 C (high = +85.0 C, hyst = +81.0 C)
>> (crit = +100.0 C, hyst = +96.0 C) sensor >> transistor
>> temp2: +32.0 C (high = +85.0 C, hyst = +81.0 C)
>> (crit = +100.0 C, hyst = +96.0 C) sensor >> transistor
>> temp3: +32.0 C (high = +70.0 C, hyst = +68.0 C)
>> (crit = +85.0 C, hyst = +83.0 C) sensor >> transistor
>>
>> k10temp-pci-00c3
>> Adapter: PCI adapter
>> CPU Temp: +26.1 C (high = +70.0 C)
>>
>>
Here is the new output for "cat /proc/ioports"
0000-0cf7 : PCI Bus 0000:00
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-0060 : keyboard
0064-0064 : keyboard
0070-0071 : rtc_cmos
0070-0071 : rtc0
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : 0000:00:14.1
0170-0177 : pata_atiixp
01f0-01f7 : 0000:00:14.1
01f0-01f7 : pata_atiixp
0220-0227 : f71882fg
0376-0376 : 0000:00:14.1
0376-0376 : pata_atiixp
03f6-03f6 : 0000:00:14.1
03f6-03f6 : pata_atiixp
0800-0803 : ACPI PM1a_EVT_BLK
0804-0805 : ACPI PM1a_CNT_BLK
0808-080b : ACPI PM_TMR
0810-0815 : ACPI CPU throttle
0820-0827 : ACPI GPE0_BLK
0cf8-0cff : PCI conf1
0d00-ffff : PCI Bus 0000:00
8000-800f : 0000:00:11.0
8000-800f : ahci
9000-9003 : 0000:00:11.0
9000-9003 : ahci
a000-a007 : 0000:00:11.0
a000-a007 : ahci
b000-b003 : 0000:00:11.0
b000-b003 : ahci
c000-c007 : 0000:00:11.0
c000-c007 : ahci
d000-dfff : PCI Bus 0000:01
d000-d0ff : 0000:01:05.0
e000-efff : PCI Bus 0000:02
e800-e8ff : 0000:02:00.0
e800-e8ff : r8169
ff00-ff0f : 0000:00:14.1
ff00-ff0f : pata_atiixp
Device 09 no longer shows up.
ls -lR /sys/bus/pnp/devices/00\:09/
and
cat /sys/bus/pnp/devices/00\:09/id
return "No such file or directory"
I will take a look at the wiki entry.
Thanks,
Logan
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
` (7 preceding siblings ...)
2012-11-02 5:29 ` Logan Freijo
@ 2012-11-02 9:09 ` Hans de Goede
2012-11-02 13:22 ` Logan Freijo
` (4 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Hans de Goede @ 2012-11-02 9:09 UTC (permalink / raw)
To: lm-sensors
Hi,
On 11/02/2012 06:29 AM, Logan Freijo wrote:
<snip>
> Device 09 no longer shows up.
> ls -lR /sys/bus/pnp/devices/00\:09/
> and
> cat /sys/bus/pnp/devices/00\:09/id
> return "No such file or directory"
>
Yeah, that is due to the pnpacpi=off option you
are using, please boot without that (or any other
special options), and then repeat the 2 above
commands. This will give us an idea if it will be
feasible to fix this in a way which will not
require passing those special kernel cmdline
options.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
` (8 preceding siblings ...)
2012-11-02 9:09 ` Hans de Goede
@ 2012-11-02 13:22 ` Logan Freijo
2012-11-02 16:28 ` Hans de Goede
` (3 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Logan Freijo @ 2012-11-02 13:22 UTC (permalink / raw)
To: lm-sensors
On 11/2/2012 5:09 AM, Hans de Goede wrote:
> Hi,
>
> On 11/02/2012 06:29 AM, Logan Freijo wrote:
>
> <snip>
>
>> Device 09 no longer shows up.
>> ls -lR /sys/bus/pnp/devices/00\:09/
>> and
>> cat /sys/bus/pnp/devices/00\:09/id
>> return "No such file or directory"
>>
>
> Yeah, that is due to the pnpacpi=off option you
> are using, please boot without that (or any other
> special options), and then repeat the 2 above
> commands. This will give us an idea if it will be
> feasible to fix this in a way which will not
> require passing those special kernel cmdline
> options.
>
> Regards,
>
> Hans
>
Alright. Here is ls -lR /sys/bus/pnp/devices/00\:09/
/sys/bus/pnp/devices/00:09/:
total 0
lrwxrwxrwx 1 root root 0 Nov 2 09:18 driver ->
../../../bus/pnp/drivers/system
lrwxrwxrwx 1 root root 0 Nov 2 09:18 firmware_node ->
../../LNXSYSTM:00/device:00/PNP0A03:00/device:17/PNP0C02:03
-r--r--r-- 1 root root 4096 Nov 2 09:18 id
-r--r--r-- 1 root root 4096 Nov 2 09:18 options
drwxr-xr-x 2 root root 0 Nov 2 09:18 power
-rw-r--r-- 1 root root 4096 Nov 2 09:18 resources
lrwxrwxrwx 1 root root 0 Nov 2 09:17 subsystem -> ../../../bus/pnp
-rw-r--r-- 1 root root 4096 Nov 2 09:17 uevent
/sys/bus/pnp/devices/00:09/power:
total 0
-rw-r--r-- 1 root root 4096 Nov 2 09:18 async
-rw-r--r-- 1 root root 4096 Nov 2 09:18 autosuspend_delay_ms
-rw-r--r-- 1 root root 4096 Nov 2 09:18 control
-r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_active_kids
-r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_active_time
-r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_enabled
-r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_status
-r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_suspended_time
-r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_usage
And cat /sys/bus/pnp/devices/00\:09/id
PNP0c02
Thanks,
Logan
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
` (9 preceding siblings ...)
2012-11-02 13:22 ` Logan Freijo
@ 2012-11-02 16:28 ` Hans de Goede
2012-11-02 20:04 ` Logan Freijo
` (2 subsequent siblings)
13 siblings, 0 replies; 15+ messages in thread
From: Hans de Goede @ 2012-11-02 16:28 UTC (permalink / raw)
To: lm-sensors
Hi,
On 11/02/2012 02:22 PM, Logan Freijo wrote:
> On 11/2/2012 5:09 AM, Hans de Goede wrote:
>> Hi,
>>
>> On 11/02/2012 06:29 AM, Logan Freijo wrote:
>>
>> <snip>
>>
>>> Device 09 no longer shows up.
>>> ls -lR /sys/bus/pnp/devices/00\:09/
>>> and
>>> cat /sys/bus/pnp/devices/00\:09/id
>>> return "No such file or directory"
>>>
>>
>> Yeah, that is due to the pnpacpi=off option you
>> are using, please boot without that (or any other
>> special options), and then repeat the 2 above
>> commands. This will give us an idea if it will be
>> feasible to fix this in a way which will not
>> require passing those special kernel cmdline
>> options.
>>
>> Regards,
>>
>> Hans
>>
> Alright. Here is ls -lR /sys/bus/pnp/devices/00\:09/
>
> /sys/bus/pnp/devices/00:09/:
> total 0
> lrwxrwxrwx 1 root root 0 Nov 2 09:18 driver -> ../../../bus/pnp/drivers/system
> lrwxrwxrwx 1 root root 0 Nov 2 09:18 firmware_node -> ../../LNXSYSTM:00/device:00/PNP0A03:00/device:17/PNP0C02:03
> -r--r--r-- 1 root root 4096 Nov 2 09:18 id
> -r--r--r-- 1 root root 4096 Nov 2 09:18 options
> drwxr-xr-x 2 root root 0 Nov 2 09:18 power
> -rw-r--r-- 1 root root 4096 Nov 2 09:18 resources
> lrwxrwxrwx 1 root root 0 Nov 2 09:17 subsystem -> ../../../bus/pnp
> -rw-r--r-- 1 root root 4096 Nov 2 09:17 uevent
>
> /sys/bus/pnp/devices/00:09/power:
> total 0
> -rw-r--r-- 1 root root 4096 Nov 2 09:18 async
> -rw-r--r-- 1 root root 4096 Nov 2 09:18 autosuspend_delay_ms
> -rw-r--r-- 1 root root 4096 Nov 2 09:18 control
> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_active_kids
> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_active_time
> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_enabled
> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_status
> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_suspended_time
> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_usage
>
Good, no other drivers are using this pnp-id, but:
>
> And cat /sys/bus/pnp/devices/00\:09/id
>
> PNP0c02
But this is bad news, this is the general pnp ID for reserving
resources, without specifying a driver to use them ...
This could mean that your ACPI code is using the device, and
the firmware authors are reserving it in a funky way. More likely
this is just a BIOS misfeature of some sorts...
Anyways there is little we can do here to fix things, as we can
not make the f71882fg driver claim that pnp id.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
` (10 preceding siblings ...)
2012-11-02 16:28 ` Hans de Goede
@ 2012-11-02 20:04 ` Logan Freijo
2012-11-03 15:43 ` Hans de Goede
2012-11-04 2:02 ` Logan Freijo
13 siblings, 0 replies; 15+ messages in thread
From: Logan Freijo @ 2012-11-02 20:04 UTC (permalink / raw)
To: lm-sensors
On 11/2/2012 12:28 PM, Hans de Goede wrote:
> Hi,
>
> On 11/02/2012 02:22 PM, Logan Freijo wrote:
>> On 11/2/2012 5:09 AM, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 11/02/2012 06:29 AM, Logan Freijo wrote:
>>>
>>> <snip>
>>>
>>>> Device 09 no longer shows up.
>>>> ls -lR /sys/bus/pnp/devices/00\:09/
>>>> and
>>>> cat /sys/bus/pnp/devices/00\:09/id
>>>> return "No such file or directory"
>>>>
>>>
>>> Yeah, that is due to the pnpacpi=off option you
>>> are using, please boot without that (or any other
>>> special options), and then repeat the 2 above
>>> commands. This will give us an idea if it will be
>>> feasible to fix this in a way which will not
>>> require passing those special kernel cmdline
>>> options.
>>>
>>> Regards,
>>>
>>> Hans
>>>
>> Alright. Here is ls -lR /sys/bus/pnp/devices/00\:09/
>>
>> /sys/bus/pnp/devices/00:09/:
>> total 0
>> lrwxrwxrwx 1 root root 0 Nov 2 09:18 driver ->
>> ../../../bus/pnp/drivers/system
>> lrwxrwxrwx 1 root root 0 Nov 2 09:18 firmware_node ->
>> ../../LNXSYSTM:00/device:00/PNP0A03:00/device:17/PNP0C02:03
>> -r--r--r-- 1 root root 4096 Nov 2 09:18 id
>> -r--r--r-- 1 root root 4096 Nov 2 09:18 options
>> drwxr-xr-x 2 root root 0 Nov 2 09:18 power
>> -rw-r--r-- 1 root root 4096 Nov 2 09:18 resources
>> lrwxrwxrwx 1 root root 0 Nov 2 09:17 subsystem -> ../../../bus/pnp
>> -rw-r--r-- 1 root root 4096 Nov 2 09:17 uevent
>>
>> /sys/bus/pnp/devices/00:09/power:
>> total 0
>> -rw-r--r-- 1 root root 4096 Nov 2 09:18 async
>> -rw-r--r-- 1 root root 4096 Nov 2 09:18 autosuspend_delay_ms
>> -rw-r--r-- 1 root root 4096 Nov 2 09:18 control
>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_active_kids
>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_active_time
>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_enabled
>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_status
>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_suspended_time
>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_usage
>>
>
> Good, no other drivers are using this pnp-id, but:
>
>>
>> And cat /sys/bus/pnp/devices/00\:09/id
>>
>> PNP0c02
>
> But this is bad news, this is the general pnp ID for reserving
> resources, without specifying a driver to use them ...
>
> This could mean that your ACPI code is using the device, and
> the firmware authors are reserving it in a funky way. More likely
> this is just a BIOS misfeature of some sorts...
>
> Anyways there is little we can do here to fix things, as we can
> not make the f71882fg driver claim that pnp id.
>
> Regards,
>
> Hans
>
Hello,
Thanks for looking into this further Hans. Is there any adverse effect
to using the pnpacpi=off option? Is it possible there is a CMOS option
that will disable the BIOS use of this resource?
Logan
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
` (11 preceding siblings ...)
2012-11-02 20:04 ` Logan Freijo
@ 2012-11-03 15:43 ` Hans de Goede
2012-11-04 2:02 ` Logan Freijo
13 siblings, 0 replies; 15+ messages in thread
From: Hans de Goede @ 2012-11-03 15:43 UTC (permalink / raw)
To: lm-sensors
Hi,
On 11/02/2012 09:04 PM, Logan Freijo wrote:
> On 11/2/2012 12:28 PM, Hans de Goede wrote:
>> Hi,
>>
>> On 11/02/2012 02:22 PM, Logan Freijo wrote:
>>> On 11/2/2012 5:09 AM, Hans de Goede wrote:
>>>> Hi,
>>>>
>>>> On 11/02/2012 06:29 AM, Logan Freijo wrote:
>>>>
>>>> <snip>
>>>>
>>>>> Device 09 no longer shows up.
>>>>> ls -lR /sys/bus/pnp/devices/00\:09/
>>>>> and
>>>>> cat /sys/bus/pnp/devices/00\:09/id
>>>>> return "No such file or directory"
>>>>>
>>>>
>>>> Yeah, that is due to the pnpacpi=off option you
>>>> are using, please boot without that (or any other
>>>> special options), and then repeat the 2 above
>>>> commands. This will give us an idea if it will be
>>>> feasible to fix this in a way which will not
>>>> require passing those special kernel cmdline
>>>> options.
>>>>
>>>> Regards,
>>>>
>>>> Hans
>>>>
>>> Alright. Here is ls -lR /sys/bus/pnp/devices/00\:09/
>>>
>>> /sys/bus/pnp/devices/00:09/:
>>> total 0
>>> lrwxrwxrwx 1 root root 0 Nov 2 09:18 driver -> ../../../bus/pnp/drivers/system
>>> lrwxrwxrwx 1 root root 0 Nov 2 09:18 firmware_node -> ../../LNXSYSTM:00/device:00/PNP0A03:00/device:17/PNP0C02:03
>>> -r--r--r-- 1 root root 4096 Nov 2 09:18 id
>>> -r--r--r-- 1 root root 4096 Nov 2 09:18 options
>>> drwxr-xr-x 2 root root 0 Nov 2 09:18 power
>>> -rw-r--r-- 1 root root 4096 Nov 2 09:18 resources
>>> lrwxrwxrwx 1 root root 0 Nov 2 09:17 subsystem -> ../../../bus/pnp
>>> -rw-r--r-- 1 root root 4096 Nov 2 09:17 uevent
>>>
>>> /sys/bus/pnp/devices/00:09/power:
>>> total 0
>>> -rw-r--r-- 1 root root 4096 Nov 2 09:18 async
>>> -rw-r--r-- 1 root root 4096 Nov 2 09:18 autosuspend_delay_ms
>>> -rw-r--r-- 1 root root 4096 Nov 2 09:18 control
>>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_active_kids
>>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_active_time
>>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_enabled
>>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_status
>>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_suspended_time
>>> -r--r--r-- 1 root root 4096 Nov 2 09:18 runtime_usage
>>>
>>
>> Good, no other drivers are using this pnp-id, but:
>>
>>>
>>> And cat /sys/bus/pnp/devices/00\:09/id
>>>
>>> PNP0c02
>>
>> But this is bad news, this is the general pnp ID for reserving
>> resources, without specifying a driver to use them ...
>>
>> This could mean that your ACPI code is using the device, and
>> the firmware authors are reserving it in a funky way. More likely
>> this is just a BIOS misfeature of some sorts...
>>
>> Anyways there is little we can do here to fix things, as we can
>> not make the f71882fg driver claim that pnp id.
>>
>> Regards,
>>
>> Hans
>>
> Hello,
>
> Thanks for looking into this further Hans. Is there any adverse effect to using the pnpacpi=off option?
Now a days not really, since there is little ISA stuff left in a modern PC, and what
is there usually is detected fine without isapnp too, since it has been at the
same isa address since the beginning of time (ie serial ports, if you're lucky enough
to have a serial port on your motherboard). However if in the future you think:
"hey why is Linux not seeing my foobar hardware" where by foobar is something
ancient like say a floppy controller, try removing the option. Note this is all
AFAIK, this is veering away a bit from my area of expertise (which is certain hwmon
chips and usb).
> Is it possible there is a CMOS option that will disable the BIOS use of this resource?
Not likely.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: [lm-sensors] f71882fg not showing motherboard temps
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
` (12 preceding siblings ...)
2012-11-03 15:43 ` Hans de Goede
@ 2012-11-04 2:02 ` Logan Freijo
13 siblings, 0 replies; 15+ messages in thread
From: Logan Freijo @ 2012-11-04 2:02 UTC (permalink / raw)
To: lm-sensors
On 11/3/2012 11:43 AM, Hans de Goede wrote:
> Hi,
>
>
> Now a days not really, since there is little ISA stuff left in a
> modern PC, and what
> is there usually is detected fine without isapnp too, since it has
> been at the
> same isa address since the beginning of time (ie serial ports, if
> you're lucky enough
> to have a serial port on your motherboard). However if in the future
> you think:
> "hey why is Linux not seeing my foobar hardware" where by foobar is
> something
> ancient like say a floppy controller, try removing the option. Note
> this is all
> AFAIK, this is veering away a bit from my area of expertise (which is
> certain hwmon
> chips and usb).
>
> > Is it possible there is a CMOS option that will disable the BIOS use
> of this resource?
>
> Not likely.
>
> Regards,
>
> Hans
>
Ok. I won't worry about it then. The wiki says that custom
configurations should be sent to the mailing list. Below is the
configuration I have that seems to work. Hopefully this will help
someone else.
Thanks,
Logan
chip "f71882fg-*"
### Voltages
#Not sure about in2. Reading changes with change to NB voltage
#and Vcore voltage
label in1 "Vcore"
label in2 "NBcore"
label in3 "+5V"
label in4 "+12V"
label in5 "5VSB"
label in6 "VDIMM"
compute in2 @ * (16/8), @ / (16/8)
compute in3 @ * (42/8), @ / (42/8)
compute in4 @ * (88/8), @ / (88/8)
compute in5 @ * (42/8), @ / (42/8)
compute in6 @ * (16/8), @ / (16/8)
set in1_min 0.7
set in1_max 1.5
set in2_min 1.2 * 0.95
set in2_max 1.2 * 1.05
set in3_min 5 * 0.95
set in3_max 5 * 1.05
set in4_min 12 * 0.95
set in4_max 12 * 1.05
set in5_min 5 * 0.95
set in5_max 5 * 1.95
set in6_min 1.5 * 0.95
set in6_max 1.5 * 1.95
###Temps
label temp1 "CPU Temp"
label temp2 "SYS Temp1"
label temp3 "SYS Temp2"
###Fans
#Fan4 doesn't exist on this motherboard
ignore fan4
label fan1 "CPU Fan"
label fan2 "SYS Fan1"
label fan3 "SYS Fan2"
set fan1_min 500
set fan2_min 500
set fan3_min 500
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2012-11-04 2:02 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-10-31 22:37 [lm-sensors] f71882fg not showing motherboard temps Logan Freijo
2012-11-01 4:49 ` Guenter Roeck
2012-11-01 16:03 ` Logan Freijo
2012-11-01 16:19 ` Hans de Goede
2012-11-01 16:38 ` Logan Freijo
2012-11-01 17:34 ` Logan Freijo
2012-11-01 19:25 ` Hans de Goede
2012-11-02 3:20 ` Guenter Roeck
2012-11-02 5:29 ` Logan Freijo
2012-11-02 9:09 ` Hans de Goede
2012-11-02 13:22 ` Logan Freijo
2012-11-02 16:28 ` Hans de Goede
2012-11-02 20:04 ` Logan Freijo
2012-11-03 15:43 ` Hans de Goede
2012-11-04 2:02 ` Logan Freijo
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.