by frugal » Sat Jul 16, 2011 2:33 am
$this->bbcode_second_pass_quote('kmihelich', 'Y')ou likely need to increase the usb_rootdelay variable in uboot. From the stock firmware you should have the fw_setenv command, or access it directly by /sbin/fw_setenv.. do this:
fw_setenv usb_rootdelay 15
Thanks for your suggestions!
First, I didn't find fw_setenv in /sbin when booted into Arch. If fact, 'which fw_setenv' didn't find it anywhere in my user or root paths (originally).
Next, when rebooted in the factory OS, I couldn't find it there either.
Following an FAQ in the Pogoplug installation instructions, I rebooted into Arch and reran install_uboot_mtd0.sh. Now, 'which fw_setenv' found it at
/usr/sbin/fw_setenv. I ran 'fw_setenv usb_rootdelay 15' and tried another cold boot and it still went into the factory OS.
Now the good news: I neglected to mention that, in addition to the boot flash drive, I have a 1TB portable desktop USB hard drive plugged into the pogoplug. It appears to be the cause of the problem. When the drive is not plugged into the pogo, cold boots work fine and go directly into Arch as expected. When it is plugged in, cold boots fail consistently.
There is no boot information on this drive, just two data partitions, one ext4 and the other was formatted ntfs but the 'mount' command shows as type fuseblk. As mentioned above, this is a desktop drive so it has it's own powersupply.
Oh, I'll also mention that the boot flash drive is plugged into the front port and the hard drive is plugged into the bottom rear usb port. The other two usb ports are unused.
Sorry I forgot to mention this drive originally. Do you have any suggestions on why adding this drive would cause it to fail to boot into Arch?
Thanks,
Mike