summaryrefslogtreecommitdiff
path: root/en/boot-installer
diff options
context:
space:
mode:
Diffstat (limited to 'en/boot-installer')
-rw-r--r--en/boot-installer/parameters.xml22
1 files changed, 16 insertions, 6 deletions
diff --git a/en/boot-installer/parameters.xml b/en/boot-installer/parameters.xml
index 5d3ea47a0..0a1dcdf00 100644
--- a/en/boot-installer/parameters.xml
+++ b/en/boot-installer/parameters.xml
@@ -27,7 +27,10 @@ common gotchas are included below in
</para>
-<para arch="linux-any" condition="supports-serial-console">
+ <sect2 id="boot-console" arch="linux-any" condition="supports-serial-console">
+ <title>Boot console</title>
+
+<para>
If you are booting with a serial console, generally the kernel will
autodetect this.
@@ -38,8 +41,15 @@ to pass the
argument to the kernel, where <replaceable>device</replaceable> is
your serial device, which is usually something like
<filename>ttyS0</filename>.
-<footnote>
-<para>
+
+</para><para>
+
+You may need to specify parameters for the serial port, such as speed and
+parity, for instance <userinput>console=ttyS0,9600n8</userinput> ; other typical
+speeds may be 57600 or 115200.
+
+</para><para>
+
In order to ensure the terminal type used by the installer matches your
terminal emulator, the parameter
<userinput>TERM=<replaceable>type</replaceable></userinput> can be added.
@@ -51,11 +61,10 @@ virtualization tool which does not provide conversion into such terminals types
itself, e.g. QEMU/KVM, you can start it inside a <command>screen</command>
session. That will indeed perform translation into the <literal>screen</literal>
terminal type, which is very close to <literal>vt102</literal>.
-</para>
-</footnote>
+</para>
-</para><para arch="sparc">
+<para arch="sparc">
For &arch-title; the serial devices are <filename>ttya</filename> or
<filename>ttyb</filename>.
@@ -65,6 +74,7 @@ Alternatively, set the <envar>input-device</envar> and
</para>
+ </sect2>
<sect2 id="installer-args"><title>&debian; Installer Parameters</title>
<para>