Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just recently installed Redhat 9.0 on a secondary machine. The install seemed to go flawlessly.... except when the first boot screen comes up my keyboard and mouse go dead. No Ctrl-Alt-X or Alt-X, no mouse movement, no Ctrl-Alt-Del, no Num lock or Cap Lock.
I read some other posts about Kudzu killing the mouse so I tried an interactive boot to not start Kudzu. Same problem.
I am lost at to what to try next. Any suggestions would be appreciated.
You can usually force these to drop to single user mode. on grub you press 'e' and add '1' on its own to the end on the kernel line. in LILO you can use the boot promt (if you in graphical press Ctrl X to get the command promt) and type linux single
Then it should boot and ask you for you root password (some distros dump you straight to a CLI which is fine)
now you can type:
and tell us what it says.
Then you can use the single user mode to fix the problem.
I was just trying some more things to get it to work and I noticed that after I start the GPM service using the (I)nteractive start mode that I loose control of the keyboard. If I don't start the service the keyboard works fine (up till the point that X starts. Then the lights go out on the keyboard and it is effectively dead).
Incidentally I had a similar problem recently. My redhat was working properly until I changed the setting of the mouse from Generic PS/2 to wheel mouse PS/2. Now exactly the same problem came up - the keyboard lights would go off just when X starts, and neither keyboard nor mouse would work. In interactive mode, the keyboard would stop working the moment 'crond' service starts. I tried all kinds of things with the XConfig file, including changing the setting of the mouse back to earlier level, but of no use. I even tried running the redhat cd in the rescue mode, but it did not work. Finally I ran the cd in the upgrade mode and reloaded all the applications related to multimedia and desktop - and now it has started working again !!! Though I could not figure out what had gone wrong in the first place.
I found this list of stuff for Redhat, about Keyboard and Mouse problems. Theirs aparently more files involved in a redhat setup, this maybe what is causing all the grief, anyway theirs a solution as well verbatim from the TLUG mailing list archives
After logging in as root run the command:less /etc/sysconfig/mouse and less /etc/sysconfig/keyboard and check the files is it contains the correct settings for your mouse and keyboard.You may also remove these files, with the command:
then run the command:
The latter command will then again generate the file /etc/sysconfig/mouse, thus, refresh the configuration file. And as for the keyboard you need to run the command:
to generate the /etc/sysconfig/keyboard file.
Check also the file /etc/X11/XF86Config file;
and check the Section "Keyboard" and Section "Pointer" and see if this contains the correct settings for your device. Try also running this command and see if this will help.
Xconfigurator --preferxf3 --server XF86_SVGA
First when I changed the run level from 5 to 3.... I could not log into the command prompt. The keyboard was dead to all keystrokes. I then started the system (I)nteractively and did not start the GPM service. I was then able to log into the CLI. I tried the startx command.... it started but the same issue happened. The mouse and keyboard were dead.
Next I changed the XF86Config file to comment out the following line:
InputDevice "Mouse0" "CorePointer"
X failed to start with the mesage "(EE) No Core Pointer device specified"
Next I undid the previous change and commented out the following line:
InputDevice "DevInputMice" "AlwaysCore"
X started this time with no messages but the keyboard and mouse were still dead. I found the following lines in the XF86Config file that explains this operation since it seems to be optional:
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
I also thought Greensleeves_2k post interesting since I have a ps2 wheel mouse installed. I don't know if this mouse type is causing the issue with both GPM and X. Any thoughts?
BTW... how can I stop the GPM service from starting up temporarily till I can figure this out? It is a real pain to interactively start everything.
I scanned through the RC.d directory but it looks like it can be started at many run levels. How can I kill it generically?