Try using a different clock source. Motherboards have several clock generators and 2.6 kernels can use tsc, pit, cyclone or pmtmr. 2.4 used pit, early 2.6 kernels I tried used tsc and now they use pmtmr. Some of the clock sources are affected by power-management on some boards.
append 'clock=<clock src>' to the kernel commandline, where <clock src> is one of the above. Check kernel logs to see which one you're currently using: [EMAIL PROTECTED] ~]# grep timesource /var/log/dmesg Using pmtmr for high-res timesource Cheers, Wilf. On 08/07/05, Michael Kimberlin <[EMAIL PROTECTED]> wrote: > > My mythtv box is losing time. I get different output from hwclock and > date...even a couple of seconds after syncing the two up. It seems to get > worse when a recording is happening. I lose quite a bit of time (into the > hours a day, on days that have more recordings). Needless to say, this > totally screws up my start and stop times. > > I read that syncing the hardware and system clock and then removing > /etc/adjtime followed by a reboot would take care of this...and it seemed > to. But as soon as a recording started I was back in the same boat again. > > It's amazingly disappointing to come home to a show that started recording > 15 minutes too late and pushes 15 into the next show...and it's everyday. > ANY help would be greatly appreciated... > > Thanks, > -michael > > > > _______________________________________________ > mythtv-users mailing list > [email protected] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > -- [EMAIL PROTECTED] _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
