Problem rebooting into ALARM

[LavaChild]

Hello,

I have followed the ALARM PogoPlug v2 (Pink/Gray) installation guide (*) to the letter and now have ALARM installed on a simple single ext2 partition. The installation is on a 100 GB HDD but only 10 GB has been partitioned for the sake of ALARM (I am aware there is a 32 GB restriction based on UBoot limitations).

Initially I thought that the installation had been unsuccessful as upon issuing '/sbin/reboot' I was returned to the Pogo OS. After trying the reinstallation several times I gave up for the evening. Returning today I booted the PogoPlug and immediately found myself within ALARM. I have since spent sometime characterising the problem:

-On initial boot from power off I boot into the ALARM installation on the HDD
-On reboot from /sbin/reboot I boot into the Pogo OS
-On further reboots from /sbin/reboot I continue to boot into the Pogo OS
-The only way to return to the ALARM installation is to unplug and plug again the PogoPlug

This is completely reproducable, irrespective of the number of times I issue /sbin/reboot I boot into Pogo OS until I physically cycle the power.

Note that (I do not think this is relevant but for completion only) when ALARM boots the PogoPlug LED goes from unlit to solid green. When Pogo OS boots the PogoPlug goes from unlit to flashing green to solid green.

Note also that even when the PogoPlug boots into Pogo OS I am able to mount the HDD and verify that I can browse the RootFS.

I have not managed to find this behaviour documented anywhere. Can you provide any advice or assistance? In the time I've spent with ALARM it's been great but this is a pretty major inconvenience.

Thank you!

(*) http://archlinuxarm.org/platforms/armv5 ... s-ui-tabs2

[hydro]

$this->bbcode_second_pass_quote('LavaChild', '
')-On initial boot from power off I boot into the ALARM installation on the HDD
-On reboot from /sbin/reboot I boot into the Pogo OS
-On further reboots from /sbin/reboot I continue to boot into the Pogo OS
-The only way to return to the ALARM installation is to unplug and plug again the PogoPlug

$this->bbcode_second_pass_quote('hydro', '')$this->bbcode_second_pass_quote('LavaChild', '
')-On initial boot from power off I boot into the ALARM installation on the HDD
-On reboot from /sbin/reboot I boot into the Pogo OS
-On further reboots from /sbin/reboot I continue to boot into the Pogo OS
-The only way to return to the ALARM installation is to unplug and plug again the PogoPlug

[WarheadsSE]

Have you tried altering the delay between power on & usb scan?

[LavaChild]

Is that delay controlled through usb_rootdelay? Currently this is set to 10. Any ideas what to try? I'll be sure to give it a go (if you confirm this is what to change) but it'd still be odd that the HDD can be ready in time from a cold boot but not from a reboot... Who knows! I'd love to try a different HDD or USB drive but I don't have any spares any longer (indeed, I purchased the HDD for ALARM ).

[WarheadsSE]

I'd likely need to see a log of the u-boot output (netcat, etc)

[LavaChild]

At the moment I've not configured netconsole and do not have serial access to the PogoPlug, therefore I have no UBoot output to share. My next step, if there are no 'simple' fixes is to try and setup netconsole but I've also yet to find any complete guides (for Windows use).

I take it the 'delay between power on & usb scan' you mention is not something that can be simply set with fw_setenv?

[WarheadsSE]

Can be set with fw_setenv? Sure, know what the hell actually happens? Nope.

[LavaChild]

I understand, thanks. I'll look into setting up netconsole. In the meantime, if anybody has any other experiences or suggestions that could help I'd be very happy to hear them.

Thanks.

[hydro]

$this->bbcode_second_pass_quote('LavaChild', '
')I take it the 'delay between power on & usb scan' you mention is not something that can be simply set with fw_setenv?