On Wed, Sep 21, 2005 at 10:57:13AM -0400, Guy Hulbert wrote:
> On Tue, 2005-26-07 at 17:27 +0200, Maximilian Attems wrote:
> > can you please test the 2.6.12 linux image in unstable?
> > does the bug still occurs?
> >
> > --
> > maks
>
> I never found time for this but I noticed in the 2.6.13 ann
On Tue, 2005-26-07 at 17:27 +0200, Maximilian Attems wrote:
> can you please test the 2.6.12 linux image in unstable?
> does the bug still occurs?
>
> --
> maks
I never found time for this but I noticed in the 2.6.13 announcement
that several Radeon fixes are included so I will either try to buil
On Tue, 2005-26-07 at 17:27 +0200, Maximilian Attems wrote:
> can you please test the 2.6.12 linux image in unstable?
> does the bug still occurs?
I never saw it ... I just explained to Chris what AC97 meant.
However, I will try the 2.6.12 kernel ... my system has been crashing
badly this week.
can you please test the 2.6.12 linux image in unstable?
does the bug still occurs?
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: kernel-image-2.6.11-1-686
Version: 2.6.11-5
Severity: important
After upgrading from kernel-image-2.6.8-1-686, the system clock drifts
ahead of the hardware clock approximately two minutes per hour,
sometimes more. It's not uncommon for it to drift 2 full hours in 7
hours' time.
I recen
5 matches
Mail list logo