Hi All,
I've been contacted by a company that is trying to use openSUSE on the
Arndale and have encountered an issue. It looks like for some reason
the single zImage isn't supported.
I'm unavailable atm to look further as I'm at a conference. If someone
could have a look and advise I will happily forward on fixes etc.
Thanks,
Andy
======
I'm trying to use the latest opensuse image for the arndale board:
http://download.opensuse.org/repositories/devel:/ARM:/12.3:/Contrib:/Arndale...
But I'm unable to go after U-boot:
May 14 15:41:27.333982 Loading file "uEnv.txt" from mmc device 0:1
May 14 15:41:27.348625 ** File not found uEnv.txt
May 14 15:41:27.353010 ext2load - load binary file from a Ext2 filesystem
May 14 15:41:27.353029
May 14 15:41:27.353632 Usage:
May 14 15:41:27.359233 ext2load <interface> [addr]
[filename] [bytes]
May 14 15:41:27.364093 - load binary file 'filename' from 'dev' on
'interface'
May 14 15:41:27.368299 to address 'addr' from ext2 filesystem
May 14 15:41:27.371872 Loading file "boot.scr" from mmc device 0:1
May 14 15:41:27.383901 1646 bytes read
May 14 15:41:27.387415 Running bootscript from mmc0 ...
May 14 15:41:27.390125 ## Executing script at 40007000
May 14 15:41:27.396179 kerneladdr=0x40007000
May 14 15:41:27.398516 ramdiskaddr=0x4f000000
May 14 15:41:27.404527 mmc0 is current device
May 14 15:41:27.409725 Loading file "boot/linux.vmx" from mmc device 0:1
May 14 15:41:28.092472 3743856 bytes read
May 14 15:41:28.096727 Loading file "boot/initrd.uboot" from mmc device 0:1
May 14 15:41:33.938595 33233176 bytes read
May 14 15:41:33.943601 Loading file "exynos5250-arndale.dtb" from mmc device 0:1
May 14 15:41:33.964079 16936 bytes read
May 14 15:41:33.967523 Unknown command 'bootz' - try 'help'
If I replace bootz by bootm with:
setenv boottype bootm
I'm able to boot OpenSuse.
======
--
Andrew Wafaa
IRC: FunkyPenguin
GPG: 0x3A36312F
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
