swift 05/06/10 18:37:43
Modified: xml/htdocs/doc/en/handbook/2005.0
hb-install-amd64-bootloader.xml
Log:
#95494 - AMD64 does not know vesafb-tng; patch from Jonathan Smith (smithj)
Revision Changes Path
1.8 +10 -25
xml/htdocs/doc/en/handbook/2005.0/hb-install-amd64-bootloader.xml
file :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.0/hb-install-amd64-bootloader.xml?rev=1.8&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.0/hb-install-amd64-bootloader.xml?rev=1.8&content-type=text/plain&cvsroot=gentoo
diff :
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/2005.0/hb-install-amd64-bootloader.xml.diff?r1=1.7&r2=1.8&cvsroot=gentoo
Index: hb-install-amd64-bootloader.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.0/hb-install-amd64-bootloader.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- hb-install-amd64-bootloader.xml 16 Apr 2005 20:37:42 -0000 1.7
+++ hb-install-amd64-bootloader.xml 10 Jun 2005 18:37:43 -0000 1.8
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
-<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.0/hb-install-amd64-bootloader.xml,v
1.7 2005/04/16 20:37:42 swift Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2005.0/hb-install-amd64-bootloader.xml,v
1.8 2005/06/10 18:37:43 swift Exp $ -->
<sections>
-<version>4.5</version>
-<date>2005-04-16</date>
+<version>4.6</version>
+<date>2005-06-10</date>
<section>
<title>Making your Choice</title>
@@ -30,7 +30,10 @@
<title>Optional: Framebuffer</title>
<body>
-<!-- Verbatim copy from x86 bootloader framebuffer explanation -->
+<!--
+Verbatim copy from x86 bootloader framebuffer explanation, minus the section on
+vesafb-tng
+-->
<p>
<e>If</e> you have configured your kernel with framebuffer support (or you used
@@ -40,18 +43,9 @@
</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>vesafb-tng</c> as the <e>VESA driver
-type</e> (which is default for these kernel sources). If this is the case, you
-are using <c>vesafb-tng</c> and do not need to set a <c>vga</c> statement.
-Otherwise you are using the <c>vesafb</c> driver and need to set the <c>vga</c>
-statement.
-</p>
-
-<p>
-The <c>vga</c> statement controls the resolution and color depth of your
-framebuffer screen for <c>vesafb</c>. As stated in
+64-bit systems must use the the <c>vesafb</c> driver, and so will need to set
+the <c>vga</c> statement. 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.
@@ -126,15 +120,6 @@
Setup MTRR registers
</ti>
</tr>
-<tr>
- <ti>mode</ti>
- <ti>
- (<c>vesafb-tng</c> only)<br/>
- Set up the resolution, color depth and refresh rate. For instance,
- <c>[EMAIL PROTECTED]</c> for a resolution of 1024x768, 32 bit color depth
and a
- refresh rate of 85 Hz.
- </ti>
-</tr>
</table>
<p>
--
[email protected] mailing list
