From: Andy Davidson <andy@nosignal.org>
To: Sebastian Tennant <sebyte@smolny.plus.com>
Cc: linux-config@vger.kernel.org
Subject: Re: How exactly does `make menuconfig' work?
Date: Tue, 07 Mar 2006 16:44:21 +0000 [thread overview]
Message-ID: <440DB865.4010907@nosignal.org> (raw)
In-Reply-To: <du780p$ohq$1@sea.gmane.org>
network_gauner wrote:
> Sebastian Tennant wrote:
>> ... when I did this, there was simply no vesafb graphics option, which
>> I need. In fact, the only way I can gain access to this option is to
>> base my new config on my existing one in /boot (which already includes
>> it) by expliciting loading it as an `alternative'.
>> Why is this?
> I don't know, but I think it should be caused by some option turned off.
> For example if you turn off ISA support, all options which are dependent
> on ISA disappear.
Assuming you want to turn CONFIG_VESA_FB on (?) drivers/video/Kconfig
holds the key here.
config FB_VESA
bool "VESA VGA graphics support"
depends on (FB = y) && X86
select FB_CFB_FILLRECT
select FB_CFB_COPYAREA
select FB_CFB_IMAGEBLIT
So you need 'Support for frame buffer devices' turned on, and X86 to be
set to 'y'. Check your .config file that make menuconfig saves for both
of these. I'm wondering whether you have, say, 'CONFIG_X86_32=y' but
not 'CONFIG_X86=y'.
Why turn all of your .config defaults to 'no' anyway ? This is the
underlying cause of your trouble.
>> I had been lead to believe that running:
>> $ make menuconfig
>> ... in a freshly unpacked kernel source automatically bases the new
>> config on your existing config. I thought this was the case until I
>> came to the missing vesafb option.
Perhaps you may find that your distribution has kindly turned on the
feature which stores the config file in /proc - in which case :
zcat /proc/config.gz > .config
will restore the config you used last time. They also may store the
.config in /boot (debian does - e.g. config-2.6.8-2-686,
config-2.6.15-rc3-mm1)
cheers
-a
prev parent reply other threads:[~2006-03-07 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-29 2:09 How exactly does `make menuconfig' work? Sebastian Tennant
2006-03-02 16:55 ` network_gauner
2006-03-07 16:44 ` Andy Davidson [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=440DB865.4010907@nosignal.org \
--to=andy@nosignal.org \
--cc=linux-config@vger.kernel.org \
--cc=sebyte@smolny.plus.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).