Synaptic touch pad and keyboard not detected on Toshiba Satellite
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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.
Synaptic touch pad and keyboard not detected on Toshiba Satellite
I have a Toshiba Satellite C850D with AMD Radeon HD graphics and 6GB of Ram with Ubuntu 13.10.
However, when I boot it sometimes the touch pad and keyboard do not work. I can eventually get them to work my continually restarting my computer.
First, I tried previous versions other than my 13.10. I tried 13.04 and 12.04. Seeing that the keyboard, nor did the touch pad work on these live CDs... I figured it must be a driver issue.
To rectify this, I checked that I did have a synaptic touch pad.
For the keyboard & mouse & whatever to work in X 2 things have to happen:
1) the Linux kernel has to recognize them and use the appropriate modules.
2) X has to find them and load the appropriate modules/drivers.
Therefore the first thing I would try to do would be to check if the Linux kernel has found those devices.
The easiest way to test if the kernel if ok with the devices would be for you to kill X (if I remember correctly the key combination to kill X is ctrl+alt+backspace, but I'm not sure) and then you should fall back into the pure "console" mode and then you can just try to type something and see if it works => if it does than your problem is only with X.
(Or maybe you can even select a boot option to go directly into console mode without starting up X?)
Alternatively, if you have a second PC/notebok available, connect to the not-working PC/notebook using SSH (you might have to set it up...).
If you're connecting remotely from a different PC then do a "cat /dev/input/event[try_every_single_one]" and then try to type something on the physical keyboard connected to the not-working-pc and try to move the mouse => if you see garbage showing up in the console it means that the keyboard or mouse was recognized by the kernel.
If nothing happens than you have a big problem, but it's very unlikely.
If you do see something then it's just a matter of configuring X11 correctly so that it finds them. This would be a separate chapter.
Cheers!
Btw., the behaviour you describe might happen when using a KVM between PC and the devices => the problem you describe is related to the physical keyboard & mouse of your notebook, right?
Yes, the issue pertains to the keyboard and mouse on my laptop.
I tried the keyboard shortcut, "ctrl+alt+bkspace" and from what I observed, it made no difference to the performance at all. (I confirmed the method on Google.)
In addition, along with the Ubuntu live CDs I mentioned previously, I tried a Fedora live CD after posting this thread and the keyboard and trackpad worked just fine on it.
So, based on this information, would you say it is an issue of configuring X11?
The easiest way to test if the kernel if ok with the devices would be for you to kill X (if I remember correctly the key combination to kill X is ctrl+alt+backspace, but I'm not sure) and then you should fall back into the pure "console" mode and then you can just try to type something and see if it works => if it does than your problem is only with X.
(Or maybe you can even select a boot option to go directly into console mode without starting up X?)
Alternatively, if you have a second PC/notebok available, connect to the not-working PC/notebook using SSH (you might have to set it up...).
If you're connecting remotely from a different PC then do a "cat /dev/input/event[try_every_single_one]" and then try to type something on the physical keyboard connected to the not-working-pc and try to move the mouse => if you see garbage showing up in the console it means that the keyboard or mouse was recognized by the kernel.
If nothing happens than you have a big problem, but it's very unlikely.
If you do see something then it's just a matter of configuring X11 correctly so that it finds them.
If the keyboard/mouse reacts when you try them out with "cat /dev/input/event[X]" then it could be for example that your X-configuration as a specific "/dev/input/event[X]" hardcoded in your X-configuration and the "X" might vary between reboots and that would be the reason why X works with mouse & keyboard only from time to time... .
I will eventually do the ssh diagnostics but how would you configure the X11 files, if that may be the case?
You should check if you have a file called "xorg.conf" lying around.
Mine is in "/etc/X11/xorg.conf", yours might be somewhere else depending on your distribution/installation.
I you find it see if you find sections for the keyboard/mouse similar to this one:
If you do you might want to check if the "/dev/input/[whatever]" is valid (if the file exists and if you do a "cat /dev/input/[whatever]" and moving your mouse / typing on your keyboard returns something). If not, it might be enough to delete/comment out that line (or maybe the whole section or even the whole file - in any case take first a backup of that file) to force Xorg to autodetect the device(s)... .
Sorry for not replying sooner. I am going to try and remove this file now.
However. I am am currently trying
sudo rm -r -f /usr/share/X11/xorg.conf.d
-r to delete everything and -f for force.
It has remove the file but then would Xorg just automatically detect the devices now or do I have to reboot? (my mouse and keyboard are working just fine now)
Last edited by metalkittykat; 11-24-2013 at 10:11 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.