From: Albert Hopkins <marduk@letterboxes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Colors corrupted in X after returning from text console
Date: Wed, 21 Oct 2009 22:59:12 -0400 [thread overview]
Message-ID: <1256180352.2082695.3.camel@centar> (raw)
In-Reply-To: <20091022021304.GA4806@waltdnes.org>
On Wed, 2009-10-21 at 22:13 -0400, waltdnes@waltdnes.org wrote:
> On Wed, Oct 21, 2009 at 06:55:50PM -0400, Albert Hopkins wrote
>
> > You may not have do that. All 3 of my systems with Intel graphics run
> > KMS with X with no xorg.conf at all. But since you're running stable
> > YMMV.
>
> Fortunately I've set up lilo to boot up from separate "Production" and
> "Experimental" kernels. This allows me to reboot and flee to a sane
> config if things go wrong. It appears that nothing is simple. The Intel
> driver works great in X, without an xorg.conf. However, it insists on
> running framebuffer in text console mode. I *CANNOT* turn off framebuffer.
> Passing parameters to lilo via...
>
> append = "noexec=on noexec32=on nofb"
>
> doesn't help. In "make menuconfig" graphics/console, I see
>
> -*- Framebuffer Console support
>
> there is no box to uncheck. Could it be related to my /etc/make.conf
>
> VIDEO_CARDS="intel vga"
>
> Would changing that to VIDEO_CARDS="intel" (and re-emerging xorg) help?
>
KMS drivers and framebuffer console drivers are different and AFAIK
mutually exclusive. The boot parameter to disable KMS would be, e.g.,
i915.modeset=0
next prev parent reply other threads:[~2009-10-22 2:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 0:55 [gentoo-user] Colors corrupted in X after returning from text console waltdnes
2009-10-21 1:30 ` Albert Hopkins
2009-10-21 4:29 ` waltdnes
2009-10-21 10:16 ` Albert Hopkins
2009-10-21 22:01 ` waltdnes
2009-10-21 22:55 ` Albert Hopkins
2009-10-22 1:11 ` [gentoo-user] " walt
2009-10-22 1:51 ` Albert Hopkins
2009-10-22 2:13 ` [gentoo-user] " waltdnes
2009-10-22 2:59 ` Albert Hopkins [this message]
2009-10-23 4:46 ` waltdnes
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=1256180352.2082695.3.camel@centar \
--to=marduk@letterboxes.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