mirror of https://github.com/tLDP/LDP
1536 lines
68 KiB
Plaintext
1536 lines
68 KiB
Plaintext
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN"[
|
|
|
|
<!ENTITY pt "[user@localhost]$ ">
|
|
|
|
]>
|
|
|
|
|
|
|
|
<article id="Conexant-Rockwell-modem-HOWTO" lang="en">
|
|
|
|
|
|
|
|
<articleinfo>
|
|
|
|
<title>Conexant/Rockwell modem HOWTO</title>
|
|
|
|
<authorgroup>
|
|
|
|
<author>
|
|
|
|
<firstname>Imran</firstname>
|
|
|
|
<surname>Ghory</surname>
|
|
|
|
<affiliation> <address><email>ImranG@btinternet.com</email></address> </affiliation>
|
|
|
|
</author>
|
|
|
|
</authorgroup>
|
|
|
|
|
|
|
|
<legalnotice>
|
|
|
|
<para>This document can be freely distributed. It's released under the GNU FDL License.</para>
|
|
|
|
</legalnotice>
|
|
|
|
|
|
|
|
<keywordset>
|
|
|
|
<keyword>Conexant</keyword>
|
|
|
|
<keyword>SoftK56</keyword>
|
|
|
|
<keyword>Rockwell</keyword>
|
|
|
|
<keyword>Modem</keyword>
|
|
|
|
<keyword>HSF</keyword>
|
|
|
|
<keyword>HCF</keyword>
|
|
|
|
<keyword>Riptide</keyword>
|
|
|
|
<keyword>winmodem</keyword>
|
|
|
|
<keyword>softmodem</keyword>
|
|
|
|
</keywordset>
|
|
|
|
|
|
|
|
<pubdate>2001-08-01</pubdate>
|
|
|
|
|
|
|
|
<revhistory>
|
|
|
|
|
|
|
|
<revision>
|
|
|
|
<revnumber>1.3</revnumber>
|
|
|
|
<date>2002-03-12</date>
|
|
|
|
<authorinitials>ig</authorinitials>
|
|
|
|
<revremark>
|
|
|
|
Updated to deal with new HCF driver.
|
|
|
|
</revremark>
|
|
|
|
</revision>
|
|
|
|
|
|
|
|
<revision>
|
|
|
|
<revnumber>1.2</revnumber>
|
|
|
|
<date>2002-02-21</date>
|
|
|
|
<authorinitials>ig</authorinitials>
|
|
|
|
<revremark>
|
|
|
|
Updated to deal with new HSF driver and release date for HCF driver.
|
|
|
|
</revremark>
|
|
|
|
</revision>
|
|
|
|
|
|
|
|
|
|
|
|
<revision>
|
|
|
|
<revnumber>1.0</revnumber>
|
|
|
|
<date>2001-09-09</date>
|
|
|
|
<authorinitials>ig</authorinitials>
|
|
|
|
<revremark>
|
|
|
|
Added entries to the FAQ, corrected grammatical errors, and update a URL.
|
|
|
|
</revremark>
|
|
|
|
</revision>
|
|
|
|
|
|
|
|
<revision>
|
|
|
|
<revnumber>0.9</revnumber>
|
|
|
|
<date>2001-08-01</date>
|
|
|
|
<authorinitials>ig</authorinitials>
|
|
|
|
<revremark>
|
|
|
|
Initial release.
|
|
|
|
</revremark>
|
|
|
|
</revision>
|
|
|
|
</revhistory>
|
|
|
|
|
|
|
|
<abstract>
|
|
|
|
<para>
|
|
|
|
A guide to using Conexant and Rockwell chipset based Software modems under Linux.
|
|
|
|
</para>
|
|
|
|
</abstract>
|
|
|
|
|
|
|
|
</articleinfo>
|
|
|
|
|
|
|
|
<sect1 id="introduction">
|
|
|
|
<title>Introduction</title>
|
|
|
|
|
|
|
|
<sect2 id="purpose">
|
|
|
|
<title>Purpose of the howto</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If you've got a Rockwell or Conexant chipset based modem and you can't seem to get the modem to work with Linux, then you've come to the right place. Chances are that you've got a Software modem (also known as a "winmodem") and you'll need a driver to get the modem working under Linux.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If you've got a Software modem whose chipset is not made by Conexant or Rockwell then you should see the <ulink url="http://www.linuxdoc.org/HOWTO/Linmodem-HOWTO.html"><citetitle>linmodem howto</citetitle></ulink>.
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Note that this guide has no information about using Conexant/Rockwell modems for operating systems other then Linux except for the following: There are no known drivers for FreeBSD or BeOS, Windows drivers can be obtained from Conexant.
|
|
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
<sect2 id="about">
|
|
|
|
<title>About the howto</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
This HOWTO originally started out as a website about installing Conexant HSF modems under linux, but after several months of being online the number of hits on the website was rapidly growing (100 hits/day at time of writing this HOWTO) and so were the number of requests for information about Rockwell/Conexant modems that were being posted to the linmodem mailing list, usenet and various web based forums. This lead me to decide that the information needed another distribution medium which would be more accessible to users. The result of this was this HOWTO which has expanded to include a far larger range of information then the original website had, in order to cover all the questions being asked on the internet.</para>
|
|
|
|
<para> At the same time as the increase in demand for information about Rockwell/Conexant modems under linux a number of non-english webpages appeared explaining how to setup the drivers in languages as diverse as Portuguese and Japanese, these webpages often lacked all the current information which was available making it harder for users to get their modems to work. I decided to release this HOWTO under the GNU Free Documentation License, so that native speakers of other language can translate this document into their own language and redistribute it freely, thus ensuring that all users get all the information regardless of what language they speak. If you're interested in making a translation of this HOWTO please contact me.</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The HOWTO assumes a basic knowledge of Linux, you should be familiar with the basics of how to use a console/terminal, how to use common commands like less and be familiar with a text editor.When the howto needs you to type something in at the console, the console prompt will look like this: '<prompt>&pt;</prompt>'
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Some parts of the howto rely upon a greater knowledge of Linux, but those section will mainly apply if you have a non-standard Linux distribution.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
<sect2 id="feedback">
|
|
|
|
<title>Feedback</title>
|
|
|
|
<para>
|
|
|
|
If you have any feedback on how I can improve this HOWTO or are interested in translating this HOWTO into another language please contact me via email at <ulink url="mailto:ImranG@btinternet.com"><citetitle>ImranG@btinternet.com</citetitle></ulink>(if you don't get a reply within a week resend the message to <ulink url="mailto:imran@bits.bris.ac.uk"><citetitle>imran@bits.bris.ac.uk)</citetitle></ulink>.</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If you need some help in getting your modem to work, rather then contacting me for help directly see the <link linkend="getting-help">Getting Help section</link> as you are more likely to be able to get a faster answer from the places indicated then if you email me direct.
|
|
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
<sect2 id="licence">
|
|
|
|
<title>License</title>
|
|
|
|
<para>Copyright (c) 2001,2002 Imran Ghory</para>
|
|
|
|
<para>
|
|
|
|
Permission is granted to copy, distribute and/or modify this document
|
|
|
|
under the terms of the GNU Free Documentation License, Version 1.1
|
|
|
|
or any later version published by the Free Software Foundation;
|
|
|
|
with the Invariant Sections being the Introduction chapter, with no Front-Cover Texts, and with no Back-Cover Texts.
|
|
|
|
A copy of the license is included in the section entitled "GNU
|
|
|
|
Free Documentation License".
|
|
|
|
</para>
|
|
|
|
|
|
|
|
</sect2>
|
|
|
|
<sect2 id="acknowledgements">
|
|
|
|
<title>Acknowledgments</title>
|
|
|
|
<para>
|
|
|
|
Thanks to:</para>
|
|
|
|
<itemizedlist mark="opencircle">
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Olitec for distributing and Conexant for producing the original HSF driver
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Marc Boucher for writing a wrapper for 2.4.* kernels
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Denis Havlik for bringing the Olitec driver to the attention of the rest of the Linmodem community
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Thomas Iversen for mirroring the drivers
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</itemizedlist>
|
|
|
|
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
<sect2 id="getting-help">
|
|
|
|
<title>Getting Help</title>
|
|
|
|
<para>If after following this HOWTO you still can't get your modem to work and you haven't already done so, check the troubleshooting section at the end of this HOWTO as it covers the most common problems. If you are still stuck then there are three main places where you can get help,</para>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry><term>Linmodem mailing list</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The Linmodem mailing list is the main place on the internet for discussion of the use of Software modems under Linux. If someone else has had the same problem as you chances are that someone on the Linmodem mailing list knows about it. To join the mailing list send a blank email to <ulink url="mailto:discuss-subscribe@linmodems.org"><citetitle>discuss-subscribe@linmodems.org</citetitle></ulink>, the mailing lists homepage is at <ulink url="http://www.linmodems.org"><citetitle>www.linmodems.org</citetitle></ulink>.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>SoftModems IRC channel</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
If you want to talk to someone real time your best bet is the #SoftModems channel on the OpenProject's IRC network. See <ulink url="http://www.openprojects.org"><citetitle>www.openprojects.org</citetitle></ulink> for details or connect to eu.opirc.nu on port 6667.</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>Newsgroups</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The newsgroups <ulink url="news://comp.os.linux.hardware"><citetitle>comp.os.linux.hardware</citetitle></ulink> and <ulink url="news://comp.os.linux.setup"><citetitle>comp.os.linux.setup</citetitle></ulink> often have people familiar with software modems. If you speak Italian the newsgroup <ulink url="news://it.comp.os.linux.iniziare"><citetitle>it.comp.os.linux.iniziare</citetitle></ulink> has people familiar with Conexant/Rockwell neewsgroups.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
</variablelist>
|
|
|
|
<para>
|
|
|
|
Remember when asking for help to include your modems Device ID, Vendor ID and any error message you got.</para>
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
</sect1>
|
|
|
|
|
|
|
|
<sect1 id="quick-start">
|
|
|
|
<title>Quick Start guide</title>
|
|
|
|
<para> This section tries to get you up and running as soon as possible, if you can follow the steps given in this section and they work for you, you can ignore the rest of this howto. This section is updated more often then the rest of the HOWTO so will contain the most up to date information.</para>
|
|
|
|
|
|
|
|
<para>First you need to find out if your modem is an HSF or HCF modem. You can find out from your modem by looking at it's Windows drivers or looking at the label on it's chipset, or alternatively you can download the <ulink url="http://www.conexant.com/customer/md_driverassistance.html"><citetitle>ListModem</citetitle></ulink> utility and run it to get the information.
|
|
|
|
|
|
|
|
Drivers are available for both types, but the HSF driver is further into development then the HCF driver so is likely to be more advanced for now. Expect the HCF driver to come out of beta sometime mid-year(2002).
|
|
|
|
|
|
|
|
See the following appropriate sections for quick starting with HSF and HCF modems.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<sect2 id="quick-start-HSF">
|
|
|
|
<title>Quick Starting with an HSF modem</title>
|
|
|
|
|
|
|
|
<orderedlist numeration="arabic">
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Download the driver from <ulink url="http://www.mbsi.ca/hsflinux/"><citetitle>http://www.mbsi.ca/hsflinux/</citetitle></ulink>, the following instruction are for the Binary RPM version which I recommend you use.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Load up a terminal (or go to a console), change to the root user and enter the directory you downloaded the driver to and use the command "rpm -i" followed by the name of the driver. For instance if it is called
|
|
|
|
<filename>hsflinmodem-4.06.06.02mbsibeta02012000-1.i586.rpm</filename> you would enter,</para><para>
|
|
|
|
<prompt>&pt;</prompt><command>rpm -i hsflinmodem-4.06.06.02mbsibeta02012000-1.i586.rpm</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem><para>
|
|
|
|
Run the program <command>hsfconfig</command> and just follow the on-screen instructions and it should automatically detect your modem and install the driver. If you have any problems consult the documentation that comes with the driver.</para></listitem></orderedlist>
|
|
|
|
<para>You will now be able to setup your internet connection software, you may need to tell it that your modem can be found at <filename>/dev/modem</filename>. If your internet connection software can't access it you may need to change the permissions on it.</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
[Technical note: If you have a modem with device ID 2005, then you will need to choose the option to manually configure it before it will work]
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If the above steps don't work for you or the above mentioned driver doesn't work with your system (for instance if you have an SMP machine) then read the rest of the howto which explains how to use the older driver in greater detail.
|
|
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
|
|
|
|
<sect2 id="quick-start-HCF">
|
|
|
|
<title>Quick Starting with an HCF modem</title>
|
|
|
|
<orderedlist numeration="arabic">
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Download the driver from <ulink url="http://www.mbsi.ca/hcflinux/"><citetitle>http://www.mbsi.ca/hcflinux/</citetitle></ulink>, the following instruction are for the Binary RPM driver which is the easiest to install, if you want to install it using another method consult the README file.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Load up a terminal (or go to a console), change to the root user and enter the directory you downloaded the driver to and use the command "rpm -i" followed by the name of the driver. For instance if it is called
|
|
|
|
<filename>hcflinmodem-0.9mbsibeta02030801-1.i586.rpm</filename> you would enter,</para><para>
|
|
|
|
<prompt>&pt;</prompt><command>rpm -i hcflinmodem-0.9mbsibeta02030801-1.i586.rpm</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Run the program <command>hcfconfig</command> and just follow the on-screen instructions and it should automatically detect your modem and install the driver. If you have any problems consult the documentation that comes with the driver.</para></listitem>
|
|
|
|
</orderedlist>
|
|
|
|
<para>You will now be able to setup your internet connection software, you may need to tell it that your modem can be found at <filename>/dev/modem</filename>. If your internet connection software can't access it you may need to change the permissions on it.</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
[Technical note: If you have an older modem, i.e one with the Rockwell brand name rather then Conexant then you will not be able to use this driver at present. You will also not be able to use modems which use SmartDAA. See <ulink url="http://www.mbsi.ca/hcflinux/latest/BUGS.txt"><citetitle>http://www.mbsi.ca/hcflinux/latest/BUGS.txt</citetitle></ulink> for updates.]
|
|
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
</sect1>
|
|
|
|
|
|
|
|
<sect1 id="getting-started">
|
|
|
|
<title>Identifying your modem type</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The first task you will need to do is to identify whether your modem's chipset is HCF or HSF. Unfortunately the traditional way of doing this (by using /proc/pci, lspci or KDE's control center) won't work for us here due to errors in the pci.ids file which can cause a misidentification of the modem. There are three main ways which you can use to identify your modem's chipset:
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<orderedlist numeration="arabic">
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
If you've got your modem working under Windows then you can identify your chipset by downloading and running <ulink url="http://www.conexant.com/customer/md_driverassistance.html"><citetitle>Conexant's ListModem Application</citetitle></ulink>. When you run it, the program will give the information we want under "MODEM TYPE".
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
If you've opened your computer up chances are that the modem's chipset will have either the letters "HSF" or "HCF" printed on it.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
You can identify your type of modem from it's device ID and vendor ID, the easiest way get this information is from the command <command>lspci -n</command> (or <command>less /proc/pci</command> on older Linux distributions) this command tells you all of the Vendor IDs and Devices IDs for all of the PCI cards in your machine. You will be able to identify your modems' IDs as it will have a vendor ID of either 14F1 (Conexant) or 127A (Rockwell). Ignore any information that the lspci command tells you about your modem being a HSF or HCF as it could be wrong.
|
|
|
|
</para>
|
|
|
|
<para>The information is often presented in the form VVVV:DDDD where VVVV is the vendor ID and DDDD is the device ID, for instance if it listed 127a:2005 it would mean the that the Vendor ID is 127a and device ID is 2005.</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If your modem is a HCF modem it will have one of the following Device IDs:
|
|
|
|
</para><para>
|
|
|
|
1033 / 1034 / 1035 / 1036 / 10b3 / 10b4 / 10b5 / 10b6 / 1003 / 1004 / 1005 / 1023 / 1024 / 1025 / 1f10 / 1f11 / 1f14 / 1f15
|
|
|
|
</para><para>
|
|
|
|
If your modem is a SmartHCF modem it will have one of the following Device IDs:
|
|
|
|
</para><para>
|
|
|
|
1052 / 1053 / 1054 / 1055 / 1056 / 1057 / 1058 / 1059 / 1063 / 1064 / 1065 / 1066
|
|
|
|
</para><para>
|
|
|
|
If your modem is a HSF modem it will have one of the following Device IDs:
|
|
|
|
</para><para>
|
|
|
|
2013 / 2014 / 2015 / 2016 / 2003 / 2004 / 2005 / 2006 / 2f10 / 2f12 / 2f00
|
|
|
|
</para><para>
|
|
|
|
If your modem is a SmartHSF modem it will have one of the following Device IDs:
|
|
|
|
</para><para>
|
|
|
|
2043 / 2044 / 2045 / 2046 / 2053 / 2054 / 2055 / 2056
|
|
|
|
</para>
|
|
|
|
|
|
|
|
</listitem>
|
|
|
|
</orderedlist>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If you have a HCF or SmartHCF modem goto to the <link linkend="hcf">HCF section</link>, if you have a HSF or SmartHSF modem go the to the <link linkend="hsf">HSF section</link>.
|
|
|
|
</para>
|
|
|
|
</sect1>
|
|
|
|
|
|
|
|
<sect1 id="hcf">
|
|
|
|
<title>HCF chipset based modems</title>
|
|
|
|
<sect2 id="hcf-history">
|
|
|
|
<title>History</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Unfortunately at the present time there is no HCF modem driver for linux. Conexant have indicated in section 11 of their FAQ (<ulink url="http://www.conexant.com:80/cnxt/customer/md_faqs.htm"><citetitle>http://www.conexant.com:80/cnxt/customer/md_faqs.htm</citetitle></ulink>) that they are currently developing one.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Several people have reported that they have got a HCF modem (in particular chipsets with the device ID of 1025) to work under Linux by using the HSF driver, however little firm information is known about this. If you successfully manage to use an HCF modem under linux please contact me to tell me about it.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
One person has reported that if you get the "No Dialtone" error when trying to use a HSF driver with a HCF modem you can correct it by using the AT command "AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0".
|
|
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
<sect2 id="misc-hcf">
|
|
|
|
<title>Miscellaneous information</title>
|
|
|
|
<para>
|
|
|
|
If you wish to embark on writing your own driver you might find the following files useful,
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>Information on how to edit the INF file</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
<ulink url="http://users.freenet.am/~hcfconf/advdocs/country.zip"><citetitle>http://users.freenet.am/~hcfconf/advdocs/country.zip</citetitle></ulink>
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>Modem command guide</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
<ulink url="http://users.freenet.am/~hcfconf/advdocs/100498C.zip"><citetitle>http://users.freenet.am/~hcfconf/advdocs/100498C.zip</citetitle></ulink>
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>Designers notes and specifications</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
<ulink url="http://www.unitronic.de/Hersteller/conexant/Modem.htm"><citetitle>http://www.unitronic.de/Hersteller/conexant/Modem.htm
|
|
|
|
</citetitle>
|
|
|
|
</ulink></para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
|
|
|
|
</sect2>
|
|
|
|
</sect1>
|
|
|
|
|
|
|
|
<sect1 id="hsf">
|
|
|
|
<title>HSF</title>
|
|
|
|
<sect2 id="hsf-history">
|
|
|
|
<title>History</title>
|
|
|
|
<para>
|
|
|
|
A HSF driver first appeared out of the blue in mid-2000 when Olitec released unto the world a binary only driver for their Olitec PCI modem for 2.2.14 kernel, it wasn't long before someone realized that the Olitec modem was based on the Rockwell/Conexant HSF Chipset. Inquiries to Olitec revealed that the driver should work with any HSF chipset as there was nothing in the driver that was specific to the Olitec modems. Many people tried to get the driver to work with non-Olitec modem unfortunately without success, however a few months later and after many hours of work by many people trying a variety of tricks to get the driver to work, several people managed to stumble across the solution. It was a simple one line change to file which solved the problem and the world was left with a working HSF driver, at the time it only worked on 2.2.14 Kernels and Olitec had refused to release the source code to let others try to get it to work with other kernels.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
A few months later Olitec released the driver for 2.2.16 and 2.2.17 kernels, this kept the HSF winmodem community satisfied until we came to the day when the 2.4 kernel was released. None of the previous drivers appeared to work with the 2.4 kernel and this caused problems for all those who wanted to upgrade and also for the large number of new users who were using 2.4.* kernel based distributions such as Mandrake 8 and RedHat 7.1. Not a word had been heard out of Olitec since the 2.4 kernel was released, but Conexant had announced that they intended to develop a Linux driver. After many months of waiting for a 2.4.* driver Marc Boucher decided to something about it and wrote a wrapper which allowed an old version of the driver to be used with 2.4.* kernels.
|
|
|
|
</para><para>
|
|
|
|
That's where we are now, Marc's wrapper is still in experimental development stage but it works and many people are using it to connect to the internet under Linux.
|
|
|
|
</para><para>
|
|
|
|
From the history you'll understand why the next section has to be split into two sections one for 2.2.14 - 2.2.18 kernels and one for 2.4.* kernels. If you don't know what kernel version you have you can find out by using the '<command>uname -r</command>' command at the console window before proceeding to the appropriate section of this HOWTO.
|
|
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
<sect2 id="kernel14-18">
|
|
|
|
<title>Kernel 2.2.14 - 18</title>
|
|
|
|
<sect3 id="requirements">
|
|
|
|
<title>Requirements</title>
|
|
|
|
<para>
|
|
|
|
Having either a 2.2.14, 2.2.16 or 2.2.17 kernel.
|
|
|
|
|
|
|
|
It has been reported that the driver for 2.2.17 kernels also works with 2.2.18 kernels.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
<sect3 id="hsf-getting-ids">
|
|
|
|
<title>Getting IDs</title>
|
|
|
|
<para>
|
|
|
|
To get the modem to work you'll need to get the Vendor ID and Device ID. The easiest way to do this is to use the command "<command>less /proc/pci</command>" and scroll until you find the PCI card which has a vendor ID of either 14F1 (Conexant) or 127A (Rockwell) and note the Device ID.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
You'll need to make an %HSFModem% line.
|
|
|
|
</para><para>
|
|
|
|
Copy down the following line somewhere,
|
|
|
|
</para><para>
|
|
|
|
%HSFModem% = ModemX, PCI\VEN_XXXX&DEV_YYYY&SUBSYS_YYYYXXXX
|
|
|
|
</para><para>
|
|
|
|
Replacing the XXXX's with your Vendor ID and the YYYY's with your Device ID, so if your Vendor ID is 127A and Device ID is 2015 your line would be,
|
|
|
|
</para><para>
|
|
|
|
%HSFModem% = ModemX, PCI\VEN_127A&DEV_2015&SUBSYS_2015127A
|
|
|
|
</para><para>You'll need to use this line later on to allow the driver to detect your modem, the next steps you need to take vary slightly depending on what kernel you have so you'll need to refer to the appropriate section depending on whether your kernel version is <link linkend="kernel-14">2.2.14</link>, <link linkend="kernel-16">2.2.16</link> or <link linkend="kernel-17">2.2.17</link></para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="kernel-14">
|
|
|
|
<title>If you have a 2.2.14 kernel</title>
|
|
|
|
|
|
|
|
<orderedlist>
|
|
|
|
<title>Installing a HSF driver on a 2.2.14 kernel</title>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Download the file HSF_V1.01.02_K2.2.14-5.0.tar, it can be obtained from <ulink url="http://www.olitec.com/pub/HSF_V1.01.02_K2.2.14-5.0.tar"><citetitle>Olitec's site</citetitle></ulink> or the
|
|
|
|
<ulink url="ftp://ftp.dina.kvl.dk/pub/Staff/Thomas.S.Iversen/linmodems_drivers/olitec/HSF_V1.01.02_K2.2.14-5.0.tar"><citetitle>mirror</citetitle></ulink>.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Copy it to your home directory </para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>In a console window change to your home directory</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>cd ~</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Decompress the file</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>tar xzvf HSF_V1.01.02_K2.2.14-5.0.tar</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Enter into the drivers directory</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>cd pci_56k_v2</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Load up the lin_hsf.inf file in your favorite text editor, under the section [generic] you'll see a few of lines like "%HSFModem% = ModemX, PCI\VEN_127A&DEV_1025&SUBSYS_1025127A" under theses lines add your own %HSFModem% line which you made earlier.</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Switch to root</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>su</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Run the ins_all script to install the driver</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>./ins_all</command></para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
</orderedlist>
|
|
|
|
<para>You will now be able to access the internet by telling your dial-up software that your modem is located at /dev/modem.</para>
|
|
|
|
|
|
|
|
<para>The ins_all will only temporarily load the modem driver and the modem driver will be removed when you reboot. So if you re
|
|
|
|
boot you will need to run the ./ins_all program to reload the driver, if you reboot on a regular basis you may want to set the .
|
|
|
|
/ins_all command to automatically run every time your computer loads up.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
|
|
|
Copy it to your home directory and use the following command tar xzvf HSF_V1.01.02_K2.2.14-5.0.tar
|
|
|
|
|
|
|
|
cd pci_56k_v2
|
|
|
|
|
|
|
|
Load up the lin_hsf.inf file in your favourite text editor, under the section [generic] you'll see a few of lines like "%HSFModem% = ModemX, PCI\VEN_127A&DEV_1025&SUBSYS_1025127A" under theses lines add your own %HSFModem% line which you made eariler.
|
|
|
|
|
|
|
|
Switch to root
|
|
|
|
|
|
|
|
enter ./ins_all and the modem should install itself.
|
|
|
|
|
|
|
|
You will now be able to access the internet by telling your dial-up software that your modem is located at /dev/modem.
|
|
|
|
|
|
|
|
The ins_all will only temporarily load the modem driver and the modem driver will be removed when you reboot. So if you reboot you will need to run the ./ins_all program to reload the driver, if you reboot on a regular basis you may want to set the ./ins_all command to automatically run every time your computer loads up.
|
|
|
|
|
|
|
|
Errors
|
|
|
|
|
|
|
|
When running ./ins_all I get a kernel mismatch error ?
|
|
|
|
|
|
|
|
This means that the driver thinks that you don't have a 2.2.14 kernel, if you have a variant of the 2.2.14 kernel (such as the one that comes with Mandrake 7) then you can still get the driver to work by loading up the file ins_all in a text editor and replacing all of the "insmod -m" commands with "insmod -f -m".
|
|
|
|
|
|
|
|
When installing the driver when it tries to load myserial.o I get a segmentation fault ?
|
|
|
|
|
|
|
|
This is caused by your computer trying to get Plug-and-Play to work with your modem. You can stop it doing this by going to your BIOS and setting an option which tells it not to do that. The settings name varies from BIOS to BIOS but is normally something like PnP OS.
|
|
|
|
|
|
|
|
After installing the driver my Laptop's modem doesn't seem to work ?
|
|
|
|
|
|
|
|
Sometime this is caused by a device conflict, you can correct it by editing the ins_all script by finding the line "mknod /dev/cnxt0 c 254 64" and replacing it with "mknod /dev/cnxt0 c 253 64"
|
|
|
|
</para>
|
|
|
|
-->
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="kernel-16">
|
|
|
|
<title>If you have a 2.2.16 kernel</title>
|
|
|
|
|
|
|
|
<orderedlist>
|
|
|
|
<title>Installing a HSF driver on a 2.2.16 kernel</title>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Download the file PCI_56K_V2_K2.2.16.tar.gz, it can be obtained from <ulink url="http://www.olitec.com/pub/PCI_56K_V2_K2.2.16.tar.gz"><citetitle>Olitec's site</citetitle></ulink> or the
|
|
|
|
<ulink url="ftp://ftp.dina.kvl.dk/pub/Staff/Thomas.S.Iversen/linmodems_drivers/olitec/PCI_56K_V2_K2.2.16.tar.gz"><citetitle>Mirror</citetitle></ulink>.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Copy it to your home directory </para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>In a console window change to your home directory</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>cd ~</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Decompress the file</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>tar xzvf PCI_56K_V2_K2.2.16.tar.gz</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Enter into the drivers directory</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>cd pci_56k_v2_k2.2.16</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Load up the lin_hsf.inf file in your favorite text editor, under the section [generic] you'll see a few of lines like "%HSFModem% = ModemX, PCI\VEN_127A&DEV_1025&SUBSYS_1025127A" under theses lines add your own %HSFModem% line which you made earlier.</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Switch to root</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>su</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Run the ins_all script to install the driver</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>./ins_all</command></para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
</orderedlist>
|
|
|
|
|
|
|
|
<para>You will now be able to access the internet by telling your dial-up software that your modem is located at /dev/modem.</para>
|
|
|
|
|
|
|
|
<para>The ins_all will only temporarily load the modem driver and the modem driver will be removed when you reboot. So if you reboot you will need to run the ./ins_all program to reload the driver, if you reboot on a regular basis you may want to set the ./ins_all command to automatically run every time your computer loads up.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="kernel-17">
|
|
|
|
<title>If you have a 2.2.17 or 2.2.18 kernel</title>
|
|
|
|
|
|
|
|
<orderedlist>
|
|
|
|
<title>Installing a HSF driver on a 2.2.17 or 2.2.18 kernel</title>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Download the file PCI_56K_V2_K2.2.17.tar.gz , it can be obtained from <ulink url="http://www.olitec.com/pub/PCI_56K_V2_K2.2.17.tar.gz"><citetitle>Olitec's site</citetitle></ulink> or the
|
|
|
|
<ulink url="ftp://ftp.dina.kvl.dk/pub/Staff/Thomas.S.Iversen/linmodems_drivers/olitec/PCI_56K_V2_K2.2.17.tar.gz"><citetitle>Mirror</citetitle></ulink>.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Copy it to your home directory </para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>In a console window change to your home directory</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>cd ~</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Decompress the file</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>tar xzvf PCI_56K_V2_K2.2.17.tar.gz</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Enter into the drivers directory</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>cd pci_56k_v2_k2.2.17</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Load up the lin_hsf.inf file in your favorite text editor, under the section [generic] you'll see a few of lines like "%HSFModem% = ModemX, PCI\VEN_127A&DEV_1025&SUBSYS_1025127A" under theses lines add your own %HSFModem% line which you made earlier.</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Switch to root</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>su</command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
|
|
|
|
<para>Run the ins_all script to install the driver</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>./ins_all</command></para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
</orderedlist>
|
|
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
<para>
|
|
|
|
Download the file PCI_56K_V2_K2.2.17.tar.gz from:
|
|
|
|
http://olitec.com/pub/PCI_56K_V2_K2.2.17.tar.gz
|
|
|
|
|
|
|
|
Mirror:
|
|
|
|
ftp://ftp.dina.kvl.dk/pub/Staff/Thomas.S.Iversen/linmodems_drivers/olitec/PCI_56K_V2_K2.2.17.tar.gz
|
|
|
|
|
|
|
|
Copy it to your home directory and use the following command tar xzvf PCI_56K_V2_K2.2.17.tar.gz
|
|
|
|
|
|
|
|
cd pci_56k_v2_k2.2.17
|
|
|
|
|
|
|
|
Load up the lin_hsf.inf file in your favorite text editor, under the section [generic] you'll see a few of lines like "%HSFModem% = ModemX, PCI\VEN_127A&DEV_1025&SUBSYS_1025127A" under theses lines add your own %HSFModem% line which you made earlier.
|
|
|
|
|
|
|
|
Switch to root
|
|
|
|
|
|
|
|
enter ./ins_all and the modem should install itself.
|
|
|
|
-->
|
|
|
|
<para>
|
|
|
|
You will now be able to access the internet by telling your dial-up software that your modem is located at /dev/modem.
|
|
|
|
</para><para>
|
|
|
|
The ins_all will only temporarily load the modem driver and the modem driver will be removed when you reboot. So if you reboot you will need to run the ./ins_all program to reload the driver, if you reboot on a regular basis you may want to set the ./ins_all command to automatically run every time your computer loads up.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
</sect3>
|
|
|
|
</sect2>
|
|
|
|
|
|
|
|
<sect2 id="kernel4-series">
|
|
|
|
<title>Kernel 2.4.*</title>
|
|
|
|
<sect3 id="hsf-24-requirements">
|
|
|
|
<title>Requirements</title>
|
|
|
|
|
|
|
|
<itemizedlist mark="opencircle">
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
You need a 2.4.* kernel which does not have SMP support.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
You will also need to have your kernel source available, if you don't have them installed already you can probably find them on your distributions CD.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
At least version 2.4.0 of ppp (you can find what version of ppp you have installed by using the command <command>pppd --version</command>)
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
|
|
|
|
</itemizedlist>
|
|
|
|
<para>To get the modem working under a 2.4.* kernel you'll need to use the driver intended for 2.2.17 kernels alongside Marc Boucher's hsfcompat wrapper program which lets the driver work with 2.4.* kernels. At the time of writing the hsfcompat driver is on version 1.0d and is still experimental and may cause problem with your system. However I haven't seen anyone have any problem from using the wrapper. For the latest details see <ulink url="http://www.mbsi.ca/hsfcompat/"><citetitle>hsfcompat's homepage</citetitle></ulink>.</para>
|
|
|
|
|
|
|
|
<variablelist><title>Files you'll need to download:</title>
|
|
|
|
<varlistentry><term><filename>hsfcompat_24-1.0d.tar.gz</filename></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Main download site:
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
<ulink url="http://www.mbsi.ca/hsfcompat/hsfcompat_24-1.0d.tar.gz"><citetitle>http://www.mbsi.ca/hsfcompat/hsfcompat_24-1.0d.tar.gz</citetitle></ulink></para><para></para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><filename>PCI_56K_V2_K2.2.17.tar.gz</filename></term>
|
|
|
|
<listitem>
|
|
|
|
<para>Main download site:</para>
|
|
|
|
<para><ulink url="http://www.olitec.com/pub/PCI_56K_V2_K2.2.17.tar.gz"><citetitle>http://www.olitec.com/pub/PCI_56K_V2_K2.2.17.tar.gz</citetitle></ulink></para>
|
|
|
|
<para>Mirrored at:</para>
|
|
|
|
<para>
|
|
|
|
<ulink url="ftp://ftp.dina.kvl.dk/pub/Staff/Thomas.S.Iversen/linmodems_drivers/olitec/PCI_56K_V2_K2.2.17.tar.gz"><citetitle>ftp://ftp.dina.kvl.dk/pub/Staff/Thomas.S.Iversen/linmodems_drivers/olitec/PCI_56K_V2_K2.2.17.tar.gz</citetitle></ulink></para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
|
|
|
|
</sect3>
|
|
|
|
<sect3 id="hsf-24-installing">
|
|
|
|
<title>Installing</title>
|
|
|
|
|
|
|
|
|
|
|
|
<orderedlist>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>Copy the <filename>hsfcompat_24-1.0d.tar.gz</filename> file to your home directory</para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>In a console window change to your home directory</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>cd ~</command></para>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>Extract the hcfcompat program by using:</para>
|
|
|
|
<para><prompt>&pt;</prompt><command>tar xzvf <filename>hsfcompat_24-1.0d.tar.gz</filename></command></para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Copy the <filename>PCI_56K_V2_K2.2.17.tar.gz</filename> file into the <filename class="directory">hsfcompat_24-1.0d</filename> directory.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Extract the driver by using: </para>
|
|
|
|
<para>
|
|
|
|
<prompt>&pt;</prompt><command>tar xzvf <filename>PCI_56K_V2_K2.2.17.tar.gz</filename></command>
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Load up the file <filename>Makefile</filename> (Found in the <filename class="directory">hsfcompat_24-1.0d</filename> directory) in a text editor and scroll down to the line which reads SBINDIR=/usr/sbin and replace <filename class="directory">/usr/sbin</filename> with the location of your system bin directory, then scroll down to the line which reads KERNELSRC=/usr/src/linux and replace <filename class="directory">/usr/src/linux</filename> with the location of your kernel source files.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Switch to superuser (root) by using: </para>
|
|
|
|
<para><prompt>&pt;</prompt><command>su</command>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
In the <filename class="directory">hsfcompat_24-1.0d</filename> directory compile hsfcompat by using:</para>
|
|
|
|
<para>
|
|
|
|
<prompt>&pt;</prompt>
|
|
|
|
<command>
|
|
|
|
make</command>
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>Install the driver by running:
|
|
|
|
<prompt>&pt;</prompt><command>make <parameter>install</parameter></command>
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Follow the on-screen instruction which explain how to load the driver into memory and how to have this done automatically.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</orderedlist>
|
|
|
|
|
|
|
|
</sect3>
|
|
|
|
</sect2>
|
|
|
|
<sect2 id="faq">
|
|
|
|
<title>Troubleshooting FAQ</title>
|
|
|
|
|
|
|
|
<qandaset>
|
|
|
|
<qandaentry>
|
|
|
|
<question>
|
|
|
|
<para>
|
|
|
|
When running ./ins_all I get a kernel mismatch error ?
|
|
|
|
</para>
|
|
|
|
</question>
|
|
|
|
<answer>
|
|
|
|
<para>
|
|
|
|
This means that the driver thinks that you don't have the appropriate kernel version, if you have a variant of the kernel (such as the one that has non-standard name) then you can still get the driver to work by loading up the file <filename>ins_all</filename> in a text editor and replacing all of the '<command>insmod -m</command>' commands with '<command>insmod -f -m</command>'.
|
|
|
|
</para>
|
|
|
|
</answer>
|
|
|
|
</qandaentry>
|
|
|
|
|
|
|
|
<qandaentry>
|
|
|
|
<question>
|
|
|
|
<para>
|
|
|
|
When I try to run ./ins_all I get the error "bash: ./ins_all No such file or directory."</para>
|
|
|
|
</question>
|
|
|
|
<answer>
|
|
|
|
<para>
|
|
|
|
This error tends to be caused by the script being unable to find C Shell at the location <filename class="directory">/bin/csh</filename>. If you have C Shell installed in a different location then you should create a symbolic link which points to the correct location. If you don't have you'll need to install it.
|
|
|
|
</para>
|
|
|
|
</answer>
|
|
|
|
</qandaentry>
|
|
|
|
|
|
|
|
<qandaentry>
|
|
|
|
<question>
|
|
|
|
<para>
|
|
|
|
When installing the driver when it tries to load <filename>myserial.o</filename> I get a segmentation fault ?
|
|
|
|
</para>
|
|
|
|
</question>
|
|
|
|
<answer>
|
|
|
|
<para>
|
|
|
|
This is caused by your computer trying to get Plug-and-Play to work with your modem. You can stop it doing this by going to your BIOS and setting an option which tells it not to do that. The settings name varies from BIOS to BIOS but is normally something like PnP OS.
|
|
|
|
</para>
|
|
|
|
</answer>
|
|
|
|
</qandaentry>
|
|
|
|
|
|
|
|
<qandaentry>
|
|
|
|
<question>
|
|
|
|
<para>
|
|
|
|
When trying to dial my ISP I get "No Carrier" error ?
|
|
|
|
</para>
|
|
|
|
</question>
|
|
|
|
<answer>
|
|
|
|
<para>
|
|
|
|
It has been reported that making the following changes to your configuration will work:
|
|
|
|
</para>
|
|
|
|
<orderedlist>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Replace the command ATZ with ATZX3
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Replace the command ATDT with ATX3DT
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</orderedlist>
|
|
|
|
</answer>
|
|
|
|
</qandaentry>
|
|
|
|
|
|
|
|
<qandaentry>
|
|
|
|
<question>
|
|
|
|
<para>
|
|
|
|
When running ./ins_alI get the error "No matching INF file is found for SoftK56 PCI device" ?
|
|
|
|
</para>
|
|
|
|
</question>
|
|
|
|
<answer>
|
|
|
|
<para>
|
|
|
|
This occurs when the driver can't find the correct %HSFModem% line in the lin_hsf.inf line, go back through the instructions and make sure that you didn't make a mistake when making or entering the %HSFModem% line.
|
|
|
|
</para>
|
|
|
|
</answer>
|
|
|
|
</qandaentry>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<qandaentry>
|
|
|
|
<question>
|
|
|
|
<para>
|
|
|
|
On my Laptop the driver seemed to install fine but I can't access my modem on /dev/modem ?
|
|
|
|
</para>
|
|
|
|
</question>
|
|
|
|
<answer>
|
|
|
|
<para>
|
|
|
|
This is often caused by the modem's device number clashing with that of PCMCIA, you can check if this is the case by entering the command,</para>
|
|
|
|
<para>&pt;<command>ls -l /dev/ | grep 254</command></para>
|
|
|
|
<para>You'll see the hsf0 device listed with the major number of 254, if any other device also has the major number of 254 it means there is a clash. You can fix this problem by loading up the ins_all file and change the line which reads "mknod /dev/cnxt c 254 64" to "mknod /dev/cnxt c 253 64".
|
|
|
|
</para>
|
|
|
|
</answer>
|
|
|
|
</qandaentry>
|
|
|
|
</qandaset>
|
|
|
|
</sect2>
|
|
|
|
</sect1>
|
|
|
|
|
|
|
|
<appendix id="fdl-app">
|
|
|
|
|
|
<appendixinfo>
|
|
|
|
<releaseinfo>
|
|
|
|
Version 1.1, March 2000
|
|
|
|
</releaseinfo>
|
|
|
|
|
|
|
|
<copyright>
|
|
|
|
<year>2000</year><holder>Free Software Foundation, Inc.</holder>
|
|
|
|
</copyright>
|
|
|
|
|
|
|
|
<legalnotice id="legalnotice">
|
|
|
|
<para>
|
|
|
|
<address>Free Software Foundation, Inc.
|
|
|
|
<street>59 Temple Place, Suite 330</street>,
|
|
|
|
<city>Boston</city>,
|
|
|
|
<state>MA</state> <postcode>02111-1307</postcode>
|
|
|
|
<country>USA</country></address>. Everyone is permitted to
|
|
|
|
copy and distribute verbatim copies of this license
|
|
|
|
document, but changing it is not allowed.
|
|
|
|
</para>
|
|
|
|
</legalnotice>
|
|
|
|
</appendixinfo>
|
|
|
|
<title>License</title>
|
|
|
|
|
|
<sect1 id="fdl">
|
|
<title>GNU Free Documentation License</title>
|
|
|
|
<sect2>
|
|
|
|
|
|
|
|
<title>GNU Free Documentation License</title>
|
|
|
|
<para>Copyright 2000 Free Software Foundation, Inc.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
<address>Free Software Foundation, Inc.
|
|
|
|
<street>59 Temple Place, Suite 330</street>,
|
|
|
|
<city>Boston</city>,
|
|
|
|
<state>MA</state> <postcode>02111-1307</postcode>
|
|
|
|
<country>USA</country></address>. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. </para>
|
|
|
|
<sect3 id="fdl-preamble">
|
|
|
|
<title>0. PREAMBLE</title>
|
|
|
|
<para>
|
|
|
|
The purpose of this License is to make a manual, textbook, or
|
|
|
|
other written document <quote>free</quote> in the sense of
|
|
|
|
freedom: to assure everyone the effective freedom to copy and
|
|
|
|
redistribute it, with or without modifying it, either
|
|
|
|
commercially or noncommercially. Secondarily, this License
|
|
|
|
preserves for the author and publisher a way to get credit for
|
|
|
|
their work, while not being considered responsible for
|
|
|
|
modifications made by others.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
This License is a kind of <quote>copyleft</quote>, which means
|
|
|
|
that derivative works of the document must themselves be free in
|
|
|
|
the same sense. It complements the GNU General Public License,
|
|
|
|
which is a copyleft license designed for free software.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
We have designed this License in order to use it for manuals for
|
|
|
|
free software, because free software needs free documentation: a
|
|
|
|
free program should come with manuals providing the same
|
|
|
|
freedoms that the software does. But this License is not limited
|
|
|
|
to software manuals; it can be used for any textual work,
|
|
|
|
regardless of subject matter or whether it is published as a
|
|
|
|
printed book. We recommend this License principally for works
|
|
|
|
whose purpose is instruction or reference.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
<sect3 id="fdl-section1">
|
|
|
|
<title>1. APPLICABILITY AND DEFINITIONS</title>
|
|
|
|
<para id="fdl-document">
|
|
|
|
This License applies to any manual or other work that contains a
|
|
|
|
notice placed by the copyright holder saying it can be
|
|
|
|
distributed under the terms of this License. The
|
|
|
|
<quote>Document</quote>, below, refers to any such manual or
|
|
|
|
work. Any member of the public is a licensee, and is addressed
|
|
|
|
as <quote>you</quote>.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para id="fdl-modified">
|
|
|
|
A <quote>Modified Version</quote> of the Document means any work
|
|
|
|
containing the Document or a portion of it, either copied
|
|
|
|
verbatim, or with modifications and/or translated into another
|
|
|
|
language.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para id="fdl-secondary">
|
|
|
|
A <quote>Secondary Section</quote> is a named appendix or a
|
|
|
|
front-matter section of the <link
|
|
|
|
linkend="fdl-document">Document</link> that deals exclusively
|
|
|
|
with the relationship of the publishers or authors of the
|
|
|
|
Document to the Document's overall subject (or to related
|
|
|
|
matters) and contains nothing that could fall directly within
|
|
|
|
that overall subject. (For example, if the Document is in part a
|
|
|
|
textbook of mathematics, a Secondary Section may not explain any
|
|
|
|
mathematics.) The relationship could be a matter of historical
|
|
|
|
connection with the subject or with related matters, or of
|
|
|
|
legal, commercial, philosophical, ethical or political position
|
|
|
|
regarding them.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para id="fdl-invariant">
|
|
|
|
The <quote>Invariant Sections</quote> are certain <link
|
|
|
|
linkend="fdl-secondary"> Secondary Sections</link> whose titles
|
|
|
|
are designated, as being those of Invariant Sections, in the
|
|
|
|
notice that says that the <link
|
|
|
|
linkend="fdl-document">Document</link> is released under this
|
|
|
|
License.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para id="fdl-cover-texts">
|
|
|
|
The <quote>Cover Texts</quote> are certain short passages of
|
|
|
|
text that are listed, as Front-Cover Texts or Back-Cover Texts,
|
|
|
|
in the notice that says that the <link
|
|
|
|
linkend="fdl-document">Document</link> is released under this
|
|
|
|
License.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para id="fdl-transparent">
|
|
|
|
A <quote>Transparent</quote> copy of the <link
|
|
|
|
linkend="fdl-document"> Document</link> means a machine-readable
|
|
|
|
copy, represented in a format whose specification is available
|
|
|
|
to the general public, whose contents can be viewed and edited
|
|
|
|
directly and straightforwardly with generic text editors or (for
|
|
|
|
images composed of pixels) generic paint programs or (for
|
|
|
|
drawings) some widely available drawing editor, and that is
|
|
|
|
suitable for input to text formatters or for automatic
|
|
|
|
translation to a variety of formats suitable for input to text
|
|
|
|
formatters. A copy made in an otherwise Transparent file format
|
|
|
|
whose markup has been designed to thwart or discourage
|
|
|
|
subsequent modification by readers is not Transparent. A copy
|
|
|
|
that is not <quote>Transparent</quote> is called
|
|
|
|
<quote>Opaque</quote>.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Examples of suitable formats for Transparent copies include
|
|
|
|
plain ASCII without markup, Texinfo input format, LaTeX input
|
|
|
|
format, SGML or XML using a publicly available DTD, and
|
|
|
|
standard-conforming simple HTML designed for human
|
|
|
|
modification. Opaque formats include PostScript, PDF,
|
|
|
|
proprietary formats that can be read and edited only by
|
|
|
|
proprietary word processors, SGML or XML for which the DTD
|
|
|
|
and/or processing tools are not generally available, and the
|
|
|
|
machine-generated HTML produced by some word processors for
|
|
|
|
output purposes only.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para id="fdl-title-page">
|
|
|
|
The <quote>Title Page</quote> means, for a printed book, the
|
|
|
|
title page itself, plus such following pages as are needed to
|
|
|
|
hold, legibly, the material this License requires to appear in
|
|
|
|
the title page. For works in formats which do not have any title
|
|
|
|
page as such, <quote>Title Page</quote> means the text near the
|
|
|
|
most prominent appearance of the work's title, preceding the
|
|
|
|
beginning of the body of the text.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="fdl-section2">
|
|
|
|
<title>2. VERBATIM COPYING</title>
|
|
|
|
<para>
|
|
|
|
You may copy and distribute the <link
|
|
|
|
linkend="fdl-document">Document</link> in any medium, either
|
|
|
|
commercially or noncommercially, provided that this License, the
|
|
|
|
copyright notices, and the license notice saying this License
|
|
|
|
applies to the Document are reproduced in all copies, and that
|
|
|
|
you add no other conditions whatsoever to those of this
|
|
|
|
License. You may not use technical measures to obstruct or
|
|
|
|
control the reading or further copying of the copies you make or
|
|
|
|
distribute. However, you may accept compensation in exchange for
|
|
|
|
copies. If you distribute a large enough number of copies you
|
|
|
|
must also follow the conditions in <link
|
|
|
|
linkend="fdl-section3">section 3</link>.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
You may also lend copies, under the same conditions stated
|
|
|
|
above, and you may publicly display copies.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="fdl-section3">
|
|
|
|
<title>3. COPYING IN QUANTITY</title>
|
|
|
|
<para>
|
|
|
|
If you publish printed copies of the <link
|
|
|
|
linkend="fdl-document">Document</link> numbering more than 100,
|
|
|
|
and the Document's license notice requires <link
|
|
|
|
linkend="fdl-cover-texts">Cover Texts</link>, you must enclose
|
|
|
|
the copies in covers that carry, clearly and legibly, all these
|
|
|
|
Cover Texts: Front-Cover Texts on the front cover, and
|
|
|
|
Back-Cover Texts on the back cover. Both covers must also
|
|
|
|
clearly and legibly identify you as the publisher of these
|
|
|
|
copies. The front cover must present the full title with all
|
|
|
|
words of the title equally prominent and visible. You may add
|
|
|
|
other material on the covers in addition. Copying with changes
|
|
|
|
limited to the covers, as long as they preserve the title of the
|
|
|
|
<link linkend="fdl-document">Document</link> and satisfy these
|
|
|
|
conditions, can be treated as verbatim copying in other
|
|
|
|
respects.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If the required texts for either cover are too voluminous to fit
|
|
|
|
legibly, you should put the first ones listed (as many as fit
|
|
|
|
reasonably) on the actual cover, and continue the rest onto
|
|
|
|
adjacent pages.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If you publish or distribute <link
|
|
|
|
linkend="fdl-transparent">Opaque</link> copies of the <link
|
|
|
|
linkend="fdl-document">Document</link> numbering more than 100,
|
|
|
|
you must either include a machine-readable <link
|
|
|
|
linkend="fdl-transparent">Transparent</link> copy along with
|
|
|
|
each Opaque copy, or state in or with each Opaque copy a
|
|
|
|
publicly-accessible computer-network location containing a
|
|
|
|
complete Transparent copy of the Document, free of added
|
|
|
|
material, which the general network-using public has access to
|
|
|
|
download anonymously at no charge using public-standard network
|
|
|
|
protocols. If you use the latter option, you must take
|
|
|
|
reasonably prudent steps, when you begin distribution of Opaque
|
|
|
|
copies in quantity, to ensure that this Transparent copy will
|
|
|
|
remain thus accessible at the stated location until at least one
|
|
|
|
year after the last time you distribute an Opaque copy (directly
|
|
|
|
or through your agents or retailers) of that edition to the
|
|
|
|
public.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
It is requested, but not required, that you contact the authors
|
|
|
|
of the <link linkend="fdl-document">Document</link> well before
|
|
|
|
redistributing any large number of copies, to give them a chance
|
|
|
|
to provide you with an updated version of the Document.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="fdl-section4">
|
|
|
|
<title>4. MODIFICATIONS</title>
|
|
|
|
<para>
|
|
|
|
You may copy and distribute a <link
|
|
|
|
linkend="fdl-modified">Modified Version</link> of the <link
|
|
|
|
linkend="fdl-document">Document</link> under the conditions of
|
|
|
|
sections <link linkend="fdl-section2">2</link> and <link
|
|
|
|
linkend="fdl-section3">3</link> above, provided that you release
|
|
|
|
the Modified Version under precisely this License, with the
|
|
|
|
Modified Version filling the role of the Document, thus
|
|
|
|
licensing distribution and modification of the Modified Version
|
|
|
|
to whoever possesses a copy of it. In addition, you must do
|
|
|
|
these things in the Modified Version:
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<itemizedlist mark="opencircle">
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>A</title>
|
|
|
|
<para>
|
|
|
|
Use in the <link linkend="fdl-title-page">Title
|
|
|
|
Page</link> (and on the covers, if any) a title distinct
|
|
|
|
from that of the <link
|
|
|
|
linkend="fdl-document">Document</link>, and from those of
|
|
|
|
previous versions (which should, if there were any, be
|
|
|
|
listed in the History section of the Document). You may
|
|
|
|
use the same title as a previous version if the original
|
|
|
|
publisher of that version gives permission.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>B</title>
|
|
|
|
<para>
|
|
|
|
List on the <link linkend="fdl-title-page">Title
|
|
|
|
Page</link>, as authors, one or more persons or entities
|
|
|
|
responsible for authorship of the modifications in the
|
|
|
|
<link linkend="fdl-modified">Modified Version</link>,
|
|
|
|
together with at least five of the principal authors of
|
|
|
|
the <link linkend="fdl-document">Document</link> (all of
|
|
|
|
its principal authors, if it has less than five).
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>C</title>
|
|
|
|
<para>
|
|
|
|
State on the <link linkend="fdl-title-page">Title
|
|
|
|
Page</link> the name of the publisher of the <link
|
|
|
|
linkend="fdl-modified">Modified Version</link>, as the
|
|
|
|
publisher.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>D</title>
|
|
|
|
<para>
|
|
|
|
Preserve all the copyright notices of the <link
|
|
|
|
linkend="fdl-document">Document</link>.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>E</title>
|
|
|
|
<para>
|
|
|
|
Add an appropriate copyright notice for your modifications
|
|
|
|
adjacent to the other copyright notices.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>F</title>
|
|
|
|
<para>
|
|
|
|
Include, immediately after the copyright notices, a
|
|
|
|
license notice giving the public permission to use the
|
|
|
|
<link linkend="fdl-modified">Modified Version</link> under
|
|
|
|
the terms of this License, in the form shown in the
|
|
|
|
Addendum below.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>G</title>
|
|
|
|
<para>
|
|
|
|
Preserve in that license notice the full lists of <link
|
|
|
|
linkend="fdl-invariant"> Invariant Sections</link> and
|
|
|
|
required <link linkend="fdl-cover-texts">Cover
|
|
|
|
Texts</link> given in the <link
|
|
|
|
linkend="fdl-document">Document's</link> license notice.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>H</title>
|
|
|
|
<para>
|
|
|
|
Include an unaltered copy of this License.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>I</title>
|
|
|
|
<para>
|
|
|
|
Preserve the section entitled <quote>History</quote>, and
|
|
|
|
its title, and add to it an item stating at least the
|
|
|
|
title, year, new authors, and publisher of the <link
|
|
|
|
linkend="fdl-modified">Modified Version </link>as given on
|
|
|
|
the <link linkend="fdl-title-page">Title Page</link>. If
|
|
|
|
there is no section entitled <quote>History</quote> in the
|
|
|
|
<link linkend="fdl-document">Document</link>, create one
|
|
|
|
stating the title, year, authors, and publisher of the
|
|
|
|
Document as given on its Title Page, then add an item
|
|
|
|
describing the Modified Version as stated in the previous
|
|
|
|
sentence.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>J</title>
|
|
|
|
<para>
|
|
|
|
Preserve the network location, if any, given in the <link
|
|
|
|
linkend="fdl-document">Document</link> for public access
|
|
|
|
to a <link linkend="fdl-transparent">Transparent</link>
|
|
|
|
copy of the Document, and likewise the network locations
|
|
|
|
given in the Document for previous versions it was based
|
|
|
|
on. These may be placed in the <quote>History</quote>
|
|
|
|
section. You may omit a network location for a work that
|
|
|
|
was published at least four years before the Document
|
|
|
|
itself, or if the original publisher of the version it
|
|
|
|
refers to gives permission.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>K</title>
|
|
|
|
<para>
|
|
|
|
In any section entitled <quote>Acknowledgements</quote> or
|
|
|
|
<quote>Dedications</quote>, preserve the section's title,
|
|
|
|
and preserve in the section all the substance and tone of
|
|
|
|
each of the contributor acknowledgements and/or
|
|
|
|
dedications given therein.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>L</title>
|
|
|
|
<para>
|
|
|
|
Preserve all the <link linkend="fdl-invariant">Invariant
|
|
|
|
Sections</link> of the <link
|
|
|
|
linkend="fdl-document">Document</link>, unaltered in their
|
|
|
|
text and in their titles. Section numbers or the
|
|
|
|
equivalent are not considered part of the section titles.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>M</title>
|
|
|
|
<para>
|
|
|
|
Delete any section entitled
|
|
|
|
<quote>Endorsements</quote>. Such a section may not be
|
|
|
|
included in the <link linkend="fdl-modified">Modified
|
|
|
|
Version</link>.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<formalpara>
|
|
|
|
<title>N</title>
|
|
|
|
<para>
|
|
|
|
Do not retitle any existing section as
|
|
|
|
<quote>Endorsements</quote> or to conflict in title with
|
|
|
|
any <link linkend="fdl-invariant">Invariant
|
|
|
|
Section</link>.
|
|
|
|
</para>
|
|
|
|
</formalpara>
|
|
|
|
</listitem>
|
|
|
|
</itemizedlist>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If the <link linkend="fdl-modified">Modified Version</link>
|
|
|
|
includes new front-matter sections or appendices that qualify as
|
|
|
|
<link linkend="fdl-secondary">Secondary Sections</link> and
|
|
|
|
contain no material copied from the Document, you may at your
|
|
|
|
option designate some or all of these sections as invariant. To
|
|
|
|
do this, add their titles to the list of <link
|
|
|
|
linkend="fdl-invariant">Invariant Sections</link> in the
|
|
|
|
Modified Version's license notice. These titles must be
|
|
|
|
distinct from any other section titles.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
You may add a section entitled <quote>Endorsements</quote>,
|
|
|
|
provided it contains nothing but endorsements of your <link
|
|
|
|
linkend="fdl-modified">Modified Version</link> by various
|
|
|
|
parties--for example, statements of peer review or that the text
|
|
|
|
has been approved by an organization as the authoritative
|
|
|
|
definition of a standard.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
You may add a passage of up to five words as a <link
|
|
|
|
linkend="fdl-cover-texts">Front-Cover Text</link>, and a passage
|
|
|
|
of up to 25 words as a <link
|
|
|
|
linkend="fdl-cover-texts">Back-Cover Text</link>, to the end of
|
|
|
|
the list of <link linkend="fdl-cover-texts">Cover Texts</link>
|
|
|
|
in the <link linkend="fdl-modified">Modified Version</link>.
|
|
|
|
Only one passage of Front-Cover Text and one of Back-Cover Text
|
|
|
|
may be added by (or through arrangements made by) any one
|
|
|
|
entity. If the <link linkend="fdl-document">Document</link>
|
|
|
|
already includes a cover text for the same cover, previously
|
|
|
|
added by you or by arrangement made by the same entity you are
|
|
|
|
acting on behalf of, you may not add another; but you may
|
|
|
|
replace the old one, on explicit permission from the previous
|
|
|
|
publisher that added the old one.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The author(s) and publisher(s) of the <link
|
|
|
|
linkend="fdl-document">Document</link> do not by this License
|
|
|
|
give permission to use their names for publicity for or to
|
|
|
|
assert or imply endorsement of any <link
|
|
|
|
linkend="fdl-modified">Modified Version </link>.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="fdl-section5">
|
|
|
|
<title>5. COMBINING DOCUMENTS</title>
|
|
|
|
<para>
|
|
|
|
You may combine the <link linkend="fdl-document">Document</link>
|
|
|
|
with other documents released under this License, under the
|
|
|
|
terms defined in <link linkend="fdl-section4">section 4</link>
|
|
|
|
above for modified versions, provided that you include in the
|
|
|
|
combination all of the <link linkend="fdl-invariant">Invariant
|
|
|
|
Sections</link> of all of the original documents, unmodified,
|
|
|
|
and list them all as Invariant Sections of your combined work in
|
|
|
|
its license notice.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The combined work need only contain one copy of this License,
|
|
|
|
and multiple identical <link linkend="fdl-invariant">Invariant
|
|
|
|
Sections</link> may be replaced with a single copy. If there are
|
|
|
|
multiple Invariant Sections with the same name but different
|
|
|
|
contents, make the title of each such section unique by adding
|
|
|
|
at the end of it, in parentheses, the name of the original
|
|
|
|
author or publisher of that section if known, or else a unique
|
|
|
|
number. Make the same adjustment to the section titles in the
|
|
|
|
list of Invariant Sections in the license notice of the combined
|
|
|
|
work.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
In the combination, you must combine any sections entitled
|
|
|
|
<quote>History</quote> in the various original documents,
|
|
|
|
forming one section entitled <quote>History</quote>; likewise
|
|
|
|
combine any sections entitled <quote>Acknowledgements</quote>,
|
|
|
|
and any sections entitled <quote>Dedications</quote>. You must
|
|
|
|
delete all sections entitled <quote>Endorsements.</quote>
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="fdl-section6">
|
|
|
|
<title>6. COLLECTIONS OF DOCUMENTS</title>
|
|
|
|
<para>
|
|
|
|
You may make a collection consisting of the <link
|
|
|
|
linkend="fdl-document">Document</link> and other documents
|
|
|
|
released under this License, and replace the individual copies
|
|
|
|
of this License in the various documents with a single copy that
|
|
|
|
is included in the collection, provided that you follow the
|
|
|
|
rules of this License for verbatim copying of each of the
|
|
|
|
documents in all other respects.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
You may extract a single document from such a collection, and
|
|
|
|
distribute it individually under this License, provided you
|
|
|
|
insert a copy of this License into the extracted document, and
|
|
|
|
follow this License in all other respects regarding verbatim
|
|
|
|
copying of that document.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="fdl-section7">
|
|
|
|
<title>7. AGGREGATION WITH INDEPENDENT WORKS</title>
|
|
|
|
<para>
|
|
|
|
A compilation of the <link
|
|
|
|
linkend="fdl-document">Document</link> or its derivatives with
|
|
|
|
other separate and independent documents or works, in or on a
|
|
|
|
volume of a storage or distribution medium, does not as a whole
|
|
|
|
count as a <link linkend="fdl-modified">Modified Version</link>
|
|
|
|
of the Document, provided no compilation copyright is claimed
|
|
|
|
for the compilation. Such a compilation is called an
|
|
|
|
<quote>aggregate</quote>, and this License does not apply to the
|
|
|
|
other self-contained works thus compiled with the Document , on
|
|
|
|
account of their being thus compiled, if they are not themselves
|
|
|
|
derivative works of the Document. If the <link
|
|
|
|
linkend="fdl-cover-texts">Cover Text</link> requirement of <link
|
|
|
|
linkend="fdl-section3">section 3</link> is applicable to these
|
|
|
|
copies of the Document, then if the Document is less than one
|
|
|
|
quarter of the entire aggregate, the Document's Cover Texts may
|
|
|
|
be placed on covers that surround only the Document within the
|
|
|
|
aggregate. Otherwise they must appear on covers around the whole
|
|
|
|
aggregate.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="fdl-section8">
|
|
|
|
<title>8. TRANSLATION</title>
|
|
|
|
<para>
|
|
|
|
Translation is considered a kind of modification, so you may
|
|
|
|
distribute translations of the <link
|
|
|
|
linkend="fdl-document">Document</link> under the terms of <link
|
|
|
|
linkend="fdl-section4">section 4</link>. Replacing <link
|
|
|
|
linkend="fdl-invariant"> Invariant Sections</link> with
|
|
|
|
translations requires special permission from their copyright
|
|
|
|
holders, but you may include translations of some or all
|
|
|
|
Invariant Sections in addition to the original versions of these
|
|
|
|
Invariant Sections. You may include a translation of this
|
|
|
|
License provided that you also include the original English
|
|
|
|
version of this License. In case of a disagreement between the
|
|
|
|
translation and the original English version of this License,
|
|
|
|
the original English version will prevail.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="fdl-section9">
|
|
|
|
<title>9. TERMINATION</title>
|
|
|
|
<para>
|
|
|
|
You may not copy, modify, sublicense, or distribute the <link
|
|
|
|
linkend="fdl-document">Document</link> except as expressly
|
|
|
|
provided for under this License. Any other attempt to copy,
|
|
|
|
modify, sublicense or distribute the Document is void, and will
|
|
|
|
automatically terminate your rights under this License. However,
|
|
|
|
parties who have received copies, or rights, from you under this
|
|
|
|
License will not have their licenses terminated so long as such
|
|
|
|
parties remain in full compliance.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="fdl-section10">
|
|
|
|
<title>10. FUTURE REVISIONS OF THIS LICENSE</title>
|
|
|
|
<para>
|
|
|
|
The <ulink type="http"
|
|
|
|
url="http://www.gnu.org/fsf/fsf.html">Free Software
|
|
|
|
Foundation</ulink> may publish new, revised versions of the GNU
|
|
|
|
Free Documentation License from time to time. Such new versions
|
|
|
|
will be similar in spirit to the present version, but may differ
|
|
|
|
in detail to address new problems or concerns. See <ulink
|
|
|
|
type="http"
|
|
|
|
url="http://www.gnu.org/copyleft">http://www.gnu.org/copyleft/</ulink>.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Each version of the License is given a distinguishing version
|
|
|
|
number. If the <link linkend="fdl-document">Document</link>
|
|
|
|
specifies that a particular numbered version of this License
|
|
|
|
<quote>or any later version</quote> applies to it, you have the
|
|
|
|
option of following the terms and conditions either of that
|
|
|
|
specified version or of any later version that has been
|
|
|
|
published (not as a draft) by the Free Software Foundation. If
|
|
|
|
the Document does not specify a version number of this License,
|
|
|
|
you may choose any version ever published (not as a draft) by
|
|
|
|
the Free Software Foundation.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
|
|
|
|
<sect3 id="fdl-using">
|
|
|
|
<title>Addendum</title>
|
|
|
|
<para>
|
|
|
|
To use this License in a document you have written, include a copy of
|
|
|
|
the License in the document and put the following copyright and
|
|
|
|
license notices just after the title page:
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<blockquote>
|
|
|
|
<para>
|
|
|
|
Copyright © YEAR YOUR NAME.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
Permission is granted to copy, distribute and/or modify this
|
|
|
|
document under the terms of the GNU Free Documentation
|
|
|
|
License, Version 1.1 or any later version published by the
|
|
|
|
Free Software Foundation; with the <link
|
|
|
|
linkend="fdl-invariant">Invariant Sections</link> being LIST
|
|
|
|
THEIR TITLES, with the <link
|
|
|
|
linkend="fdl-cover-texts">Front-Cover Texts</link> being LIST,
|
|
|
|
and with the <link linkend="fdl-cover-texts">Back-Cover
|
|
|
|
Texts</link> being LIST. A copy of the license is included in
|
|
|
|
the section entitled <quote>GNU Free Documentation
|
|
|
|
License</quote>.
|
|
|
|
</para>
|
|
|
|
</blockquote>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If you have no <link linkend="fdl-invariant">Invariant
|
|
|
|
Sections</link>, write <quote>with no Invariant Sections</quote>
|
|
|
|
instead of saying which ones are invariant. If you have no
|
|
|
|
<link linkend="fdl-cover-texts">Front-Cover Texts</link>, write
|
|
|
|
<quote>no Front-Cover Texts</quote> instead of
|
|
|
|
<quote>Front-Cover Texts being LIST</quote>; likewise for <link
|
|
|
|
linkend="fdl-cover-texts">Back-Cover Texts</link>.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
If your document contains nontrivial examples of program code,
|
|
|
|
we recommend releasing these examples in parallel under your
|
|
|
|
choice of free software license, such as the <ulink type="http"
|
|
|
|
url="http://www.gnu.org/copyleft/gpl.html"> GNU General Public
|
|
|
|
License</ulink>, to permit their use in free software.
|
|
|
|
</para>
|
|
|
|
</sect3>
|
|
|
|
</sect2>
|
|
|
|
</sect1>
|
|
|
|
</appendix>
|
|
|
|
|
|
|
|
</article>
|
|
|
|
|
|
|