If you have n900-configs installed you should already be using it. /etc/X11/xorg.conf.d/90-input.conf

EDIT: Probably worth mentioning: Some DE's have their own way of handling keyboard layouts, so, I ship configuration files for X and that's about it. Also, symbols etc are in package extra/xkeyboard-config and I'm not sure if there's been a change in packaging that stuff or what but that package is not a dependency of X anymore, which I think it used to be, or it may be a new package also. So if you don't have rx-51 symbols, you're probably missing that package and/or your DE forces it's own settings.

EDIT2: pacman -Qi xkeyboard-config shows that it is a dependency for xorg-server-common, so it should be installed automagically with X. So, it looks like some update somewhere broke this.

If there is someone about to install Alarm on his/her device, I have a rootfs tarball in the works (probably usable in few days), which I need someone to test. So if you're willing, PM me here or query me at IRC.

RE: problems with keyboard maps.

To solve this I did:

The above might be a bit tricky to type without a working Blue key so, It might be a good idea to run it at the startup of you DE, or if you're like me and use startx, add it to .xinitrc, or create ~/.Xmodmap.

Now, I currently don't have enough time to look at this problem any further (see my previous post), so if this fix makes it work, please report, if it does not help, report.

EDIT:
I'm really upset about this issue. My tea got cold while solving it.

EDIT3:
Explained and solved in here.

Fixed for me, many thanks

Fixed for me too.

I really want to thank you for the great work you do! I just got an N900 (finally...) and I think it would be great to help you testing.

(I have some experience with alarm on a NAS and quite a bit with Arch in general. I do not have any experience with hacking on the N900, though.)

Missed you twice on IRC, sorry. Sure, you can get to test stuff out, I'll probably/hopefully have the rootfs ready someday this week.

There will be some updates to my repo and packages, which will require user intervention on existing installs:

Kernel package no longer installs uImage-n900 to /, instead it will go to /boot only, with a name 'uImage', so you need to either copy (and possibly rename) it to / and/or update your menu items.

Configs package is now splitted, and you will need (well, everything is optional, but you probably want it) to install n900-integration package manually. This will overwrite any changes made to files owned by n900-configs, so you might want to backup.

Modem init is moved to n900-integration, and needs to be re-enabled manually if you need it.

Display backlight and keyboard leds are now set up by systemd service via script. There is also configuration file in /etc where you can set up initial brightness values for both. This too must be manually enabled with systemctl.

DSP and SGX are now handled by their own packages, and require enabling them manually with systemctl.

Watchdog handling must be enabled in systemd.

I will make another post with more precise instructions once the updates go live.

More positive news probably are that shutdown, reboot, audio and clock issues are now gone, suspending works a lot better and is actually usable now. Wlan problems should be gone, and the kernel config is more in line with Alarm, so you can crypt all your porn, setup raid with emmc+uSD, go router and/or firewall and so on.
Also, kernel is now small enough to be flashed. In addition, I've added several packages compiled with neon support enabled, to my repo, names suffixed with -neon.

Please test:

ArchLinuxARM-N900-2013.02-rootfs.tar.gz
ftp://bokmal.de/arch-n900/ArchLinuxA...-rootfs.tar.gz
http://www45.zippyshare.com/v/91278544/file.html

Installation:
- Untar to a partition (ext2/3/4) of your choice.
- Configure U-Boot to load /boot/uImage from that partition.
- Reboot

So, no need to chroot, install anything or edit anything, just untar, sync, boot, network up (wifi-menu), configure, use.

If you boot to Maemo frequently, you may see some devices failing when booting to Alarm afterwards. If this happens, do systemctl poweroff and boot again.

Any feedback is welcome from the brave souls testing

Why separate archive? Is there something that can't be done with packages? WIll it be the same if I just get default ALARM rootfs and install kernel+integration?