SheevaPlug will not boot after Install

[incmrg]

Hi all,

a view days ago, i want to reactivate my old SheevaPlug.
I installed the latest ArchLinux: http://os.archlinuxarm.org/os/armv5te/ArchLinuxARM-2014.03-kirkwood-rootfs.tar.gz
with the Installer ver. 1.1: http://us.mirror.archlinuxarm.org/mirror/sheeva/sheevaplug-installer-v1.1-lite.tar.gz

But after the reset i got this error:
$this->bbcode_second_pass_quote('', 'e')lcome to Arch Linux ARM!

systemd[1]: Inserted module 'autofs4'
NET: Registered protocol family 10
systemd[1]: Inserted module 'ipv6'
systemd[1]: Set hostname to <alarm>.
systemd[1]: Failed to create root cgroup hierarchy: Invalid argument
systemd[1]: Failed to allocate manager object: Invalid argument
scsi 0:0:0:0: Direct-Access Intenso Rainbow 0.00 PQ: 0 ANSI: 2
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 15794176 512-byte logical blocks: (8.08 GB/7.53 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI removable disk

[incmrg]

Hello again,

My SheevaPlug works great now...... with Debian Wheezy
So it's time to say goodbye to ArchLinux for ARMv5

Regards
IncMrG

[moonman]

It looks like an error when kernel doesn't have a cgroup support compiled in. See if it boots the kernel from archlinux tarball and not something else if you are still up for it, otherwise good luck with debian.

[WarheadsSE]

Yeah, looks like he wasn't booting the right kernel.

[incmrg]

Hi to all,

i thought the right Kernel was build in the two packages seen in my frist post??
Where can i find the right Kernel for my SheevaPlug with ArchLinux?

Thanx

IncMrG

[WarheadsSE]

Confirm which kernel it was that was booted, for one.

[MMcM]

The rcS from the plug installer lite copies the kernel uImage from USB, that is, the one it is running. For MMC install, it needs to copy from p2's /boot to p1's root. For NAND, nothing needs to be done.

An additional problem for MMC is that the boot partition is too small for recent kernels. The 4M given to fdisk by the same script needs to be 5M or so.

I worked around these issues here by hand. But I do not imagine that a new initrd would be very hard to build, if there is interest.