Hi Ian, On 28/10/2014 20:38, Ian Campbell wrote: > On Tue, 2014-10-28 at 04:08 +0100, drEagle wrote: >> The kernel flavour is not detected. >> Sheevaplug now use a dtb file and no kernel are installed into the target system. > > A dtb shouldn't be necessary for the Sheevaplug, I don't think. Did you > manually supply one or did something do that for you? I'm not that > familiar with how a Sheevaplug is set up to boot by default. The tests was done using a patched uboot. > I think that if you install by booting without an fdt (in "board file" > mode) then everything should just work. This do not work with latest kernel (d-i for jessie), which require a fdt for sheeva and some others kirkwood as raidsonic or guruplug. > Alternatively if you want to boot in DTB mode (I don't think there is > any direct benefit to doing so right now) then you will need to figure > out an appropriate stanza for the flash-kernel database. Probably this > will be very similar to the existing non-DTB one, except the Machine > line should be the contents of /proc/device-tree/model instead > of /proc/cpuinfo:hardware and you will probably want a DTB-Id line > naming the correct DTB file. It's possible you might be able to combine > the DTB and boardfile entires into one (the "Marvell Armada XP GP Board" > does this) See flash-kernel's README for more information. You can > experiment with entries in /etc/flash-kernel/db instead of editing the > main DB. Theses tests was done for jessie support. Before jessie, sheevaplugs were support by the debian kernel and the debian installer. Debian installer had also a netconsole and a netboot image which give the choice of the method of installing by ssh. Is sheevaplugs and derivatives support abandonned by debian ? I hope not. Regards, Gérald
Attachment:
signature.asc
Description: OpenPGP digital signature