[Bug 462645] New: Touchpad unusable on Dell D830
https://bugzilla.novell.com/show_bug.cgi?id=462645 Summary: Touchpad unusable on Dell D830 Product: openSUSE 11.1 Version: Final Platform: 64bit OS/Version: openSUSE 11.1 Status: NEW Severity: Blocker Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: led@lenday.com QAContact: qa@suse.de Found By: Customer Created an attachment (id=262523) --> (https://bugzilla.novell.com/attachment.cgi?id=262523) xorg.conf file When I put my finger on the touchpad, the mouse jumps to a location on the screen that seems to be mapped to the location where I touched the touchpad. Kind of like it is acting like a digitizer tablet... Also, touching seems to activate a button press because everything between where the mouse was and the new location gets selected and as I move my finger the selection changes. Based on other things I found I added Option "FingerPress" "255" to mouse[3] and mouse[5] in xorg.conf, there was no change. I also added i8042.nomux=1 i8042.reset=1 to my boot line, it made no difference. And I changed the driver in mouse[3] and mouse[5] from "synaptics" to "mouse", it also made no difference. And I set MaxTapTime to 0, it made no difference. The problem repeats in kde3 and kde4. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=462645
User led@lenday.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c1
--- Comment #1 from Len Day
https://bugzilla.novell.com/show_bug.cgi?id=462645
User led@lenday.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c2
--- Comment #2 from Len Day
https://bugzilla.novell.com/show_bug.cgi?id=462645
User stbinner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c3
Stephan Binner
https://bugzilla.novell.com/show_bug.cgi?id=462645
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=462645
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=462645
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c4
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=462645
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c5
--- Comment #5 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=462645
User led@lenday.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c6
Len Day
https://bugzilla.novell.com/show_bug.cgi?id=462645
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c7
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=462645
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=462645
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c8
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=462645
User dbailey@datanetworks.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c9
David Bailey
https://bugzilla.novell.com/show_bug.cgi?id=462645
User dbailey@datanetworks.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c10
--- Comment #10 from David Bailey
https://bugzilla.novell.com/show_bug.cgi?id=462645
User dbailey@datanetworks.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c11
--- Comment #11 from David Bailey
https://bugzilla.novell.com/show_bug.cgi?id=462645
User dbailey@datanetworks.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c12
--- Comment #12 from David Bailey
https://bugzilla.novell.com/show_bug.cgi?id=462645
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c13
Stefan Dirsch
This also happens with a Dell M4400. The work-around I found was to specify each mouse individually in the xorg.conf file (/dev/input/mouse0, /dev/input/mouse1, etc), instead of pointing all mouse devices to /dev/input/mice.
This is not an option for us. Not having plugged in a mouse and touchpad being disabled (which happens to some machines if you close the LID) would result in X no longer starting at all. The multiplexer /dev/input/mice is always available. Reassigning this one to our mouse expert. Matthias, David is not the original reporter, so this could be two completely unrelated issues! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=462645
User mhopf@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c14
Matthias Hopf
https://bugzilla.novell.com/show_bug.cgi?id=462645
User dbailey@datanetworks.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c15
--- Comment #15 from David Bailey
https://bugzilla.novell.com/show_bug.cgi?id=462645
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=462645
User mhopf@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c16
Matthias Hopf
https://bugzilla.novell.com/show_bug.cgi?id=462645
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c17
Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=462645
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c18
--- Comment #18 from Stefan Dirsch
I don't know if this helps but my Thinkpad T61p behaves very badly whenever evdev is used. With the exact same Mouse sections, only changing the keyboard section from kbd to evdev, produces erratic mouse behavior for the /specified/ mice (but mice plugged in later work fine),
You specify the mouse device for a evdev driver based keyboard configuration ?!? Sounds weird.
and eventually upon exit X and evdev segfault.
Backtrace: 0: /usr/sbin/xw(xf86SigHandler+0x65) [0x47e715] 1: /lib64/libc.so.6 [0x7f98bd5d76e0] 2: /usr/lib64/xorg/modules//input/evdev_drv.so(evBrainRemoveDevice+0x9b) [0x7f98ba5474eb]
This is Bug #437651. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=462645
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c19
--- Comment #19 from Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=462645
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c20
Stefan Dirsch
Not exactly - with no other changes to anything except the *keyboard* sections (same mouse specifications, etc...) if I change from using the "kbd" driver for my keyboard to using "evdev" then the mice behave strangely. Why? I have no idea. It just does.
How does your keyboard section look like before and after you changed the driver to evdev?
Again, if you google for evdev and down and right you'll find plenty of hits. The *current* (shipping in openSUSE 11.1) evdev driver is relatively broken. The version I tried below appears to work much, much better!
I tried the update X stuff from here:
http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_11.1/
and it (almost) completely solves my problem, the evdev crash goes away (yes, it's clearly the bug you linked to), and I can use evdev for everything and it all works.... except my volume up/down/mute keys, thus far.
evdev on 11.1 is still 1.1.5 whereas evdev in the X11:XOrg repo is already 2.1.99.1. These versions are completely incompatible WRT configuration, which is also the reason why we didn't use 2.x yet on 11.1.
I suspect that is a different issue, but I'd really like to help solve it. My current xorg.conf file, using the above version of X, does not have *any* Input sections or items specified at all, it's all grabbed from HAL, and with the exception of the volume up/down/mute keys everything works great.
I suspect improving the HAL descriptors here makes the biggest difference.
This sounds interesting for me. I saw that evdev is already configured via /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi, but for some reason this file seems to be ignored. At least evdev is no loaded by the Xserver. :-( Any hint how to get this working would be appreciated, since I would like to switch to hal based configuration for evdev driver for openSUSE 11.2. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=462645
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=462645
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c21
Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=462645
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c22
Stefan Dirsch
openSUSE 11.0:
Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbRules" "xfree86" Option "XkbKeycodes" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection
openSUSE 11.1:
Section "InputDevice" Identifier "Keyboard[1]" Driver "evdev" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbModel" "microsoftnek4k" Option "XkbRules" "base" Option "Pass" "3" Option "evBits" "+1" Option "keyBits" "~1-255 ~352-511" EndSection
The long and short of it is this: if (in the current shipping version) evdev > is used, at all, for anything, X will try to use it for a bunch of stuff, including already-configured devices. For some reason this is very spotty and in general doesn't work very well at all. The version I'm using above works great, so far.
Hmm. So where is the issue? The above evdev configuration is what sax2 has created
I'd love to help get evdev used for openSUSE 11.2. I'm happy to finally have an xorg.conf that has *no* input specified, finally the beginnings of the auto-configuration dream for Linux and Xorg.
So do you have this already working or not? If yes, please let me know what you did exactly, i.e. how does your xorg.conf look like, what did you change in HAL configuration? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=462645
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c23
Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=462645
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c24
--- Comment #24 from Stefan Dirsch
While googling for a solution to my own problem, I found that this might help with evdev-related issues:
Add
Option "AutoAddDevices" "False"
in the ServerFlags section.
I have not changed my HAL config.
Thanks. I'll give it a try. Although when reading the manual pages it should be the other way round. # man xorg.conf [...] Option "AllowEmptyInput" "boolean" If enabled, don't add the standard keyboard and mouse drivers, if there are no input devices in the config file. Enabled by default if AutoAddDevices and AutoEnableDevices is enabled, oth- erwise disabled. If AllowEmptyInput is on, devices using the kbd, mouse or vmmouse driver are ignored. Option "AutoAddDevices" "boolean" If this option is disabled, then no devices will be added from HAL events. Enabled by default. Option "AutoEnableDevices" "boolean" If this option is disabled, then the devices will be added (and the DevicePresenceNotify event sent), but not enabled, thus leaving policy up to the client. Enabled by default. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=462645
User jnelson-suse@jamponi.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c25
--- Comment #25 from Jon Nelson
https://bugzilla.novell.com/show_bug.cgi?id=462645
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462645#c26
--- Comment #26 from Stefan Dirsch
I believe I spoke too soon. I mistook the (apparently new in 1.6.0) Xorg behavior for evdev. I was not able to get X to enumerate and activate any devices using evdev/hal.
Ok. Same for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com