Re: Dreamplug Modern Kernel
On Mon, 2013-11-25 at 14:02 +0000, Robert James wrote:
> the result of flash-kernel does not boot, in my opinion due to the
> kernel rather than flash-kernel doing something wrong. flash-kernel
> works with the initrd.img-3.2.0-4-kirkwood & vmlinuz-3.2.0-4-kirkwood.
Why aren't you using the Debian kernels, if you want something newer
than what is in Wheezy you can still use the kernels from backports for
example.
> But not for the make install of the kernel which puts, vmlinuz-3.11.9,
> initrd.img-3.11.9 & System.map-3.11.9 into /boot. My understanding is
> that flash-kernel combines those 3 file to create uImage & uInitrd?
You also need a Device Tree (dtb) file, which will be concatenated with
the vmlinuz.
Flash kernel knows how to find this for packaged kernels but depending
on how you got your own kernel onto the system it may not be able to
find yours.
IIRC the Debian kernel packages put the DTB under /usr/lib/*$(uname -r)*
somewhere. The name of the file it expects to find is in f-k's database.
> Flash-Kernel looks for vmlinuz-version & initrd-version to make the
> required uImage & uInitrd & fails with
>
> Kernel suffix 3.11.9 does not match any of the expected flavors
> (kirkwood), therefore not writing it to flash.
If you get this message then you aren't actually updating anything. This
would seem to contradict your opinion that the kernel rather than
flash-kernel is where things are failing.
> changing filenames doesn't work.
What have you changed them to? When you say doesn't work do you mean
"still isn't written to flash" or do you mean that it is and that the
result does not boot?
Ian.
Reply to: