Bug 63530

Summary:	Wireless keyboard not properly configured
Product:	xorg	Reporter:	Marc Arthur Camilien <marcarthur>
Component:	Input/evdev	Assignee:	Peter Hutterer <peter.hutterer>
Status:	RESOLVED NOTOURBUG	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	medium	CC:	peter.hutterer
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Marc Arthur Camilien 2013-04-14 18:37:53 UTC

-- Copied from launchpad.net:

I recently purchased a VIZIO CA24-01 all-in-one PC, and found out that my wireless keyboard is not working properly, using a liveCD.

I've tried it with the latest Ubuntu Precise, Kubuntu Quantal, and Fedora17 liveCD images, all to no avail. So I know this is not an ubuntu-specific bug, but probably some kernel bug. I'm suspecting something is wrong either with usbhid, or something that it communicates to.
The keyboard is displaying the exact same behavior as that reported in 2009 by jmharris:
→ https://bugzilla.kernel.org/show_bug.cgi?id=14787
→ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/405390
I hesitated putting this as a duplicate of #405390, since it's a different hardware, and a patch was already submitted to deal with the issue over there.
If however, my reasoning is wrong, please do let me know, and accept my apologies.

For those not versed with the other(old) bug report, this is what happens:
The keyboard works properly in GRUB, but once the kernel is loaded, and control is handed off, somehow, most of the keyboard keys no longer work.
The only keys that do work are Shift_L, Shift_R, Alt_L, Alt_R, Ctrl_L, Ctrl_R, and Meta_L.
There is no Meta_R, nor Menu key on that particular keyboard's layout, so no need to worry about those.
All other keys, however, do not "work" properly.
I placed work in quotes because while somehow they are ignored in X, they still cause some errors to be logged, which leads me to believe that somehow, somewhere, the events are being received, but just not properly parsed.
There is no xev output however, so the problem is at a lower level than that.

I am not an expert at this stuff, so I could not replicate the workaround mentioned in the other bug, or create a patch of my own, so I've come here to beg for help instead.

I'll attach a few outputs I figured would be helpful in diagnosing the problem. If something else is required, I more outputs are needed, I'm more than happy to provide them.

SIDENOTE: The wireless touchpad is also not properly recognized. It is being recognized as a generic mouse, with no touchpad functions. So I've no way to enable two/three-finger gestures, which the hardware supports.

Comment 1 Marc Arthur Camilien 2013-04-14 18:41:10 UTC

This bug report is a cross-post from an identical bug report filed at launchpad.net

reporting here instead because evdev is managed here.
The original bug report can be found via: https://bugs.launchpad.net/evdev/+bug/1090956

Comment 2 Peter Hutterer 2013-04-14 22:01:31 UTC

(In reply to comment #0)
> For those not versed with the other(old) bug report, this is what happens:
> The keyboard works properly in GRUB, but once the kernel is loaded, and
> control is handed off, somehow, most of the keyboard keys no longer work.

I'm going to close this as NOTOURBUG for now, if the keys don't work on the kernel (and the above sounds like it) then there isn't anything we can do in X. if you boot into runlevel 3 (i.e. no X), does the keyboard work there? If so, then it's an X bug. if it doesn't work on the tty either, then this is definitely a kernel issue.
 
> SIDENOTE: The wireless touchpad is also not properly recognized. It is being
> recognized as a generic mouse, with no touchpad functions. So I've no way to
> enable two/three-finger gestures, which the hardware supports.

kernel issue, the kernel needs to switch this touchpad into touchpad mode.

Comment 3 Marc Arthur Camilien 2013-11-10 02:47:48 UTC

The keyboard is also not recognized when booted to runlevel 3.
This would seem to confirm that this is indeed a kernel bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.