public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Anyone successfully booted a custom kernel on Fedora 17?
Date: Wed, 30 May 2012 20:15:35 -0700	[thread overview]
Message-ID: <4FC6E257.4070608@candelatech.com> (raw)
In-Reply-To: <4FC6B85C.20201@candelatech.com>

On 05/30/2012 05:16 PM, Ben Greear wrote:
> This is probably a Fedora 17 issue..but hoping someone will have mercy on me :)

Must be something to do with my kernel config or how I generate
the initrd with mkinitrd:  I tried vanilla 3.3.7 compiled and
installed with:

Copy Fedora kernel config to ./config
make -j8 bzImage modules
make modules_install
make install

(and fixed up grub2)
and it booted just fine.

Thanks,
Ben


>
> I upgraded a system to Fedora 17 (from 16), and now none of my
> custom-built kernels are booting. I'm compiling the kernels on
> another machine, running the 'make modules install', tarring everything
> up, and then running 'mkinitrd ...' after un-tarring on the F17 machine.
>
> The F17 machine hangs right before it should begin starting services.
>
> I tried 3.3.7+, 3.0.32+, etc. The kernels that come with F17 boot fine.
>
> If anyone has any ideas, please let me know.
>
> Thanks,
> Ben
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2012-05-31  3:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31  0:16 Anyone successfully booted a custom kernel on Fedora 17? Ben Greear
2012-05-31  3:15 ` Ben Greear [this message]
2012-06-01  0:28   ` valdis.kletnieks
2012-06-01  0:45     ` Ben Greear
2012-06-01  9:49       `  
2012-06-01 21:49         ` valdis.kletnieks

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=4FC6E257.4070608@candelatech.com \
    --to=greearb@candelatech.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