Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
How is this for weird? I recently upgraded from kernel 2.4.27 to 2.6.16 and now my mouse scrollwheel is acting rather funny. Whenever I scroll through tabs, it skips every other one and when scrolling through pages, it skips farther than usual (two scroll lengths). I don't even have a guess as to what changed between kernels.
dmesg|grep mouse :
mice: PS/2 mouse device common for all mice
Do you have a second section using the "mouse" driver? If so, then X is using events from both entries for the 1 mouse (with the 2.4 series USB mice and ps/2 mice were handled separately, so required 2 sections in the X config file, but they've been combined in 2.6).
Also - do you have a Microsoft Intellimouse? If not, then "ImPS/2" is not exactly correct. You should use "ExplorerPS/2" instead.
Could you post your xorg.conf file (preferably with all comment lines removed)? Also if possible remove each mouse section and try to start X with only 1, and if it doesn't start then post the result of the following:
Code:
cat /var/log/Xorg.0.log | grep EE
btw, in case you weren't aware, to remove a section you have to remove everything from the "Section "InputDevice"" line to the "EndSection" line
I've been searching the interweb quite a bit, trying to figure this out. I recently tried editing Buttons and ZAxisMapping options to say 7 and '6 7', respectively, but then my mouse was really messed up, with the scrollwheel switching between pages in the browser history, so I changed it back. I've always tried catting /dev/psaux and /dev/input/mice,mouse0 and moving the mouse around. Funny characters were displayed, which is supposed to signify the incorrect device...
I fixed this, finally, and it was way too simple. I was able to start X when each of them were commented out. What eventually did it was the commenting out of the section with /dev/input/mice as device. I'm relatively certain I was forgetting to comment out the respective ServerLayout line this whole time and that's why X failed to start.
Thanks very much for your help, ciotog. I can see that you're viewing this thread right now, so I should hurry and post.
You have two mouse entries in your ServerLayout section - there should be only 1. I would recommend keeping the "Generic Mouse", as it looks to be more correct (I don't think it matters whether the device is /dev/psaux or /dev/input/mice). I would also recommend removing the other section altogether.
Another thing I noticed from your conf file is that you're using the "nv" video driver, but you're loading the "glx" module. With "nv" you should not be loading "glx", but rather "glcore" and also "dri". If you were to use the hardware accelerated "nvidia" driver you would load "glx" but not "glcore" and "dri". In other words, you should either disable "glx" and load "glcore" and "dri", or get nVidia's proprietary driver instead.
edit: hmm, ought to have checked to see if there were new posts first
However, I appreciate your pointing out the thing about the nv driver. I've been trying to get the nvidia display driver to work for a long time now and I actually just posted a thread about it a few minutes ago.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.