Le vendredi 15 avril 2005 à 20:15 +0200, Richard Fish a écrit : > F > > Assuming I understand the probelm correctly, that is that the bios clock > keeps correct time, but the linux system time drifts,
Exacly, > you could try > using the clock= kernel parameter, which specifies what timesource the > kernel (and thus the rest of the system) uses for tracking time. > > I've had to do this when running linux inside of VMware on a laptop, > because of cpu frequency scaling. But then the affect wasn't 5min/day, > it was more like 2sec/sec. > > Your choices are "clock=[pit,tsc,cyclone,pmtmr]", although I have no > idea what "cyclone" is. pit is the default, but you might try pmtmr. > > You could also resort to a cron job that does a "hwclock --hctosys" > every hour or so, although as the hwclock man page says, you might want > to do this with adjtimex instead. I'll choose the simpler cronjob solution, thanks. Anyway, isn't that a kernel bug ? How sould I report this ? And Thanks to everyone for the help. Fred -- Frédéric Grosshans <[EMAIL PROTECTED]> -- gentoo-user@gentoo.org mailing list