SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have an issue with a recently installed Slackware 10.2 box running a custom kernel based on 2.6.13.3, whereby irrespective of whether you are logged in remotely via SSH or on the local terminal, the keyboard has a kind of "stutter" where keys are pressed but they don't register on the screen.
I've checked through /var/log/messages to see if anything has been reported, such as keystrokes not being registered but alas nothing.
I've double checked through the .config which I can attach here if neccessary, however everything looks fine. If I switch back to the original 2.4 kernel that comes with Slackware, then the problem disappears.
Originally posted by duffmckagan Did you forget to load the proper Keyboard map?
What type of Keyboard are you using?
They board that I'm using is a standard generic PC-102 keyboard manufacturered by Dell. The keyboard mapping that is loaded is GB.
I don't believe the keyboard mapping is anything to do with this though, as I've tried different mappings and the keyboard still reacts the same. You say go to type in "ls -l" and you end up with "l-l" because the s and space haven't been registered. However, when you go back to push the same keys they again aren't registered. It takes something like 2 or 3 presses to get the key registered.
Moving from Linux 2.6x to Linux 2.4x corrects the problem, so I guessing its something to do with the kernel that I've built. Any kind of information on say a kernel option that would correct this or cause it?
I would get access to the system, but at the moment it doesn't seem to be operational and I won't be back to it until Wednesday at the earliest
Originally posted by duffmckagan Did you forget to load the proper Keyboard map?
What type of Keyboard are you using?
Sorry about the extraordinaryly long time since I last updated with this. Have been floating all around the world (
Okay the keyboard mapping that is loaded at boottime is uk.map.gz from /usr/share/kbd/keymaps/i386/qwerty/ which is the correct keyboard mapping.
I also noticed (or rather one of my colleagues), the problem only happens after you initally log into the system. Leave it for a couple of seconds and the problem dissappears *scratches head*
Anybody help me further with this or which config files I should post?
Ta
Dino
BTW: The machine is a Dell Optiplex GX270, just incase that helps
As you say the problem disappears with the 2.4 kernel, perhaps you could diff the two config files and look for anomalies. Possibly something in the 2.6 configuration is awry.
Quote:
I also noticed (or rather one of my colleagues), the problem only happens after you initially log into the system. Leave it for a couple of seconds and the problem disappears *scratches head*
As you say the problem disappears several seconds after initially logging in, then possibly are you running something that is CPU-intensive at that moment and that is triggered only at login?
Are you running something from .bash_login, .bashrc, /etc/bashrc, or /etc/profile?
Are you running something on a time-delayed basis from within one of the /etc/rc.d scripts?
Distribution: slackware, the occasional five minute ubuntu run
Posts: 1
Rep:
i have the same problem with a 104/105-key usb keyboard made by saitek. i read in the forums a while back that someone else had this problem and fixed it, but they never said how.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.