From: John Whitmore <arigead@gmail.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: RaspberryPi "is this a real kernel?"
Date: Fri, 29 May 2015 15:02:53 +0100 [thread overview]
Message-ID: <20150529140251.GB20974@bamboo.electronicsoup> (raw)
In-Reply-To: <55647AC3.7010803@gmail.com>
On Tue, May 26, 2015 at 09:53:07AM -0400, Austin S Hemmelgarn wrote:
> On 2015-05-25 05:24, John Whitmore wrote:
> >On Sun, May 24, 2015 at 09:11:56PM -0400, Valdis.Kletnieks@vt.edu 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.
>
>
Hey thanks for that. That really solves the problem thanks a million for the
info.
John
prev parent reply other threads:[~2015-05-29 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 10:32 RaspberryPi "is this a real kernel?" John Whitmore
2015-05-25 1:11 ` Valdis.Kletnieks
2015-05-25 9:24 ` John Whitmore
2015-05-26 13:53 ` Austin S Hemmelgarn
2015-05-29 14:02 ` John Whitmore [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150529140251.GB20974@bamboo.electronicsoup \
--to=arigead@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=ahferroin7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox