Bugzilla – Bug 388003
sax2: Wrong mouse detected
Last modified: 2008-05-10 06:14:02 UTC
Created attachment 213320 [details] Automatically generated xorg.conf file Platform: MacBook, first generation (core duo) Product: openSUSE 11.0 Beta 2 Media: openSUSE Beta 2 KDE 4 Live-CD (not installed) Problem: The wrong mouse type is detected on my Macbook when using the live-cd. The mouse type detected is called "Apple USB Mouse" and does neither offer right-click functionality nor is it possible to use the touch pad to scroll through pages. Setting the driver to "Synaptics" helps with the right-click functionality but the mouse pointer becomes very slow to the point where it is almost unusable. I have yet to find a setting in Yast or KDE 4 to speed up the mouse movement. Attached you'll find the generated xorg.conf and I'll happily provide further information if needed.
I don't have such a hardware for testing so if the following doesn't help I would like to address this one to the X11 team: 1) call sysp -q mouse 2) search for your mouse in the output and grub the vendor and device id information 3) edit the file /usr/share/sax/sysp/maps/Input.map and add the line: 0x<vendor-id> : 0x<device-id> : synaptics 4) save the Input.map file and call 5) init3 sax2 better results ?
/usr/share/sax/sysp/maps/Input.maps already contained a line with the vendor and device id provided by "sysp -q mouse" pointing to a driver called "alps". Changed the entry from "alps" to "synaptics" The command "init3" does not exist, so I assumed that you meant "init 3". Changing to runlevel 3 killed my X server and "sax2" couldn't start a new one. I returned to runlevel 5 with "init 5". The mouse worked, albeit very slow as mentioned in the initial report. Additionally, the monitor settings changed to the wrong resolution and the keyboard stopped working completely. Scrolling through pages with the touchpad still didn't work. Rebooted, changed the line in Input.maps again and did a "sax2 -r" this time. The mouse entry was changed to "synaptics" but neither right-click with a three finger tap nor scrolling worked.
(In reply to comment #2 from First Last) > /usr/share/sax/sysp/maps/Input.maps already contained a line with the vendor > and device id provided by "sysp -q mouse" pointing to a driver > called "alps". Changed the entry from "alps" to "synaptics" "alps" is the reference to a SaX2 profile, in which the driver is specified as "synaptics". See also /usr/share/sax/profile/alps. There is also a synaptics profile, so you're now using the wrong profile. > The command "init3" does not exist, so I assumed that you meant "init 3". Correct. > Changing to runlevel 3 killed my X server and "sax2" couldn't start a new > one. I returned to runlevel 5 with "init 5". The mouse worked, albeit very > slow as mentioned in the initial report. Additionally, the monitor settings > changed to the wrong resolution and the keyboard stopped working completely. > Scrolling through pages with the touchpad still didn't work. > > Rebooted, changed the line in Input.maps again and did a "sax2 -r" this > time. The mouse entry was changed to "synaptics" but neither right-click > with a three finger tap nor scrolling worked. Please change the entry in Input.map back to "alps" and attach /var/log/SaX.log after running sax2 from runlevel 3.
Created attachment 214073 [details] SaX.log after running "sax2" in runlevel 3 I've created the SaX.log as instructed (init 3, sax2). I booted into a new live session for this but didn't change anything else. I hope it helps.
Forgot to add something to my last comment: The SaX.log contains a xorg.conf configuration which looks all wrong. For instance, my Macbook supports a resolution up to 1280x800, has no 3 mice but at least one keyboard (this looks to me like bug 374101). Switching back to runlevel 5 didn't give me a wrong resolution though.
(In reply to comment #4 from First Last) > Created an attachment (id=214073) [details] > SaX.log after running "sax2" in runlevel 3 > > I've created the SaX.log as instructed (init 3, sax2). The config file looks broken. No keyboard section. 2 synaptics driver sections. I think this is a duplicate of another SaX2 bug. > I booted into a new live session for this but didn't change anything else. I > hope it helps. ... which freshly recreated xorg.conf
*** This bug has been marked as a duplicate of bug 374101 ***