support temp sensor

Bug #676080 reported by Dustin Kirkland 
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
byobu
Fix Released
Wishlist
Unassigned
byobu (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

SabreWolfy said 23 minutes ago:
Thanks. I found a file containing the temperature for each core:

/sys/devices/platform/coretemp.0/temp1_input

contains "46000" and the temperature for core 0 is 46 according to "sensors".

So

$ cat /sys/devices/platform/coretemp.*/temp1_input

agrees with the output for all four cores from "sensors".

No idea how to parse/include this in byobu though :)

Related branches

Changed in byobu:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Aaron Haviland (aaron-haviland) wrote :

This would be nice, however on my system, the module coretemp is not auto-loaded, and also this path provided only applies to Core processors.

/proc/acpi/thermal_zone does not exist here, but I'm assuming the script *only* looks there because it's a standardized location for ACPI reporting, rather than chipset-specific like coretemp (or any other lm-sensors driver for that matter).

Revision history for this message
Aaron Haviland (aaron-haviland) wrote :

Also, I have provided by the ACPI driver for my motherboard (asus_atk0110) thermal sensors visible in:

/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:03/ATK0110:00/hwmon/hwmon0/temp1_input

Again, a driver-specific location.

Although all these seem visible through a common path:
/sys/class/hwmon/hwmonX/temp1_input (where X is the specific device, I have 0=asus_atk0110, 1=coretemp.0 2=coretemp.1, for the two cores)

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Will be released in 3.20.

Changed in byobu:
status: Triaged → Fix Committed
Changed in byobu (Ubuntu):
status: New → Fix Committed
importance: Undecided → Wishlist
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package byobu - 3.20-0ubuntu1

---------------
byobu (3.20-0ubuntu1) natty; urgency=low

  * usr/lib/byobu/network: drop unnecessary unit=kbps
  * usr/bin/byobu: allow for -xS or the like, LP: #684926
  * usr/bin/byobu-select-session, usr/share/man/man1/byobu.1,
    usr/share/man/man1/byobu-select-session.1: support "hiding"
    sessions, by prepending a "." to the session name, LP: #599334
  * usr/share/man/man1/byobu-launcher.1: update documentation
  * usr/bin/byobu-launcher-install, usr/share/man/man1/byobu-launcher-
    install.1, usr/share/man/man1/byobu-launcher-uninstall.1,
    usr/share/man/man1/Makefile.am:
    - add an option for -n|--no-logout to byobu-launcher-install,
      document changes in new manpages, LP: #604931
  * usr/lib/byobu/cpu_temp: find the temp monitor, LP: #676080
  * usr/lib/byobu/battery, usr/share/man/man1/byobu.1: allow for
    overriding detected BATTERY, LP: #693560
  * usr/lib/byobu/cpu_temp: test that file exists, is readable, and has
    size > 0, LP: #696071
 -- Dustin Kirkland <email address hidden> Tue, 28 Dec 2010 00:05:13 -0600

Changed in byobu (Ubuntu):
status: Fix Committed → Fix Released
Changed in byobu:
status: Fix Committed → Fix Released
Revision history for this message
SabreWolfy (sabrewolfy) wrote :

Thanks. I've updated to 3.20 and toggled the CPU temperature notification on. It reports 35 degrees C. Output from "$ sensors":

atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage: +1.14 V (min = +0.85 V, max = +1.60 V)
 +3.3 Voltage: +3.30 V (min = +2.97 V, max = +3.63 V)
 +5 Voltage: +5.09 V (min = +4.50 V, max = +5.50 V)
 +12 Voltage: +12.04 V (min = +10.20 V, max = +13.80 V)
CPU FAN Speed: 1180 RPM (min = 600 RPM)
CHASSIS FAN Speed: 0 RPM (min = 800 RPM)
CPU Temperature: +35.0°C (high = +60.0°C, crit = +95.0°C)
MB Temperature: +39.0°C (high = +45.0°C, crit = +95.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +47.0°C (high = +74.0°C, crit = +100.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +43.0°C (high = +74.0°C, crit = +100.0°C)

coretemp-isa-0002
Adapter: ISA adapter
Core 2: +45.0°C (high = +74.0°C, crit = +100.0°C)

coretemp-isa-0003
Adapter: ISA adapter
Core 3: +45.0°C (high = +74.0°C, crit = +100.0°C)

So byobu is picking up the "CPU temperature" output. I have no idea why this output (35 degrees C) is so different from the temperature of each core, but of course this is not a byobu-related issue.

Revision history for this message
Aaron Haviland (aaron-haviland) wrote :

SabreWolfy,

They will almost always be different: (I believe) one is what is reported by sensors built-in to the motherboard, the other is what's reported by on-chip sensors built into the CPU.

(My situation is reversed, the coretemps report lower than the mobo's CPU temp. I'm making an educated guess that I have a better CPU fan than you, or you have better ventilation *underneath* the motherboard than I.)

Dustin, Thank you for updating this!

Revision history for this message
SabreWolfy (sabrewolfy) wrote :

Aaron,

Thanks for the information. The text I pasted in my previous post shows that my sensors reports a CPU temperature, a MB (motherboard I presume) temperature and core temperatures. Are you saying there is a "CPU motherboard" value and a "motherboard" value?

byobu is picking up the one called "CPU", which is fine I think. I have confirmed that this values DOES change over time, so sensors is reporting something dynamic. In my experience, some sensors temperatures report some arbitrary fixed temperature value which never changes.

Also my thanks to Dustin for adding this :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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