Hi,
I think this is the same problem as described in 284477, maybe you can
try some of the ideas in this bugreport
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284477)...
Martin
--
SULFURCELL Solartechnik GmbH
Martin Stigge
Barbara-McClintock-Str. 11
12489 Berlin
[EMAIL PROTECTED]
--
On Wed, Jul 20, 2005 at 01:09:52AM +0200, Martin Stigge wrote:
> Hi,
>
> I'm facing exactly the same problems here with some Thinkcentres and
> Kernel Image 2.6.8-2-686 (Version 2.6.8-16). Do you have any solution or
> workaround?
My ugly workaround was:
1. switch to vanila 2.6.11 (was latest th
Hi,
I'm facing exactly the same problems here with some Thinkcentres and
Kernel Image 2.6.8-2-686 (Version 2.6.8-16). Do you have any solution or
workaround?
Best regards,
Martin
--
SULFURCELL Solartechnik GmbH
Martin Stigge
Barbara-McClintock-Str. 11
12489 Berlin
[EMAIL PROTECTED]
--
To U
Update: Not a Debian-specific issue, but definetly a Kernel-specific
issue.
2.6.7-1-686 (2.6.7-2) has no problems. OTOH, a vanila 2.6.10 with the
software suspend patch exibits very similar symptos: The clock only
loops, but doesn't go forward and backword 4291 seconds. It also manages
to advance
Package: kernel-image-2.6.8-2-386
Something is very strange with my system's clock. The following is from
the output of 'date' run from the same shell about
1 second apart:
12:13:37
13:25:08
12:13:34
I have already described this in a thread in my local LUG:
http://mirror.hamakor.org
5 matches
Mail list logo