On Wed, 21 May 2014, Nils R wrote:
since the snapshot from 18.05., the wrong MHz of my CPU is displayed in
both dmesg and apm. apmd is started at boot, here is my rc.conf.local:
Approximately what was the date of the build you were running *before* you
upgraded to the misbehaving May 18
On 2014/05/21 23:00, Philip Guenther wrote:
On Wed, 21 May 2014, Nils R wrote:
since the snapshot from 18.05., the wrong MHz of my CPU is displayed in
both dmesg and apm. apmd is started at boot, here is my rc.conf.local:
Approximately what was the date of the build you were running
Philip Guenther schrieb am 22.05.2014 08:00:
On Wed, 21 May 2014, Nils R wrote:
since the snapshot from 18.05., the wrong MHz of my CPU is displayed in
both dmesg and apm. apmd is started at boot, here is my rc.conf.local:
Approximately what was the date of the build you were running
Philip Guenther schrieb am 22.05.2014 09:36:
On Wed, 21 May 2014, Nils R wrote:
Philip Guenther schrieb am 22.05.2014 08:00:
On Wed, 21 May 2014, Nils R wrote:
since the snapshot from 18.05., the wrong MHz of my CPU is displayed in
both dmesg and apm. apmd is started at boot, here is
Hi,
since the snapshot from 18.05., the wrong MHz of my CPU is displayed
in both dmesg and apm. apmd is started at boot, here is my
rc.conf.local:
ntpd_flags= # enabled during install
dhcpd_flags=re0 # dhcp server for wired network
nginx_flags= #
