Kernel 2.6 Keyboard/Mouse problems

TonyPul · 01-29-2005, 09:01 AM

Hi

My keyboard and mouse stopped working completely in kernel 2.6.9 but they work fine in 2.4. They're both ps/2

Any ideas?

linuxLuser · 01-29-2005, 09:48 AM

What do you have marked off in your kernel config in the following the section:

Device Drivers --->
Input device support --->

I have the following in mine:

Device Drivers --->
Input device support --->[*] Provide legacy /dev/psaux device
(1024) Horizontal screen resolution
(768) Vertical screen resolution
< > Joystick interface
< > Touchscreen interface
< > Event interface
< > Event debugging
--- Input I/O drivers
< > Gameport support
< > Serial port line discipline
< > ct82c710 Aux port controller
< > Parallel port keyboard adapter
< > PCI PS/2 keyboard and PS/2 mouse
< > Raw access to serio ports
--- Input Device Drivers
--- Keyboards
< > Sun Type 4 and Type 5 keyboard support
< > DECstation/VAXstation LK201/LK401 keyboard support
< > XT Keyboard support
< > Newton keyboard[*] Mice
<*> PS/2 mouse
< > Serial mouse
< > DEC VSXXX-AA/GA mouse and VSXXX-AB tablet
[ ] Joysticks
[ ] Touchscreens[*] Misc
<M> PC Speaker support
< > User level driver support

and everything seems to work fine.

Also, does your computer boot into a graphical loggin screen or to the console? If it's the GUI then maybe it's an X configuration issue. Maybe see what's toward the end of log file for X (if you're using xorg, then the log file is in /var/log/Xorg.0.log).

-- the dudeman

TonyPul · 01-29-2005, 10:19 AM

I have pretty much the same config for the kernel.
It boots into a graphical login like the 2.4 does.

The XFree86 log says:

Code:

(II) Keyboard "Generic Keyboard" handled by legacy driver
(**) Option "Protocol" "ExplorerPS/2"
(**) Generic Mouse: Protocol: "ExplorerPS/2"
(**) Option "SendCoreEvents" "true"
(**) Generic Mouse: always reports core events
(**) Option "CorePointer"
(**) Generic Mouse: Core Pointer
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons" "true"
(**) Generic Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Generic Mouse: ZAxisMapping: buttons 4 and 5
(**) Generic Mouse: Buttons: 5
(II) XINPUT: Adding extended input device "Generic Mouse" (type: MOUSE)
(II) Generic Mouse: ps2EnableDataReporting: succeeded

And this is from the XF86Config-4

Code:

Section "InputDevice"
	Identifier  "Generic Keyboard"
	Driver      "keyboard"
	Option	    "CoreKeyboard"
	Option	    "XkbRules" "xfree86"
	Option	    "XkbModel" "pc102"
	Option	    "XkbLayout" "se"
EndSection

Section "InputDevice"
	Identifier  "Generic Mouse"
	Driver      "mouse"
	Option	    "SendCoreEvents" "true"
	Option	    "Device" "/dev/psaux"
	Option	    "Protocol" "ExplorerPS/2"
	Option	    "Emulate3Buttons" "true"
	Option	    "ZAxisMapping" "4 5"
EndSection

linuxLuser · 01-29-2005, 11:06 AM

Is everything for the mouse compiled into the kernel, or as a module (you DO NOT want it as a module)?

TonyPul · 01-29-2005, 11:57 AM

Quote:

Originally posted by linuxLuser
Is everything for the mouse compiled into the kernel, or as a module (you DO NOT want it as a module)?

Yes, they are compiled in.

linuxLuser · 01-29-2005, 12:43 PM

Well, that just about rules out anything "normal" to check, as it looks like it's loading everything right and setup correctly.

A little (desparate) googling revealed a few things:

lkml.org suggests disabling "Legacy USB keyboard/mouse" support in the BIOS.

lists.debian.org seems to suggest that X might be picky with what kind of keyboard and possibly mouse settings you have (which may not make sense in your situation as it works with the olde kernel).

linuxforums.org seems to indicate a device issue. Check /dev/ for the /dev/psaux. If it doesn't exist then that's probably your problem. See if you can find mouse or input/mouse0 or something.
If you wanted to go through the trouble of finding which device it is (I don't have FC3 so I don't know), you could boot into single-user runlevel and just "cat" a device to see if it's working. For example, add a boot entry in LILO or GRUB which appends "-single" as part of a kernel parameter. Then it'll boot in single user mode (no GUI). You can log int and type:

Code:

# cat /dev/mouse

at the prompt. Then move your mouse and you should see jibberish on the screen. If you don't, it's not getting any input from the mouse. Try a different device.

I hope that's not too confusing. I don't know what your level of knowledge is. I can elaborate more on any point if you need. I'm just kind of grabbing at straws and thinking of everything there is to check.

-- the dudeman