mirror of https://github.com/tLDP/LDP
DocBook validation correction
adding a bunch of terminating </sect1> </sect2> </sect3> </sect4> and </para> tags
This commit is contained in:
Martin A. Brown
parent
a52bf88f4f
commit
8ceb8a930b
|
|
@ -90,7 +90,7 @@ confidently even when the outlook was dimmest and others unforgiving. I'm yours
|
|||
|
||||
<sect2 id="feedback"> <title>Feedback</title> <para> Please send any additions
|
||||
or comments pertaining to this document to the following email address:
|
||||
<email>hshane[AT]austin.rr.com</email>. </para> <sect2 id="conventions">
|
||||
<email>hshane[AT]austin.rr.com</email>. </para></sect2> <sect2 id="conventions">
|
||||
<title>Conventions Used in this Document</title> <para> The following conventions are
|
||||
used in this document and are outlined here for those who may not yet have a complete
|
||||
understanding of how to access and control the underlying operating system in Linux,
|
||||
|
|
@ -122,6 +122,7 @@ Most cable modems have two possible interfaces for connection to your computer:
|
|||
Ethernet or USB. If your version of Linux is like most, there is very little you will need to do to to get your cable modem
|
||||
working with an Ethernet interface as long as you have support for networking and the driver for your specific networking hardware installed.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="nic">
|
||||
<title>Ethernet Support</title>
|
||||
|
|
@ -144,6 +145,7 @@ using whatever kernel configuration front-end application (whether <command>make
|
|||
xconfig</command>) prior to compiling a custom kernel. For 2.4.x and earlier kernels under the heading 'Networking options' you will require 'TCP/IP Networking' along with 'Network Device Support,' go to 'Ethernet (10 or 100Mbit) Support' and enable your specific NIC driver. If you use the 2.6.x series, the heading 'Drivers' has a sub-heading 'Networking Support,' where you should enable 'Network Device Support' and 'Ethernet Connection Support/Ethernet (10 or 100Mbit), as well as your specific NIC hardware driver.</para>
|
||||
|
||||
<para>If you are interested in how to configure the USB interface go to <xref linkend="usbconfig">; otherwise you can go to <xref linkend="modem">.</para>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2 id="usbconfig"><title>USB Interface Support</title>
|
||||
|
|
@ -167,6 +169,7 @@ For kernel 2.6.x you will need
|
|||
</itemizedlist>
|
||||
<para>
|
||||
See <xref linkend="usb"> for instructions on how to load modules when time to test the modem.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="modem"> <title>The Modem Device</title> <para> First, plug in and turn on
|
||||
the cable modem. Connect your Ethernet card to the modem with 10BaseT/100BaseT cable
|
||||
|
|
@ -202,7 +205,7 @@ url="http://www.tldp.org/HOWTO/mini/DHCP/x74.html">DHCP mini-HOWTO</ulink>. </p
|
|||
get a dynamic IP address. </para> </sect3> </sect2> </sect1>
|
||||
|
||||
|
||||
<sect1 id="configuration"> <title>Configuration</title> <para> <sect2 id="eth">
|
||||
<sect1 id="configuration"> <title>Configuration</title> <sect2 id="eth">
|
||||
<title>Ready to Start With an Ethernet-Modem connection</title> <para> Once you
|
||||
are plugged into the system, your modem is on and your dhcp server is running as
|
||||
outlined in <xref linkend="dhcp">, you should be provided your own IP address that
|
||||
|
|
@ -226,6 +229,7 @@ successfully acquired an IP address (the 'inet addr') provided by our cable inte
|
|||
service provider.</para> <para> A simple Ethernet-based configuration should be complete
|
||||
at this step. If you have more than one Ethernet interface available and want to select
|
||||
a specific one for the cable service, go on to <xref linkend="device-iface">. </para>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2 id="device-iface"> <title>Grabbing A Specific Interface</title> <para> Let's say
|
||||
|
|
@ -261,6 +265,7 @@ hardware or for just plain testing. Use ifconfig: </para>
|
|||
</screen></para> <para>You can check if it worked by calling
|
||||
<command>ifconfig</command> without options after your next reboot. See <command>man
|
||||
ifconfig</command> for more options.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3 id="autoconfig"> <title>Automatic Configuration of Devices</title> <para> The
|
||||
method for automatically assigning a particular interface name <emphasis>ethX</emphasis>,
|
||||
|
|
@ -284,6 +289,7 @@ eth1</command> it won't work. The easy way to do this at boot up is to make an i
|
|||
script to load the dhcp address to the correct interface, which should be placed in
|
||||
<filename>/etc/init.d</filename>. Then run <command>update-rc.d</command> as root with
|
||||
the correct arguments (see <command>man update-rc.d</command>). </para>
|
||||
</sect4>
|
||||
|
||||
<sect4 id="rh"> <title>Red Hat</title> <para> The file to
|
||||
edit will of the form <filename>ifcfg-ethX</filename>, located in
|
||||
|
|
@ -303,10 +309,12 @@ save it. If the file doesn't exist for the interface you need you can create it,
|
|||
for example <filename>ifcfg-eth1</filename>. You can then use <command>ifconfig eth1
|
||||
up</command> from the command line to use it immediately. Upon reboot the correct
|
||||
hardware settings should be loaded automatically.</para>
|
||||
</sect4>
|
||||
|
||||
<sect4 id="slackware">
|
||||
<title>Slackware</title>
|
||||
<para> Slackware has a configuration utility named 'netconfig' that you can use at the command line as root to modify your network settings and configure interfaces by static IP addresses or dhcp. You can rerun it at any time to reconfigure things once you have installed your modem. </para>
|
||||
</sect4>
|
||||
|
||||
|
||||
<sect4 id="others">
|
||||
|
|
@ -316,6 +324,7 @@ distribution-specific information to add; see <xref linkend="feedback">. Consult
|
|||
distribution documentation where appropriate.</para>
|
||||
</sect4>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="usb"> <title>Using the USB interface instead of an Ethernet card</title>
|
||||
|
||||
|
|
@ -338,7 +347,7 @@ There are two ways your kernel may support a device driver: either by being stat
|
|||
0.98.6 7 Jan 2002 Brad Hards and another
|
||||
Mar 2 11:00:52 K7 kernel: usb.c: registered new driver CDCEther </screen> </para>
|
||||
|
||||
<para>in the case of a statically compiled driver or a module loaded at boot.
|
||||
<para>in the case of a statically compiled driver or a module loaded at boot.</para>
|
||||
|
||||
<para>If you don't see it, to find out if your kernel has already loaded the CDCEther (Communications Device Class Ethernet) driver as a module, on
|
||||
the command line issue <command>lsmod</command> as root. You should see the module <filename>CDCEther</filename> listed for 2.4.x kernels, or alternatively <filename>usbnet</filename> for 2.6.x kernels.</para>
|
||||
|
|
@ -357,7 +366,7 @@ or at the end of <command>dmesg | less</command> from the command line:
|
|||
Mar 2 11:00:52 K7 kernel: usb.c: registered new driver CDCEther </screen> </para>
|
||||
|
||||
<para> If all goes well you should see something like the following in your system log
|
||||
files or at the end of <command>dmesg</command>:
|
||||
files or at the end of <command>dmesg</command>:</para>
|
||||
|
||||
<para><screen> Mar 2 11:00:52 K7 kernel: CDCEther.c:
|
||||
0.98.6 7 Jan 2002 Brad Hards and another
|
||||
|
|
@ -379,16 +388,23 @@ device have been addressed in <xref linkend="networking">.
|
|||
configuring a cable modem and cable internet service providers in Israel on <ulink url="http://www.freewebs.com/linuxnet/CableUSBLinuxEn.html">Jess' webpage</ulink> for those that live there. I have personally subscribed to two large cable ISPs in the U.S. without any trouble using the instructions outlined above. The previous incarnation of this document had a large catalogue of ISPs listed by geography, but as a rule the identity of the upstream provider should not affect configuration. If your cable ISP claims not to support linux, it is not because of any technical difficulties related to the operating system. Just don't expect them to configure if for you on your end like they do for most other users (that's why you're reading this document, right?).</para>
|
||||
|
||||
<sect2 id="ambit"><title>Ambit Modems</title><para>Supported by Ethernet and CDCEther.</para>
|
||||
</sect2>
|
||||
<sect2 id="broadcom"><title>Broadcom Cable Modems</title><para>Supported by Ethernet and CDCEther.</para>
|
||||
</sect2>
|
||||
<sect2 id="ericson"><title>Ericson PipeRider Modems</title><para>Supported by Ethernet and CDCEther.</para>
|
||||
</sect2>
|
||||
<sect2 id="motorola"> <title>Motorola SurfBoard Modems</title> <para>This model has enjoyed widespread use by cable providers. There is a separate <ulink
|
||||
url="http://tldp.org/HOWTO/Motorola-Surfboard-Modem/index.html">HOWTO,</ulink>
|
||||
written by your humble author. Supported by both Ethernet and USB CDCEther. Refer to that document for any hardware
|
||||
specific questions. The generic instructions above generally work.</para>
|
||||
<sect2 id="RCA"><title>RCA (Tompson) Modems</title><para>Supported with Ethernet, CDCEther untested.
|
||||
</sect2>
|
||||
<sect2 id="RCA"><title>RCA (Tompson) Modems</title><para>Supported with Ethernet, CDCEther untested.</para>
|
||||
</sect2>
|
||||
<sect2 id="terayon"><title>Terayon Modems</title><para>At minimum the tj715 is known to be supported using Ethernet and CDCEther.</para>
|
||||
</sect2>
|
||||
<sect2 id="toshiba"> <title>Toshiba PCX-XXXX Cable Modems</title> <para>The four X's in the name indicate model number. Works with Ethernet, CDCEther untested.
|
||||
'out-of-the-box' with the above instructions. </para>
|
||||
</sect2>
|
||||
<sect2 id="WebStar"><title>Webstar Modems</title><para>Supported with Ethernet, CDCEther untested.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
|
|
|||
Loading…
Reference in New Issue