From: Ben Greear <greearb@candelatech.com>
To: valdis.kletnieks@vt.edu
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Anyone successfully booted a custom kernel on Fedora 17?
Date: Thu, 31 May 2012 17:45:39 -0700 [thread overview]
Message-ID: <4FC810B3.5040208@candelatech.com> (raw)
In-Reply-To: <23353.1338510488@turing-police.cc.vt.edu>
On 05/31/2012 05:28 PM, valdis.kletnieks@vt.edu wrote:
> On Wed, 30 May 2012 20:15:35 -0700, Ben Greear said:
>> 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:
>
> For what it's worth, over on the Rawhide side of the fence, dracut-018-74
> builds bad initramfs images for me,while dracut-081-53 works. Not sure
> what release is in the F17 updates repository. I'm going to file a bug report
> with Fedora soon as I figure out what -74 is doing wrong.
At least my problem appears to be some missing feature in the kernel, probably
one of the 'fooFS' things releated to ramdisk and/or early startup.
I enabled several things I found in the F17 .config file that were not in my
config file, and now my kernel boots, at least when I
build and install it on the F17 machine.
I'm going to try building on F13 and just (re)making the initrd on
F17 like I have been for all other distributions, but that will be
a day or two..got a release to shove out the door first!
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-06-01 0:45 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
2012-06-01 0:28 ` valdis.kletnieks
2012-06-01 0:45 ` Ben Greear [this message]
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=4FC810B3.5040208@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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