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.thiba...@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 - sect2titleBoard Devices/title + sect2titleBoard 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 -userinputfb=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. userinputqemu +-curses/userinput). To get them to work framebuffer support must be disabled +by using the userinputvga=0 fb=false/userinput boot parameter. This will +however reduce the number of available languages. /para /sect2
Bug#577461: installation-guide: Updates to textmode activation
Ah, sorry, I thought that what follows would have been independent from this bugreport but actually it's not. The help menu is in textmode and can be used to type boot parameters etc., so let's document that too. Samuel Index: en/boot-installer/accessibility.xml === --- en/boot-installer/accessibility.xml (révision 62894) +++ en/boot-installer/accessibility.xml (copie de travail) @@ -81,13 +81,24 @@ /para /sect2 - sect2titleBoard Devices/title + sect2titleBoard 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 -userinputfb=false/userinput boot parameter. This will however reduce +machine and that read text directly from the video memory. Also, some +virtualization tools have a textual interface (e.g. userinputqemu +-curses/userinput). + +/parapara + +For such case, a textual version of the bootloader can be activated by typing +userinputh/userinput enterkey; . This permits to easily append boot +parameters at will. + +/parapara + +The purely textual version of the installer must also be activated by using the +userinputvga=0 fb=false/userinput boot parameter. This will however reduce the number of available languages. /para
Bug#577461: installation-guide: Updates to textmode activation
tag 577461 pending thanks On Sunday 11 April 2010, Samuel Thibault wrote: Samuel Thibault, le Sun 11 Apr 2010 22:58:39 +0200, a écrit : Squeeze apparently needs vga=0 in addition to fb=false, else the kernel switches to graphical mode very early. That being said, it could actually been considered as a regression, since fb=false used to be enough. It's not a regression but a necessary change since we now use VESA framebuffer by default for all x86 installs in order to have a better display resolution. The fact that now two parameters are needed is the simple consequence of the fact that one is a kernel parameter (which *must* be passed at boot time) and one is a D-I parameter and the fact that the one does not automatically imply the other. I've applied a modified version of both your patches. I've left out the virtualization bits as I don't think they belong in a section about accessibility and disabling framebuffer in general is already also documented in the general boot parameters section. Cheers, FJP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577461: installation-guide: Updates to textmode activation
On Monday 12 April 2010, Frans Pop wrote: The fact that now two parameters are needed is the simple consequence of the fact that one is a kernel parameter (which *must* be passed at boot time) and one is a D-I parameter and the fact that the one does not automatically imply the other. Actually, *maybe* we could remove the need for fb=false for x86 if we dropped support for the vga16 framebuffer driver. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
