I tried to subscribe to the RaspberryPi Kernel mailing list a few days ago but
I guess that my request has not been accepted as yet. Maybe it was missed so I
re-tried a moment ago. Since I can't get in there I thought I'd try
here. Apologies, bit of a panic.
So I'm trying to make a few changes to the Ubuntu Mate kernel for the
RaspberryPi V2. The Ubuntu kernel is 3.18.0-22 so I checked out, what I
thought was the last version of 3.18.0 from the RaspberryPi Kernel git repo,
did a make oldconfig, make menuconfig, to include CAN and stuff and then built
the kernel without any issues.
Now I'm not fully understanding the rest of the process but there's a utility
in the RaspberryPi tools to actually take the output from the build and
produce the image file for your SD card. It's questioning the integrity of my
built kernel and I've no idea why. (I think it's lovely and can't see why
anybody could question it!)
$ ./mkknlimg ../../linux/arch/arm/boot/zImage 3.18.0-can+.img
tail: +: invalid number of bytes
* Is this a valid kernel? In pass-through mode.
I'm using "mkknlimg" as the other utility "imagetool-uncompressed.py" is just
giving me a data file.
So can anybody help me to understand what it is that's going wrong with this
process.
John
On Sun, 24 May 2015 11:32:36 +0100, John Whitmore said:
> $ ./mkknlimg ../../linux/arch/arm/boot/zImage 3.18.0-can+.img
> tail: +: invalid number of bytes
> * Is this a valid kernel? In pass-through mode.
Looks like they try to use 'tail' to skip over something, but the + sign
in your uname -r gives it indigestion. Try building with a version name
that doesn't include a + sign, and complain to the maintainers of mkknlimg
that they've probably got a parameter quoting problem (most likely, there's
someplace a
tail -this -that $foo
needs to be
tail -this -that "$foo"
On Sun, May 24, 2015 at 09:11:56PM -0400, [email protected] wrote:
> On Sun, 24 May 2015 11:32:36 +0100, John Whitmore said:
>
> > $ ./mkknlimg ../../linux/arch/arm/boot/zImage 3.18.0-can+.img
> > tail: +: invalid number of bytes
> > * Is this a valid kernel? In pass-through mode.
>
> Looks like they try to use 'tail' to skip over something, but the + sign
> in your uname -r gives it indigestion. Try building with a version name
> that doesn't include a + sign, and complain to the maintainers of mkknlimg
> that they've probably got a parameter quoting problem (most likely, there's
> someplace a
>
> tail -this -that $foo
>
> needs to be
>
> tail -this -that "$foo"
Thanks a million for that help. I'll do a bit of looking into the scripts.
On 2015-05-25 05:24, John Whitmore wrote:
> On Sun, May 24, 2015 at 09:11:56PM -0400, [email protected] wrote:
>> On Sun, 24 May 2015 11:32:36 +0100, John Whitmore said:
>>
>>> $ ./mkknlimg ../../linux/arch/arm/boot/zImage 3.18.0-can+.img
>>> tail: +: invalid number of bytes
>>> * Is this a valid kernel? In pass-through mode.
>>
>> Looks like they try to use 'tail' to skip over something, but the + sign
>> in your uname -r gives it indigestion. Try building with a version name
>> that doesn't include a + sign, and complain to the maintainers of mkknlimg
>> that they've probably got a parameter quoting problem (most likely, there's
>> someplace a
>>
>> tail -this -that $foo
>>
>> needs to be
>>
>> tail -this -that "$foo"
>
> Thanks a million for that help. I'll do a bit of looking into the scripts.
>
Actually, unless you are using ancient firmware (from prior to the first
production revisions of the Model B), you should be able to boot the
zImage directly, just drop it in /boot and edit config.txt to point to it.