Quote:
As far as I can tell the kernel doesn't know about touchpads. It just sees pointing devices, no matter whether they're pads or "normal" mice. So if your touchpad and your "normal" mouse are of the same type, then I guess you'll have to either:
And perhaps there are even more options (for example, maybe gpm can somehow be configured to only listen to the "normal" mouse and ignore the touchpad) but I haven't looked at those yet because the kernel config method works for me. Alphons |
Prolbem not not really sorted!
I have the same (not really) prolem: disable the touchpad for a different reason: I think I have an hardware prolem and I would like to isolate it. The target is the same: exclude the touchpad! In first instance the /etc/X11/xorg.conf has this lines: Code:
Section "InputDevice" what I use right now. (No other input stuff in that file [beside keyoard and the like..].) Also BIOS is of no help. Shall I trust Quote:
In my case I have an hardware prolem: It looks like if the touchpad is keeping moving on the right all the time. Depending on temperature and stage. I guess it is a pretty personal prolem, but excluding the touchpad at kernel/modules level might help me to isolate the prolem and also to keep using the machine. cheers S |
Sorry...
I forgot to mention a detail. It is much more easier if I can load and unload modules. Recompiling the kernel might be an option but it will bring me too far away from an easy hardware debug. I'll better change the hardware! Soon S |
Quote:
in the same time. The kernel is the OS and soon or later it will have to know about the devices it handles. One side is due to security and an other side is due to the hardware it runs on. I guess that on X servers/clients the kernel is not going to play a role as soon as the hardware is not on its own machine. Indeed the access to a simple mouse device is handled by the kernel. At least as an hardware device. You will not even see a mouse if the kernel doesn't allow it. Here are the modules: Make available to the kernel as a device: via modules (drivers). Also my shiny one. Yep, indeed: Now the 4 points you made are simply off. 1 - this might be a solution: if you can. (nobody can) 2 - Do not open the case. Unless like me you have an harware prolem do not ever open the case for software prolems! 3&4 - seek a solution. Unless you have a buggy problem there is always a standard normal easy solution. 4 - No. You do not need to start X. best S |
All times are GMT -5. The time now is 07:43 PM. |