Date: Wed, 14 Nov 2018 01:56:29 +0300 From: Rozhuk Ivan <rozhuk.im@gmail.com> To: Conrad Meyer <cem@freebsd.org> Cc: shoesoft@gmx.net, Daniel Eischen <deischen@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G Message-ID: <20181114015629.7086d55c@gmail.com> In-Reply-To: <CAG6CVpVacUOJe%2B19DHbyYQkg8CJWq3QuZCeaQWc6PQxRwmAMGQ@mail.gmail.com> References: <Pine.GSO.4.64.1811131259350.27287@sea.ntplx.net> <1542138631.2638.0@smtp.migadu.com> <Pine.GSO.4.64.1811131456130.27826@sea.ntplx.net> <e83fd549-a647-546c-3fe9-b361bb725601@gmx.net> <CAG6CVpVacUOJe%2B19DHbyYQkg8CJWq3QuZCeaQWc6PQxRwmAMGQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Tue, 13 Nov 2018 13:14:46 -0800 Conrad Meyer <cem@freebsd.org> wrote: > You can adjust dev.amdtemp.N.sensor_offset as needed. By default, the > amdtemp sysctl gives you the unadjusted value. On different Ryzen > models the raw value is wrong by different amounts. E.g. on my 1950X, > I have sensor_offset set to "-27" to show correct temperature > readings. > Looks like new AGESA/BIOS change something, my fork of amdtemp now show (read) same value as on onboard led in "CurTmpTjSel" ... dev.amdtemp.0.rtc.CurTmpTjSel: 47.7C dev.amdtemp.0.rtc.CurTmp: 96.7C ... 49C diff, this was some sort of offset for older AMD CPU, used to calc CurTmpTjSel then it set to 3.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181114015629.7086d55c>