mirror of
https://review.haiku-os.org/userguide
synced 2026-02-04 07:53:42 +01:00
The updated welcome package with all translations. Thanks everyone.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@36782 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Joachim Seemer
106
welcome/it/bugreports.html
Normal file
106
welcome/it/bugreports.html
Normal file
@@ -0,0 +1,106 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2009, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Reporting bugs</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/it.png" alt="" /> Italiano</li>
|
||||
<li><a href="../fr/bugreports.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/bugreports.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../ru/bugreports.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/bugreports.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/bugreports.html"><img src="../images/flags/sv_SE.png" alt="" />Svensk</a></li>
|
||||
<li><a href="../jp/bugreports.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/bugreports.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../en/bugreports.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
<span>
|
||||
<a href="../welcome_it.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
|
||||
<h1>Reporting bugs</h1>
|
||||
|
||||
<p>Since our developers are unable to test every hardware combination, nor every different way of interacting with the operating system, we are relying on users to give us some input on how things work at their end. Since Haiku is still quite young, it's very likely that you will encounter bugs. We thank you for taking the time to report these. Together we can improve Haiku, bit by bit.</p>
|
||||
<p>To keep our bugtracker effective, it's essential to abide by the <a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">Bug Tracker Etiquette</a>.</p>
|
||||
|
||||
<h2>Getting a Trac account</h2>
|
||||
<p>To file a ticket, you need to have an account at <a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku's Bugtracker</a>.<br />
|
||||
When creating a new account, be certain to <b>provide your email address</b> as it is necessary to obtain basic ticket modification privileges. Be sure to <b>check your spam folder</b> shortly afterwards, as the all important verification mail often ends up there.</p>
|
||||
|
||||
<h2>Creating a bug report</h2>
|
||||
<p>Before reporting a bug, please <a href="http://dev.haiku-os.org/query?status=new&status=assigned&status=reopened&status=closed&summary=%7Etext+you+want+to+search+for&order=priority">make sure</a> that it does not yet exist. You can also use the <a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">search</a> function for this.<br />
|
||||
After you have established that it's a unique bug, make your information as accurate as possible:</p>
|
||||
<ul>
|
||||
<li><p>Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).</p></li>
|
||||
<li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in '<i>About This System...</i>' from the Deskbar menu.</p></li>
|
||||
<li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
|
||||
<li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
|
||||
<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the <span class="key">PRINT</span> key saves a <acronym title="Portable Network Graphics image format">PNG</acronym> in <span class="path">/boot/home/</span>).</p></li>
|
||||
</ul>
|
||||
|
||||
<h3>Software Bugs</h3>
|
||||
<p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bug report.</p>
|
||||
|
||||
<h3>Hardware Bugs</h3>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
|
||||
<ul>
|
||||
<li><span class="cli">listdev</span> - a detailed listing of your hardware, including vendor and pci id's, similar to Linux' <span class="cli">lshw</span> and <span class="cli">lspci</span>.</li>
|
||||
<li><span class="cli">listusb -v</span> - assuming its a USB related issue, similar to <span class="cli">lsusb</span>.</li>
|
||||
<li><span class="cli">open /var/log/syslog</span> - the primary system log used by Haiku, akin to on screen debugging during boot. With the <span class="cli">open</span> command you can crop down the relevant part of the syslog in a text editor.</li>
|
||||
<li><span class="cli">listimage | grep drivers/</span> - lists all used drivers.</li>
|
||||
<li><span class="cli">ints</span> - only available within <i>Kernel Debugging Land</i> (see below). Shows interrupt usage. There shouldn't be too many that are shared by different devices.</li>
|
||||
</ul>
|
||||
<p>You enter these commands into Terminal. Add a <span class="cli"> > output.txt</span> after a command, and it's piped into a text file called "output.txt" that you can attach to your bug report or email.</p>
|
||||
|
||||
<h3>Kernel Debugging Land - KDL</h3>
|
||||
<p>When some very low level system component crashed, you may end up in the kernel debugger. It can also be entered deliberately with <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span> (<span class="key">SysReq</span> being <span class="key">PRINT</span> on most keyboards).</p>
|
||||
<ul>
|
||||
<li><span class="cli">co</span> - will exit KDL and continue normal system operation, if possible.</li>
|
||||
<li><span class="cli">int</span> - will show interrupt usage (as described above).</li>
|
||||
<li><span class="cli">bt</span> - shows a backtrace, detailing where exactly the crash happened.</li>
|
||||
</ul>
|
||||
|
||||
<h2>What's next?</h2>
|
||||
<p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding
|
||||
non-descriptive comments.</p>
|
||||
<p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked
|
||||
as 'fixed'.</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_it.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
144
welcome/it/wifi.html
Normal file
144
welcome/it/wifi.html
Normal file
@@ -0,0 +1,144 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2010, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta http-equiv="Content-Style-Type" content="text/css" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Wifi</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner">
|
||||
<ul class="lang-menu">
|
||||
<li class="now"><img src="../images/flags/it.png" alt="" /> Italiano</li>
|
||||
<li><a href="../fr/wifi.html"><img src="../images/flags/fr.png" alt="" />Français</a></li>
|
||||
<li><a href="../de/wifi.html"><img src="../images/flags/de.png" alt="" />Deutsch</a></li>
|
||||
<li><a href="../ru/wifi.html"><img src="../images/flags/ru.png" alt="" />Русский</a></li>
|
||||
<li><a href="../es/wifi.html"><img src="../images/flags/es.png" alt="" />Español</a></li>
|
||||
<li><a href="../sv_SE/wifi.html"><img src="../images/flags/sv_SE.png" alt="" />Svensk</a></li>
|
||||
<li><a href="../jp/wifi.html"><img src="../images/flags/jp.png" alt="" />日本語</a></li>
|
||||
<li><a href="../uk/wifi.html"><img src="../images/flags/uk.png" alt="" />Українська</a></li>
|
||||
<li><a href="../en/wifi.html"><img src="../images/flags/gb.png" alt="" />English</a></li>
|
||||
</ul>
|
||||
|
||||
<span>
|
||||
<a href="../welcome_it.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
<div id="content">
|
||||
<div>
|
||||
<div class="box-info">The translation of this page isn't yet complete. Until it is, unfinished parts use the English original.</div>
|
||||
|
||||
<h2>Wifi in Haiku</h2>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="hardware" rel="nofollow" id="hardware">Expected supported hardware</a></h3>
|
||||
<p>All of FreeBSD 8 wlan drivers should be working. Any PCMCIA, CardBus, ExpressCard, USB or ISA based cards will not work. Only PCI, miniPCI, PCI-Express, miniPci-Express and PCI-X are supposed to work.<br />
|
||||
This includes:
|
||||
</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> supporting at least<br />
|
||||
Cisco Aironet 350 Series<br />
|
||||
Aironet PCI4500<br />
|
||||
Aironet PCI4800<br />
|
||||
</p></li>
|
||||
<li><p><i>atheroswifi</i> supporting almost every chipset outthere (though no AR9285 chips)</p></li>
|
||||
<li><p><i>broadcom43xx</i> supporting<br />
|
||||
BCM4301, BCM4306, BCM4307, BCM4309, BCM4311, BCM4312 and BCM4318
|
||||
</p></li>
|
||||
<li><p><i>iprowifi2100</i> supporting the 2100 chips</p></li>
|
||||
<li><p><i>iprowifi2200</i> supporting<br />
|
||||
2200BG<br />
|
||||
2225BG<br />
|
||||
2915ABG
|
||||
</p></li>
|
||||
<li><p><i>iprowifi3945</i> supporting the 3945 chips</p></li>
|
||||
<li><p><i>iprowifi4965</i> supporting the 4965 chips</p></li>
|
||||
<li><p><i>marvell88w8335</i> supporting<br />
|
||||
Marvell Libertas 88W8310<br />
|
||||
Marvell Libertas 88W8335
|
||||
</p></li>
|
||||
<li><p><i>marvell88w8363</i> supporting the 88W8363 chips</p></li>
|
||||
<li><p><i>ralinkwifi</i> supporting<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p><i>wavelanwifi</i> supporting at least<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
Intersil Prism2.5<br />
|
||||
Linksys WDT11<br />
|
||||
Netgear MA301<br />
|
||||
PRISM2STA WaveLAN<br />
|
||||
Siemens SpeedStream<br />
|
||||
SMC 2602W<br />
|
||||
Us Robotics 2415<br />
|
||||
Addtron AWA-100 PCI
|
||||
</p></li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wep" rel="nofollow" id="wep">WEP encryption</a></h3>
|
||||
<p>WEP encryption is available through a command-line application <span class="cli">setwep</span>. It is a temporary means for joining an unencrypted or WEP encrypted wifi network. <span class="cli">setwep</span> works with 64- and 128-bit WEP and supports both text keys as well as hex digit keys (see <a href="#wep-notes" rel="nofollow">WEP notes</a> below).
|
||||
</p>
|
||||
<p>The usage is: <span class="cli">setwep device_path [ssid] [key]</span></p>
|
||||
<p>Below are two examples. Let us assume your wifi network card is "/dev/net/iprowifi3945/0" and the wireless network is named "haikuwifi".</p>
|
||||
<h4>Example 1: Connect with 64-bit WEP encryption using a hex digit key</h4>
|
||||
<pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
|
||||
</pre><h4>Example 2: Connect to an unencrypted wireless network</h4>
|
||||
<pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi
|
||||
</pre><div class="box-info">
|
||||
<li>To find out what your device_path is, have a look in Preferences -> Network</li>
|
||||
<li>To make your wifi device connect to a given SSID at each boot, add the <tt>setwep</tt> command to your <tt>home/config/boot/UserBootscript</tt></li>
|
||||
</div>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
|
||||
<ul>
|
||||
<li>64-bit WEP uses a 40-bit key, which means 5 text characters or 10 hex digits</li>
|
||||
<li>128-bit WEP uses a 104-bit key, which means 13 text characters or 26 hex digits</li>
|
||||
<li>hexadecimal digits = characters 0-9 and A through F (prepended with "0x" in <tt>setwep</tt>)</li>
|
||||
</ul>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA encryption</a></h3>
|
||||
<p>At the moment there is no WPA encryption available in Haiku. However, there is some <a target="_blank" class="ext" href="http://alexbl.net/%7Ealexbl/haiku-wpa/" rel="nofollow">preliminary and unfinished code for implementing WPA</a><span class="ext"></span> available. Some tasks for improving this is to plug it into the wpa_supplicant build process and then fixing compile & runtime issues.</p>
|
||||
<h3>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a name="install_script" rel="nofollow" id="install_script">install-wifi-firmwares.sh</a></h3>
|
||||
<p>To install the firmware for Intel ipw2100, Intel ipw2200/2225/2915, Broadcom 43xx & Marvell 88W8335, you need to run</p>
|
||||
<pre class="terminal">install-wifi-firmwares.sh
|
||||
</pre>
|
||||
<p>The Intel ipw2100 and ipw22xx will install without an internet connection, as the licensing terms allow Haiku to distribute the original firmware archives. However, they do require acknowledgment by the end-user prior to their installation. The Broadcom 43xx and Marvell 88W8335 will require an active internet connection, as the files containing their respective firmwares cannot be distributed with Haiku.</p>
|
||||
<p>People building their own Haiku image can modify their <span class="cli">build/jam/UserBuildConfig</span> accordingly. Details for that and general updates on the wifi topic are found at the <a href="http://www.haiku-os.org/guides/wifi">online version of this document</a>.</p>
|
||||
<p>If you have to download the firmware, but don't have a working internet connection under Haiku, the online version offers a <a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell script</a>, which will create a zip file for you to extract to Haiku's <tt>/boot</tt>. After that you'll have all files needed by install-wifi-firmwares.sh.</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
<div class="inner"><span>
|
||||
<a href="../welcome_it.html" class="uplink">Welcome</a>
|
||||
</span></div>
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
Reference in New Issue
Block a user