summaryrefslogtreecommitdiff
path: root/en/boot-installer/parameters.xml
diff options
context:
space:
mode:
Diffstat (limited to 'en/boot-installer/parameters.xml')
-rw-r--r--en/boot-installer/parameters.xml28
1 files changed, 2 insertions, 26 deletions
diff --git a/en/boot-installer/parameters.xml b/en/boot-installer/parameters.xml
index bbc2837c1..91d981406 100644
--- a/en/boot-installer/parameters.xml
+++ b/en/boot-installer/parameters.xml
@@ -66,16 +66,6 @@ terminal type, which is very close to <literal>vt102</literal>.
</para>
-<para arch="sparc">
-
-For &arch-title; the serial devices are <filename>ttya</filename> or
-<filename>ttyb</filename>.
-Alternatively, set the <envar>input-device</envar> and
-<envar>output-device</envar> OpenPROM variables to
-<filename>ttya</filename>.
-
-</para>
-
</sect2>
<sect2 id="installer-args"><title>&debian; Installer Parameters</title>
@@ -248,21 +238,7 @@ you can disable the feature using the parameter
Problem symptoms are error messages about bterm or bogl, a blank screen,
or a freeze within a few minutes after starting the install.
-</para><para arch="hppa">
-
-Such problems have been reported on hppa.
-
-</para><note arch="sparc"><para>
-
-Because of display problems on some systems, framebuffer support is
-<emphasis>disabled by default</emphasis> for &arch-title;. This can result
-in ugly display on systems that do properly support the framebuffer, like
-those with ATI graphical cards.
-If you see display problems in the installer, you can try booting with
-parameter <userinput>debian-installer/framebuffer=true</userinput> or
-<userinput>fb=true</userinput> for short.
-
-</para></note></listitem>
+</para></listitem>
</varlistentry>
<varlistentry arch="not-s390">
@@ -433,7 +409,7 @@ disable that authentication.
</para></listitem>
</varlistentry>
-<varlistentry arch="mips;mipsel;mips64el">
+<varlistentry arch="mipsel;mips64el">
<term>ramdisk_size</term>
<listitem><para>