lm-sensors don't work

Bug #478762 reported by Ricardo Jorge Borges Guimarães
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
lm-sensors (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: lm-sensors

lm-sensors show temp of HD

lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] Device 0656 (rev 10)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS965 [MuTIOL Media IO] (rev 48)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:05.0 IDE interface: Silicon Integrated Systems [SiS] 182 SATA/RAID Controller (rev 01)
00:06.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
00:07.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
00:0b.0 Communication controller: Agere Systems Lucent V.92 Data/Fax Modem
00:0e.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
01:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]

ProblemType: Bug
Architecture: i386
CheckboxSubmission: 8051d94fcfdf22dc70e9fee529cd3e00
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Sun Nov 8 20:40:37 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-system-monitor
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: gnome-system-monitor 2.28.0-0ubuntu1
ProcEnviron:
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: gnome-system-monitor
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
Ricardo Jorge Borges Guimarães (rjbgbo) wrote :
Revision history for this message
Chuck Short (zulcss) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

Changed in lm-sensors (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Petar Velkovski (pvelkovski) wrote :

Found this explanation and solution on the Internet:

...
lm-sensors appears to have stopped working in Ubuntu Karmic Koala (basically for any distro running Kernel 2.6.31). If you look at your Kernel messages, you will see something like this:

ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region IP__
[0x295-0x296]
ACPI: Device needs an ACPI driver

If you want to restore the old behaviour (which might be dangerous) add: "acpi_enforce_resources=lax" to the kernel cmdline when booting (or add it in grub.conf to make this permanent).

To add acpi_enforce_resources=lax to your Grub, in Ubuntu Karmic,

1.press Alt + F2, and enter: gksu gedit /etc/default/grub
2. And enter the following line: GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax"
3. Then save the file.
4. Run this in console: sudo update-grub2

This is copy/pasted from the following link(it is missing step 4):
http://www.webupd8.org/2009/10/make-lm-sensors-work-in-ubuntu-karmic.html

Revision history for this message
francesco bat (nerobat2004) wrote :

I have the same problem !!!
lm sensor doesn't work !
I tried with grub with: GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax"
But with sudo update-grub2 i had this:

/etc/default/grub: 9: acpi_enforce_resources=lax: not found

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

francesco this is my output of /etc/default/grub:
-------------------------------------------------------------------------------------------------------------------------------
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=2
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT="10"
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
GRUB_GFXMODE=1680x1050

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entrys
#GRUB_DISABLE_LINUX_RECOVERY="true"
--------------------------------------------------------------------------------------------------------------------

Are you sure that you have typed it correctly?
Try it again, AND DO NOT COPY PASTE THE WHOLE LISTING!!! I made other changes to it, so that it would suit my needs better!

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

@francesco bat
and report back what you did no matter if you succeeded or not.

Revision history for this message
francesco bat (nerobat2004) wrote :

Hello !
Today i solved in this way:

sudo gedit /etc/default/grub

and i modified the old string:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

in

GRUB_CMDLINE_LINUX_DEFAULT="acpi_enforce_resources=lax quiet splash"

Now it's all right !
But i hope that is being to solve in official way, beacuse many people couldn't solve it ! :-(

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

By the way I forgot to mention that this is not officially a bug. I remember reading in some of the linux kernel 2.6.31 release notes that lm-sensors has been disabled by default because it made problem with some other code. But it's good that we have this workaround. It works for me (and obviously for others too) but probably it can affect some systems in a bad manner.

Revision history for this message
francesco bat (nerobat2004) wrote :

What problems ?
I would know these problems, because if it can do me problem I edited the grub as it was before. ;-)
Bye
Francesco bat

tags: added: karmic
Revision history for this message
Jeremy Nickurak (nickurak) wrote :

Hypothetically, what's the right way to get temperature data if the module isn't supposed to be used anymore? Is it safe to use LAX here?

Changed in lm-sensors (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Ricardo Jorge Borges Guimarães (rjbgbo) wrote :
Revision history for this message
Jeremy Nickurak (nickurak) wrote :

That's a work-around... but the warning would seem to suggest that this isn't safe. Is there an API/ABI/socket/sysfile that we're supposed to used? Until that's the case, this is a regression. Given that, and that people might be using this to tell if a system is running at a safe temperature, this should probably be a higher priority than Low.

Revision history for this message
francesco bat (nerobat2004) wrote : Re: [Bug 478762] Re: lm-sensors don't work

In data 21 dicembre 2009 alle ore 23:25:33, Jeremy Nickurak
<email address hidden> ha scritto:

> That's a work-around... but the warning would seem to suggest that this
> isn't safe. Is there an API/ABI/socket/sysfile that we're supposed to
> used? Until that's the case, this is a regression. Given that, and that
> people might be using this to tell if a system is running at a safe
> temperature, this should probably be a higher priority than Low.
>

I also agree
--
Creato con il rivoluzionario client e-mail di Opera:
http://www.opera.com/mail/

Revision history for this message
Jeremy Nickurak (nickurak) wrote :

Workaround not working here:

tv@katran:~$ cat /proc/cmdline
root=UUID=af655e0f-6e77-4305-8c6d-5a92ef317d3e ro acpi_enforce_resources=lax splash

tv@katran:~$ dmesg
...
...
[368848.890310] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[368848.890317] ACPI: I/O resource 0000:00:1f.3 [0x3080-0x309f] conflicts with ACPI region SMB0 [0x3080-0x3097]
[368848.890320] ACPI: This conflict may cause random problems and system instability
[368848.890322] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
tv@katran:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +60.0°C (crit = +255.0°C)

Revision history for this message
Jeremy Nickurak (nickurak) wrote :

Hrm, nevermind, after adding the lax option, sensors-detect found a module to load. Odd.

Revision history for this message
Paul van Genderen (paulvg) wrote :

Is this bug reproduceable with the current 9.10 (2.6.31-20-generic) or current lucid (2.6.32-21-generic) kernel?

Revision history for this message
Petar Velkovski (pvelkovski) wrote :

Without the "acpi_enforce_resources=lax" boot option the Fan sensors are not reachable in Lucid! But again keep in mind that there was a warning for using this option that it may lead to system instability (not in my case).

Revision history for this message
tsh (tsh) wrote :

I have no working sensors apart from 1 hdd temperature (used to work with 9.04)
2.6.32-21-generic x86_64

lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext gfx port 0)
00:0a.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 5)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [IDE mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Link Control
01:00.0 VGA compatible controller: ATI Technologies Inc RV620 LE [Radeon HD 3450]
01:00.1 Audio device: ATI Technologies Inc RV620 Audio device [Radeon HD 34xx Series]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

See atachment for output of dmesg | grep ACPI

Revision history for this message
Phillip Susi (psusi) wrote :

This report has become an extended support discussion, and does not describe an actual bug, therefore I am closing it.

Changed in lm-sensors (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.