Mouse dead under kernel 2.6.10
Claudio Jolowicz
touchpad on a Medion notebook.
This happened with upgrade to kernel 2.6. It used to work under kernel
2.4 and 2.2. Now it doesn't work under any kernel.
I have tried about everything I could think of... Please, any help would
be GREATLY appreciated. I'm stuck!
More information is pasted below.
How can it be that the device files remain silent when I move the mouse?
kernel modules not working, wrong kernel modules, hardware not
working...?
The mouse still works when I boot Windows on same computer.
According to dmesg it's a PS/2 mouse. According to windows device
manager, PS/2 mouse using IRQ 12. But /proc/interrupts shows IRQ 12
isn't used.
ON-TOPIC-NESS
if off-topic, what is the appropriate usenet group for mouse problem
under kernel 2.6 + debian sarge?
MORE INFO COMES HERE:
Hardware: Medion MD5061 Notebook (about 2003, German)
Kernel: 2.6.10 (precompiled debian 2.6.10-1-686)
Distro: Debian sarge (testing)
Touchpad: PS/2 compatible mouse?
# cat /proc/bus/input/devices
[nothing about mouse or touchpad!]
Move the mouse and cat device files:
# cat /dev/psaux
[silent]
# cat /dev/input/mice
[silent]
# cat /dev/input/mouse{0,1,2,3}
no such device
# dmesg | grep -i mouse
mice: PS/2 mouse device common for all mice
# dmesg | grep -i synaptics
[nothing]
# lsmod
psmouse
mousedev
evdev
# dpkg -l
xfree86-driver-synaptics
gpm (installed and removed, no change)
discover
mdetect
tpconfig
kernel-image-2.6.10-1-686
# cat /proc/version
Linux version 2.6.10-1-686 (dili...@toaster.hq.voxel.net) (gcc
version 3.3.5 (Debian 1:3.3.5-6)) #1 Tue Jan 18 04:34:19 EST 2005
# cat /boot/config-2.6.10-1-686 | grep -i mouse
CONFIG_INPUT_MOUSEDEV=m
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_EVDEV=m
CONFIG_INPUT_EVBUG=m
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_SERIAL=m
CONFIG_MOUSE_INPORT=m
# CONFIG_MOUSE_ATIXL is not set
CONFIG_MOUSE_LOGIBM=m
CONFIG_MOUSE_PC110PAD=m
CONFIG_MOUSE_VSXXXAA=m
CONFIG_USB_MOUSE=m
Configurations in XF86Config-4 which I tried:
Device: Protocol:
"/dev/psaux" "PS/2" (current state)
"/dev/psaux" "ImPS/2"
"/dev/psaux" "auto-dev" (driver "synaptics"; crashed X)
"/dev/input/event1" "event" (evdev module is loaded by default)
"/dev/input/mice" "ImPS/2"
"/dev/input/mice" "PS/2"
Tried the following configs, without success:
* http://www.frosty-geek.net/x5/x11/XF86Config-4.synaptics
* http://gpoppy.org/XF86Config-4
# mdetect -x
/dev/psaux
ImPS/2
# tpconfig -i
fatal: no synaptics or alps touchpad device found
----------Current XF86Config-4-----------
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/psaux"
Option "Protocol" "PS/2"
# Option "Emulate3Buttons" "true"
# Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
Identifier "Generic Mouse"
Driver "mouse"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "PS/2"
# Option "Emulate3Buttons" "true"
# Option "ZAxisMapping" "4 5"
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Generic Mouse"
EndSection
---------End Current XF86Config-4--------
# cat /proc/interrupts
CPU0
0: 908506 XT-PIC timer
1: 2419 XT-PIC i8042
2: 0 XT-PIC cascade
3: 352925 XT-PIC serial
5: 249620 XT-PIC SiS SI7012, ohci_hcd, ohci_hcd,
ohci_hcd, ehci_hcd, radeon@PCI:1:0:0
7: 2 XT-PIC parport0
10: 13 XT-PIC yenta, ohci1394, eth0
11: 2 XT-PIC acpi
14: 11077 XT-PIC ide0
15: 7 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
From Windows:
-------------
- Control Panel:Mouse:Hardware
- Device Manager:Mice and other pointing devices:PS/2 Compatible Mouse
Name=PS/2 Compatible Mouse
Type=Mice and other pointing devices
Manufacturer: Microsoft
Location: plugged into PS/2 mouse port
Device Status: This device is working properly
Driver files:
- C:\Windows\system32\drivers\i8042prt.sys
- C:\Windows\system32\drivers\mouclass.sys
file version: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Resources: IRQ 12
Details:
Device Instance ID=ACPI\PNP0F13\4&7574933&0
Hardware Ids=ACPI\PNP0F13
*PNP0F13
Matching Device Id=*pnp0f13
Service=i8042prt
Enumerator=ACPI
Class Upper Filters=mouclass
--
,= ,-_-. =. Claudio Jolowicz
((_/)o o(\_)) http://www.jolowicz.com
`-'(. .)`-' cla...@jolowicz.com
\_/
Dances With Crows
Black Sun and said:
> My mouse is completely dead when X comes up. The mouse device is a
> touchpad on a Medion notebook. This happened with upgrade to kernel
> everything I could think of...
ISTR seeing a number of messages about this when 2.6 was first released.
You need another kernel parameter in the kernel command line.
> How can it be that the device files remain silent when I move the
> mouse? kernel modules not working, wrong kernel modules? According
> to dmesg it's a PS/2 mouse. The mouse still works when I boot Windows
> on same computer.
The kernel has to be told the highest mouse protocol to probe for on the
PS/2 interface. Don't ask me why; it just does. For kernel 2.4, I used
this line in /boot/grub/menu.lst :
kernel /boot/2.4.26 root=/dev/hda6 hdc=ide-scsi
For kernel 2.6, I need to use:
kernel /boot/2.6.10 root=/dev/hda6 psmouse.proto=bare
...note the psmouse.proto parameter; it can be set to "bare", "imps", or
"exps" for the PS/2, IMPS/2, or ExplorerPS/2 protocols. I *think* this
is because the 2.6 kernel reports all mouse events on /dev/input/mice in
a fairly standard protocol (IMPS/2?) no matter which mouse the events
came from. USB mice are all supposed to use IMPS/2, but PS/2 mice may
use other things, and the kernel needs to know what to do to translate
mouse events from the PS/2 port into the appropriate protocol. My
Thinkpad A22p's Trackpoint uses the PS/2 protocol, so I set my
psmouse.proto to "bare". YLaptopMV.
If you've built PS/2 mouse support as a module, you'll need to fiddle
with your modules.conf file so it gets passed the correct parameters.
> if off-topic, what is the appropriate usenet group for mouse problem
> under kernel 2.6 + debian sarge?
This one.
> Medion MD5061 Notebook (about 2003, German)
> 2.6.10 (precompiled debian 2.6.10-1-686)
> Debian sarge (testing)
> Touchpad: PS/2 compatible mouse?
>
> Section "InputDevice"
> Identifier "Configured Mouse"
> Driver "mouse"
> Option "Device" "/dev/psaux"
> Option "Protocol" "PS/2"
> EndSection
If that worked for X under kernel 2.4, you probably want to use "bare".
HTH,
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / mail: TRAP + SPAN don't belong
http://www.brainbench.com / Hire me!
-----------------------------/ http://crow202.dyndns.org/~mhgraham/resume
Claudio Jolowicz
>On Thu, 24 Mar 2005 17:41:37 +0000, Claudio Jolowicz staggered into the
>Black Sun and said:
>> My mouse is completely dead when X comes up. The mouse device is a
>> touchpad on a Medion notebook. This happened with upgrade to kernel
>> 2.6.
>You need another kernel parameter in the kernel command line.
>kernel /boot/2.6.10 root=/dev/hda6 psmouse.proto=bare
>...note the psmouse.proto parameter; it can be set to "bare", "imps", or
>"exps" for the PS/2, IMPS/2, or ExplorerPS/2 protocols.
Thanks for your advice.
I've tried bare and imps, but /dev/psaux and /dev/input/mice still
remain silent when I move the mouse. (exps for next reboot.)
Is there some IRQ problem? Windows says mouse uses IRQ 12, but
/proc/interrupts doesn't show this interrupt. How would I fix an IRQ
issue?
Should I see something in /dev/ttyS0 or /dev/ttyS1 when moving the
mouse? cat /dev/ttyS0 shows nothing. cat /dev/ttyS1 gives "Input/output
error".
>If you've built PS/2 mouse support as a module, you'll need to fiddle
>with your modules.conf file so it gets passed the correct parameters.
What do I need to change in modules.conf?
>> Medion MD5061 Notebook (about 2003, German)
>> 2.6.10 (precompiled debian 2.6.10-1-686)
>> Debian sarge (testing)
>> Touchpad: PS/2 compatible mouse?
>>
>> Section "InputDevice"
>> Identifier "Configured Mouse"
>> Driver "mouse"
>> Option "Device" "/dev/psaux"
>> Option "Protocol" "PS/2"
>> EndSection
>
>If that worked for X under kernel 2.4, you probably want to use "bare".
Yes, this might have been the original configuration. Not sure.
Dances With Crows
Black Sun and said:
> On Thu, 24 Mar 2005, Dances With Crows wrote:
>>On Thu, 24 Mar 2005 17:41:37 +0000, Claudio Jolowicz staggered into the
>>> My mouse is completely dead when X comes up. The mouse device is a
>>> touchpad on a Medion notebook. This happened with upgrade to kernel
>>> 2.6.
>>># lsmod
>>>psmouse
>>>mousedev
>>kernel /boot/2.6.10 root=/dev/hda6 psmouse.proto=bare
>>...note the psmouse.proto parameter; it can be set to "bare", "imps",
> I've tried bare and imps, but /dev/psaux and /dev/input/mice still
> remain silent when I move the mouse. (exps for next reboot.)
Well, the lsmod report shows that you've built PS/2 mouse support as a
module. So the kernel command line won't do anything for you. I've
always built that in directly, because in the 2.2 and 2.4 series, you
couldn't build it as a module. So... like so:
rmmod psmouse
modprobe psmouse proto=bare
...should do *something*.
> Is there some IRQ problem? Windows says mouse uses IRQ 12, but
> /proc/interrupts doesn't show this interrupt.
/proc/interrupts only lists IRQs that have been claimed by active
drivers.
> How would I fix an IRQ issue?
You shouldn't have to; IRQ 12 has been reserved for mouse use for a very
long time and no other device should be attempting to use it.
> Should I see something in /dev/ttyS0 or /dev/ttyS1 when moving the
> mouse?
Not unless you have a serial mouse.
>>If you've built PS/2 mouse support as a module, you'll need to fiddle
>>with your modules.conf file so it gets passed the correct parameters.
> What do I need to change in modules.conf?
Add this line:
options psmouse proto=bare
...note that some distros regenerate /etc/modules.conf every time they
boot, so you may have to find something that lives in the mess under
/etc and change it instead.
>>> Option "Device" "/dev/psaux"
Hm. If you didn't set "enable old PS/2 mouse device" in your kernel
config, you may want to change that to /dev/input/mice .
>>> Option "Protocol" "PS/2"
>>If that worked for X under kernel 2.4, you probably want to use "bare".
> Yes, this might have been the original configuration. Not sure.
Try it.
Claudio Jolowicz
>>>On Thu, 24 Mar 2005 17:41:37 +0000, Claudio Jolowicz staggered into the
>>>> My mouse is completely dead when X comes up. The mouse device is a
>>>> touchpad on a Medion notebook. This happened with upgrade to kernel
>>>> 2.6.
>rmmod psmouse
>modprobe psmouse proto=bare
This solved my problem! The mouse works ok, and it can be seen in both
/dev/input/mice and /dev/psaux.
Many thanks!!!
Summary:
Change modules.conf as shown below if PS/2 mouse support is built as a
module. If compiled into the kernel, add psmouse.proto=bare to the
kernel command line. Other possible values for proto are "imps" and
"exps".
[ /etc/modules.conf ]
>> What do I need to change in modules.conf?
>
>Add this line:
>
>options psmouse proto=bare
>
>...note that some distros regenerate /etc/modules.conf every time they
>boot, so you may have to find something that lives in the mess under
>/etc and change it instead.
[ /etc/X11/XF86Config-4 ]
>>>> Option "Device" "/dev/psaux"
>
>Hm. If you didn't set "enable old PS/2 mouse device" in your kernel
>config, you may want to change that to /dev/input/mice .
"Device" "/dev/psaux" with "Protocol" "PS/2" worked after the modprobe.
(kernel config and output of various commands is pasted in initial
post.)
--
,= ,-_-. =. Claudio Jolowicz
((_/)o o(\_)) http://www.jolowicz.com
`-'(. .)`-'
\_/