LG N2A2DD2 won't boot Arch userland

[Mijzelf]

I'm trying to run Arch on an LG N2A2DD2 (2 bays, 1GHz Kirkwood, 128MB ram, 512kB rom).

I have serial access, but I can only read. u-boot reads a /boot/uImage from partition one, and boots it with command line
$this->bbcode_second_pass_code('', 'console=ttyS0,115200 mtdparts=spi_flash:0x78000@0(uboot),0x1000@0x78000(env) root=/dev/md0 rw lpj=4964352 nas_type=0x00000221')So I created a partiton of type 'linux raid', created a single disk raid1 array in it, put an ext3 partition in it, extracted the latest arch rootfs in it, added the stock uImage (2.6.36.2) and kernel modules.

Now the box boots the stock kernel, I can see the raid array is autodetected and -assembled as md0, but the serial log stops at 'Freeing init memory'. No kernel panic, just silence.
As far as I can see there is no activity on the network port. It doesn't request an ip address. The 2 disk leds are blinking, but of course it's possible the orginal firmware had to do some initialisation on it.

What could cause this behaviour?

[WarheadsSE]

Never heard of it before, to be honest, but it is possible that there are indeed things that need to be initialized. Also, That kernel may have hard-coded uInitrd & ramfs, which could be taking over.

[Mijzelf]

$this->bbcode_second_pass_quote('WarheadsSE', 'T')hat kernel may have hard-coded uInitrd & ramfs, which could be taking over.

[WarheadsSE]

devtmpfs?

[Mijzelf]

Indeed. That was it. Thanks.

[moonman]

Does it even work with that kernel? the minimum for systemd is 2.6.39

[Mijzelf]

Really? As far as I can tell so far it works fine. Which part should give problems?

[WarheadsSE]

The minimum mainline is 2.6.38/39 for features. Some of them may have been backported.