From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PaqSE-0001rT-2m for garchives@archives.gentoo.org; Thu, 06 Jan 2011 14:04:38 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AD923E0806 for ; Thu, 6 Jan 2011 14:04:37 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by pigeon.gentoo.org (Postfix) with ESMTP id C53F3E0782 for ; Thu, 6 Jan 2011 13:13:50 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Papf3-0003d3-Q7 for gentoo-amd64@lists.gentoo.org; Thu, 06 Jan 2011 14:13:49 +0100 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Jan 2011 14:13:49 +0100 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Jan 2011 14:13:49 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: Some multimedia keys not working Date: Thu, 6 Jan 2011 13:13:39 +0000 (UTC) Message-ID: References: <1294241958.18513.6.camel@caguiar-gentoo.madeiratecnopolo.pt> <1294311681.28668.81.camel@caguiar-gentoo.madeiratecnopolo.pt> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies; GIT 25ed40d branch-testing) Content-Transfer-Encoding: quoted-printable X-Archives-Salt: a5200ab9-7562-4001-939d-4645a863e146 X-Archives-Hash: 09f8a1afc401f55443e8447282db5b8c Clemente Aguiar posted on Thu, 06 Jan 2011 11:01:21 +0000 as excerpted: > I run xev and the result on the 3 keys that I first mentioned are as > follows: >=20 > If press "My Documents" I get the following events: >=20 > KeyPress event, serial 33, synthetic NO, window 0x4000001, > root 0x1ad, subw 0x0, time 67664120, (686,264), root:(879,344), > state 0x10, keycode 120 (keysym 0x0, NoSymbol), same_screen YES, > XLookupString gives 0 bytes: > XmbLookupString gives 0 bytes: > XFilterEvent returns: False >=20 > KeyRelease event, serial 33, synthetic NO, window 0x4000001, > root 0x1ad, subw 0x0, time 67664246, (686,264), root:(879,344), > state 0x10, keycode 120 (keysym 0x0, NoSymbol), same_screen YES, > XLookupString gives 0 bytes: > XFilterEvent returns: False >=20 > If I press "My Images" or "My Music" nothing happens. >=20 > I then tried to see what happened at console level, with showkey. I'm too sleepy ATM to do a reply real justice, but here's a brief one... 1) I've never worked at the kernel level or below, only at the X level, s= o=20 don't know anything about the "nothing happens" keys or how to get them t= o=20 "something happens". 2) The "Docs" key, however, has a keycode of 120, so you can do something= =20 with that. The "something" involves either finding or adding an=20 appropriate mapping in X so it gets a valid symbol. As I mentioned, I've= =20 done it before by fiddling with the existing mappings, now found in=20 /usr/share/X11/xkb, but I've forgotten the details and am not in a state=20 to try to figure it out again ATM. But that should give you a place to=20 look if you want to start reading the files therein and trying to figure=20 it out, which should be possible as it's basically what I did, before, an= d=20 what I'd do again only it should take less time this time as I've been th= ru=20 it before. At this level, tho, it's simply a matter of setting up a conf= ig=20 file or three properly, no complex recompiling or the like. I'll see about posting more on that if I get time to go back and look at=20 them, later, but don't promise to get to it. 3) Without a valid keysym, it's no wonder gnome can't see it to map=20 anything. You'll need to get the sym working and then see what gnome (or= =20 whatever else) can do with it. 4) The other keys, without even a valid keycode... will take deeper magic= =20 than I've ever tried, tho I've come across hints and bits of documentatio= n=20 here and there. Really, you've gotten farther than I know already, with=20 showkey. Presumably you must add those scancodes to some table somewhere= =20 and then perhaps recompile something to build them in. A speculative=20 guess would be either evdev or keyboard driver, but I'm not sure if it'd=20 be at the kernel driver or xorg driver module level. That's the docs I'd= =20 start reading, tho. Or type in your precise keyboard model into google.com/linux (the Linux- specific search, I have a kde web shortcut setup for it here as I use it=20 frequently enough...), and see if anyone else has come up with a better=20 working solution. You can also try contacting the xorg and/or evdev folks and asking, but=20 I'd do some research first. No need to bother them if the answer's only = a=20 few clicks away on google, or simply involves setting a couple config=20 options in your xorg.conf after you figure out how the stuff in that xkb=20 dir mentioned above works. Oh... one more thing... if you have microsoftmult or whatever set in your= =20 xorg.conf or if still using hal instead of udev for xorg hotplugging,=20 whatever *.fdi file, try commenting/deleting that, and see if it auto- detects better settings than the ones you were manually using. With xorg= - server-1.8 and 1.9 udev based hotplugging and evdev, as I said, all my=20 keys "just work", at least as good if not better than they did with hal=20 and xkb, and manually setting the keyboard type. I was pleasantly=20 surprised on both my netbook and my desktop, as it detected the special=20 keys on both and they "just worked". --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman