On 20/11/12 17:10, Bill Merriam wrote:
I want to join the discussion about booting the cubox. Solid Run has an updated version on u-boot available to install. http://www.solid-run.com/mw/index.php/CuBox_Installer
"The CuBox Installer contains a newer version of U-Boot. This version adds support for EXT4 file systems, fast ethernet, and the bootcmd command. Follow the instructions for CuBox Installer. If an older version of U-Boot is detected, the installer will upgrade this first. After that, it is possible to quit to installer without installing a distribution."
With ext4 support it isn't necessary to have a separate ext2 partition to boot from. You can boot from the /boot directory in the root partition.
It also seems like the newer u-boot loads itself at 0x3600000. This causes problems if you try to load a ramdisk image at 0x3000000.
I don't understand why you need a initrd image to boot from some media and not others, but you don't need one to boot from a mmc.
It seems to me that life would be easier if everybody was using the new u-boot so everybody can boot the same. They could either install it themselves, using solid run's installer, or we could install it for them during our first boot. Here is the code the solid run installer uses, in u-boot. Do you have any suggestions about how I could try out this new uboot without needing to download one of the CuBox "official linux ports"? Could I just run the installer and try to stop it once uboot is flashed, or would that leave me with a horribly corrupted system?
Ciaran
That would require we keep the ext2 boot partition, put a copy of the new u-boot code there, install it if necessary (followed by a reset), then boot opensuse from the ext4 partition.
Bill
-- Ciaran Farrell, Attorney at Law SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org