Hi,
After much messing around I have managed to compile trunk and get the kernel flashed onto a pronghorn metro. This was the easy part as I didn't realise that I also had to reflash the root file system!

In a practical world, I would not want to do this - is there a way of upgrading the old file system with the relevant modules that the trunk kernel needs? Or is the process make a list of all relevant configurations and installed packages then apply these to the new root fs?

Cheers,
Ade

Hi adyb,

Working with stable kamikaze_7.09 on the prohnghorn Intel IXP4xx board worked out fine.

Now, I am experiencing a problem in upgrading kamikaze to the latest "trunk" for
the ADI pronghorn IXP425 board. 

I just checkout svn latest version of the trunk and in the make menuconfig selected Intel Xscale IXP4xx with default profile.

After successful build, booting the image with openwrt-ixp'xx-jffs2-128k.img rootfs on the board throws
....
VFS: Mounted root (jffs2 filesystem).
Freeing unused kernel memory: 128k freed
Please be patient, while OpenWrt loads ...
Kernel panic - not syncing: Attempted to kill init!

Also does the build setup on the latest trunk is changed ? like while building using kamikaze_7.09 i can find build_armeb, toochain_build_armeb and staging_dir_armeb whereas i didn't find it in latest trunk instead theres simply build_dir, toochain and staging_dir.

Could you pls clarify me and any idea would be really helpful.

Thanks
Sara

(Last edited by sara on 20 Aug 2008, 11:26)

Which kernel are you using?

I am running openwrt-pronghornmetro-zImage kernel and openwrt-ixp425xx-jffs2-128k.img rootfs image successfully
on my pronghorn SBC-250 IXP 425 board.