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 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 (about 2 seconds each > >>second). > > > > The timer interrupt is probably called twice for some reason and therefore > > time runs twice as fast. Try using HPET for interrupt timing. > > > >>I don't have visual on the boot sequence anymore (only remote access). > > > > Use serial console or netconsole. The boot information is logged. Try > > dmesg. > > I am seeing similar results on my Acer Ferrari 4000 (Turion64 ML-37). It > does appear that time is running 2x normal time. > > Booting with noapictimer cleared up the timing issues, though it did > introduce some IRQ badness. > > - -Jeff > > - -- > Jeff Mahoney > SuSE Labs > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.0 (GNU/Linux) > > iD8DBQFDAnPzLPWxlyuTD7IRAuQ+AKCoK4Bvj9YaSxK1cYzK/LQUGcj2pQCgmBKK > hGeSfGE+CvdNzqW3pN5LQq8= > =wtra > -----END PGP SIGNATURE----- > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
