[gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml

[Joshua Saddler (nightmorph)]

nightmorph    09/11/17 05:55:40

  Modified:             hb-install-x86+amd64-bootloader.xml
  Log:
  ripped out VESA/VGA stuff in favor of only uvesafb, as it's in all kernels, not just gentoo-sources. bug 293455

Revision  Changes    Path
1.15                 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.15&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.15&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.14&r2=1.15

Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- hb-install-x86+amd64-bootloader.xml	24 Sep 2009 20:26:50 -0000	1.14
+++ hb-install-x86+amd64-bootloader.xml	17 Nov 2009 05:55:40 -0000	1.15
@@ -4,12 +4,12 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.14 2009/09/24 20:26:50 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.15 2009/11/17 05:55:40 nightmorph Exp $ -->
 
 <sections>
 
-<version>6.4</version>
-<date>2009-09-24</date>
+<version>6.5</version>
+<date>2009-11-16</date>
 
 <section>
 <title>Making your Choice</title>
@@ -49,76 +49,19 @@
 <p>
 <e>If</e> you have configured your kernel with framebuffer support (or you used
 <c>genkernel</c> default kernel configuration), you can activate it by adding a
-<c>vga</c> and/or a <c>video</c> statement to your bootloader configuration
-file.
+a <c>video</c> statement to your bootloader configuration file.
 </p>
 
 <p>
-First of all, you need to know what type of framebuffer device you're using. If
-you use a Gentoo patched kernel tree (such as <c>gentoo-sources</c>) you will
-have had the possibility of selecting <c>uvesafb</c> as the <e>VESA driver</e>.
-If this is the case, you are using <c>uvesafb</c> and <e>do not need</e> to set
-a <c>vga</c> statement. Otherwise you are using the <c>vesafb</c> driver and
-<e>need</e> to set the <c>vga</c> statement.
+First of all, you need to know your framebuffer device. You should have used
+<c>uvesafb</c> as the <e>VESA driver</e>.
 </p>
 
 <p>
-The <c>vga</c> statement controls the resolution and color depth of your
-framebuffer screen for <c>vesafb</c>. As stated in
-<path>/usr/src/linux/Documentation/fb/vesafb.txt</path> (which gets installed
-when you install a kernel source package), you need to pass the VESA number
-corresponding to the requested resolution and color depth to it.
-</p>
-
-<p>
-The following table lists the available resolutions and color depths and
-matches those against the value that you need to pass on to the <c>vga</c>
-statement.
-</p>
-
-<table>
-<tr>
-  <ti></ti>
-  <th>640x480</th>
-  <th>800x600</th>
-  <th>1024x768</th>
-  <th>1280x1024</th>
-</tr>
-<tr>
-  <th>256</th>
-  <ti>0x301</ti>
-  <ti>0x303</ti>
-  <ti>0x305</ti>
-  <ti>0x307</ti>
-</tr>
-<tr>
-  <th>32k</th>
-  <ti>0x310</ti>
-  <ti>0x313</ti>
-  <ti>0x316</ti>
-  <ti>0x319</ti>
-</tr>
-<tr>
-  <th>64k</th>
-  <ti>0x311</ti>
-  <ti>0x314</ti>
-  <ti>0x317</ti>
-  <ti>0x31A</ti>
-</tr>
-<tr>
-  <th>16M</th>
-  <ti>0x312</ti>
-  <ti>0x315</ti>
-  <ti>0x318</ti>
-  <ti>0x31B</ti>
-</tr>
-</table>
-
-<p>
 The <c>video</c> statement controls framebuffer display options. It needs to be
 given the framebuffer driver followed by the control statements you wish to
 enable. All variables are listed in
-<path>/usr/src/linux/Documentation/fb/vesafb.txt</path>. The most-used options
+<path>/usr/src/linux/Documentation/fb/uvesafb.txt</path>. The most-used options
 are:
 </p>
 
@@ -148,7 +91,6 @@
 <tr>
   <ti><c>mode</c></ti>
   <ti>
-    (<c>uvesafb</c> only)<br/>
     Set up the resolution, color depth and refresh rate. For instance,
     <c>1024x768-32@85</c> for a resolution of 1024x768, 32 bit color depth and a
     refresh rate of 85 Hz.
@@ -157,8 +99,7 @@
 </table>
 
 <p>
-The result of those two statements could be something like <c>vga=0x318
-video=vesafb:mtrr:3,ywrap</c> or
+The result could be something like
 <c>video=uvesafb:mtrr:3,ywrap,1024x768-32@85</c>. Write this setting down; you
 will need it shortly.
 </p>
@@ -185,7 +126,7 @@
 The most critical part of understanding GRUB is getting comfortable with how
 GRUB refers to hard drives and partitions. Your Linux partition
 <path>/dev/sda1</path> will most likely be called <path>(hd0,0)</path> under
-GRUB.  Notice the parentheses around the <path>hd0,0</path> - they are
+GRUB. Notice the parentheses around the <path>hd0,0</path> - they are
 required.
 </p>
 
@@ -338,11 +279,11 @@
 </p>
 
 <p>
-If you need to pass any additional options to the kernel, simply add
-them to the end of the kernel command. We're already passing one option
+If you need to pass any additional options to the kernel, simply add them to the
+end of the kernel command. We're already passing one option
 (<c>root=/dev/sda3</c> or <c>real_root=/dev/sda3</c>), but you can pass others
-as well, such as the <c>video</c> and/or <c>vga</c> statements for framebuffer
-as we discussed previously.
+as well, such as the <c>video</c>> statement for framebuffer as we discussed
+previously.
 </p>
 
 <p>
@@ -605,7 +546,7 @@
   label=gentoo
   read-only
   root=/dev/sda3
-  <i>append="video=vesafb:mtrr,ywrap,1024x768-32@85"</i>
+  <i>append="video=uvesafb:mtrr,ywrap,1024x768-32@85"</i>
 </pre>
 
 <p>