Update userguide translations
Also purge old documents
This commit is contained in:
committed by
waddlesplash
parent
4fd69b6cc2
commit
7852aa0525
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Copyright 2008-2018, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -97,7 +97,7 @@
|
||||
Disables Advanced Configuration and Power Interface hardware support, overriding the ACPI setting in the kernel settings file.</p>
|
||||
<p><span class="menu">Blacklist entries</span><br />
|
||||
Allows to select system files that shall be ignored. Useful e.g. to disable drivers temporarily. See <a href="#troubleshooting">Troubleshooting</a> below.</p></td></tr>
|
||||
<tr><td><b>Select debug options</b></td><td> </td><td>Here you'll find several options that help with debugging or getting details for a <a href="../../welcome/en/bugreports.html">bug report</a>. Again, a short explanation for each option is displayed at the bottom.</td></tr>
|
||||
<tr><td><b>Selectează opțiuni depanare</b></td><td> </td><td>Here you'll find several options that help with debugging or getting details for a <a href="../../welcome/en/bugreports.html">bug report</a>. Again, a short explanation for each option is displayed at the bottom.</td></tr>
|
||||
<tr><td></td><td></td><td>
|
||||
<p><span class="menu">Enable serial debug output</span><br />
|
||||
Turns on forwarding the syslog output to the serial interface (default: 115200, 8N1).</p>
|
||||
@@ -122,12 +122,13 @@
|
||||
</table>
|
||||
<h2>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="troubleshooting" name="troubleshooting">Troubleshooting</a></h2>
|
||||
<a id="troubleshooting" name="troubleshooting">Depanare</a></h2>
|
||||
<p>If Haiku refuses to boot on your hardware from the get-go, try out setting different options under <span class="menu">Select safe mode options</span>. Consider filing a <a href="../../welcome/en/bugreports.html">bug report</a> in any case.</p>
|
||||
<p>On the other hand, if Haiku only suddenly acts up after you have installed some software, especially hardware drivers, you have several options to get Haiku bootable again so you can uninstall the offending package:</p>
|
||||
<ul>
|
||||
<li><p>Activating <span class="menu">Safe mode</span> will prevent most servers, daemons and the UserBootscript from being started.</p></li>
|
||||
<li><p>Activating <span class="menu">Disable user add-ons</span> will prevent using any add-ons (drivers, translators, etc.) you have installed in the user hierarchy under your Home folder.</p></li>
|
||||
<li><p>If activating <span class="menu">Use fail-safe graphics driver</span> solves your troubles by falling back to VESA graphics, you can make the setting permanent by removing the <tt>#</tt> of the line <i>#fail_safe_video_mode true</i> in the text file <span class="path">/boot/home/config/settings/kernel/drivers/kernel</span>.</p></li>
|
||||
<li><p>If the offending driver, add-on etc. is installed in the system hierarchy, things get a bit more complicated, because that area is read-only. Here, the <span class="menu">Blacklist entries</span> comes into play. With it, you can navigate through the whole system hierarchy and disable the component that's messing things up for you by checking an entry with the <span class="key">SPACE</span> or <span class="key">RETURN</span> key. <span class="key">ESC</span> returns you up one level to the parent directory.</p>
|
||||
<p>Online, there's the article <a href="http://www.haiku-os.org/blog/barrett/2013-12-15_how_permanently_blacklist_package_file">How to Permanently Blacklist a Package File</a> showing how to make that setting stick.</p></li>
|
||||
<li><p>Under <span class="menu">Select boot volume</span> you can specify what former "version" of Haiku to boot. Every time you un/install a package, the old state is saved and you can boot into it by choosing it from the list presented in the boot loader options.<br />
|
||||
@@ -135,20 +136,20 @@ So, if you encounter boot problems after installing some package, boot a Haiku s
|
||||
</ul>
|
||||
<h2>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="booting" name="booting">Booting Haiku</a></h2>
|
||||
<p>After activating one or more options, you return to the main menu and continue booting, which presents you with this boot screen:</p>
|
||||
<a id="booting" name="booting">Pornirea Haiku</a></h2>
|
||||
<p>După activarea uneia sau mai multor opțiuni, vă întoarceți la meniul principal și continuați pornirea sistemului, care vă arată acest ecran de boot:</p>
|
||||
<img src="../images/bootloader-images/boot-screen.png" alt="boot-screen.png" />
|
||||
|
||||
<p>If everything works OK, one symbol after another quickly lights up.<br />
|
||||
The different symbols roughly correspond to these boot stages:</p>
|
||||
<p>Dacă totul fucționează corect, se aprinde rapid un simbol, unul după altul.<br />
|
||||
Diferitele simboluri corespund aproximativ cu aceste etape de boot:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><b>Atom</b></td><td style="width:10px;"> </td><td>Initializing modules.</td></tr>
|
||||
<tr><td><b>Disk + magnifier</b></td><td> </td><td>Creating rootfs (<span class="path">/</span>) and mounting devfs (<span class="path">/dev</span>).</td></tr>
|
||||
<tr><td><b>Plug-in card</b></td><td> </td><td>Initializing device manager.</td></tr>
|
||||
<tr><td><b>Boot disk</b></td><td> </td><td>Mounting boot disk.</td></tr>
|
||||
<tr><td><b>Chip</b></td><td> </td><td>Loading CPU specific modules.</td></tr>
|
||||
<tr><td><b>Folder</b></td><td> </td><td>Final initialization of subsystems.</td></tr>
|
||||
<tr><td><b>Rocket</b></td><td> </td><td>Launch_daemon has started the system.</td></tr>
|
||||
<tr><td><b>Atom</b></td><td style="width:10px;"> </td><td>Se inițializează modulele.</td></tr>
|
||||
<tr><td><b>Disc + lupă</b></td><td> </td><td>Se creează rootfs (<span class="path">/</span>) și se montează devfs (<span class="path">/dev</span>).</td></tr>
|
||||
<tr><td><b>Card plug-in</b></td><td> </td><td>Se inițializează gestionarul de dispozitive.</td></tr>
|
||||
<tr><td><b>Disc de boot</b></td><td> </td><td>Se montează discul de boot.</td></tr>
|
||||
<tr><td><b>Cip</b></td><td> </td><td>Se încarcă modulele specifice CPU.</td></tr>
|
||||
<tr><td><b>Dosar</b></td><td> </td><td>Se finalizează inițializarea subsistemelor.</td></tr>
|
||||
<tr><td><b>Rachetă</b></td><td> </td><td>Launch_daemon a pornit sistemul.</td></tr>
|
||||
</table>
|
||||
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user