From: Albert Hopkins <marduk@letterboxes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: about boot with framebuffer
Date: Mon, 04 Jul 2011 15:35:22 -0400 [thread overview]
Message-ID: <1309808123.3414.9.camel@localhost.localdomain> (raw)
In-Reply-To: <87liwd29y6.fsf@newsguy.com>
On Monday, July 4 at 13:10 (-0500), Harry Putnam said:
> Are you saying it does not require `xorg-x11'.
>
> Step 2) says in large type:
> `2. Installing Xorg'
>
> Then a big note in a green box later on says:
>
> ,----
> | Note: You could install the xorg-x11 metapackage instead of the more
> | lightweight xorg-server. Functionally, xorg-x11 and xorg-server are
> | the same. However, xorg-x11 brings in many more packages that you
> | probably don't need, such as a huge assortment of fonts in many
> | different languages. They're not necessary for a working desktop.
> `----
>
> So I'm a little confused.
Perhaps pointing to the xorg documentation was a mistake. I only
pointed there because it had instructions on setting up KMS.
KMS (kernel mode setting) does not require X. It gives the kernel the
ability to set the modes of your graphics cards, more efficiently and
usually beyond the capabilities of what the *vesa drivers can do.
Perhaps a better, non X-centered explanation of what KMS is can be found
here [1].
Regardless, KMS is the newer, better, what-all-the-cool-kids-are-doinger
way to what we've traditionally called "framebuffer console". It also
helps with X, especially switching between console and Xorg (faster and
more seamless). It also gives you some xrandr-like abilities for the
console.
E.g. my laptop does native 1366x768 but does not support that vesa mode
(it's not in the VESA standard afaik). But KMS can set that mode without
me even having to specify it.[2]
Anyway some proprietary X drivers (I've heard) don't support KMS (some
still don't even support xrandr), but if you are not running Xorg then
that may not be applicable to you anyway.
[1]
http://kernelnewbies.org/Linux_2_6_29#head-e1bab8dc862e3b477cc38d87e8ddc779a66509d1
[2] http://ompldr.org/vOWN0cg/kms.png
next prev parent reply other threads:[~2011-07-04 19:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 21:39 [gentoo-user] about boot with framebuffer Harry Putnam
2011-07-03 22:07 ` Albert Hopkins
2011-07-04 3:07 ` [gentoo-user] " Harry Putnam
2011-07-04 3:33 ` covici
2011-07-04 18:12 ` Harry Putnam
2011-07-04 18:46 ` covici
2011-07-04 4:18 ` Albert Hopkins
2011-07-04 18:10 ` Harry Putnam
2011-07-04 18:20 ` Mark Knecht
2011-07-04 20:40 ` Alan McKinnon
2011-07-04 20:47 ` Mark Knecht
2011-07-04 20:57 ` Alan McKinnon
2011-07-04 21:15 ` Mark Knecht
2011-07-04 21:34 ` Alan McKinnon
2011-07-04 22:25 ` Neil Bothwick
2011-07-04 23:45 ` Mark Knecht
2011-07-05 0:52 ` Joshua Murphy
2011-07-04 19:07 ` Nikos Chantziaras
2011-07-05 0:48 ` Harry Putnam
2011-07-05 1:41 ` Nikos Chantziaras
2011-07-04 19:35 ` Albert Hopkins [this message]
2011-07-05 15:27 ` covici
2011-07-05 22:50 ` Albert Hopkins
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=1309808123.3414.9.camel@localhost.localdomain \
--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