doc-sle/xml/aarch64_inst_problem.xml at dc97cc15b2a1884aed31e8179ab1e94909a8d0d2 · SUSE/doc-sle · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
<?xml version="1.0"?>
<!DOCTYPE sect1
[
  <!ENTITY % entities SYSTEM "generic-entities.ent">
    %entities;
]>
<sect1 xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="sec-bootproblem-aarch64">
 <title>Dealing with Boot and Installation Problems</title>

 <info>
  <meta name="description">Configure your system to log system messages at boot time and troubleshoot boot and installation issues</meta>
  <dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">
   <dm:bugtracker/>
   <dm:translation>yes</dm:translation>
  </dm:docmanager>
 </info>

 <para>
  Prior to delivery, &productnamereg; is subjected to an extensive test
  program. Despite this, problems occasionally occur during boot or
  installation.
 </para>

 <sect2 xml:id="sec-bootproblem-aarch64-boot">
  <title>Problems Booting</title>
  <para>
   Boot problems may prevent the &yast; installer from starting on your system.
   Another symptom is when your system does not boot after the installation has
   been completed.
  </para>
  <variablelist>
   <varlistentry>
    <term>Installed System Boots, Not Media</term>
    <listitem>
     <para>
      Change your computer's firmware so that the boot sequence is correct. To
      do this, consult the manual for your hardware.
     </para>
    </listitem>
   </varlistentry>
   <varlistentry>
    <term>The Computer Hangs</term>
    <listitem>
     <para>
      Change the console on your computer so that the kernel outputs are
      visible. Be sure to check the last outputs. This is normally done by
      pressing
      <keycombo><keycap function="control"/><keycap function="alt"/><keycap>F10</keycap></keycombo>.
      If you cannot resolve the problem, consult the &productname; support
      staff. To log all system messages at boot time, use a serial connection
      as described in <xref linkend="sec-prep-boot"/>.
     </para>
    </listitem>
   </varlistentry>
<!-- FIXME cwickert 2016-07-22: Are boot disks still a thing? -->
   <varlistentry>
    <term>Boot Disk</term>
    <listitem>
     <para>
      The boot disk is a useful interim solution if you have difficulties
      setting the other configurations or if you want to postpone the decision
      regarding the final boot mechanism. For more details on
      creating boot disks, see <xref linkend="vle-grub2-mkrescue"/>.
     </para>
    </listitem>
   </varlistentry>
  </variablelist>
 </sect2>

 <sect2 xml:id="sec-bootproblem-aarch64-install">
  <title>Problems Installing</title>
  <para>
   If an unexpected problem occurs during installation, information is needed
   to determine the cause of the problem. Use the following directions to help
   with troubleshooting:
  </para>
  <itemizedlist mark="bullet" spacing="normal">
   <listitem>
    <para>
     Check the outputs on the various consoles. You can switch consoles with
     the key combination <keycombo>
     <keycap function="control"/><keycap function="alt"/><keycap>Fn</keycap></keycombo>.
     For example, obtain a shell in which to execute various commands by
     pressing <keycombo>
     <keycap function="control"/><keycap function="alt"/><keycap>F2</keycap></keycombo>.
    </para>
   </listitem>
   <listitem>
    <para>
     Try launching the installation with <quote>Safe Settings</quote> (press
     <keycap>F5</keycap> on the installation screen and choose <guimenu>Safe
     Settings</guimenu>). If the installation works without problems in this
     case, there is an incompatibility that causes either
     <systemitem>ACPI</systemitem> or <systemitem>APIC</systemitem> to fail. In
     some cases, a firmware update fixes this problem.
    </para>
   </listitem>
   <listitem>
    <para>
     Check the system messages on a console in the installation system by
     entering the command <command>dmesg -T</command>.
    </para>
   </listitem>
  </itemizedlist>
 </sect2>

 <sect2 xml:id="sec-bootproblem-aarch64-redirect">
  <title>Redirecting the Boot Source to the Boot DVD</title>
  <para>
   To simplify the installation process and avoid accidental installations, the
   default setting on the installation DVD for &productname; is that your
   system is booted from the first hard disk. At this point, an installed boot
   loader normally takes over control of the system. This means that the boot
   DVD can stay in the drive during an installation. To start the installation,
   choose one of the installation possibilities in the boot menu of the media.
  </para>
 </sect2>
</sect1>