Date: Sun, 10 Aug 2014 11:01:29 +0200 From: Polytropon <freebsd@edvax.de> To: David Benfell <benfell@parts-unknown.org> Cc: freebsd-questions@FreeBSD.org Subject: Re: operation not permitted on entropy file Message-ID: <20140810110129.14d858ab.freebsd@edvax.de> In-Reply-To: <20140810085710.GB59380@home.parts-unknown.org> References: <20140810070239.GA80734@home.parts-unknown.org> <53E72634.5050608@FreeBSD.org> <20140810083440.GA59380@home.parts-unknown.org> <20140810104523.5ccdaf6f.freebsd@edvax.de> <20140810085710.GB59380@home.parts-unknown.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 10 Aug 2014 01:57:11 -0700, David Benfell wrote: > On Sun, Aug 10, 2014 at 10:45:23AM +0200, Polytropon wrote: > > Examination of the hardware is also a thing worth looking into, > > for example, voltages, temperatures, and CPU "correctness". > > I'm wondering how to do this. The system does have an SMBus, but the > smb module doesn't create /dev/smb0 and the tool--I'm forgetting the > command name--that will identify the hardware on a system suggests > that it's too recent a version to be fully accurate with. As I'm using a custom kernel, I have set those options: device smbus device iicbus device iicsmb device iicbb device iic It's probably possible to achieve the same goal using loadable modules via /boot/loader.conf. There are some "moving parts" involved to get the whole thing working, and the default installation does not reflect this. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140810110129.14d858ab.freebsd>