Bug 43058
Summary: | i8042 PS/2 mouse not working | ||
---|---|---|---|
Product: | Drivers | Reporter: | Tim Bauer (gt6) |
Component: | Input Devices | Assignee: | drivers_input-devices |
Status: | NEW --- | ||
Severity: | normal | CC: | Actualize.in.Material+bugzillakernel, alan, dmitry.torokhov, joseluis.varela1, mat.jonczyk, pmenzel+bugzilla.kernel.org |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.2 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
i8042.debug=1 log file
dmesg | grep i8042 |
Description
Tim Bauer
2012-04-06 16:36:16 UTC
Maybe I should mention which version of Linux this is... Name : linux Version : 3.2.14-1 Name : linux-api-headers Version : 3.3-1 Name : linux-firmware Version : 20120227-1 Name : util-linux Version : 2.21.1-2 I have the same problem as Tim Bauer but with a different PC. I have a tablet Archos 9 (Link: http://www.archos.com/products/tw/archos_9/index.html) Also as Tim Bauer, it has a resistive touch screen (eGalax touch screen by eeti manufacturer)connected to the PS / 2 port. Again as Tim Bauer, it has a optical PS /2 mouse. I have contacted EETI developers (http://home.eeti.com.tw/web20/eg/Touch_Division.html). I tried they make public the source code of their drivers for windows, but they refuse. They tell me "There's Some know-how in source code, so we can not release it to client." The biggest problem is I'm trying to put on this computer Android for x86 processors (www.android-x86.org). As you know, Android is like Linux but do not use the X Windows graphics engine (use the framebuffer). The manufacturer eeti has 2 types of drivers for Linux: - One that uses X-windows (does not work on Android) - A new one that does not use X-windows (not supported devices PS / 2). I can help as needed. Thanks. Hmm, there is a kernel driver for eGalax PS/2 touchscreen, do you have CONFIG_MOUSE_PS2_TOUCHKIT enabled? Yes, Yes, I have tried in the past compiling the kernel with CONFIG_MOUSE_PS2_TOUCHKIT enabled. But does not work. The driver touchkit_ps2.c(http://lxr.linux.no/linux+v3.5/drivers/input/mouse/touchkit_ps2.c) is correct. I know it is correct because EETI programmers confirmed (I send a email and they read the source code of touchkit_ps2.c). Is correct! They did not know that code existed !!! I think the problem is the chip i8042 of our PC and the ps/2 multiplexed mode. In Windows the driver works in multiplexed mode, that is why touchscreen and optical mouse work well in Windows. The problem is that when I don't put the boot parameter i8042.nomux=1 and I put i8042.debug=1 in linux logs I found: "MUX error, status is 35, data is fe" PS/2 Multiplexed mode is not working. Created attachment 76011 [details]
i8042.debug=1 log file
This is the log file with i8042.debug=1 parameter.
Created attachment 76131 [details]
dmesg | grep i8042
I'm glad to see I'm not the only one with this problem. Similarily to Jose Luis Varela, I see MUX errors in dmesg when adding the i8042.debug=1 parameter.
Attached is the output of dmesg | grep i8042. The output in the second half is from using the touch screen. I see different MUX errors:
[ 1.836928] i8042: [17] MUX error, status is 35, data is fe
[ 1.880323] i8042: [30] MUX error, status is 75, data is fe
[ 1.923735] i8042: [43] MUX error, status is b5, data is fe
These MUX errors mean simply that nothing is connected to ports 0 and 3 of the MUX (or that these ports are not implemented at all) - nothing important. These are the interesting parts: [ 11.831664] i8042: [20] 91 -> i8042 (command) [ 11.831732] i8042: [20] f2 -> i8042 (parameter) [ 11.832053] i8042: [21] fa <- i8042 (interrupt, 4, 12) [ 12.028134] i8042: [70] 91 -> i8042 (command) [ 12.028206] i8042: [70] ed -> i8042 (parameter) [ 12.028566] i8042: [70] fa <- i8042 (interrupt, 4, 12) The devices do not return any ID when requested. Do the reporters still have the problematic devices? It’d be great, if you could verify the problem still occurs with the current mainline Linux series. I don't have this device anymore (the UMID SE pocketable PC from my initial report). |