Bug 201703

Summary: Improving Cherry CyMotion Support
Product: [openSUSE] openSUSE 11.4 Reporter: Karl Eichwalder <ke>
Component: X.OrgAssignee: Stefan Dirsch <sndirsch>
Status: RESOLVED NORESPONSE QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Enhancement    
Priority: P5 - None CC: suse-beta
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Documentation Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on: 171130    
Bug Blocks:    

Description Karl Eichwalder 2006-08-25 07:46:27 UTC 
The Kernel now knows about the keycodes.  Stefan Brandner says (bug 171130):

No, they [the buttons] have to be defined during startup. I am doing that in
/etc/init.d/boot.local

Usually the kernel creates the keycode for all keys. Since the kernel is not
aware about the special
keys of the Cymotion this has to be done with the setkeycodes command.
The code in boot.local creates this missing keycodes from the scancode.
The keycodes for all keys can then be checked with xev. 

----
See http://bugzilla.novell.com/attachment.cgi?id=97074&action=view
Comment 1 Matthias Koenig 2006-08-28 15:22:43 UTC 
Jürgen, not sure if you are responsible for this. Any ideas?
Comment 2 Karl Eichwalder 2006-10-26 09:11:30 UTC 
Jürgen, ping?
Comment 3 Juergen Weigert 2006-11-06 14:40:38 UTC 
What needs to be done here?
Comment 4 Karl Eichwalder 2006-11-06 14:58:22 UTC 
The kernel now knows about the keycodes.  I'm not sure whether it is possible to autodetect these CyMotion keyboards, but at least, if you select it in SaX, I expect SaX the proper key definition as described in comment #0 .
Comment 5 Juergen Weigert 2006-11-06 16:34:47 UTC 
okay, so let us consult our Sax Maintainer. 
Marcus?
Comment 6 Marcus Schaefer 2006-11-07 11:50:59 UTC 
to activate it automatically I need:

a) a working InputDevice section for my reference
b) the output of

     /usr/sbin/sysp -s keyboard

Thanks
Comment 7 Christoph Thiel 2008-04-25 12:04:54 UTC 
Karl, please provide the information requested in comment #6.
Comment 8 Karl Eichwalder 2008-08-06 12:19:24 UTC 
Probably too late, but here is the requested info:

a)

Section "InputDevice"
  Driver       "kbd"
  Identifier   "Keyboard[0]"
  Option       "Protocol" "Standard"
  Option       "XkbLayout" "us"
  Option       "XkbModel" "microsoftpro"
  Option       "XkbRules" "xfree86"
EndSection



b)

ke@frechet:~> sudo /usr/sbin/sysp -s keyboard
Keyboard0 =>  XkbModel   : microsoftpro
Keyboard0 =>  XkbLayout  : us
Keyboard0 =>  Name       : Cherry Cymotion Master Linux Keyboard
Keyboard0 =>  VendorID   : 0x046a
Keyboard0 =>  DeviceID   : 0x0023
Keyboard0 =>  Profile    : <undefined>
Keyboard0 =>  RealDevice : /dev/input/event1

Some keys now work out of the box (volume settings), others do not.
Comment 9 Larry Finger 2011-04-04 13:49:34 UTC 
The version with which you had the bug is now obsolete. I'll close this as NORESPONSE. If you can still reproduce it in current 11.4, please reopen the bug and move it to the appropriate version. Thanks!
Comment 10 Juergen Weigert 2011-04-04 14:34:01 UTC 
Marcus, Karl: Was this resolved?
Comment 11 Karl Eichwalder 2011-04-14 14:15:26 UTC 
No, it is basically still the same on 11.4.  Even it I select "Cherry CyMotion Master Linux" in the XFCE Keyboard config module, keys such as "Open CD-ROM" ("XF86Eject" in the upper-right corner), do not work.  I can see the keycode and keysym with xev.
Comment 14 Stefan Dirsch 2011-05-26 13:10:05 UTC 
Do we have such a keyboard available for testing?
Comment 15 Karl Eichwalder 2011-05-26 13:58:38 UTC 
I use such a keyboard @work.  Not sure whether there are more...
Comment 16 Stefan Dirsch 2011-09-01 14:13:05 UTC 
Unfortunately we do not have the ressources to address that issue
still for openSUSE 11.4. Could you please test again with
a current Milestone of openSUSE 12.1, whether the issue still
exists and give me feedback about the result? Thanks.
Comment 17 Karl Eichwalder 2011-09-01 14:46:34 UTC 
I think by now we can consider this piece of hardware as obsolete.  At home I no longer use this keyboard (at least, not ATM), and at work it works good enough as is for me.

I basically withdraw the report (hoping that that's possible).