Date: Wed, 03 May 2006 15:50:33 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: pav@FreeBSD.org Cc: freebsd-acpi@FreeBSD.org Subject: Re: acpi_thermal on nforce 4 board Message-ID: <4458C339.60503@dial.pipex.com> In-Reply-To: <1146666013.38125.69.camel@pav.hide.vol.cz> References: <1146231595.94164.25.camel@pav.hide.vol.cz> <20060502154819.GA16135@poupinou.org> <1146585606.31507.38.camel@pav.hide.vol.cz> <20060503134248.GB31815@poupinou.org> <4458B873.2020608@dial.pipex.com> <1146666013.38125.69.camel@pav.hide.vol.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Pav Lucistnik wrote: >Alex Zbyslaw p=ED=B9e v st 03. 05. 2006 v 15:04 +0100: > > =20 > >>>BTW I don't see why mbmon failed. Maybe you should >>>try something like that: >>> >>>mbmon -P winbond >>>=20 >>> >>> =20 >>> >>Also for some winbond chips healthd can work where mbmon doesn't. >> =20 >> > >Riight, healthd works and reports sane values. Funny, that it reports >different temperatures on the cores of my dual core CPU. > =20 > I would think that it was reporting the temps for your "second"=20 (non-existent) CPU, not per core, but I could be wrong. The 2nd CPU=20 temps and Vcore are just noise if you don't have 2 CPUs. --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4458C339.60503>