[opensuse] Keyboard gone Craaaziiiiiey
10.2 has just been upgraded by bits relating to KDE and now my keyboard not only will not register keystrokes but I had to turn off the key repeat feature because pressing any keyproduc ces a non-ending rpeat of thatkey. Is none else experiencing this or is my Logiteh keyboard/mouse combo on its last legs of a 3-year illustrious career? Chees Chheers evn.Damn thiskeyoard! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 21 February 2007 07:48:56 Basil Chupin wrote:
10.2 has just been upgraded by bits relating to KDE and now my keyboard not only will not register keystrokes but I had to turn off the key repeat feature because pressing any keyproduc ces a non-ending rpeat of thatkey.
Is none else experiencing this or is my Logiteh keyboard/mouse combo on its last legs of a 3-year illustrious career?
Chees Chheers evn.Damn thiskeyoard!
Hi Basil Same problems here with autorepeat - sometimes it just goes ballistic and won't stop without me hitting the keyboard :( Not good for SSHing over a slow connection. Keyboard here is also a Logitech... Cheers Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 21 February 2007, Pete Connolly wrote:
On Wednesday 21 February 2007 07:48:56 Basil Chupin wrote:
10.2 has just been upgraded by bits relating to KDE and now my keyboard not only will not register keystrokes but I had to turn off the key repeat feature because pressing any keyproduc ces a non-ending rpeat of thatkey.
Is none else experiencing this or is my Logiteh keyboard/mouse combo on its last legs of a 3-year illustrious career?
Chees Chheers evn.Damn thiskeyoard!
Hi Basil
Same problems here with autorepeat - sometimes it just goes ballistic and won't stop without me hitting the keyboard :( Not good for SSHing over a slow connection.
Keyboard here is also a Logitech...
Cheers
Pete
I stopped buying Logitech hardware because of crappy quality control. Back in the day Logitech used to put out some fairly good products. But the last 3 joysticks got worse every successive time I bought one (after the 2 kludgy model I gave it one more shot). The last keyboard from them went bad after about 18 months (dead keys and flaky behavior - Linux or Win). The mouse is about the best thing they seem to make now - I have an MX500 and so far it's the only Logitech device that seems worth the money. To give some insight into my experience, lets consider the joystick - the accuracy was so bad that I couldn't fly a flight sim with any reliabilty. Throttle wouldn't zero and on full wouldn't kick on afterburners regardless of how I set it up in the OS or game config. It wouldn't stay level because the stick wouldn't zero and if I took my hand off it the craft would roll or turn - regardless of any trim adjustments. The keyboard would flake out in both OS'es and in Linux it would freak out - after replacing it I have had no problems (pick any generic keyboard - how can you screw up a keyboard?). I replace the joystick with a Saitek and almost fell out of my chair - it's accurate, smooth, precise and I have had absolutely no problems with it - the same goes for the Saitek game pad as well. Given the price Logitech has been asking for their products I likely won't be buy a Logitech mouse when the time comes. The 800 dpi/resolution doesn't really seem to make a difference in Windows and in Linux - unless it's plugged into a usb port the 800 res doesn't matter either. And when plugged into a usb port one must use an app to enable the mouses higher res functions. As you can tell my opinion of Logitch products is less than favorable - I used to love 'em, not I avoid them. Cheers, Curtis. -- Spammers Beware: Trespassers will be shot, survivors will be shot again! I don't want a politician I can believe in. I simply want a politician I can believe! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 22 February 2007 09:24:32 Curtis Rey wrote:
On Wednesday 21 February 2007, Pete Connolly wrote:
On Wednesday 21 February 2007 07:48:56 Basil Chupin wrote:
10.2 has just been upgraded by bits relating to KDE and now my keyboard not only will not register keystrokes but I had to turn off the key repeat feature because pressing any keyproduc ces a non-ending rpeat of thatkey.
Is none else experiencing this or is my Logiteh keyboard/mouse combo on its last legs of a 3-year illustrious career?
Chees Chheers evn.Damn thiskeyoard!
Hi Basil
Same problems here with autorepeat - sometimes it just goes ballistic and won't stop without me hitting the keyboard :( Not good for SSHing over a slow connection.
Keyboard here is also a Logitech...
Cheers
Pete
Personally I don't think it's down to the keyboard, I've 3 desktop machines running Suse which all have a habiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiit of doing that without warning, they're all different (2 clones, 1 Dell laptop) and I've tried different keyboards (USB & PS2). I started having this problem from Suse 10.0 Matthew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Pete Connolly wrote:
Same problems here with autorepeat - sometimes it just goes ballistic and won't stop without me hitting the keyboard :( Not good for SSHing over a slow connection.
I've always had this problem with Linux and USB keyboards. If the CPU is really busy it misses the key release and just keeps repeating. When I had a 133 MHz Pentium it was really bad -- an Xterm scrolling rapidly would peg the CPU enough to not allow USB events through, so if you held down the enter key for a moment at a command prompt it would just keep going until you minimized the window. I've never seen this with a PS/2 keyboard. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 20 February 2007, Basil Chupin wrote:
10.2 has just been upgraded by bits relating to KDE and now my keyboard not only will not register keystrokes but I had to turn off the key repeat feature because pressing any keyproduc ces a non-ending rpeat of thatkey.
Is none else experiencing this or is my Logiteh keyboard/mouse combo on its last legs of a 3-year illustrious career?
Chees Chheers evn.Damn thiskeyoard!
Its BAAaaaaaaK! This problem was rampant in 10.1 but for me at least it disappeared in 10.2. (there was a bug report in bugzilla). Two things to check out. 1) did you boot with acpi enabled. Machines that are designed for acpi frequently can not reliably run all peripherals if it gets turned off. Some machines with a bios date of prior to 2001 need to have acpi forced on. For instance this old clunk I am typing on needs acpi=force on the boot command line (in /boot/grub/menu.lst ). 2) Dual processor machines (as in core 2 duo) on occasion will not keep both processors clocks properly synchronized. As the X server gets swapped from one processor to the other, there is a clock difference, and that gets timing very confused. So if you have a dual processor, see this bugzilla entry https://bugzilla.novell.com/show_bug.cgi?id=223561#c22 and see if the problem goes away with taskset trick, and if so be sure to post to that bug and mention it still exists with 10.2. -- _____________________________________ John Andersen
On Tuesday 20 February 2007, Basil Chupin wrote:
10.2 has just been upgraded by bits relating to KDE and now my keyboard not only will not register keystrokes but I had to turn off the key repeat feature because pressing any keyproduc ces a non-ending rpeat of thatkey.
Is none else experiencing this or is my Logiteh keyboard/mouse combo on its last legs of a 3-year illustrious career?
Chees Chheers evn.Damn thiskeyoard!
Its BAAaaaaaaK! This problem was rampant in 10.1 but for me at least it disappeared in 10.2. (there was a bug report in bugzilla).
Two things to check out.
1) did you boot with acpi enabled. Machines that are designed for acpi frequently can not reliably run all peripherals if it gets turned off. Some machines with a bios date of prior to 2001 need to have acpi forced on. For instance this old clunk I am typing on needs acpi=force on the boot command line (in /boot/grub/menu.lst ).
2) Dual processor machines (as in core 2 duo) on occasion will not keep both processors clocks properly synchronized. As the X server gets swapped from one processor to the other, there is a clock difference, and that gets timing very confused.
So if you have a dual processor, see this bugzilla entry https://bugzilla.novell.com/show_bug.cgi?id=223561#c22 and see if the problem goes away with taskset trick, and if so be sure to post to that bug and mention it still exists with 10.2. Thanks for your response, John. Sorry for the very tardy reply but other
John Andersen wrote: things had priority. The problem with the keyboard was only a "momentary" glitch and everything is now working AOK. What I suspect occurred is that I had the Logitech wireless/optical keyboard/mouse connected to a 2-port USB extension cable and the hardware inside this unit started to collapse; firstly the small USB desk fan suddenly stopped working and I thought that it had burnt out (but it works when plugged into another USB port) and then the keyboard when beresk. Plugging the keyboard/mouse into a 'standard' USB port and rebooting fixed the problem. The USB extension cable has since been relegated to the rubbish bin. Cheers. -- Never believe anything until it's been officially denied. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 21 February 2007 01:48, Basil Chupin wrote:
pressing any keyproduc ces a non-ending rpeat of thatkey. Every Suse distro I have used has had this problem to a greater or lesser degree... particularly on the ThinkPad. You won't notice it on a black console screen (alt-F1) but you will notice it in X; seems like the key-release event is not being sensed or processed. The work-around is to set the key-repeat low... or usually just turn it off.
-- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 21 February 2007, M Harris wrote:
On Wednesday 21 February 2007 01:48, Basil Chupin wrote:
pressing any keyproduc ces a non-ending rpeat of thatkey.
Every Suse distro I have used has had this problem to a greater or lesser degree... particularly on the ThinkPad. You won't notice it on a black console screen (alt-F1) but you will notice it in X; seems like the key-release event is not being sensed or processed. The work-around is to set the key-repeat low... or usually just turn it off.
On the other side, I have never seen this problem till 10.1 and I've been on suse since 7.0, on a wide variety of machines and laptops. Even the 10.1 problem only occurd on core2duo machines, not ALL dual processor machined. I don't think it is fair to say that "Every Suse distro I have used has had this problem to a greater or lesser degree" unless you state up front that the lesser degree includes ZERO!. -- _____________________________________ John Andersen
On the other side, I have never seen this problem till 10.1 and I've been on suse since 7.0, on a wide variety of machines and laptops.
Even the 10.1 problem only occurd on core2duo machines, not ALL dual processor machined.
I have to agree. Used SUSE since 6.3, and never had any problems win keyboard repeat... until 10.1 (I use a Cherry Linux keyboard, so it' snot just a Logitech thing). In 10.1 (on an AMD X2 3800+) it was so bad that the whole GUI (KDE and Gnome) became unusable. I posted about the whole keyboard repeat several times during the 10.1 lifetime (ie before 10.2 came out). There are a lot of threads on this back in November/December. I never saw an acceptable solution - I don't consider turning off keyboard repeat in KDE a solution. It's a half-assed workaround. That all said... 10.2 has been working perfectly. Whatever was wrong - for me - with the kernels in 10.1, it's been fixed in 10.2... I hope. I would like to know what it was, why it only affected some people, and why it's cropping up yet again. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 22 February 2007 00:24, John Andersen wrote:
I don't think it is fair to say that "Every Suse distro I have used has had this problem to a greater or lesser degree" unless you state up front that the lesser degree includes ZERO!. Specifically, I noticed this first on Suse 9.0... then on 9.2, 9.3, and now on 10.0. I skipped 10.1 *duh* and have not yet loaded my 10.2 (I'm a little scared). I noticed the problem using *hello* single core processors (we're talking emachines here) and the IBM ThinkPad R30. When I say lessor degree I am talking about frequency... one night I beat on my keyboard in order to reproduce the failure (9.3) and could not reproduce it at will... but it would happen once or twice an evening. On 10.0 the problem was so bad on my ThinkPad R30 I had to turn the repeat off... every other paragraph the repeat went nuts. I'm not picking on anybody... just the facts mam.
-- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Basil Chupin -
Clayton -
Curtis Rey -
David Brodbeck -
John Andersen -
M Harris -
Matthew Stringer -
Pete Connolly