pwmconfig does not work after upgrade to 9.10 on TYAN server

[Greg Tippitt]

Prior to upgrading from 9.04 to 9.10 I had configured pwmconfig/sensors/fancontrol so that the cooling fans on my servers were not too loud. I have 2 TYAN Transport GX28 servers with Tyan Thunder K8S Pro S2881G2NR motherboards, which have the latest BIOS updates from TYAN. These are 1U servers, which have very loud fans. I am using them outside of a rack in my home, and they stayed cool with fans running at about 1/3 the maximum default speeds. After upgrading to Ubuntu version 9.10, the fans are now running very loud again. When I run sensors, I get only the basic k8temp CPU temperatures and do not get the long version of the output that showed fan speed, temp, or voltage sensors.

--------------------------------------------------------------------------
I tried to run pwmconfig again to configure the '/etc/fancontrol configuration file, but I get an error that says:

         /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed
--------------------------------------------------------------------------
I ran /usr/sbin/sensors-detect and it said the following:
         Driver `w83627hf' (should be inserted):
            Detects correctly:
                * ISA bus, address 0x290
               Chip `Winbond W83627HF/F/HG/G Super IO Sensors' (confidence: 9)

         Driver `k8temp' (should be inserted):
            Detects correctly:
              * Chip `AMD K8 thermal sensors' (confidence: 9)

       I will now generate the commands needed to load the required modules.
       Just press ENTER to continue:

       To load everything that is needed, add this to /etc/modules:

          #----cut here----
          # Chip drivers
            w83627hf
            k8temp
          #----cut here----

     Do you want to add these lines automatically? (yes/NO)y
--------------------------------------------------------------------------
I have also tried a reinstall of lm-sensors that did not help.
     lm-sensors:
        Installed: 1:3.0.2-2ubuntu4
        Candidate: 1:3.0.2-2ubuntu4
        Version table: 1:3.0.2-2ubuntu4 0
--------------------------------------------------------------------------
I get the following error reported for ACPI by dmesg

[ 0.817620] powernow-k8: Found 2 AMD Opteron(tm) Processor 246 HE processors (2 cpu cores) (version 2.20.00)
[ 0.817640] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found.
[ 0.817642] [Firmware Bug]: powernow-k8: Try again with latest BIOS.

[ 11.213821] w83627hf: Found W83627HF chip at 0x290
[ 11.213859] ACPI: I/O resource w83627hf [0x295-0x296] conflicts with ACPI region IHHM [0x295-0x296]
[ 11.213864] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 11.252068] w83627hf: Found W83627HF chip at 0x290
[ 11.252105] ACPI: I/O resource w83627hf [0x295-0x296] conflicts with ACPI region IHHM [0x295-0x296]
[ 11.252110] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 11.286635] w83627hf: Found W83627HF chip at 0x290
[ 11.286678] ACPI: I/O resource w83627hf [0x295-0x296] conflicts with ACPI region IHHM [0x295-0x296]
[ 11.286683] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
--------------------------------------------------------------------------
On one of my servers the /boot/grub/menu.lst still had the option to load the 2.6.28-16 kernal image.
When I booted with this prior kernel image, the pwmconfig and fancontrol worked correctly and
and sensors produced the output in the attached "sensors.log" file.
With the current 2.6.31-14 kernel, sensors only reported the first 6 lines for CPU temp.

--------------------------------------------------------------------------
I have tried to edit menu.lst on my second server, but it no longer has the
old kernel available, and I cannot figure out how to load it.

I tried to run:
      sudo apt-get install linux-image-2.6.28-16-generic
but got the following:

Package linux-image-2.6.28-16-generic is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package linux-image-2.6.28-16-generic has no installation candidate

--------------------------------------------------------------------------

This is my first bug report. I am sorry if I have been given your too much or
too little information.

Please let me know if I can provide any other information that you need.

Thanks,
Greg

[Greg Tippitt (gtippitt)]

For other newbies like myself that find this bug report and need a work-around:

I was able to download a prior image from the link below.

http://packages.ubuntu.com/jaunty-updates/linux-image-2.6.28-16-generic

After installing this package with the DEB package installer, I made the linux-image-2.6.28-16-generic kernel my default at boot time using the following commands.

sudo /boot/grub/menu.lst

change
     default 0 to select the 2.5.28-16 kernel from the list at the bottom of the menu.lst file

These are numbered 0,1,2, etc so you could change "default 0" to "default 2" if you you want the 3rd entry to be used at boot time.

[Jeremy Foshee (jeremyfoshee)]

Hi gtippitt,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 475641

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Greg Tippitt (gtippitt)]

On April 23, 2010
I have downloaded current LiveCD versions of Ubuntu and tested the following:

ubuntu-8.04.4-desktop-amd64.iso
ubuntu-9.10-desktop-amd64.iso
ubuntu-9.10-desktop-i386.iso

After setting up USB-Flash versions of each

I booted up USB-LiveCD
sudo apt-get install lm-sensors
sudo /usr/sbin/sensors-detect (accepted all defaults)
rebooted
sudo pwnconfig
sudo sensors -s
sudo sensors

When running the 8.04.4 - AMD64 version:
     pwmconfig detected the motherboard modules, and
     sensors reported their status.

When running either 9.10 - 386 or AMD64 versions:
     pwmconfig said no modules detected
     sensors reported only the AMD-K8temp CPU temps

[Greg Tippitt (gtippitt)]

On my running system, I have all updates installed. I have all security, recommended, pre-release, and unsupported updates for software sources.

I am running Ubuntu 9.10, kernel 2.6.31-21-generic.

When running pwmconfig, it still get the following message:
     "/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed"

When I load the latest upstream kernel
linux-image-2.6.34-999-generic_2.6.34-999.201004241005_amd64.deb
Ubuntu 9.10, kernel 2.6.34-999-generic
I get the same" There are no pwm-capable sensor modules installed" message.

[Greg Tippitt (gtippitt)]

AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 1: default [USB AUDIO ], device 0: USB Audio [USB Audio]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: default [USB AUDIO ], device 0: USB Audio [USB Audio]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ahwood 2747 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card1.Amixer.info:
 Card hw:1 'default'/'USB AUDIO at usb-0000:03:00.1-1, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB1130:f211'
   Controls : 4
   Simple ctrls : 2
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=62cf26ab-4147-4eb7-83f3-83387be19ce0
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
PciMultimedia:

ProcCmdLine: root=UUID=7f46e5aa-e1c0-4ae0-9832-6af8d16762b9 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
RfKill:

Uname: Linux 2.6.34-999-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev pulse pulse-access sambashare video
WpaSupplicantLog:

XsessionErrors:
 (gnome-settings-daemon:2784): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2784): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2864): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2886): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 10/26/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080010
dmi.board.name: TYAN High-End Dual AMD Opteron, S2882
dmi.board.vendor: TYAN
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080010:bd10/26/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTYAN:rnTYANHigh-EndDualAMDOpteron,S2882:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Greg Tippitt (gtippitt)]

After upgrading servers to 10.04 LTS, I still get the same error message from pwmconfig

[Manoj Iyer (manjo)]

Looks like this bug was reported in karmic, we wont be able to fix this bug for karmic as this is not a serious kernel stability issue. Can you please try Lucid (10.04)?

[Manoj Iyer (manjo)]

I was able to use pwmconfig on lucid (10.04) with no problems after I loaded the modules sensor-detect recommends.

manjo@hungry:~/devel/ubuntu/kernel$ sudo modprobe adt7473
manjo@hungry:~/devel/ubuntu/kernel$ sudo modprobe coretemp
manjo@hungry:~/devel/ubuntu/kernel$ sudo modprobe f71882fg
manjo@hungry:~/devel/ubuntu/kernel$ sudo pwmconfig
# pwmconfig revision 5770 (2009-09-16)
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

Found the following devices:
   hwmon0/device is coretemp
   hwmon1/device is coretemp
   hwmon2/device is coretemp
   hwmon3/device is coretemp
   hwmon4/device is f8000

Found the following PWM controls:
   hwmon4/device/pwm1
hwmon4/device/pwm1 is currently setup for automatic speed control.
In general, automatic mode is preferred over manual mode, as
it is more efficient and it reacts faster. Are you sure that
you want to setup this output for manual control? (n)
   hwmon4/device/pwm2
hwmon4/device/pwm2 is currently setup for automatic speed control.
In general, automatic mode is preferred over manual mode, as
it is more efficient and it reacts faster. Are you sure that
you want to setup this output for manual control? (n)
   hwmon4/device/pwm3
hwmon4/device/pwm3 is currently setup for automatic speed control.
In general, automatic mode is preferred over manual mode, as
it is more efficient and it reacts faster. Are you sure that
you want to setup this output for manual control? (n)
There are no usable PWM outputs.
manjo@hungry:~/devel/ubuntu/kernel$

[Manoj Iyer (manjo)]

Please see my comment #22, it works on Lucid, so marking this bug as fixed released for Lucid.

[Greg Tippitt (gtippitt)]

On May 20th, I posted the comment to the bug report that says "After
upgrading servers to 10.04 LTS, I still get the same error message from
pwmconfig."

In my posts of 6 Nov 2009, I said that the bug was introduced with kernel
2.6.28-16-generic. This is not a problem with just my TYAN servers. If you
search Google for "karmic fancontrol" you will find that people are having
this problem with laptops, desktops, and servers of almost every brand. For
some people the fan never turns on resulting in systems that overhead, while
others like myself are wearing earplugs because their systems sound like a
C130 Hercules Turboprop taking off.

This is not a stability issue for me, but for people with systems with fans
that never turn on, it is a serious stability problem. I agree that it is
not probably worth fixing in Karmic, but it should be fixed in Lucid, since
it is LTS.

Greg Tippitt

On Wed, Jun 2, 2010 at 10:42 AM, Manoj Iyer <email address hidden>wrote:

> Looks like this bug was reported in karmic, we wont be able to fix this
> bug for karmic as this is not a serious kernel stability issue. Can you
> please try Lucid (10.04)?
>
> ** Tags added: kernel-candidate kernel-reviewed
> ** Tags removed: kernel-needs-review
>
> --
> pwmconfig does not work after upgrade to 9.10 on TYAN server
> https://bugs.launchpad.net/bugs/475641
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Prior to upgrading from 9.04 to 9.10 I had configured
> pwmconfig/sensors/fancontrol so that the cooling fans on my servers were not
> too loud. I have 2 TYAN Transport GX28 servers with Tyan Thunder K8S Pro
> S2881G2NR motherboards, which have the latest BIOS updates from TYAN. These
> are 1U servers, which have very loud fans. I am using them outside of a
> rack in my home, and they stayed cool with fans running at about 1/3 the
> maximum default speeds. After upgrading to Ubuntu version 9.10, the fans
> are now running very loud again. When I run sensors, I get only the basic
> k8temp CPU temperatures and do not get the long version of the output that
> showed fan speed, temp, or voltage sensors.
>
> --------------------------------------------------------------------------
> I tried to run pwmconfig again to configure the '/etc/fancontrol
> configuration file, but I get an error that says:
>
> /usr/sbin/pwmconfig: There are no pwm-capable sensor modules
> installed
> --------------------------------------------------------------------------
> I ran /usr/sbin/sensors-detect and it said the following:
> Driver `w83627hf' (should be inserted):
> Detects correctly:
> * ISA bus, address 0x290
> Chip `Winbond W83627HF/F/HG/G Super IO Sensors' (confidence:
> 9)
>
> Driver `k8temp' (should be inserted):
> Detects correctly:
> * Chip `AMD K8 thermal sensors' (confidence: 9)
>
> I will now generate the commands needed to load the required modules.
> Just press ENTER to continue:
>
> To load everything that is needed, add this to /etc/modules:
>
> ...

[plopp (jirihusak)]

pwmconfig does not detect any pwm capable sensor modules on Lucid, my laptop is between 50 and 60° C all the time, fan running very sparely

[Greg Tippitt (gtippitt)]

Despite Manoj Iyer saying that this bug was fixed, the bug persists in Lucid. I was able to find a work-around by disabling ACPI support in the BIOS. Where the BIOS setup asks if OS supports ACPI, I set it to "NO". This fixed the problem where ASCI was conflicting with the W83627HF chip that lm-sensors needs to access.

After changing the BIOS setting to say that the OS did not support ACPI, I no longer got the message in DMESG that says "ACPI: I/O resource w83627hf [0x295-0x296] conflicts with ACPI". The PWMCONFIG program was then able to find the w83627hf chip and configure the fan settings for FANCONTROL.

If you need help with the process of installing and configuring the sensors and fancontrol, any of the following links explain the process.

http://www.garryconn.com/linux/how-to-control-cpu-and-case-fan-speeds-on-a-linux-server/

http://ubuntumanual.org/posts/127/how-to-control-fan-speed-lm-sensors-in-ubuntu

http://tuxtweaks.com/2008/08/how-to-control-fan-speeds-in-ubuntu/

http://www.robotsystematic.com/2009/howto/howto-fan-control-in-ubuntu

Greg

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.