Re: 2.6.12.3 clock drifting twice too fast (amd64)

thanks YH On 8/17/05, Jeff Mahoney <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > fyhlu wrote: > > Me too. If use latest kernel mouse is dead. > > > > By the way, did you solve the battery problem in Linux. "Can not read > > battery status" > > Yes. It's a

Re: 2.6.12.3 clock drifting twice too fast (amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 fyhlu wrote: > Me too. If use latest kernel mouse is dead. > > By the way, did you solve the battery problem in Linux. "Can not read > battery status" Yes. It's a problem with the DSDT. Install pmtools (for iasl - the acpi compiler) and grab

Re: 2.6.12.3 clock drifting twice too fast (amd64)

Me too. If use latest kernel mouse is dead. By the way, did you solve the battery problem in Linux. "Can not read battery status" YH On 8/16/05, Jeff Mahoney <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Christoph Lameter wrote: > > On Tue, 16 Aug 2005,

Re: 2.6.12.3 clock drifting twice too fast (amd64)

Me too. If use latest kernel mouse is dead. By the way, did you solve the battery problem in Linux. Can not read battery status YH On 8/16/05, Jeff Mahoney [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christoph Lameter wrote: On Tue, 16 Aug 2005, jerome lacoste

Re: 2.6.12.3 clock drifting twice too fast (amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 fyhlu wrote: Me too. If use latest kernel mouse is dead. By the way, did you solve the battery problem in Linux. Can not read battery status Yes. It's a problem with the DSDT. Install pmtools (for iasl - the acpi compiler) and grab

Re: 2.6.12.3 clock drifting twice too fast (amd64)

thanks YH On 8/17/05, Jeff Mahoney [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 fyhlu wrote: Me too. If use latest kernel mouse is dead. By the way, did you solve the battery problem in Linux. Can not read battery status Yes. It's a problem with the

Re: 2.6.12.3 clock drifting twice too fast (amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christoph Lameter wrote: > On Tue, 16 Aug 2005, jerome lacoste wrote: > >>Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme >>AX 300 SE/t mainboard. >> >>I remember seeing a message in the boot saying something along: >> >>

Re: 2.6.12.3 clock drifting twice too fast (amd64)

On 8/16/05, john stultz <[EMAIL PROTECTED]> wrote: > On Tue, 2005-08-16 at 12:10 +0200, jerome lacoste wrote: > > Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme > > AX 300 SE/t mainboard. > > > > I remember seeing a message in the boot saying something along: > > > >

Re: 2.6.12.3 clock drifting twice too fast (amd64)

On Tue, 2005-08-16 at 12:10 +0200, jerome lacoste wrote: > Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme > AX 300 SE/t mainboard. > > I remember seeing a message in the boot saying something along: > > "cannot connect to hardware clock." > > And now I see that the

Re: 2.6.12.3 clock drifting twice too fast (amd64)

On 8/16/05, Christoph Lameter <[EMAIL PROTECTED]> wrote: > On Tue, 16 Aug 2005, jerome lacoste wrote: > > > Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme > > AX 300 SE/t mainboard. Ooops the main board is a Sapphire Axion XP200PA-A58SL. The aforementionned name is the

Re: 2.6.12.3 clock drifting twice too fast (amd64)

On Tue, 16 Aug 2005, jerome lacoste wrote: > Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme > AX 300 SE/t mainboard. > > I remember seeing a message in the boot saying something along: > > "cannot connect to hardware clock." > > And now I see that the time is changing

2.6.12.3 clock drifting twice too fast (amd64)

Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme AX 300 SE/t mainboard. I remember seeing a message in the boot saying something along: "cannot connect to hardware clock." And now I see that the time is changing too fast (about 2 seconds each second). I don't have

2.6.12.3 clock drifting twice too fast (amd64)

Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme AX 300 SE/t mainboard. I remember seeing a message in the boot saying something along: cannot connect to hardware clock. And now I see that the time is changing too fast (about 2 seconds each second). I don't have visual

Re: 2.6.12.3 clock drifting twice too fast (amd64)

On Tue, 16 Aug 2005, jerome lacoste wrote: Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme AX 300 SE/t mainboard. I remember seeing a message in the boot saying something along: cannot connect to hardware clock. And now I see that the time is changing too fast

Re: 2.6.12.3 clock drifting twice too fast (amd64)

On 8/16/05, Christoph Lameter [EMAIL PROTECTED] wrote: On Tue, 16 Aug 2005, jerome lacoste wrote: Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme AX 300 SE/t mainboard. Ooops the main board is a Sapphire Axion XP200PA-A58SL. The aforementionned name is the video

Re: 2.6.12.3 clock drifting twice too fast (amd64)

On Tue, 2005-08-16 at 12:10 +0200, jerome lacoste wrote: Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme AX 300 SE/t mainboard. I remember seeing a message in the boot saying something along: cannot connect to hardware clock. And now I see that the time is

Re: 2.6.12.3 clock drifting twice too fast (amd64)

On 8/16/05, john stultz [EMAIL PROTECTED] wrote: On Tue, 2005-08-16 at 12:10 +0200, jerome lacoste wrote: Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme AX 300 SE/t mainboard. I remember seeing a message in the boot saying something along: cannot connect to

Re: 2.6.12.3 clock drifting twice too fast (amd64)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christoph Lameter wrote: On Tue, 16 Aug 2005, jerome lacoste wrote: Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme AX 300 SE/t mainboard. I remember seeing a message in the boot saying something along: cannot connect to