Summary: | evdev breaks after launching mozilla-firefox | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joseph D. Wieber, Jr. <jdwieber> |
Component: | Current packages | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | x11 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Joseph D. Wieber, Jr.
2005-03-15 13:10:21 UTC
Well, X is just reading /dev/input, so if the actual event interface screw up, it's not X's fault. Perhaps you should check what happens when you cat the device and move your mouse around on a command line, before and after X stops working properly. I never suspected that X is the problem. The references to my X config are there to show how the event interface and synaptics driver are utilized. I've removed evdev from my kernel and let the mouse driver handle the touchpad (on /dev/input/mice) and nothing breaks. In the kernel compiled with evdev I tried changing my X config back to its initial state with the mouse driver handling the touchpad on /dev/input/mice, but the kernel loads evdev as soon as it detects the touchpad. Thus, the touchpad stops responding after mozilla-firefox is launched. I think the problem lies with evdev because in this version the synaptics driver is removed from the X config and should not be loading. In the kernel w/o evdev capabilities, using the same X config (mouse driver) the touchpad continues to work after firefox is launched. In the original post, I stated that restarting X makes the touchpad work again. I do not know why it works again after restart. Perhaps it is because the synaptics driver is reloaded and performs some initialization sequence that repairs the event interface. I'm just speculating here, I never looked under the hood to see what happens. In any case, it works sufficiently without using the event interface. Kernel folks may be able to assist with this better. Can you please test 2.6.12-rc1? There have been a number of evdev changes there. 2.6.12-rc1 is not in my portage tree yet, I'll have to d/l it and put it there (syncing didn't bring it down). I'll do that prolly on Wednesday. In the mean time, 2.6.11-r4 does not have the problem with evdev that the previous kernel had. Interestingly enough, I get a roblem with pci bus recognition. It'll hang on boot if my wireless nic is in. I have to boot and then put the nic in, but then syslog has an error about an unrecognised bus PCI... but that is another battle which I fight when time permits. 2.6.11-r5 is compiling now and I'll post the results soon. When I get 2.6.12-rc1 I'll test it and post the results asap. Thanks for the help. 2.6.12-rc1 is available under vanilla-sources The synaptics drivers fail to detect the touchpad when X loads under kernel 2.6.12-rc1. However, the kernel sees the touchpad. Below are excerpts from dmesg and /var/log/Xorg.0.log respectively. ********************FROM OUTPUT OF DMESG******************** [...] Synaptics Touchpad, model: 1 Firmware: 5.0 Sensor: 20 new absolute packet format Touchpad has extended capability bits -> multifinger detection -> palm detection input: SynPS/2 Synaptics TouchPad on isa0060/serio1 [...] ********************FROM /var/log/Xorg.0.log******************** X Window System Version 6.8.2 Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: Linux 2.6.10-gentoo-r6 i686 [ELF] Current Operating System: Linux laptop 2.6.12-rc1 #2 Tue Apr 5 15:29:11 EDT 2005 i686 Build Date: 13 March 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Apr 6 10:46:23 2005 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Simple Layout" (**) |-->Screen "Screen 1" (0) (**) | |-->Monitor "My Monitor" (**) | |-->Device "NeoMagic (laptop/notebook)" (**) |-->Input Device "synaptics touchpad" (**) |-->Input Device "Keyboard1" (**) |-->Input Device "Mouse1" [...] (II) Synaptics touchpad driver version 0.14.0 (**) Option "Device" "/dev/input/event1" (**) Option "SHMConfig" "on" (**) Option "LeftEdge" "1900" (**) Option "RightEdge" "5400" (**) Option "TopEdge" "1400" (**) Option "BottomEdge" "4500" (**) Option "FingerLow" "25" (**) Option "FingerHigh" "30" (**) Option "MaxTapTime" "180" (**) Option "MaxTapMove" "220" (**) Option "VertScrollDelta" "100" (**) Option "TouchpadOff" "2" (EE) synaptics touchpad no synaptics touchpad detected and no repeater device (EE) synaptics touchpad Unable to query/initialize Synaptics hardware. (EE) PreInit failed for input device "synaptics touchpad" (II) UnloadModule: "synaptics" [...] (WW) No core pointer registered (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD) (--) Mouse1: PnP-detected protocol: "ExplorerPS/2" (II) Mouse1: ps2EnableDataReporting: succeeded No core pointer Fatal server error: failed to initialize core devices Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. Strange. Can you please try 2.6.12_rc3 and attach the contents of /proc/bus/input/devices from that kernel, assuming X still won't start. Bad news... That laptop is no more. I apologize for the inconvenience. The good news (for me) is that my new laptop (ACER Ferarri 3400!! 64bit) will arrive soon. Thanks to all who were working on this issue. Aslo, a big thanks to all the folks who make Gentoo possible; you make life worth living! Ok, thanks for reporting anyway. If anyone else experiences this problem, please post on this bug. |