Hello, On Sat, Feb 25, 2006 at 12:05:28AM +0100, Christian T. Steigies wrote: > > disable_timer_pin_1 > > Can you be a little more specific? I've been pulling my hair over this, we > have a bunch of (different) AMD64 boxes, and only the one I got has this > problem, and I could not fix it with ntp, chrony, or rdate cron jobs...
disable_timer_pin_1 is for broken ATI chipsets, see for example http://www.ussg.iu.edu/hypermail/linux/kernel/0511.3/0457.html for a brief explanation. > I just had two identical machines on my desk to set up, so they will have > the same problem? Is this a mainboard "feature"? A little search tells me > this might be nvidia related, but IIRC all our boxed have nvidia chipsets, > only mine was the first dual core. The dual CPU machine has no clock > problems... It's broken hardware, not a feature. I might investigate this too concerning nvidia boards; Nvidia had a problem with APICs ever since, but you cannot deactivate it on SMP. Does the clock still run twice as fast if you boot the non-SMP 2.6.15-1-amd64-k8 with noapic nolapic? > Can this be mentioned in the linux-image package somewhere? I am sure more > people will experience this problem... maybe we should add a debconf note to amd64-k8 kernels, shown only if they are installed on an ATI based box? Best regards Frederik Schueler -- ENOSIG
signature.asc
Description: Digital signature
