OK. Here we go again.... Is anyone still having problems here with this happening with any kernel newer than 2.6.13-1526? There are two bugzilla jobs for this #171554 & 55223 and people are still having problems even with the 2.6.14 kernel in testing.
Gavin
On Wed, 2005-11-02 at 05:36 +1000, Gavin Graham wrote:
OK. Here we go again.... Is anyone still having problems here with this happening with any kernel newer than 2.6.13-1526? There are two bugzilla jobs for this #171554 & 55223 and people are still having problems even with the 2.6.14 kernel in testing.
I updated to 2.6.14-1633 this morning, and so far my keyboard has been working nicely. I booted without any of the modifier options. I spent a little time exercising the CPUs to try to get it into a situation where it used to get the keyboard going, but so far so good. My clock has been behaving as well.
So I can't say definitively that I'm not having any problems with the new kernel, but so far it's quite promising.
FYI, my hardware is Gigabyte K8N Pro-SLI with AMD X2 3800+.
Dan
Gavin
On Tue, 2005-11-01 at 15:38 -0700, Dan Hensley wrote:
On Wed, 2005-11-02 at 05:36 +1000, Gavin Graham wrote:
OK. Here we go again.... Is anyone still having problems here with this happening with any kernel newer than 2.6.13-1526? There are two bugzilla jobs for this #171554 & 55223 and people are still having problems even with the 2.6.14 kernel in testing.
I updated to 2.6.14-1633 this morning, and so far my keyboard has been working nicely. I booted without any of the modifier options. I spent a little time exercising the CPUs to try to get it into a situation where it used to get the keyboard going, but so far so good. My clock has been behaving as well.
So I can't say definitively that I'm not having any problems with the new kernel, but so far it's quite promising.
FYI, my hardware is Gigabyte K8N Pro-SLI with AMD X2 3800+.
It looks as if 2.6.14-1633 did improve, but does not yet solve all problems My HW: Asus A8N-SLI De luxe with AMD X2 4200
On Wed, 2005-11-02 at 11:29 +0000, Andy Green wrote:
Louis Lagendijk wrote:
It looks as if 2.6.14-1633 did improve, but does not yet solve all problems My HW: Asus A8N-SLI De luxe with AMD X2 4200
What do the remaining troubles look like?
-Andy
Keyboard repeat problems: improve, but definitely still there (it took me a while to find out that the problems are still there). Now these keyboard problems are re-appearing, the clock problem is back as well /Louis
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Louis Lagendijk wrote:
Keyboard repeat problems: improve, but definitely still there (it took me a while to find out that the problems are still there). Now these keyboard problems are re-appearing, the clock problem is back as well
Hum seems you are right, I have a handful of these still
Nov 2 09:03:40 siamese kernel: rtc: lost some interrupts at 1024Hz. Nov 2 09:05:55 siamese kernel: rtc: lost some interrupts at 1024Hz. Nov 2 09:09:30 siamese last message repeated 2 times Nov 2 09:12:37 siamese kernel: rtc: lost some interrupts at 1024Hz.
the clock problem has not reappeared here so far though: at least, not as badly as even 1 minute over 14hrs, where previously it would be out by an hour or more.
I have also seen errors from this USB keyboard from time to time, an extra character, different from the pressed one is added, or a fake shift action on a character, once every 300 or more characters, say. Not sure if it is related or a keyboard / hub problem.
Sticking this in Bugzilla too.
-Andy