On Mon, Feb 25, 2013 at 01:55:40AM +1100, Tim Long wrote: > Package: lm-sensors > Version: 1:3.3.2-2 > Severity: normal > > Dear Maintainer, > > Updating my (HP Compaq 6730s) laptop to wheezy I can't get fancontrol to run > properly.
Was it working correctly before upgrading to wheezy? Note also that on a laptop the fan speed is supposed to already be controlled by the BIOS, at the fan is usually common to the CPU and the GPU. > I think lm-sensors is unable to find/configure the fan control system. > > After the install I get the following message on boot up: > === > [warn] Not starting fancontrol; run pwmconfig first. ... (warning). > === > > Running pwmconfig I get the following error message: > === > /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed > === > > Running the 'sensors' command I turn up the following: > === > acpitz-virtual-0 > Adapter: Virtual device > temp1: +53.0°C (crit = +110.0°C) > temp2: +49.0°C (crit = +256.0°C) > temp3: +49.0°C (crit = +112.0°C) > temp4: +51.0°C (crit = +105.0°C) > temp5: +30.6°C (crit = +112.0°C) > temp6: +50.0°C (crit = +110.0°C) > > coretemp-isa-0000 > Adapter: ISA adapter > Core 0: +45.0°C (high = +105.0°C, crit = +105.0°C) > Core 1: +49.0°C (high = +105.0°C, crit = +105.0°C) > === > > Running sensors-detect I get the following: > === > # sensors-detect > # sensors-detect revision 6031 (2012-03-07 17:14:01 +0100) > # System: Hewlett-Packard HP Compaq 6730s [F.07] (laptop) > # Board: Hewlett-Packard 30E9 > > 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): ^C > walter:/var/log# sensors-detect | tee /tmp/sensors-detect.log > ^Cwalter:/var/log# clear > > walter:/var/log# sensors-detect > # sensors-detect revision 6031 (2012-03-07 17:14:01 +0100) > # System: Hewlett-Packard HP Compaq 6730s [F.07] (laptop) > # Board: Hewlett-Packard 30E9 > > 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 > 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'... Yes > Found unknown chip with ID 0x4501 > 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 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 > Sorry, no supported PCI bus adapters found. > Module i2c-dev loaded successfully. > > Next adapter: Radeon i2c bit bus 0x90 (i2c-0) > Do you want to scan it? (YES/no/selectively): y > > Next adapter: Radeon i2c bit bus 0x91 (i2c-1) > Do you want to scan it? (YES/no/selectively): y > > Next adapter: Radeon i2c bit bus 0x92 (i2c-2) > Do you want to scan it? (YES/no/selectively): y > > Next adapter: Radeon i2c bit bus 0x93 (i2c-3) > Do you want to scan it? (YES/no/selectively): y > > Next adapter: Radeon i2c bit bus 0x14 (i2c-4) > Do you want to scan it? (YES/no/selectively): y > Client found at address 0x4f > Probing for `National Semiconductor LM75'... No > Probing for `National Semiconductor LM75A'... No > Probing for `Dallas Semiconductor DS75'... No > Probing for `Dallas Semiconductor DS1621/DS1631'... No > Probing for `Maxim MAX6642'... No > Probing for `Texas Instruments TMP421'... No > Probing for `Texas Instruments TMP422'... No > Probing for `Maxim MAX6633/MAX6634/MAX6635'... No > Probing for `NXP/Philips SA56004'... No > 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) > > 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) > > To load everything that is needed, add this to /etc/modules: > #----cut here---- > # Chip drivers > coretemp > #----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 > === Indeed sensors-detect found sensors to get the temperature, but didn't find any way to control the fan. What driver was in used before you upgrade to wheezy? > Finally, sniffing through the dmesg log I found two things that might be > relevant. > > There is a kernel oops aboutt a bad BIOS: > === > [ 0.000000] WARNING: at > /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/drivers/iommu/dmar.c:492 > warn_invalid_dmar+0x77/0x85() > [ 0.000000] Hardware name: HP Compaq 6730s > [ 0.000000] Your BIOS is broken; DMAR reported at address 0! > [ 0.000000] BIOS vendor: Hewlett-Packard; Ver: 68PZD Ver. F.07; Product > Version: F.07 > [ 0.000000] Modules linked in: > [ 0.000000] Pid: 0, comm: swapper Not tainted 3.2.0-4-amd64 #1 Debian > 3.2.35-2 > [ 0.000000] Call Trace: > [ 0.000000] [<ffffffff81046a75>] ? warn_slowpath_common+0x78/0x8c > === This is not related to the issue. > There is also a i2c error message: > === > [ 6552.951207] i2c /dev entries driver > [ 6572.123203] i2c i2c-4: sendbytes: NAK bailout. > [ 6572.124176] i2c i2c-4: sendbytes: NAK bailout. > [ 6572.125070] i2c i2c-4: sendbytes: NAK bailout. > [ 6572.125956] i2c i2c-4: sendbytes: NAK bailout. > === This is not related to your issue, as it is the I2C bus of your Radeon card. -- Aurelien Jarno GPG: 1024D/F1BCDB73 [email protected] http://www.aurel32.net -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
