mirror of
https://review.haiku-os.org/userguide
synced 2026-02-04 07:53:42 +01:00
Updated user guide.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@37849 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
Joachim Seemer
@@ -10,17 +10,19 @@
|
||||
* Authors:
|
||||
* Niels Reedijk and Matt Madia who wrote http://dev.haiku-os.org/wiki
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Pengphei Han
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
<meta name="robots" content="all" />
|
||||
<title>Reporting bugs</title>
|
||||
<title>报告错误</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>用户指南</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -45,55 +47,54 @@
|
||||
|
||||
<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>
|
||||
<h1>报告错误</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>
|
||||
<p>由于我们的开发人员不可能测试每种硬件组合和每种不同的系统交互方式，所以我们依赖于用户，通过用户来给予我们Haiku的运行情况。由于Haiku还很年轻，您在使用时很有可能会遇到错误。我们非常感谢您能够分出时间来提交这些错误报告。我们可以共同的一位一位的提高Haiku的性能。</p>
|
||||
<p>为了确保我们的错误跟踪系统的有效性，遵守共同的<a href="http://dev.haiku-os.org/wiki/BugTrackerEtiquette">错误报告规范</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>获取Trac账户</h2>
|
||||
<p>为了提交任务单，您需要在<a href="http://dev.haiku-os.org/register" title="Register at Haiku's Bugtracker">Haiku的错误跟踪系统</a>中注册一个账户。
|
||||
<br />
|
||||
在新建账户时，你需要<b>提供自己的电子邮箱</b> ，否则您将不具有基本的任务单修改权限。之后，您一定要保证<b>检查您的垃圾邮件文件夹</b>，因为所有重要的验证邮件都会被发送到那儿去。</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>
|
||||
<h2>创建错误报告</h2>
|
||||
<p>在报告一个错误之前，请您<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">确保</a>该错误报告之前不存在。你可以使用<a href="http://dev.haiku-os.org/search?q=&noquickjump=1&ticket=on">查找</a>功能来查找其是否存在。
|
||||
<br />
|
||||
在确定它是一个独特的错误之后，您需要尽可能的找出有关的详细信息：</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>
|
||||
<li><p>包括基本的信息，例如以何种方式测试Haiku（利用真实的硬件，VMware，还是QEMU）。</p></li>
|
||||
<li><p>提及您正在运行的系统的 <acronym title="Subversion, the source code management system we use">SVN</acronym> 发布版本。你可以在桌面栏菜单中的 '<i>About This System...</i>' 中找出相关信息。</p></li>
|
||||
<li><p>描述您所遇到的问题。尽量把问题讲得精确和明白：描述详细的系统行为反馈，和您期望的反馈。</p></li>
|
||||
<li><p>描述暴露该错误所需要的操作步骤。这将会有助于开发者重现该错误，并对其进行修复和完善。</p></li>
|
||||
<li><p>附带你所掌握的尽可能多的信息。如果是一个GUI错误，或者图形程序错误，尽量附带出现错误时的屏幕截图。（<span class="key">PRINT</span> 键保存了一个<acronym title="Portable Network Graphics image format">PNG</acronym> 图像到 <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>软件错误</h3>
|
||||
<p>如果出现了程序崩溃，您应该从弹出的警告窗口中启动调试程序。 在启动的调试终端中，输入<span class="cli">bt</span>，你将会创建关于调试信息的“回溯”，然后你应该把它复制到您的错误报告中。</p>
|
||||
|
||||
<h3>Hardware Bugs</h3>
|
||||
<p>When dealing with a hardware/driver related bug, you should attach the following information:</p>
|
||||
<h3>硬件错误</h3>
|
||||
<p>如果遇到了硬件或者驱动相关的错误，您应该附带下列信息：</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>
|
||||
<li><span class="cli">listdev</span> - 有关您的硬件的详细列表，包括提供商和PCI ID。类似于Linux下的 <span class="cli">lshw</span> 和 <span class="cli">lspci</span> 。</li>
|
||||
<li><span class="cli">listusb -v</span> - 如果存在USB相关的问题；类似于Linux下的 <span class="cli">lsusb</span>。</li>
|
||||
<li><span class="cli">open /var/log/syslog</span> - Haiku主要的系统日志，近似于在启动期间的屏幕调试。使用 <span class="cli">open</span> 命令，您可以把在文本编辑器中把系统日志中重要的部分裁剪下来。</li>
|
||||
<li><span class="cli">listimage | grep drivers/</span> - 列出所有使用的驱动。</li>
|
||||
<li><span class="cli">ints</span> - 只在 <i>内核调试状态</i> 下才可用（参见下文）。它显示了中断的使用情况，而由不同的硬件所共享的中断并不是很多。</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>
|
||||
<p>您在终端中输入这些命令，在每个命令后面添加 <span class="cli"> > output.txt</span> 。 然后命令输出的结果就被重定向到一个称为 “output.txt” 的文本文件；您可以把它附带到您的错误报告或者邮件中。</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>
|
||||
<h3>内核调试 - KDL</h3>
|
||||
<p>如果某些底层的系统组件发生了崩溃，您可能就会进入了内核调试状态。您也可以有意识的使用 <span class="key">ALT</span><span class="key">SysReq</span><span class="key">D</span>（<span class="key">SysReq</span> 在多数键盘中都是 <span class="key">PRINT</span>）来进入内核调试状态。</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>
|
||||
<li><span class="cli">co</span> - 如果可能的话，系统将会结束内核调试状态，返回正常的系统操作界面。</li>
|
||||
<li><span class="cli">int</span> - 将会显示中断使用情况（如上所述）。</li>
|
||||
<li><span class="cli">bt</span> - 显示一个调试信息的回溯，详细的给出了崩溃发生的地方。</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>
|
||||
<h2>下一步？</h2>
|
||||
<p>在您提交了错误报告之后，开发人员将会检查您的错误，然后尝试进行修复。但是需要注意的是，我们所有的人员都是志愿者，有时候一个错误报告可能会很长时间没有人来进行回答。如果可以的话，添加新的信息将会有助于早点修复错误，但是请不要添加非描述性的评论来将“炒热”该错误。</p>
|
||||
<p>切记，提交错误报告不是花些很少的时间写个报告的事。如果您提交了一个错误，然后您属于Haiku开发过程中的一部分。开发人员在解决您的错误过程中可能会遇到问题，因此请你一定要始终关注该错误，然后回答相关的问题。如果该问题没有“fixed”，你的任务就没有“done”。</p>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -10,18 +10,20 @@
|
||||
* Authors:
|
||||
* Matt Madia who wrote http://www.haiku-os.org/guides/wifi
|
||||
* Humdinger <humdingerb@gmail.com>
|
||||
* Translators:
|
||||
* Pengphei Han
|
||||
*
|
||||
-->
|
||||
<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>
|
||||
<title>无线网络</title>
|
||||
<link rel="stylesheet" type="text/css" href="../Haiku-doc.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div id="banner">
|
||||
<div><span>User guide</span></div>
|
||||
<div><span>用户指南</span></div>
|
||||
</div>
|
||||
|
||||
<div class="nav">
|
||||
@@ -47,45 +49,47 @@
|
||||
|
||||
<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>
|
||||
<h2>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:
|
||||
<a name="hardware" rel="nofollow" id="hardware">预期的硬件支持</a></h3>
|
||||
<p>FreeBSD 8的所有无线驱动都应该可以工作。但是任何的PCMCIA，CardBus，ExpressCard，USB或者基于ISA的网卡将无法工作。只有PCI，miniPCI，PCI-Express，miniPci-Express 和 PCI-X 才应该可以工作。<br />
|
||||
包括以下：
|
||||
</p>
|
||||
<ul>
|
||||
<li><p><i>aironetwifi</i> supporting at least<br />
|
||||
<li><p><i>aironetwifi</i> 至少支持：<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
|
||||
<li><p><i>atheroswifi</i>支持几乎所有的芯片集(但是除了 AR9285 芯片)</p></li>
|
||||
<li><p><i>broadcom43xx</i> 支持：<br />
|
||||
BCM4301，BCM4306，BCM4307，BCM4309，BCM4311，BCM4312和 BCM4318
|
||||
</p></li>
|
||||
<li><p><i>iprowifi2100</i> supporting the 2100 chips</p></li>
|
||||
<li><p><i>iprowifi2200</i> supporting<br />
|
||||
<li><p><i>iprowifi2100</i> 支持 2100 芯片</p></li>
|
||||
<li><p><i>iprowifi2200</i> 支持：<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 />
|
||||
<li><p><i>iprowifi3945</i> 支持 3945 芯片</p></li>
|
||||
<li><p><i>iprowifi4965</i>支持 4965 芯片</p></li>
|
||||
<li><p><i>marvell88w8335</i> 支持：
|
||||
<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 />
|
||||
<li><p><i>marvell88w8363</i> 支持 88W8363 芯片</p></li>
|
||||
<li><p><i>ralinkwifi</i> 支持：
|
||||
<br />
|
||||
RT2560<br />
|
||||
RT2561S<br />
|
||||
RT2561<br />
|
||||
RT2661
|
||||
</p></li>
|
||||
<li><p><i>wavelanwifi</i> supporting at least<br />
|
||||
<li><p><i>wavelanwifi</i> 目前支持：
|
||||
<br />
|
||||
3Com Airconnect<br />
|
||||
GLPRISM2 WaveLAN<br />
|
||||
Intersil Prism3<br />
|
||||
@@ -101,38 +105,39 @@ Addtron AWA-100 PCI
|
||||
</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).
|
||||
<a name="wep" rel="nofollow" id="wep">WEP 加密</a></h3>
|
||||
<p>WEP 加密可以通过命令行程序 <span class="cli">setwep</span> 来进行启动。它是一种用于加入未加密或者WEP加密的无线网络的临时方法。 <span class="cli">setwep</span> 可用于64位或者128位的WEP，而且同时支持文本输入密钥和十六进制产品密钥（详细内容可以参阅下面的<a href="#wep-notes" rel="nofollow">WEP备注</a> ）。
|
||||
</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>
|
||||
<p>用法是：<span class="cli">setwep device_path [ssid] [key]</span></p>
|
||||
<p>下面是两个示例。我们假定您的无线网卡是 “/dev/net/iprowifi3945/0”，而无线网络是“haikuwifi”。</p>
|
||||
<h4>示例1：使用十六进制产品密钥连接64位WEP加密网络。</h4>
|
||||
<pre class="terminal">setwep /dev/net/iprowifi3945/0 haikuwifi 0x3456789abc
|
||||
</pre><h4>Example 2: Connect to an unencrypted wireless network</h4>
|
||||
</pre><h4>示例2：连接到未加密的无线网络</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>
|
||||
<li>为找出您的硬件的路径，你可以查看Preferences -> Network</li>
|
||||
<li>为了使您的无线设备在每次启动时都连接到给定的SSID，您可以添加 <tt>setwep</tt> 命令到 <tt>home/config/boot/UserBootscript</tt> 。
|
||||
</li>
|
||||
</div>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP notes</strong></a></p>
|
||||
<p><a name="wep-notes" rel="nofollow" id="wep-notes"><strong>WEP 备注</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>
|
||||
<li>64位的WEP使用了40位的密钥，也就是5个文本字符或者10个十六进制数字。</li>
|
||||
<li>128位的WEP是引用了104位密钥，也就是13个文本字符或者26个十六进制数字。</li>
|
||||
<li>十六进制位数字 = 0-9和A-F十六个字符 (在 <tt>setwep</tt> 命令中，它们前面冠以 “0x” )。</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>
|
||||
<a name="wpa" rel="nofollow" id="wpa">WPA加密</a></h3>
|
||||
<p>现在，在Haiku中还未有可用的WPA加密。但是，存在一些可用的<a target="_blank" class="ext" href="http://alexbl.net/%7Ealexbl/haiku-wpa/" rel="nofollow">用于实现WPA的私有或者未完成的代码</a><span class="ext"></span>。为了提高代码的可用性，您需要在构建wpa_supplicant的过程中加入相关代码，并且要袖管在编译和使用过程中存在的错误。</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>
|
||||
<p>为了安装用于 Intel ipw2100，Intel ipw2200/2225/2915，Broadcom 43xx 和 Marvell 88W8335 等的固件，您需要运行</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>
|
||||
<p> Intel ipw2100 和 ipw22xx 无需网络连接也可以进行安装，这是因为它们的许可条款允许Haiku发行原始的固件档案。但是在安装之前，它们确实需要用户的确认。Broadcom 43xx 和 Marvell 88W8335 需要活动的网络连接，这是因为包含固件的文件不能够随着Haiku一同发布。</p>
|
||||
<p>构建自己的Haiku镜像的人们可以在 <span class="cli">build/jam/UserBuildConfig</span> 中进行相应的改动。更多详细信息和关于无线网络的主题更新可以参阅 <a href="http://www.haiku-os.org/guides/wifi">有关的在线文档</a>。</p>
|
||||
<p>如果您确实需要下载该固件，而且在 Haiku 下也没有可用的网络连接，在线文档提供了一个<a href="http://www.haiku-os.org/files/download-data-for-wlan-firmwares.txt" rel="nofollow">shell 脚本</a>，它将会为你创建用于解压到 Haiku 的 <tt>/boot</tt> 文件夹下的Zip文件。之后，您就具有了所有 install-wifi-firmwares.sh 所需要的所有文件。</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user