On 2015-01-03, John Merriam j...@johnmerriam.net wrote:
Is it worth messing around with to try to get HPET working on the
OptiPlex 320 in OpenBSD or would it be written off as buggy hardware? I
guess that assumes it could work at all...
Probably write off as buggy. Some automated way to
On Mon, 5 Jan 2015, Stuart Henderson wrote:
On 2015-01-03, John Merriam j...@johnmerriam.net wrote:
Is it worth messing around with to try to get HPET working on the
OptiPlex 320 in OpenBSD or would it be written off as buggy hardware? I
guess that assumes it could work at all...
On Fri, Jan 02, 2015 at 10:47:02AM -0500, John Merriam wrote:
Hello. I have a strange issue with OpenBSD on my Dell OptiPlex 320. The
clock doesn't move:
# date; sleep 55; date
Thu Jan 1 02:25:47 EST 2015
Thu Jan 1 02:25:47 EST 2015
# sysctl kern.timecounter.choice
I have a Dell that
On Sun, Jan 04, 2015 at 01:23:24PM -0500, Jonathon Sisson wrote:
# sysctl kern.timecounter.choice
I have a Dell that has a broken clocksource that exhibits the same.
Set kern.timecounter.choice to one of the other choices (you'll have
to experiment with that, I can't help you there). Once
On 1/2/2015 2:00 PM, Nathan Wheeler wrote:
Try changing the value for the sysctl variable
kern.timecounter.hardware? Its just a guess, but its helped me when
I had problems with the clock before.
On Fri, Jan 2, 2015 at 7:47 AM, John Merriam j...@johnmerriam.net wrote:
Hello. I have a strange
Try changing the value for the sysctl variable
kern.timecounter.hardware? Its just a guess, but its helped me when
I had problems with the clock before.
On Fri, Jan 2, 2015 at 7:47 AM, John Merriam j...@johnmerriam.net wrote:
Hello. I have a strange issue with OpenBSD on my Dell OptiPlex 320.
Hello. I have a strange issue with OpenBSD on my Dell OptiPlex 320.
The clock doesn't move:
# date; sleep 55; date
Thu Jan 1 02:25:47 EST 2015
Thu Jan 1 02:25:47 EST 2015
I see the same behavior with 5.6-release amd64 and -current amd64. The
clock works fine in Windows and Linux on this
7 matches
Mail list logo
