On May 16, 2015, at 10:33 AM, Rodrigo Valiña Gutiérrez <rodr...@gmail.com> wrote:
> I had the same problem installing Debian 8 'Jessie' on a SheevaPlug. > > I solved it temporarily by doing the following: > > - In u-boot: > > setenv machid 00000692 > saveenv > > - Then install normally. The 'make the system bootable' phase will fail > because flash-kernel fails: > ---- /var/log/installer/syslog: > May 16 13:47:28 in-target: Setting up u-boot-tools (2014.10+dfsg1-5) ...^M > 4-kirkwood > May 16 13:47:46 in-target: Unsupported platform. > May 16 13:47:46 flash-kernel-installer: error: flash-kernel failed > May 16 13:47:46 main-menu[170]: WARNING **: Configuring > 'flash-kernel-installer' failed with error code 1 > May 16 13:47:46 main-menu[170]: WARNING **: Menu item > 'flash-kernel-installer' failed. > ---- > > - Then select 'execute a shell' and write: > > cd /target/boot/ > /target/usr/bin/mkimage -A arm -O linux -T kernel -C none -n uImage -a > 0x00008000 -e 0x00008000 -d vmlinuz uImage > /target/usr/bin/mkimage -A arm -O linux -T ramdisk -C none -n uInitrd > -d initrd.img uInitrd > > - It may be neccesary to change 0x00008000 to 0x00800000 in both cases, but > in my case it worked the way above. > - Then 'exit' the shell and select 'continue without boot loader'. > - I think that this last phase of mkimage should be repeated on every kernel > upgrade because I think flash-kernel (which calls mkimage) will fail again. Thanks for the analysis, Rodrigo! Could you submit a bug report against uboot-mkimage so the rest of us users of sheevaplug devices can get a working system without having to work-around this bug? I think it’s just a matter of having mkimage recognize the sheevaplug’s machid as valid, but I’m not an expert. Hopefully! Rick -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/341975e0-fffd-4480-a9ad-944fd06d2...@pobox.com
