From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756118AbbE2OGQ (ORCPT ); Fri, 29 May 2015 10:06:16 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:33617 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753184AbbE2OGE (ORCPT ); Fri, 29 May 2015 10:06:04 -0400 Date: Fri, 29 May 2015 15:02:53 +0100 From: John Whitmore To: Austin S Hemmelgarn Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org Subject: Re: RaspberryPi "is this a real kernel?" Message-ID: <20150529140251.GB20974@bamboo.electronicsoup> References: <20150524103235.GA7663@bamboo.electronicsoup> <36886.1432516316@turing-police.cc.vt.edu> <20150525092456.GD7663@bamboo.electronicsoup> <55647AC3.7010803@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55647AC3.7010803@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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