All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel Panic .....
Date: Wed, 20 Dec 2006 16:43:04 +0100	[thread overview]
Message-ID: <20061220154303.GA24288@aon.at> (raw)
In-Reply-To: <Pine.LNX.4.64.0612192344000.31862@smtcorms05.samuelmanutech.com>

On Tue, Dec 19, 2006 at 11:47:54PM -0500, Robin Mordasiewicz wrote:
>On Tue, 19 Dec 2006, Joe Pruett wrote:
>> On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:
>>> On Tue, 19 Dec 2006, Robin Mordasiewicz wrote:
>>>
>>>> I am trying to boot the image as an initrd filesystem over pxe, but I see
>>>> an error
>>>> 'Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers'
>>>>
>>>> in my pxelinux.cfg/default
>>>>
>>>> label test
>>>>   kernel linux-kernel-2.6.19.1-i386
>>>>   append ramdisk_blocksize=4096 initrd=rootfs.i386.ext2 root=/dev/ram0 ramdisk_size=524288
>>>>
>>>> Is there anything I am required to change to make this kernel and image
>>>> work over booting from pxe ?
>>>
>>> I needed to build some RAM disk drivers into the kernel.
>>
>> how exactly did you do that?  that is where i have finally gotten after
>> making that kernel-patches directory (as you also just posted) and fixing
>> the problem that grub no longer has a -19 version at debian.org (-20 seems
>> to be working).  i made an iso image and ran into the same kernel panic
>> because it seems to want a cpio image.  i have just rebuilt using the
>> linux26.config file instead of busybox.config and will be booting in a few
>> minutes to see how that goes...
>
>Not sure if I am following you. I think you may be getting the kernel 
>config and the busybox config confused. The documentation for customizing 
>busybox does not mention modifying the kernel, but what I did to customize 
>the kernel is something like the following.
>
>cd build_i386/linux-2.6.19.1
>cp .config .config.original
>make mrproper
>make menuconfig
>(set the kernel options you require)
>cd ../../
>make

there is a make linux26-menuconfig target for that (for i386 with
the generic x86 target support option turned on, at least).

  reply	other threads:[~2006-12-20 15:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 18:05 [Buildroot] Kernel Panic Robin Mordasiewicz
2006-12-20  4:37 ` Robin Mordasiewicz
2006-12-20  4:42   ` Joe Pruett
2006-12-20  4:45     ` Joe Pruett
2006-12-20  4:47     ` Robin Mordasiewicz
2006-12-20 15:43       ` Bernhard Fischer [this message]
2006-12-21  5:19         ` Joe Pruett
2006-12-21  9:04           ` Bernhard Fischer
2006-12-21 15:26             ` Joe Pruett
     [not found] <1F383CDA589639468828C7E2B75EDE9D096BB9DE@POCITMSEXMB02.LntUniverse.com>
2011-12-06  9:13 ` [Buildroot] Kernel panic! Peter Korsgaard
2011-12-06  9:50   ` Mahanteshwari Hiremath
2011-12-06 10:49   ` Mahanteshwari Hiremath

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=20061220154303.GA24288@aon.at \
    --to=rep.nop@aon.at \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.