From: Etaoin Shrdlu <shrdlu@unlimitedmail.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel setting for frame buffer (2.6.23-r5)
Date: Wed, 9 Jan 2008 20:43:51 +0100 [thread overview]
Message-ID: <200801092043.51305.shrdlu@unlimitedmail.org> (raw)
In-Reply-To: <87odbu982e.fsf@newsguy.com>
On Wednesday 9 January 2008, reader@newsguy.com wrote:
> For a good while now I've had a setting like this in grub.conf:
>
> (wrapped for mail)
> kernel /kernel-2.6.23-r5 root=/dev/hda5 \
> vga=0x31A video=vesafb:mtrr,ywrap
>
> I'm not sure any more how much of that is necessary.
FWIW, I have only the vga= part (more exactly, I have vga=791, with the
argument in decimal. Yours would be vga=794, but the base is just a
matter of habit).
> I have it there to allow console mode to have much larger resolution
> than default (The appearance is much smaller text)
>
> I think this setting in kernel config is the one needed for that:
> CONFIG_FB_VESA=y
Correct.
>
> But I'm trying to build a pared down kernel a console only setup.
> Going thru the kernel settings in menuconfig... I'm not finding the
> one that creates that `CONFIG_FB_VESA=y' element.
During make menuconfig, hit / and enter the text you want to search for
(in this case, obviously, it's FB_VESA), and hit enter. It should show
you where that particular option is found in the configration. In my
case (vanilla 2.6.23.9), it shows
Symbol: FB_VESA [=y]
Prompt: VESA VGA graphics support
Defined at drivers/video/Kconfig:595
Depends on: HAS_IOMEM && FB=y && X86
Location:
-> Device Drivers
-> Graphics support
-> Support for frame buffer devices (FB [=y])
Selects: FB_CFB_FILLRECT && FB_CFB_COPYAREA && FB_CFB_IMAGEBLIT &&
VIDEO_SELECT
Notice the "Location:" bit.
> I've gone back and forth through the setting under:
> Device drivers/Graphics-support .. checking Support for FrameBuffer
> devices (both as module and builtin in different saves).
It should be there. Which kernel sources and release are you using?
Also note, in the above output, that VESA_FB depends on HAS_IOMEM and FB.
If you don't select either, the VESA_FB option will not be shown.
Since you obviously have FB set (otherwise you would not see the
Userspace VESA option), you can check the status of HAS_IOMEM. With the
same / trick described above, search for HAS_IOMEM. It does not give you
a lot of information this time, but at least it should tell you whether
the option is enabled. In my case, it just says
Symbol: HAS_IOMEM [=y]
In case you don't have it active (very strange, since it should be part
of the default configuration and not modifiable), try a "make mrproper"
and start over with make menuconfig, which should start with the default
config this time.
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-09 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 18:18 [gentoo-user] Kernel setting for frame buffer (2.6.23-r5) reader
2008-01-09 19:43 ` Etaoin Shrdlu [this message]
2008-01-09 19:50 ` Etaoin Shrdlu
2008-01-09 20:33 ` [gentoo-user] " reader
2008-01-09 20:49 ` reader
2008-01-09 21:17 ` Etaoin Shrdlu
2008-01-09 22:57 ` Renat Golubchyk
2008-01-10 9:18 ` Etaoin Shrdlu
2008-01-11 10:16 ` Roy Wright
2008-01-09 20:50 ` Tony Stohne
2008-01-09 20:59 ` Tony Stohne
2008-01-09 21:32 ` Alan McKinnon
2008-01-09 21:13 ` Etaoin Shrdlu
2008-01-09 21:30 ` Etaoin Shrdlu
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=200801092043.51305.shrdlu@unlimitedmail.org \
--to=shrdlu@unlimitedmail.org \
--cc=gentoo-user@lists.gentoo.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