From: James Simmons <jsimmons@infradead.org>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
Sylvain Meyer <sylvain.meyer@worldonline.fr>,
linux-fbdev@vger.kernel.org
Subject: Re: 2.6.33-rc3 -- Intel 945GME (inteldrmfb) -- Two Tux images displayed are side by side (should only show one).
Date: Wed, 6 Jan 2010 17:48:18 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.00.1001061747250.5372@casper.infradead.org> (raw)
In-Reply-To: <a44ae5cd1001060942p7672768yec3b1f5ea2426682@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 712 bytes --]
> On Wed, Jan 6, 2010 at 12:37 PM, James Simmons <jsimmons@infradead.org> wrote:
> >
> >> For a long time I have gotten two pictures of Tux showing up when I
> >> include the Tux display option in my custom kernel builds. I don't
> >> know how many kernel revisions ago it was when I started noticing
> >> this. It seems like it might have been early in the 2.6 series
> >> kernels.
> >>
> [...]
> >> # Frame buffer hardware drivers
> >> #
> >> CONFIG_FB_VESA=y
> >> CONFIG_FB_EFI=y
> >
> > Try disabling these two above options.
>
> Well, that means that I don't get Tux at all. The point is that only
> one copy should be displayed.
I thought you had KMS enabled?? That provides a fbdev emulation layer.
next prev parent reply other threads:[~2010-01-06 17:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 17:16 Miles Lane
2010-01-06 17:37 ` James Simmons
2010-01-06 17:42 ` Miles Lane
2010-01-06 17:48 ` James Simmons [this message]
2010-01-06 18:08 ` Miles Lane
2010-01-06 17:59 ` Bruno Prémont
2010-01-06 18:06 ` Miles Lane
2010-01-06 18:07 ` Peter Zijlstra
2010-01-06 18:10 ` Miles Lane
2010-01-06 18:25 ` Peter Zijlstra
2010-01-06 18:35 ` Miles Lane
2010-01-09 10:34 ` Pavel Machek
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=alpine.LFD.2.00.1001061747250.5372@casper.infradead.org \
--to=jsimmons@infradead.org \
--cc=airlied@linux.ie \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=sylvain.meyer@worldonline.fr \
/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
all inboxes | Powered by JetHome®