One more thing, has anyone tried to suspend the system? Suspend to RAM to be particular.

For my configuration, suspending and resuming all works, but it seems that proximity sensor keeps working and will force the kernel to resume if it catches any "input".

I have been googling for a while and didn't seem to find a good solution. No one has mentioned how to tell the kernel to suspend input devices upon suspending to ram, or ignoring some input events that could cause the kernel to wake.

i am getting an error at u-boot when trying to boot the Arch Linux menu entry

Reading bootmenu.img.d/uImage
** Unable te read “bootmenu.img.d/uImage” from mmc 1:1 **

Some one who can tell me what the hell is going wrong

i tried every thing step by step and evry thing from the guide did go as it needed to go by the guide but i still get the error

Is there any way to manually lock the screen in X ? Xscreensaver and xlock are just crashing my desktop(LXDE).

What is the content of your item file?
Where is your Arch partition reside?
Which guide did you follow?

Let say you have /dev/mmcblk0p5 (formatted as ext3 filesystem) as your Arch partition and you have installed u-boot to boot into Arch.
Then you need to put this on your item file (/etc/bootmenu.d/40-ArchLinuxARM.item):
run u-boot-update-bootmenu (as root) command to add Arch Linux ARM into u-boot menu:
Reboot your phone and you shold be able to boot into Arch Linux ARM installed on your phone.

i have got exactly the same in the item file as you posted
it wil boot until the point it gives mee alot of tty lines.

EXT4-fs (mmcblk0p4) unable to read superblock.
smia-sensor 2-0010: read from offset 0x0 error -121

and it hangs there wih blinkin cursor

If you have EXACTLY the same content in item file, you won't be able to boot to Arch.
You should have this on your item file:
Then run u-boot-update-bootmenu again.

Anyway, try fsck-ing your Arch partition from Maemo to check any error on your Arch partition:

ok i will give that a try

it then give back invailid partition 4

why do i need to use partition 4 instead of 5

because when i do the steps of the guide itgive me this config file

ITEM_NAME="Arch Linux ARM (eMMC)"
ITEM_KERNEL="/boot/uImage"
ITEM_DEVICE="${INT_CARD}p5"
ITEM_FSTYPE="ext4"
ITEM_OMAPATAG="1"
ITEM_CMDLINE="root=/dev/mmcblk0p5 rootwait
init=/bin/systemdomapfb.vram=0:3M,1:3M,2:3M quiet"


and later on it lets you untar the root fs to mmcblk0p5
(root) mount /dev/mmcblk0p5 /mnt/ && cd /mnt
(root) wget ftp://bokmal.de/arch-n900/ArchLinuxA...-rootfs.tar.gz
(root) tar -zxvf

so someone can give me some guidence for where its gooing wrong

the guide i reverd to is here
http://blog.jakgibb.com/2013/03/28/a...stall-on-n900/

Because on your previous post, you write
From this information, it seems you want to install Arch on /dev/mmcblk0p5 (5th partition on you Internal MMC). Is it true?
If it is, then you should follow my previous post.
btw have you previously format /dev/mmcblk0p5 with mkfs.ext4?

yes thats what the guide on that site also does.

and yes i did that and i did it over agian bofore i worte this post its unpacking the root of to mmcblk0p5 as im writing this.

Could you give the output of this command:
# fdisk -l /dev/mmcblk0

---edit---
btw, in the tutorial, it has:
ITEM_CMDLINE="root=/dev/mmcblk0p5 rootwait init=/bin/systemdomapfb.vram=0:3M,1:3M,2:3M quiet"

when it should be:
ITEM_CMDLINE="root=/dev/mmcblk0p5 rootwait init=/bin/systemd omapfb.vram=0:3M,1:3M,2:3M quiet"

there is a space between systemd and omapfb