Months passed and I finally made progress. I managed to compile and boot a 3.7.10 kernel on SS4000-E. I basically went through the ordeal of doing the compile on the box itself, instead of cross-compiling on an x86 VM,
Took ages, but it worked. One thing I noticed is that flash-kernel refuses to flash if the kernel image does not end with iop32x, like /boot/vmlinuz-3.7.10-iop32x I had too look at the flash-kernel source to figure it was just being fussy about a file name! Anyway to bring the system up to speed from Debian's 3.2 kernel I'm going to compile my own e2fstools and iproute2 as I need them for experiments with new ext4 features and want to use fq_codel on network interface. Is there anything else you suggest that I recompile from things like util-linux, etc? Best regards, Maciej On Fri, Sep 14, 2012 at 6:15 PM, Arnaud Patard <arnaud.pat...@rtp-net.org>wrote: > Maciej Soltysiak <mac...@soltysiak.com> writes: > > >> the ss4000e is using redboot not uboot. You'll have to check but I think > >> that redboot doesn't handle uImage format so you're about to brick > >> your system. > > Thanks for the warning! I see that I have in arch/arm/boot these 3 files > > -rwxr-xr-x 1 root root 3459268 Sep 14 09:33 arch/arm/boot/Image > > -rw-r--r-- 1 root root 1328848 Sep 14 09:33 arch/arm/boot/uImage > > -rwxr-xr-x 1 root root 1328784 Sep 14 09:33 arch/arm/boot/zImage > > > > Looks like zImage is the right one then? > > yes. > > Arnaud >
