On Wed, Sep 14, 2011 at 06:38:04PM +1000, Tim Connors wrote:
I have a USB-serial cable connecting my laptop (running 2.6.39 from Debian) to a weather station.
My keyboard is connected to a different USB port on the laptop. Whenever the met software is reading and/or writing to the serial port (I haven't yet debugged whether it only happens during read or write), the keyboard badly lags when in X, but not at the console. I don't *think* the mouse is affected, most of the time, unless X is waiting for the keyboard to catch up.
have you tried hard-coding your input devices into xorg.conf and telling X to not auto add/enable new devices? i used to have something very much like the following in my xorg.conf to prevent the scroll wheel from being enabled (before my game playing habit developed to the point where i decided that a working scroll wheel might suck in terminals but it's really bloody useful in games). note: reconstructed from commented out bits of crap in my xorg.conf, but reasonably close to a working config. or was reasonably close at some point in time. x has changed a lot in the last year or two. and the input layer has received a huge amount of attention. Section "ServerLayout" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "Protocol" "Auto" Option "Device" "/dev/input/by-id/usb-Logitech_USB-PS_2_Optical_Mouse-mouse" EndSection Section "ServerFlags" Option "AllowEmptyInput" "false" Option "AutoAddDevices" "false" Option "AutoEnableDevices" "false" EndSection
So now, given the bloat (sorry, abstraction) that has been thrown at X/HAL/udev over the last few years, where do I start debugging this one? (friggin give me back XFree86 and a keyboard driver understood by more than 3 people on the damn planet!).
Can anyone else reproduce this? You probably don't need a USB-serial converter. It's probably just some conflict reading things from /dev/input/* or in the kernel TTY layer or something, and so any old serial connection busily talking will do it.
i have a USB serial converter. bought it cheap at a swap meet, figuring it might be a useful thing to have lying around...haven't used it yet. it's probably crap. I can probably dig up an old modem or something to have something for it to talk to. i can test it if you want. just plugged it in for the first time, it's a: Bus 008 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
(god knows why I upgraded. Oh yeah, squeeze. I should have learnt by now).
because upgrading is usually good. in the long run. btw, 2.6.39 is old and buggy. try 3.0 craig -- craig sanders <cas@taz.net.au> BOFH excuse #23: improperly oriented keyboard