Have any v5 owners been able to boot lately?

[tedm]

Been using arch on the pogo (dockstar) for a couple of years. With latest tar.gz I can't boot - anyone else having this issue?

[WarheadsSE]

Might want to note: FROM FRESH INSTALL.


Because I have 6 v5 devices, none of which are having issues.

[tedm]

Thanks WarheadSE, Yes, I should have put from FRESH install, and also using the Seagate Dockstar with the instructions there.

[shellwig]

Did a pacman -Su Friday and a bunch of updates came down, rebooted and Dockstar never came back. I mounted the disk elsewhere, copied off a few config files and did a fresh install, no dice.

Since I blew everything away I can not see what the recent updates were, I do not see any packets on the network, thinking maybe uboot is out of whack.

I am pulling an early May image from rollback.adminempire.com to try and get it back online. Site is unbelievably slow, is it mirrored elsewhere?

[WarheadsSE]

Check which kernel package you have installed, and if necessary install linux-kirkwood on kirkwood devices. Solves the 'systemd-needs-cgroups-xattr' issues and the kernel version being under 3.7 until we get that section back ported everything not mainlined.

[shellwig]

A fresh install of the "month" build (1 May) brought my Dockstar back to like. First thing I tried was the installing uboot-dockstar, it did not take the first try. The script was failing because fw_printenv was not returning my MAC address, I set the hardware address with fw_setenv and it ran fine.
I updated to all the latest packages without incident.

[Elroy]

See my response in another thread to similar issue:
http://archlinuxarm.org/forum/viewtopic.php?f=58&t=7396&start=10#p40521

You may need to merge in changes from .pacnew files into your /etc/group and /etc/passwd files after updates.