Clarify ArchLinuxArm installation instructions

[permitivity]

When setting up ALArm on Pogoplug v2, I got the the step where you type in "./install_uboot_mtd0.sh", and answer yes and OK to installing the new bootloader and disabling pogoplug.

http://archlinuxarm.org/platforms/armv5 ... 2-pinkgray

I thought this step installs the new bootloader onto the nvram...which basically makes this new pogoplug exactly the same as my old pogoplugs that I've got Alarm running on already. If I stop there and power off and power on, I get a "pogoplug" prompt instead of the "bash" prompt that was on the original pogoplug. At this point, isn't the new boot loader installed?

I thought that at this point, I can take the USB drive from a previously modified Pogoplug containing ArchLinuxArm rootfs and just plug it into the new Pogoplug, and it should boot up in ALArm. But it doesn't. Instead, it can't SSH into it.

Maybe I'm misunderstanding what the bootloader installation does? I thought everything after step 4 involves installing Alarm on the USB drive, but doesn't do anything to the pogoplug itself.

[moonman]

You are right, but you might have followed the old instructions which told you to make ext2 filesystem, while the new instructions tell you to create an ext3 filesystem and modify U-Boot accordingly. Is your flashdrive ext2 formatted?

[permitivity]

The flashdrive I'm using is pretty up to date - I just did a fresh install about 3 weeks ago. It is ext3.

But I don't think the flashdrive should matter. Once I've put the new bootloader onto nvram, the new pogoplug should act just like the old pogoplug and boot from the flash drive that I've moved over from one to the other.

This has happened before, and I solved the problem by going all the way through the install instruction. At which point, both pogoplugs are interchangeable.

[WarheadsSE]

The bootloader installation should not be changing the bash prompt on the NAND's stock os, AFAIK.

[permitivity]

$this->bbcode_second_pass_quote('WarheadsSE', 'T')he bootloader installation should not be changing the bash prompt on the NAND's stock os, AFAIK.