This commit is contained in:
gferg 2002-04-02 14:37:04 +00:00
parent 3cf62cc13e
commit 38e0ded77b
1 changed files with 185 additions and 75 deletions

View File

@ -1,4 +1,5 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN"
"/usr/share/sgml/docbook/sgml-dtd-4.1/docbook.dtd">
<article id="index">
@ -9,12 +10,18 @@
<firstname>
Sayamindu</firstname> <surname>Dasgupta</surname> <affiliation>
<address> <email>unmadindu@Softhome.net</email> </address>
<address> <email>unmadindu_NO_SPAM_@Softhome.net</email> </address>
</affiliation> </author> <author> <firstname>Jan</firstname> <surname>Stifter</surname>
<affiliation>
<address> <email>j.stifter@medres.ch</email> </address>
<address> <email>j.stifter_NO_SPAM_@medres.ch</email> </address>
</affiliation> </author>
<revhistory>
<revision>
<revnumber>2.0</revnumber>
<date>2002-3-30</date>
<revremark> Made changes in the drivers section, other corrections </revremark>
</revision>
</revhistory>
<revhistory>
<revision>
<revnumber>1.10</revnumber>
@ -48,7 +55,7 @@ your PCTel HSP MicroModem work in linux.</para>
<title>Copyright Information</title>
<blockquote><para>
Copyright (c) 2001 Sayamindu Dasgupta, Jan Stifter.
Copyright (c) 2002 Sayamindu Dasgupta, Jan Stifter.
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;
@ -91,46 +98,46 @@ your PCTel HSP MicroModem work in linux.</para>
<para>
The latest version of this mini-HOWTO will always be made available on
my home page, in a variety of formats:
The latest version of this mini-HOWTO will always be made available in my
<ulink url="http://www.peacefulaction.org/sayamindu">homepage </ulink>(many thanks to
<ulink url="http://www.peacefulaction.org"> Peaceful Action </ulink> for hosting my homepage) in a variety of formats:
</para>
<para>
<itemizedlist>
<listitem>
<para>
<ulink url="http://sayamindu.topcities.com/pctel.html">HTML</ulink>.
<ulink url="http://www.peacefulaction.org/sayamindu/pctel.html">HTML</ulink>.
</para>
</listitem>
<listitem>
<para>
<ulink url="http://sayamindu.topcities.com/pctel.txt">plain text</ulink>.
</para>
<para>
<ulink url="http://www.peacefulaction.org/sayamindu/pctel.txt">plain text</ulink>.
</para>
</listitem>
<listitem>
<para>
<ulink url="http://sayamindu.topcities.com/pctel.pdf">PDF</ulink>.
<ulink url="http://www.peacefulaction.org/sayamindu/pctel.pdf">PDF</ulink>.
</para>
</listitem>
<listitem>
<para>
<ulink url="http://sayamindu.topcities.com/pctel.rtf">RTF</ulink>.
<ulink url="http://www.peacefulaction.org/sayamindu/pctel.rtf">RTF</ulink>.
</para>
</listitem>
<listitem>
<para>
<ulink url="http://sayamindu.topcities.com/pctel.tar.gz">compressed
<ulink url="http://www.peacefulaction.org/sayamindu/pctel.tar.gz">compressed
html (multiple pages format)</ulink>.
</para>
</listitem>
<listitem>
<para>
<ulink url="http://sayamindu.topcities.com/pctel.sgml">SGML source</ulink>.
<ulink url="http://www.peacefulaction.org/sayamindu/pctel.sgml">SGML source</ulink>.
</para>
</listitem>
</itemizedlist>
@ -144,7 +151,7 @@ your PCTel HSP MicroModem work in linux.</para>
<sect2 id="credits">
<title>Credits</title>
<para> I am extremely grateful to the howtos@kcircle.com list members for their support, especially to <ulink url="http://geocities.com/usmbish/">USM Bish</ulink>.
<para> I am extremely grateful to the howtos_NO_SPAM@kcircle.com list members for their support, especially to <ulink url="http://geocities.com/usmbish/">USM Bish</ulink>.
</para><para>
The members of the discuss@linmodems.org list have been very helpful too, specially in the initial phase of the howto-writing.
I am also extremely grateful to Phil Richard Burchill, Rajesh Fowkar, KV Pham and Andrew Kar (akar)
@ -152,7 +159,7 @@ for their valuable suggestions.
</para>
<para>
The sgml-stuff has been done with the help of the template written by Stein Gjoen, Gregory Leblanc and Greg Ferguson.
I am also indebted to Greg Ferguson for cleaning up the mess i had made with Docbook.
I am also indebted to Greg Ferguson for cleaning up the mess i had made with Docbook:).
</para>
</sect2>
@ -163,7 +170,13 @@ I am also indebted to Greg Ferguson for cleaning up the mess i had made with Doc
<para>
If you have any comments, criticisms, ideas, additions, corrections, then please do mail them to <email>unmadindu@Softhome.net</email>. But for technical queries, we suggest that you ask at the discuss@linmodems.org mailing list.</para>
If you have any comments, criticisms, ideas, additions, corrections, then please do mail them to
<email>unmadindu_NO_SPAM_@Softhome.net</email>. But for technical queries, we suggest that you ask at the
discuss@linmodems.org mailing list.</para>
<para>
NOTE: Please do not mail me with your problems. You will NOT get any answer. For answers ask at
discuss@linmodems.org
</para>
</sect2>
<sect2 id="translations">
<title>Translations</title>
@ -177,7 +190,7 @@ If you have any comments, criticisms, ideas, additions, corrections, then please
<surname>Cardoso</surname>
<contrib>Translation from English to Portuguese.</contrib>
</othercredit>
<email>rafamvc@yahoo.com.br</email>
<email>rafamvc_NO_SPAM_@yahoo.com.br</email>
</para>
</listitem>
</itemizedlist>
@ -197,7 +210,7 @@ If you have any comments, criticisms, ideas, additions, corrections, then please
<varlistentry>
<term>Warnings</term>
<listitem>
<para><emphasis>WARNING</emphasis></para>
<para><warning><para>WARNING</para></warning></para>
</listitem>
</varlistentry>
<varlistentry>
@ -247,7 +260,10 @@ with linux (the manufacturers use patented technologies and so drivers for these
developed as Open Source). For a few of these winmodems, drivers have been developed </para><para>The PCTel
modems belong to this category and fall under linmodems. </para>
<para>
NOTE: Though I am referring PCTel modems here, actually PCTel only manufactures the chips for these modems, so if have say, XXX modem and you get a </para><para><computeroutput>00:09.0 Communication controller: PCTel Inc HSP MicroModem 56 (rev 01)</computeroutput></para><para> when you issue the <command>bash$ lspci</command> command, then do not worry, you have what we call a PCTel linmodem.</para>
NOTE: Though I am referring PCTel modems here, actually PCTel only manufactures the chips for these modems, so if you
have say, XXX modem and you get a </para><para><computeroutput>00:09.0 Communication controller: PCTel Inc HSP MicroModem
56 (rev 01)</computeroutput></para><para> when you issue the <command>bash$ lspci</command> command, then do not
worry, you have what we call a PCTel linmodem.</para>
</sect1>
@ -258,9 +274,11 @@ NOTE: Though I am referring PCTel modems here, actually PCTel only manufactures
<sect1 id="downloaddrivers">
<title>Where to get the drivers</title>
<para>Now let me come to the next obvious question, that is; Where are the drivers??</para>
<para>Well, if you are impatient, then go to </para>
<para><ulink url="http://www.medres.ch/~jstifter/linux/pctel.html">http://www.medres.ch/~jstifter/linux/pctel.html</ulink></para>
<para>But there are a number of drivers there, and you will definitely feel confused..so read on.</para>
<para>Well, if you are impatient, and if you have a 2.4x series kernel then go to </para>
<para><ulink url="http://www.medres.ch/~jstifter/pctel/">http://www.medres.ch/~jstifter/pctel/</ulink>, and if you
are stuck with the older 2.2.x kernels, go to <ulink url="http://modems.dewback.cl">http://modems.dewback.cl</ulink> (the exact link for
the file it self is <ulink url="http://modems.dewback.cl/pctel-2.2.tar.gz"> http://modems.dewback.cl/pctel-2.2.tar.gz </ulink>)</para>
<para>But there are a number of drivers in both the sites, and you will definitely feel confused..so read on.</para>
</sect1>
@ -270,21 +288,36 @@ NOTE: Though I am referring PCTel modems here, actually PCTel only manufactures
<sect1 id="rightdrivers">
<title>Choosing a suitable driver</title>
<para> The driver version that you will have to use depends on the kernel version you have. To know your kernel version, you will
have to issue the command </para>
<para>
There are a number of drivers in <ulink url="http://www.medres.ch/~jstifter/linux/pctel.html">http://www.medres.ch/~jstifter/linux/pctel.html</ulink> for modems with PCTel chip sets. To know what driver to download, you will have to know what kernel version you are running. To do that you will have to issue the command </para>
<para><command>bash$
uname -r
</command></para>
<para>
and that will give the version of your kernel.</para><para>
If you have a 2.2.x kernel, you will have to use the pctel-2.2 drivers . For kernels between 2.4.0 and 2.4.6, you can use the pctel-2.4 driver and for kernel 2.4.7 and above, you can use the pctel-2.4.7 drivers.</para><para>
But I personally recommend that you use the pctel-0.8.6 driver (the latest version) which is a continuation of the drivers from PCTel with added configure support and some bug fixes.</para><para>
You may find some other drivers for PCTel based modems on the internet. See <link linkend="other-drivers">section 9.3 </link>for more information regarding these drivers </para>
<para>NOTE: You will find that Jan's site also contain a number of other old drivers. I recommend that you do not use them as they are very much outdated.
<command>
uname -r
</command>
</para>
<para>
If you see something like 2.2.x, go to <ulink url="http://modems.dewback.cl">http://modems.dewback.cl</ulink> and download
the <ulink url="http://modems.dewback.cl/pctel-2.2.tar.gz">pctel 2.2x </ulink> drivers from the PCTel section of that site.
</para>
<para>
If you see something like 2.4x, go to <ulink url="http://www.medres.ch/~jstifter/pctel/">http://www.medres.ch/~jstifter/pctel/</ulink>
and download the pctel 0.9.0 (pctel-0.9.0.tar.gz) drivers from that site.
</para>
<para>
<warning>
<para>
NOTE: There has been some complaints of system instability while using the pctel 0.9.0 drivers, if you experience problems, then download
the pctel 0.8.6 drivers from <ulink url="http://www.medres.ch/~jstifter/pctel/">http://www.medres.ch/~jstifter/pctel/</ulink>.
</para>
</warning>
</para>
<para>
<warning>
<para>
Also note that only the pctel 0.9.0 drivers have support for the new <link linkend='amr'>AMR</link> modems.
</para>
</warning>
</para>
</sect1>
<!-- Section1: installation -->
@ -302,7 +335,7 @@ then the drivers would not work.</para>
don't have a smp/uniprocessor mismatch ( that is, running uniprocessor kernel but having a kernel
source with smp support in /usr/src/linux). Also, you will need a kernel
which supports loadable modules.</para>
<para>
<para>
And of course, you need to have gcc installed, check it by issuing the command <command>bash$ gcc -v </command>. If you do not get any errors, the everything is all right </para>
<sect2><title>Installing the 2.2x drivers.</title>
<para>Login as root.</para>
@ -339,33 +372,102 @@ the script, but once you reboot, you will have to load the modules by</para><par
<para><command>bash$ insmod pctel.o</command></para>
<para><command>bash$ insmod ptserial.o </command>)</para>
</sect2>
<sect2><title>
Installing the pctel-2.4 and the pctel-2.4.7 drivers
</title>
<para>The 2.4 driver works for kernel 2.4.0 to kernel 2.4.6 and the 2.4.7 driver works for kernel 2.4.7
upwards. But the methods of installation for both are the same, and so I put the instructions under one
section.
Make sure that you have the appropriate kernel with the command <command>bash$ uname -r</command></para>
<para>.</para>
<sect2>
<title>Installing the pctel-0.9.0 driver</title>
<para>Make sure that you have kernel 2.4.0 or greater by the command</para>
<para><command>bash$ uname -r</command></para>
<para>Unpack the downloaded files with the commands</para>
<para><command>bash$ tar -xzvf `the filename`.tar.gz</command></para>
<para>You will be now left with a <filename>pctel-2.4</filename> or a <filename>pctel-2.4.7 </filename> directory..move into that with the command</para>
<para><command>bash$ cd pctel-2.4/</command><emphasis>(pctel-2.4.7/ if needed)</emphasis>;</para>
<para>Compile the drivers with the command </para>
<para><command>bash$ make</command></para>
<para>The next steps require you to be logged in as root.To do so use the command</para>
<para><command>bash$ su</command></para>
<para>If you do not get any error messages from the <command>bash$ make</command>, then install the drivers by the command</para>
<para><command>bash$ make install</command></para>
<para>Now you just have to load the drivers (which are in <filename>/lib/modules/`your kernel version`/misc/</filename>) with the commands</para>
<para><command>bash$ insmod pctel</command></para>
<para><command>bash$ insmod ptserial</command></para>
<para>(these can be issued from any directory as the <application>insmod</application> program will automatically find the drivers <application>pctel.o</application> and <application>ptserial.o</application> in
<filename>/lib/modules/`your kernel version`/misc/ </filename>) </para>
<para><command>bash$ tar -xzvf 0.9.0.tar</command></para>
<para>Now you will have a pctel-0.9.0 directory</para>
<para>cd into that with the command</para>
<para><command>bash$ cd pctel-0.9.0/</command></para>
<para>Now comes the complicated part.</para>
<para>To proceed further you will have to know what chip set your modem has.See section <link linkend="identify"> 9.4 </link>for more information on this.</para>
<para>Once you have got the name of the chip set, just type one of the following commands (depending on the chip set)
</para>
<para>
If you have a PCT 789 chip set,
</para>
<para>
<command>bash$
./configure --with-hal=pct789</command>
</para>
<para>
If you have a CM8738 chip set,
</para>
<para><command>bash$
./configure -with-hal=cm8738</command>
</para>
<para>
If you have a chip set integrated with an Intel 810 chip set based motherboard from Intel,
</para>
<para> <command>bash$
./configure --with-hal=i810 </command>
</para>
<para>
If you have a chip set integrated in a motherboard from SIS,
</para>
<para> <command>bash$
./configure --with-hal=sis </command>
</para>
<para>
If you have a chip set integrated with an VIA 686a chip set based motherboard ,
</para>
<para><command>bash$
./configure --with-hal=via686a </command>
</para>
<para>
The configure script will run and a number of messages will fly past.
Check for any error messages that may fly past.
When you have the prompt again, (and if you have not got any errors),
compile the drivers with the command
</para>
<para>
<command>bash$ make
</command>
</para>
<para>
Then if you do not get any error messages, install the drivers with the command
</para>
<para>
<command>bash$ make install</command>
</para><para>
(You will have to be logged in as root for performing the last step)
</para><para>
Then just load the drivers with the commands
</para>
<para>
<command>bash$ insmod pctel</command>
</para>
<para>
<command>bash$ insmod ptserial</command>
</para>
<para>
NOTE: These commands can be issued from any directory as the <application>insmod</application> program will automatically find
the drivers <application>pctel.o</application> and <application>ptserial.o</application> in
<filename>/lib/modules/`your kernel version`/misc/ </filename>)
</para>
<para>
<warning>
<para>
NOTE: Please note that the pctel-0.9.0 drivers are comparatively new, and there has been some complaints of lock ups
and system unstabilty while using these drivers. If you experience stabilty problems while using these drivers, please, please
revert back to the pctel-0.8.6 drivers.
</para>
<para>
However, if you have an <link linkend='amr'>AMR</link> modem, then you will have to
use the 0.9.0 drivers.
</para>
</warning>
</para>
</sect2>
<sect2>
<title>Installing the pctel-0.8.6 driver</title>
<warning>
<para>
Use this driver only if you experience problems with the pctel-0.9.0 drivers
</para>
</warning>
<para>Make sure that you have kernel 2.4.0 or greater by the command</para>
<para><command>bash$ uname -r</command></para>
<para>Unpack the downloaded files with the commands</para>
@ -435,7 +537,7 @@ Then just load the drivers with the commands
<command>bash$ insmod ptserial</command>
</para>
<para>
(these too, like in the case of the pctel-2.4x drivers, can be issued from any directory as the <application>insmod</application> program will automatically find
(these too, like in the case of the pctel-0.9.0 drivers, can be issued from any directory as the <application>insmod</application> program will automatically find
the drivers <application>pctel.o</application> and <application>ptserial.o</application> in <filename>/lib/modules/`your kernel version`/misc/ </filename>)
</para>
</sect2>
@ -669,7 +771,7 @@ rmmod pctel
</sect2>
<sect2>
<title>
Bugs in the 2.4x versions.
Bugs in the pctel-0.9.0 and the 0.8.6 versions.
</title>
<para>
<anchor id="bug"/>
@ -679,7 +781,8 @@ beeeeeeeeee... sound from the modem speaker and later, the dialer gives a messag
and disconnects.
</para>
<para>
This problem has no real workaround , but sometimes unloading and reloading of the modules work.For that the commands will be (assuming that you have the modules in <filename>/lib/modules/'your kernel version`/misc/ </filename>)</para>
This problem has no real workaround , but sometimes unloading and reloading of the modules work. For that the commands
will be (assuming that you have the modules in <filename>/lib/modules/'your kernel version`/misc/ </filename>)</para>
<para>
<command>bash$
rmmod ptserial
@ -702,6 +805,10 @@ NOTE:You must exit from your dialer before trying to unload the drivers, otherwi
</para><para>
When the problems become too acute, the only solution seems to be rebooting.
</para>
<para>
It has been also noticed that sometimes, this problem is ISP dependent, with the problem surfacing when using a particular
ISP.
</para>
</sect2>
<sect2>
<title>
@ -745,7 +852,9 @@ You will be presented with the BIOS configuration menu. Enter the "PNP/PCI Confi
AMR modems
</title>
<para>
There are certain PCTel chip set based internal modems that go into AMR slots instead of the normal PCI slots. Linux support for these types of modems is not very well developed, though the upcoming drivers may support them. They are usually identified as <computeroutput> HSP MR </computeroutput> by the <command>bash$ lspci </command> command.
There are certain PCTel chip set based internal modems that go into AMR slots instead of the normal PCI slots. They are
usually identified as <computeroutput> HSP MR </computeroutput> by the <command>bash$ lspci </command> command. These modems
are supported by the pctel-0.9.0 drivers only.
</para>
</sect2>
</sect1>
@ -840,7 +949,7 @@ and seeing whether smp support is selected.
</para>
<para>
Another way to get rid of the unresolved symbols problem is to use the fixscript package from
<ulink url="http://www.medres.ch/~jstifter/linux/fixscript.gz">http://www.medres.ch/~jstifter/linux/fixscript.gz</ulink>
<ulink url="http://www.medres.ch/~jstifter/pctel/fixscript.gz">http://www.medres.ch/~jstifter/pctel/fixscript.gz</ulink>
</para>
<para>
The procedure is to:
@ -1054,10 +1163,10 @@ tail /var/log/messages
<para>
will give you a lot of information if anything goes wrong
The normal output should be something like this</para><para><screen>
Nov 26 13:19:31 madcow kernel: PCTel device[00:09.0](0x48) found "PCTel Inc HSP MicroModem 56 (rev 01)", iobase=0xe400, irq=12.
Nov 26 13:19:31 madcow kernel: PCTel driver version 0.8.9 [5.05c-4.27.215 (09-14-2001)] (PCT789) (2001-09-07) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled.
Nov 26 13:19:31 madcow kernel: PCTel driver built on [Linux 2.4.14 i686 unknown "2.4.14 <132110>"] with gcc-2.96.
Nov 26 13:19:31 madcow kernel: ttyS15 at 0xe400 (irq = 12) is a PCTel
PCTel device[00:09.0](0x48) found "PCTel Inc HSP MicroModem 56 (rev 01)", iobase=0xe400, irq=12.
PCTel driver version 0.9.0 [5.05c-4.27.215 (09-14-2001)] (PCT789) (2002-01-31) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled.
PCTel driver built on [Linux 2.4.18 i686 unknown "2.4.18 <132114>"] with gcc-2.96.
ttyS15 at 0xe400 (irq = 12) is a PCTel
</screen>
</para>
<para>Mail the output you get to the <email>discuss@linmodems.org</email> list( more on this in section <link linkend="mailinglist">9.2.2</link>), and wait for a reply.</para>
@ -1100,8 +1209,8 @@ cp modemon /usr/bin/modemon
<para>There are a number of websites, mailing lists that may help you while you try to configure your modem.</para>
<sect3>
<title>Web sites</title>
<para>The unofficial pctel linux driver site at <ulink url="http://www.medres.ch/~jstifter/linux/pctel.html">
http://www.medres.ch/~jstifter/linux/pctel.html</ulink></para>
<para>The unofficial pctel linux driver site at <ulink url="http://www.medres.ch/~jstifter/pctel/">
http://www.medres.ch/~jstifter/pctel/</ulink></para>
<para>The linmodem site (the mother page of all linmodem projets) at <ulink url="http://www.linmodems.org">http://www.linmodems.org</ulink></para>
<para>A huge lists of lin/winmodems at <ulink url=" http://www.idir.net/~gromitkc/winmodem.html
">http://www.idir.net/~gromitkc/winmodem.html</ulink></para>
@ -1113,7 +1222,7 @@ The linmodem-howto is available at <ulink url="http://www.linuxdoc.org/HOWTO/Lin
<sect3>
<title>Mailing lists</title>
<para>
<anchor id="mailinglist"/>
<anchor id="mailinglist">
The most important mailing list for linmodems is </para>
<para><email>discuss@linmodems.org</email></para>
<para>You can subscribe to that list by going to &nbsp;</para><para>
@ -1125,7 +1234,8 @@ The most important mailing list for linmodems is </para>
<title> Other drivers that are available </title>
<para>
I have seen a number of modem manufacturers (Dax, Zoltrix, Lectron, Tiacom etc) providing linux drivers for their modems that have PCTel chip sets.</para><para>
Actually most (if not all) of these drivers are slightly modified form of the drivers at Jan's site, and so, in most cases, there is no point in downloading them.</para>
Actually most (if not all) of these drivers are slightly modified form of the drivers at Jan's and the modems.dewback.cl
site, and so, in most cases, there is no point in downloading them.</para>
<para>
Moreover, in the early days of 2.4x kernels, Thomas Wright had made a PCTel driver and you can find it in his website at <ulink url="http://www.geocities.com/tom_in_rc/">http://www.geocities.com/tom_in_rc/</ulink>.</para>
</sect2>