[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#577461: installation-guide: Updates to textmode activation



Package: installation-guide
Version: 20090901
Severity: normal
Tags: patch

Hello,

Squeeze apparently needs vga=0 in addition to fb=false, else the kernel
switches to graphical mode very early. This needs to be documented in
the accessibility section, here is a patch, which also mentions how
useful it can be for qemu.

Samuel

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.33 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
Samuel Thibault <samuel.thibault@fnac.net>
Pour un p�re, autant mourir que de faire plein de calculs et pas s'occuper
de son fils
 -+- y sur #ens-mim - sombres histoires de zombies -+-
Index: en/boot-installer/accessibility.xml
===================================================================
--- en/boot-installer/accessibility.xml	(révision 60852)
+++ en/boot-installer/accessibility.xml	(copie de travail)
@@ -81,14 +81,15 @@
 </para>
   </sect2>
 
-  <sect2><title>Board Devices</title>
+  <sect2><title>Board Devices and virtualization</title>
 <para>
 
 Some accessibility devices are actual boards that are plugged inside the
-machine and that read text directly from the video memory. To get them
-to work framebuffer support must be disabled by using the
-<userinput>fb=false</userinput> boot parameter. This will however reduce
-the number of available languages.
+machine and that read text directly from the video memory. Also, some
+virtualization tools have a textual interface (e.g. <userinput>qemu
+-curses</userinput>). To get them to work framebuffer support must be disabled
+by using the <userinput>vga=0 fb=false</userinput> boot parameter. This will
+however reduce the number of available languages.
 
 </para>
   </sect2>

Reply to: