[SuSE Linux] Mouse problem after kernel compile
I have Suse 6.1. I wanted to compile the kernel to add PPP support. I added that and a few other things, which I may not need, like parellel port support. This is kernel 2.2.5, I haven't touched the source or upgraded anything. Anyway, now, in X Windows, my mouse won't work. Any ideas as to what in the kernel would cause this? I have a serial MS mouse, which works fine with the kernel as shipped with 6.1. I'm kind of new, so let me know if you need any more information. Thanks! Barbara ______________________ Postmaster 1.0b6 for BeOS <A HREF="http://cs.ubishops.ca/postmaster"><A HREF="http://cs.ubishops.ca/postmaster</A">http://cs.ubishops.ca/postmaster</A</A>> -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Barbara Pfieffer wrote:
I have Suse 6.1. I wanted to compile the kernel to add PPP support. I added that and a few other things, which I may not need, like parellel port support. This is kernel 2.2.5, I haven't touched the source or upgraded anything.
Anyway, now, in X Windows, my mouse won't work. Any ideas as to what in the kernel would cause this? I have a serial MS mouse, which works fine with the kernel as shipped with 6.1.
I'm kind of new, so let me know if you need any more information.
Thanks!
Barbara
Hi Barbara, Kernel compiles are sometimes a bit confusing, since things can either be done as a module or monolytic (into the kernel). There is for instance a chance that you set up the serial stuff to be *in* kernel and in another menue decide to use mouse support as a module. IŽd check my kernel setup first, the stuff about serial support and mouse support. IŽd confused myself with the PS2 mouse (aux port) which I simply forgot to switch on. Caused a few hart attacks, two days after I got my new system with the "broken" mouse port.... ;-)) Juergen -- ========================================== __ _ Juergen Braukmann mail: brauki@cityweb.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu| /\\ /__/ / _ \/ // /\ \/ / ==========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Juergen Braukmann wrote:
Barbara Pfieffer wrote:
I have Suse 6.1. I wanted to compile the kernel to add PPP support. I added that and a few other things, which I may not need, like parellel port support. This is kernel 2.2.5, I haven't touched the source or upgraded anything.
Anyway, now, in X Windows, my mouse won't work. Any ideas as to what in the kernel would cause this? I have a serial MS mouse, which works fine with the kernel as shipped with 6.1.
I'm kind of new, so let me know if you need any more information.
Thanks!
Barbara
Hi Barbara,
Kernel compiles are sometimes a bit confusing, since things can either be done as a module or monolytic (into the kernel). There is for instance a chance that you set up the serial stuff to be *in* kernel and in another menue decide to use mouse support as a module. IŽd check my kernel setup first, the stuff about serial support and mouse support.
IŽd confused myself with the PS2 mouse (aux port) which I simply forgot to switch on. Caused a few hart attacks, two days after I got my new system with the "broken" mouse port.... ;-))
-- I just read about this only this morning while browsing the 2.2.7 kernel readmes. It seems that in prior versions of the kernel the mouse configurtion variable was considered to be of a type called "tri-state" (y,n,m) but programmers (who?) set the variable to type boolean (y,n), which confuses the kernel building interpreters, which still think it is tristate, if that was what the previous setting in the config file was. According to the info in the readme the mouse config variable should be returned to 'm'. Of course, I am only recalling this using a 1941 version (out-of-date) organic memory module, so it would be best if you read the kernel readmes for the mouse, which is in the /usr/src/Linux-2.2.XX..../documentation/mouse subdirectory, if I remember correctly. JLK Linux, because it's STABLE, the source code is included, the price is right. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Hi, On Fri, Jun 04, Barbara Pfieffer wrote:
I have Suse 6.1. I wanted to compile the kernel to add PPP support. I added that and a few other things, which I may not need, like parellel port support. This is kernel 2.2.5, I haven't touched the source or upgraded anything.
Anyway, now, in X Windows, my mouse won't work. Any ideas as to what in the kernel would cause this? I have a serial MS mouse, which works fine with the kernel as shipped with 6.1.
There's a bug in the kernel wrt modules: If you add the serial support to the kernel, it will additionally try to load as a module. The bad thing: It "succeeds", rendering your serial ports unusable. Solution: Use the serial driver as module or delete /lib/modules/2.2.5/misc/serial.o so that it cannot longer be loaded as module.
I'm kind of new, so let me know if you need any more information.
Thanks!
Barbara -o) Hubert Mantel Goodbye, dots... /\\ _\_v
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
participants (4)
-
bjp@bejay.com
-
brauki@cityweb.de
-
jlkreps@navix.net
-
mantel@suse.de