int_ua | # 101 | 2013-02-03, 02:30 | Report

I've found an ideal solution:
Now Fn+Volume keys switch vts. I think that's a good addition to the config for anyone's benefit, isn't it?

Trying to make
altgr keycode 103 = Page_Up
altgr keycode 108 = Page_Down

Also,
camera halfway down = keycode 528
camera pressed = keycode 212

From Ubuntu I remember that while 212 was mapped to something, 528 wasn't.

Update: the keymap doesn't work after I start X (lxdm -> lxde)...

---

Last edited by int_ua; 2013-02-03 at 12:19.

Skry | # 102 | 2013-02-03, 12:38 | Report

Yes, this wil be included, you can send me a patch or do a pull request on github once I get all this in there. Working on it.

Yes, we will want this one too if you find sane mapping for it.

EDIT: that's fine for me, wasn't fully awake when reading.

If you can find some useful use for those, go ahead and suggest.

This is like it is supposed to be, keymappings for VC and X are defined separately. For X we probably need to discuss about shipping our own map, and about what changes we will include in it.

---

Last edited by Skry; 2013-02-03 at 13:28.

int_ua | # 103 | 2013-02-03, 14:35 | Report

Maybe meta or compose? I'm not sure yet if we can make it a modifier

int_ua | # 104 | 2013-02-03, 15:19 | Report

Why not make them identical?

edited

---

Last edited by int_ua; 2013-02-03 at 16:59.

Skry | # 105 | 2013-02-03, 16:57 | Report

VC mapping is single layout, however we have device with differentiating keypads and a lot of different mappings for different languages. So to some extent we could make English mapping similar as it is for VC, others probably need some extra work, like in my case, I have a device with fi/se keyboard so the arrow key stuff etc obviously would be non functional as it is.

/usr/share/X11/xkb/symbols/nokia_vndr/rx-51 ?

int_ua | # 106 | 2013-02-03, 17:02 | Report

oh, didn't think of that.
I was just editing my post when you answered, check it again, I've added Xorg.log errors.

Älä hakkaa | # 107 | 2013-02-04, 12:47 | Report

I'm very keen to get different keyboard mappings with my bluetooth keyboard working.¹ In Maemo, despite all efforts, I'm stuck with it behaving as if it was the internal keyboard, i.e. no numbers but long-pressing q gives 1 etc. Chances are that things are easier with a newer kernel and codebase.

Anyway, two indispensable tools here are evtest and xinput. Both don't pop up in the standard Arch (Arm) packages list but they have very little dependencies to compile them ad hoc.

______
¹ Medion P81034 = Perixx PERIBOARD-804i

peterleinchen | # 108 | 2013-02-04, 20:07 | Report

I once (maybe twice, but did not know solution at that time) experienced a very similar behaviour at a place with open WiFi.
And it took me quite some time to find out: it was caused by somehow not setting up correctly the routing.
This is what I did:
put a small script into /etc/network/if-up.d/... (script attached)
made it executable (chmod +x ,..)

From now on everything worked smoothly.
Maybe it helps. Lemme know.

BTW:
I am talking about Maemo.

Attached Files

90_up_wifiscripts.gz (175 Bytes, 167 views)

---

Last edited by peterleinchen; 2013-02-04 at 20:14.

int_ua | # 109 | 2013-02-05, 00:46 | Report

Screenlock button quick hack:
add these lines to /etc/acpi/handler.sh :
It will wake up after pressing Enter.
But it doesn't switch off keyboard leds. PanzerSajt, what were the commands you used for this?

Now trying to make it with a separate /etc/acpi/events/button-screenlock

Also, if you've missed:

---

Last edited by int_ua; 2013-02-05 at 02:03.

Skry | # 110 | 2013-02-05, 02:39 | Report

Clarification to the above, that does not lock the screen, it suspends.