Tilman Linneweh <[EMAIL PROTECTED]> writes:
> > I have a problem with my ASUS P5A-B motherboard, where the timer
> > runs too fast. This is with -CURRENT, cvsup'd from 1.5 weeks ago.
> Same motherboard, same problem. No idea.
I used to have the same problem with the same board. At the time, I
wo
On Tue, Nov 12, 2002 at 07:23:51PM +0100, Poul-Henning Kamp wrote:
> >I just tried this, and it seems to work fine.
> >So TSC seems to work, and i8254 does not seem to work.
>
> And ACPI doesn't work either, right ?
That's right, doing:
sysctl -w kern.timecounter.hardware=ACPI-safe
does not work
In message <[EMAIL PROTECTED]>, Craig Rodrigues writes:
>On Tue, Nov 12, 2002 at 05:44:36PM +, David Malone wrote:
>> On Tue, Nov 12, 2002 at 10:20:00AM -0500, Craig Rodrigues wrote:
>> > However, this fix (adding kern.timecounter.hardware=i8254 to /etc/sysctl.conf)
>> > does not seem to work a
On Tue, Nov 12, 2002 at 05:44:36PM +, David Malone wrote:
> On Tue, Nov 12, 2002 at 10:20:00AM -0500, Craig Rodrigues wrote:
> > However, this fix (adding kern.timecounter.hardware=i8254 to /etc/sysctl.conf)
> > does not seem to work anymore. The clock still runs too fast.
>
> Could you try k
On Tue, Nov 12, 2002 at 10:20:00AM -0500, Craig Rodrigues wrote:
> However, this fix (adding kern.timecounter.hardware=i8254 to /etc/sysctl.conf)
> does not seem to work anymore. The clock still runs too fast.
Could you try kern.timecounter.hardware=TSC - this worked for someone
else sometime las
On Tue, Nov 12, 2002 at 05:18:13PM +0100, Poul-Henning Kamp wrote:
> Are you saying that the i8254 also runs twice as fast as it should ?
It looks like it. Here is some additional output from
dmesg. Does it give a clue?
Calibrating clock(s) ... TSC clock: 400911902 Hz, i8254 clock: 1193190 Hz
C
In message <[EMAIL PROTECTED]>, Tilman Linneweh writes:
>> I have a problem with my ASUS P5A-B motherboard, where the timer
>> runs too fast. This is with -CURRENT, cvsup'd from 1.5 weeks ago.
>>
>> I encountered this problem before, and found a fix which worke;:
>>
>http://docs.freebsd.org/cgi/
> I have a problem with my ASUS P5A-B motherboard, where the timer
> runs too fast. This is with -CURRENT, cvsup'd from 1.5 weeks ago.
>
> I encountered this problem before, and found a fix which worke;:
>
>http://docs.freebsd.org/cgi/getmsg.cgi?fetch=145760+0+archive/2002/freebsd-current/200209
Hi,
I have a problem with my ASUS P5A-B motherboard, where the timer
runs too fast. This is with -CURRENT, cvsup'd from 1.5 weeks ago.
I encountered this problem before, and found a fix which worke;:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=145760+0+archive/2002/freebsd-current/20020915.free
On Sun, Sep 08, 2002 at 12:16:26PM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Craig Rodrigues writes:
> >Is there a problem with the ACPI code or with my
> >hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago).
> >
> >How can I default to i8254 as my default tim
In message <[EMAIL PROTECTED]>, Craig Rodrigues writes:
>I reset my timecounter:
>sysctl kern.timecounter.hardware=i8254
>
>Now the clock seems to run at a more reasonable rate.
>
>Is there a problem with the ACPI code or with my
>hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago).
Craig Rodrigues schrieb:
>Hi,
>
>I have been having this problem with -current for the past 2 weeks now
>(I am new to -current and just started using it 2 weeks ago).
>I just did a cvsup and rebuilt the kernel and rebuilt the world.
>
>My clock seems to be running too fast, and I keep resetting i
On Sat, Sep 07, 2002 at 11:19:52PM -0400, Craig Rodrigues wrote:
> Is there a problem with the ACPI code or with my
> hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago).
Several people (including me) have reported this problem with this
motherboard. Poul had a look at it, but could
Hi,
I have been having this problem with -current for the past 2 weeks now
(I am new to -current and just started using it 2 weeks ago).
I just did a cvsup and rebuilt the kernel and rebuilt the world.
My clock seems to be running too fast, and I keep resetting it
with ntpdate.
I looked at this
14 matches
Mail list logo
