On 1/19/06, Wolfgang S. Rupprecht
> Turns out this was caused by the most recent changes to kern_clock.c
> and kern_time.c. Compiling with these previous versions gave me a
> functional system clock again.
grr
I wrote:
> A GENERIC amd64 kernel compiled from today's sources is causing my
> Asus k8v-se-d to run fast by approximately 3 seconds per minute.
> (Obviously that was with ntpd not running.) This has never been a
> problem before. Is anyone else seeing this?
Turns out this was caused by the most
> > Upon booting I also get quite a bit of hex-dump output right after the
> > iic line. I'm not sure if that is related and an indication that
> > something on the iic bus is not getting configured. (dmesg appended)
>
> This is the i2c sensor probe finding devices that it cannot recognise
> and
On Wed, 18 Jan 2006, Wolfgang S. Rupprecht wrote:
> Upon booting I also get quite a bit of hex-dump output right after the
> iic line. I'm not sure if that is related and an indication that
> something on the iic bus is not getting configured. (dmesg appended)
This is the i2c sensor probe findi
On 18/01/06, Wolfgang S. Rupprecht
<[EMAIL PROTECTED]> wrote:
> A GENERIC amd64 kernel compiled from today's sources is causing my
> Asus k8v-se-d to run fast by approximately 3 seconds per minute.
> (Obviously that was with ntpd not running.) This has never been a
> problem before. Is anyone els
A GENERIC amd64 kernel compiled from today's sources is causing my
Asus k8v-se-d to run fast by approximately 3 seconds per minute.
(Obviously that was with ntpd not running.) This has never been a
problem before. Is anyone else seeing this?
Upon booting I also get quite a bit of hex-dump output
6 matches
Mail list logo
