summaryrefslogtreecommitdiff
path: root/nl/boot-installer/trouble.xml
diff options
context:
space:
mode:
Diffstat (limited to 'nl/boot-installer/trouble.xml')
-rw-r--r--nl/boot-installer/trouble.xml65
1 files changed, 60 insertions, 5 deletions
diff --git a/nl/boot-installer/trouble.xml b/nl/boot-installer/trouble.xml
index 3a715fc89..e4efda20d 100644
--- a/nl/boot-installer/trouble.xml
+++ b/nl/boot-installer/trouble.xml
@@ -1,5 +1,5 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 43514 untranslated -->
+<!-- original version: 43694 untranslated -->
<sect1 id="boot-troubleshooting">
<title>Troubleshooting the Installation Process</title>
@@ -368,7 +368,7 @@ installer.
</sect3>
<sect3>
- <title>System Freeze while Loading the USB Modules</title>
+ <title>System Freeze while Loading USB Modules</title>
<para>
The kernel normally tries to install USB modules and the USB keyboard driver
@@ -382,6 +382,58 @@ at the boot prompt, which will prevent the modules from being loaded.
</sect3>
</sect2>
+ <sect2 arch="sparc" id="sparc-boot-problems">
+ <title>Common &arch-title; Installation Problems</title>
+<para>
+
+There are some common installation problems that are worth mentioning.
+
+</para>
+ <sect3>
+ <title>Misdirected video output</title>
+<para>
+
+It is fairly common for &arch-title; to have two video cards in one machine,
+for example an ATI card and a Sun Creator 3D. In some cases, this may result
+in the video output getting misdirected soon after the system boots. In
+typical cases, the display will only show:
+
+<informalexample><screen>
+Remapping the kernel... done
+Booting Linux...
+</screen></informalexample>
+
+To work around this, you can either pull out one of the video cards, or
+disable the one not used during the OpenProm boot phase using a kernel
+parameter. For example, to disable an ATI card, you should boot the
+installer with <userinput>video=atyfb:off</userinput>.
+
+</para><para>
+
+Note that you may also have to manually add this parameter to the silo
+configuration (edit <filename>/target/etc/silo.conf</filename> before
+rebooting) and, if you installed X11, modify the video driver in
+<filename>/etc/X11/xorg.conf</filename>.
+
+</para>
+ </sect3>
+
+ <sect3>
+ <title>Failure to Boot or Install from CD-ROM</title>
+<para>
+
+Some Sparc systems are notoriously difficult to boot from CD-ROM and
+even if they do boot, there may be inexplicable failures during the
+installation. Most problems have been reported with SunBlade systems.
+
+</para><para>
+
+We recommend to install such systems by netbooting the installer.
+
+</para>
+ </sect3>
+ </sect2>
+
<sect2 id="kernel-msgs">
<title>Interpreting the Kernel Startup Messages</title>
@@ -450,9 +502,12 @@ you use an E-Mail address that you do not mind being made public.
</para><para>
If you have a working Debian system, the easiest way to send an installation
-report is to install the installation-report and reportbug packages
-(<command>apt-get install installation-report reportbug</command>) and run
-the command <command>reportbug installation-report</command>.
+report is to install the <classname>installation-report</classname> and
+<classname>reportbug</classname> packages
+(<command>aptitude install installation-report reportbug</command>),
+configure <classname>reportbug</classname> as explained in
+<xref linkend="mail-outgoing"/>, and run the command <command>reportbug
+installation-report</command>.
</para><para>