Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Feb 2013 09:43:10 +0100
From:      Torfinn Ingolfsen <torfinn.ingolfsen@getmail.no>
To:        freebsd-stable@freebsd.org
Subject:   Re: RELENG_8: amdtemp module and newer CPUs not working. MFC?
Message-ID:  <20130222094310.c478054b10c2b96c2b5fda5b@getmail.no>
In-Reply-To: <201302210629.r1L6T5VU001000@gw.catspoiler.org>
References:  <20130217135317.5c4d10819e8d12440785a3a0@getmail.no> <201302210629.r1L6T5VU001000@gw.catspoiler.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 20 Feb 2013 22:29:05 -0800 (PST)
Don Lewis <truckman@FreeBSD.org> wrote:

> 
> Updating amdtemp is on my TODO list.  It has some issues even on
> -CURRENT.  This is kind of far down my priority list because on most of
> my AMD machines, I can also get the temperature without amdtemp:
> 
> % sysctl hw.acpi.thermal.tz0.temperature
> hw.acpi.thermal.tz0.temperature: 30.0C

In addition to what has already been mentioned in this thread, on most of *my*
AMD machines hw.acpi.thernal yields nothing. Typical example:
root@kg-quiet# sysctl hw.acpi.thermal.tz0.temperature
sysctl: unknown oid 'hw.acpi.thermal.tz0.temperature'
root@kg-quiet# sysctl hw.acpi.thermal
sysctl: unknown oid 'hw.acpi.thermal'

Typically, hw.acpi doesn't contain useful data:
root@kg-quiet# sysctl hw.acpi
hw.acpi.supported_sleep_state: S3 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S3
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: NONE
hw.acpi.suspend_state: S3
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.disable_on_reboot: 0
hw.acpi.handle_reboot: 1
hw.acpi.reset_video: 0
hw.acpi.cpu.cx_lowest: C1

HTH
-- 
Torfinn Ingolfsen <torfinn.ingolfsen@getmail.no>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130222094310.c478054b10c2b96c2b5fda5b>