os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove the mini-FAQ. It will be replaced with a more formal document.

Browse source
This commit is contained in:
Tom Rhodes 2003-05-20 22:13:35 +00:00
parent 1ce60fc6d2
commit 1a19d90d60
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=17003
1 changed files with 0 additions and 96 deletions
Download patch file Download diff file Expand all files Collapse all files

96
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -821,103 +821,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
<secondary>Troubleshooting</secondary>
</indexterm>
<qandaset>
<qandaentry>
<question>
<para>Where can I find information about possible trouble
I may experience with my network card?</para>
</question>
<answer>
<para>The manual page of the driver is the first piece of
documentation to read. The mailing lists archives can
also be useful.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>When I try to ping a machine on my LAN, I get this
message: <errorname>ping: sendto: Permission
denied</errorname>.</para>
</question>
<answer>
<para>This means that you do not have permission to
send ICMP packets. Check to see if a firewall is
running on the machine and if there are any rules
blocking ICMP.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I see a lot of <errorname>watchdog
timeout</errorname> messages in the system logs, and
when I try to ping a machine on the LAN, I get this
message: <errorname>ping: sendto: No route to
host</errorname>.</para>
</question>
<answer>
<para>The first thing to do is to check your network
cable. Many cards require a PCI slot supporting the
Bus Mastering. On some old motherboards, only one PCI
slot allows it (most of time slot 0). Check the
network card and the motherboard documentation to
determine if that may be the problem.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>I see a lot of <errorname>device timeout</errorname>
messages in the system logs, and my network card does not
work.</para>
</question>
<answer>
<para>Having one or two of these messages is sometimes
normal with some cards. However, if they persist and the
network is not usable, make sure the network cable is
plugged in and that there are no IRQ conflicts between
the network card and another device (or devices) on the
system.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>The performance of the card is poor, what can I
do?</para>
</question>
<answer>
<para>It is difficult to answer to that question. What is
your definition of <quote>poor performance</quote>? Double
check everything in your configuration, read the
&man.tuning.7; manual page, and try to avoid cheap
network cards. Many users have noted that setting the
media selection mode to <literal>autoselect</literal>
results in bad performance on some hardware.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>Are there any recommended network cards or cards I
should stay away from?</para>
</question>
<answer>
<para>You should avoid cheap cards for serious usage. Cheap
cards often use buggy chipsets, and most of time do not
provide very good performance. Many FreeBSD users like
cards using the &man.fxp.4; chipset, however, this does
not mean that all other chipsets are bad.</para>
</answer>
</qandaentry>
</qandaset>
</sect3>
</sect2>
</sect1>