Booting Arch from /dev/sda2

[phireph0x]

I have a TonidoPlug v1 and am trying to boot from the second partition on my USB HD. The first partition is also a Linux fs (ext3), but is data only and has no /boot or Linux OS. My partition table is MBR and the second partition is flagged as bootable and is ext4. How do I boot ALARM from /dev/sda2?

[moonman]

You have to edit the uboot environment. It does not matter if it is flagged as active or not, you have to edit the wnvironment to point uboot where to load the kernel from, and then pass this partition to kernel as root

[phireph0x]

Thank you. I thought that was the case based on what I'd read (i.e. must modify U-boot vars to boot from a different partition), but wanted to confirm. The issue is I can't read the values from my U-boot, see viewtopic.php?f=53&t=9055 for my post regarding that. Any advice on that?

[WarheadsSE]

Do you have a serial interface to the TP1?

It should be similar to one either the PPV1 or the SheevaPlug

[phireph0x]

I don't have a serial interface. Do you mean the /etc/fw_printenv.config file settings are similar? I've tried a number of different ones, as described here viewtopic.php?f=53&t=9055. It could be that my U-boot is corrupted and I need to reflash. How would I do that?

[moonman]

It probably is not corrupt, but rather you need the tools from your version of uboot and not mainstream ones that we provide. With serial you should be able to edit the environment from within uboot itself.

[phireph0x]

I installed uboot-envtools in the stock TonidoPlug OS (Ubuntu 9.04). dpkg says the package version is 20080520-4. Manpage for fw_printenv is dated August 2008.

As an alternative, I have also compiled uboot-envtools from source from http://anonscm.debian.org/cgit/pkg-fso/ ... tools.git/. This version also produces the warning text:

$this->bbcode_second_pass_code('', 'Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200')

[phireph0x]

So, since I'm using the tools that came with my version of u-boot and I still see the Warning CRC message, it appears that my U-boot is corrupted. Unless there are suggestions for trying something else.

I have compiled U-boot from source on my TPv1 and have an image to flash to my NAND. In the configure included support for ARM, Marvell Kirkwood, and the Sheevaplug. Is there a guide for flashing a U-boot image? I don't have serial so can't use kwboot.

[phireph0x]

Is there a guide for flashing a U-boot image? I don't have serial so can't use kwboot.

[WarheadsSE]

I strongly suggest getting the serial interface.