Date: Mon, 21 Dec 2009 22:03:42 -0800 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: freebsd-stable@freebsd.org Subject: Re: 8-STABLE: support for this SMB controller? Message-ID: <20091222060342.GA77889@icarus.home.lan> In-Reply-To: <20091222065104.77b11df4.lehmann@ans-netz.de> References: <20091221174225.84748c0d.lehmann@ans-netz.de> <4B2FA913.5030501@icyb.net.ua> <20091222063415.9c2284ea.lehmann@ans-netz.de> <4B305C3C.6060703@icyb.net.ua> <20091222065104.77b11df4.lehmann@ans-netz.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 22, 2009 at 06:51:04AM +0100, Oliver Lehmann wrote: > Andriy Gapon wrote: > > > BTW, mbmon haven't seen any updates in quite a long while, so it's missing > > support for many newer chips. > > Unfortunately, state of hardware/sensors monitoring is relatively poor in FreeBSD. > > Hm so I guess there is no other way in determining the CPUs temperature? > Why do we have the ichsmb driver then anyway? ;) If all you're looking for is CPU temperature, try looking at ACPI thermal zones. Some BIOSes/mainboard manufacturers implement this on workstations. Otherwise, if you have a Intel Core, C2D, or C2Q CPU, load the coretemp(4) driver. Re: HW monitoring: bsdhwmon can talk to smb(4) (thus ichsmb), but is only intended for server boards (at the time of this writing only supporting Supermicro). Many motherboard manufacturers don't provide a HW monitoring IC -- and if they do, don't state whether or not it's tied in to the SMBus, what its base address is, or memory offsets for the data. "Probing" for such is risky business. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091222060342.GA77889>