[prev in list] [next in list] [prev in thread] [next in thread] 

List:       trac
Subject:    [Trac] Re: lm-sensors and failure to control fan speed in Ubuntu
From:       Matt Good <matt+goog () matt-good ! net>
Date:       2009-12-27 19:03:52
Message-ID: 34263bd9-6aa4-4d0f-8d3c-bb610bfc12a8 () j19g2000yqk ! googlegroups ! com
[Download RAW message or body]

Sorry, you've got the wrong mailing list.  This is for the Trac
software.

On Dec 27, 9:06 am, nano <thomas.be...@gmail.com> wrote:
> Hi,
>
> I have a question related to lm-sensors and in particular fan control.
> I've tried to find
> a solution in many places online but with no luck, I think the people
> at
> lm-sensors will be the last place I look.
>
> I recently installed Ubuntu Karmic 9.10 (dual boot) on a Vista Acer
> Aspire 3810t laptop. Processor and chipset specs are:
> ---------------------------------------------------------
>       * - Intel® Core™2 Solo ultra low voltage processor SU3500
>       * - Mobile Intel® GS45 Express Chipset
> Power:
>       * ACPI 3.0 CPU power management standard: supports Standby and
>         Hibernation power-saving modes, 62.16 W 5600 mAh 6-cell Li-ion
>         battery pack: Acer PowerSmart 3-pin 65 W AC adapter, ENERGY
>         STAR® 5.0
> ----------------------------------------------------------
>
> Under Ubuntu 9.10 there appears to be a significant increase in the
> fan
> operation. Both when the laptop is plugged in and unplugged the fans
> operate almost
> constantly and at a strong speed. Since this did not happen under
> Vista
> and is quite bothersome, I started looking around for a solution.
>
> I installed the "Sensors Applet on the gnome panel" but that only
> gives
> me temperature readouts (the Core0 temp is always around 41 C, with
> the
> fan spinning all the time).
>
> I then installed "coretemp" through Synaptic, "lm-sensors", ran
> "sensors-detect" (I have pasted the output of sensors-detect after the
> end of the email as it is quite long). After that I ran "sensors" on
> the
> Terminal. This is what I got:
>
> ------------------------------------------------------------
> cpitz-virtual-0
> Adapter: Virtual device
> temp1:       +26.8°C  (crit = +127.0°C)
>
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +42.0°C  (high = +100.0°C, crit = +100.0°C)
> ------------------------------------------------------------
>
> Thus, no readouts for voltages or fan speeds.
>
> After that I tried running "pwmconfig" through the terminal, to
> receive:
>
> ----------------------------------------------------------------------
> /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed
> ----------------------------------------------------------------------
>
> My knowledge is limited and I could not find
> any solutions to making the fan spin properly, that's why I decided to
> ask you guys last.
>
> I should mention that I use kernel 2.6.31-16-generic, Grub2(beta-4),
> my
> Acer laptop BIOS is 1.17 (the most recent one), and that inside the
> BIOS
> there are no options for fan speeds or voltages.
>
> If anyone can provide any information as to what the problem is it
> would
> be hugely appreciated.
>
> I paste the contents of "sensors-detect" command below. Thanks,
>
> Thomas
>
> -----------------------------------------------------------------------
> (contents of "sensors-detect'):
>
> "We can start with probing for (PCI) I2C or SMBus adapters.
> Do you want to probe now? (YES/no): y
> Probing for PCI bus adapters...
> Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH9
>
> We will now try to load each adapter module in turn.
> Load `i2c-i801' (say NO if built into your kernel)? (YES/no): y
> Module loaded successfully.
> If you have undetectable or unsupported I2C/SMBus adapters, you can
> have
> them scanned by manually loading the modules before running this
> script.
>
> To continue, we need module `i2c-dev' to be loaded.
> Do you want to load `i2c-dev' now? (YES/no): y
> Module loaded successfully.
>
> We are now going to do the I2C/SMBus adapter probings. Some chips may
> be double detected; we choose the one with the highest confidence
> value in that case.
> If you found that the adapter hung after probing a certain address,
> you can specify that address to remain unprobed.
>
> Next adapter: intel drm CRTDDC_A (i2c-0)
> Do you want to scan it? (YES/no/selectively): y
>
> Next adapter: intel drm LVDSDDC_C (i2c-1)
> Do you want to scan it? (YES/no/selectively): y
> Client found at address 0x28
> Probing for `National Semiconductor LM78'...                No
> Probing for `National Semiconductor LM78-J'...              No
> Probing for `National Semiconductor LM79'...                No
> Probing for `National Semiconductor LM80'...                No
> Probing for `Winbond W83781D'...                            No
> Probing for `Winbond W83782D'...                            No
> Probing for `Winbond W83627HF'...                           No
> Probing for `Winbond W83627EHF'...                          No
> Probing for `Winbond W83627DHG'...                          No
> Probing for `Asus AS99127F (rev.1)'...                      No
> Probing for `Asus AS99127F (rev.2)'...                      No
> Probing for `Asus ASB100 Bach'...                           No
> Probing for `Analog Devices ADM1029'...                     No
> Probing for `ITE IT8712F'...                                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)
>
> Next adapter: intel drm HDMIB (i2c-2)
> Do you want to scan it? (YES/no/selectively): y
>
> Next adapter: DPDDC-B (i2c-3)
> Do you want to scan it? (YES/no/selectively): y
>
> Next adapter: DPDDC-D (i2c-4)
> Do you want to scan it? (YES/no/selectively): y
>
> Next adapter: SMBus I801 adapter at 3000 (i2c-5)
> Do you want to scan it? (YES/no/selectively): y
> 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'...                                No
> Client found at address 0x52
> Probing for `Analog Devices ADM1033'...                     No
> Probing for `Analog Devices ADM1034'...                     No
> Probing for `SPD EEPROM'...                                 No
> Probing for `EDID EEPROM'...                                No
>
> Some chips are also 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 LM78-J' 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
> Probing for `IPMI BMC KCS' at 0xca0...                      No
> Probing for `IPMI BMC SMIC' at 0xca8...                     No
>
> Some Super I/O chips may also contain 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'...                   No
> Trying family `SMSC'...                                     No
> Trying family `VIA/Winbond/Fintek'...                       No
> Trying family `ITE'...                                      No
> Probing for Super-I/O at 0x4e/0x4f
> Trying family `National Semiconductor'...                   No
> Trying family `SMSC'...                                     No
> Trying family `VIA/Winbond/Fintek'...                       No
> Trying family `ITE'...                                      No
>
> Some south bridges, CPUs or memory controllers may also contain
> embedded sensors. Do you want to scan for them? (YES/no): y
> Silicon Integrated Systems SIS5595...                       No
> VIA VT82C686 Integrated Sensors...                          No
> VIA VT8231 Integrated Sensors...                            No
> AMD K8 thermal sensors...                                   No
> AMD K10 thermal sensors...                                  No
> Intel Core family thermal sensor...                         Success!
>     (driver `coretemp')
> Intel AMB FB-DIMM thermal sensor...                         No
>
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
>
> Driver `coretemp' (should be inserted):
>   Detects correctly:
>   * Chip `Intel Core family thermal sensor' (confidence: 9)"
> --------------------------------------------------------------------

--

You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@googlegroups.com.
To unsubscribe from this group, send email to trac-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic