601 lines
9.8 KiB
HTML
601 lines
9.8 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Resolving Installation and Configuration Problems</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
|
|
"><LINK
|
|
REL="HOME"
|
|
TITLE="Linux ACP Modem (Mwave) mini-HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Compilation, Installation, and Startup"
|
|
HREF="startup.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Debugging Tips"
|
|
HREF="debugging.html"></HEAD
|
|
><BODY
|
|
CLASS="SECT1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>Linux ACP Modem (Mwave) mini-HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="startup.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="debugging.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="PROBLEMS">3. Resolving Installation and Configuration Problems</H1
|
|
><P
|
|
>The following sections list solutions to possible problems you may experience.</P
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="NOSTART">3.1. DSP Does Not Start</H2
|
|
><P
|
|
>In order to recognize memory above 64 Meg, it may be necessary to append the "mem=" option to the kernel command line.
|
|
|
|
If you are using LILO for your boot loader, you would do this in the <TT
|
|
CLASS="FILENAME"
|
|
>lilo.conf</TT
|
|
> file.
|
|
|
|
For example, if you had a machine with 128 Meg you would type:</P
|
|
><TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>append="mem=130496K"</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><DIV
|
|
CLASS="NOTE"
|
|
><P
|
|
></P
|
|
><TABLE
|
|
CLASS="NOTE"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="25"
|
|
ALIGN="CENTER"
|
|
VALIGN="TOP"
|
|
><IMG
|
|
SRC="../images/note.gif"
|
|
HSPACE="5"
|
|
ALT="Note"></TD
|
|
><TH
|
|
ALIGN="LEFT"
|
|
VALIGN="CENTER"
|
|
><B
|
|
>NOTE</B
|
|
></TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
> </TD
|
|
><TD
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
><P
|
|
>Your statement must reflect 576K less than you actually
|
|
|
|
have. Specifying the full amount of memory will prevent the DSP from starting. In the above
|
|
|
|
example, the formula used to arrive at the proper number was 1024 * nMB - 576 = nK.</P
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
><P
|
|
>If you forget to run the Thinkpad™ utility to enable the ACP
|
|
|
|
Modem and you didn't specify any command line arguments when
|
|
|
|
inserting the mwave module (or it didn't work), you will receive a message in the syslog,
|
|
|
|
similar to the one below:</P
|
|
><TABLE
|
|
BORDER="0"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="PROGRAMLISTING"
|
|
>ACP Modem, UART settings IRQ 0x3 IO 0x2f8
|
|
|
|
tp3780::EnableDSP, pSettings->bDSPEnabled 0 failed
|
|
|
|
Mwave Modem, ERROR cannot Enable DSP error fffffffb
|
|
|
|
Mwave Modem, ERROR cannot perform Mwave Initialization retval fffffffb</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><P
|
|
>If you receive a message like the one above, check the command line arguments you provided
|
|
|
|
to <B
|
|
CLASS="COMMAND"
|
|
>insmod</B
|
|
>.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="CONFLICTS">3.2. Resource Conflicts</H2
|
|
><P
|
|
>The ACP Modem requires the use of system resources for both
|
|
|
|
the DSP and the UART provided by the ACP chip. For Linux systems, you will specify parameters
|
|
|
|
to use for the duration of the boot with the
|
|
|
|
<B
|
|
CLASS="COMMAND"
|
|
>insmod mwave</B
|
|
> command line parameters listed in <A
|
|
HREF="startup.html#LOAD"
|
|
>Section 2.4.1</A
|
|
>.</P
|
|
><P
|
|
>Typically the configured resources are:</P
|
|
><TABLE
|
|
BORDER="0"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="PROGRAMLISTING"
|
|
>For the DSP: IRQ 10, I/O address 0x130-0x13f
|
|
|
|
For the UART: IRQ 3, I/O address 0x2f8 (if using ttyS1)
|
|
|
|
IRQ 4, I/O address 0x3f8 (if using ttyS0)</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><P
|
|
>For dual boot systems we recommeded that you use the Thinkpad™ Configuration Utility
|
|
|
|
on Windows NT or DOS to configure these system resources. </P
|
|
><P
|
|
>Windows NT Thinkpad Configuration Utility Notes:
|
|
|
|
(Under the <EM
|
|
>Internal Modem</EM
|
|
> --> <EM
|
|
>Advanced</EM
|
|
> selection)</P
|
|
><P
|
|
></P
|
|
><OL
|
|
TYPE="1"
|
|
><LI
|
|
><P
|
|
> Set IRQ sharing to disabled</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Set 1st IRQ to your DSP IRQ (10 is recommened)</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Set 2nd IRQ to your UART IRQ (i.e. ttyS1 is equivalent to COM2)</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Set the DSP I/O address (0x130 is recommended)</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Set the internal modem I/O address to the UART I/O address
|
|
|
|
(i.e. 0x2f8 for COM2)</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>The DMA address is unused and can be set to anything.</P
|
|
></LI
|
|
></OL
|
|
><DIV
|
|
CLASS="NOTE"
|
|
><P
|
|
></P
|
|
><TABLE
|
|
CLASS="NOTE"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="25"
|
|
ALIGN="CENTER"
|
|
VALIGN="TOP"
|
|
><IMG
|
|
SRC="../images/note.gif"
|
|
HSPACE="5"
|
|
ALT="Note"></TD
|
|
><TH
|
|
ALIGN="LEFT"
|
|
VALIGN="CENTER"
|
|
><B
|
|
>NOTE</B
|
|
></TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
> </TD
|
|
><TD
|
|
ALIGN="LEFT"
|
|
VALIGN="TOP"
|
|
><P
|
|
>You may also specify parameters to use for the duration of the boot by using the
|
|
|
|
<B
|
|
CLASS="COMMAND"
|
|
>insmod mwave</B
|
|
> line parameters listed in section <A
|
|
HREF="startup.html#LOAD"
|
|
>Section 2.4.1</A
|
|
>.</P
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="SPEED">3.3. Not Connecting at Specified Starting Speed</H2
|
|
><P
|
|
>The configured initial connection speed is set to 64000.
|
|
|
|
The modem should start there and negotiate down to a
|
|
|
|
connection speed based on target modem and line capabilities.
|
|
|
|
If the modem is unable to connect it may be having difficulty
|
|
|
|
negotiating with the target modem. Try setting the SPEED
|
|
|
|
parameter in <TT
|
|
CLASS="FILENAME"
|
|
>mwavem.conf</TT
|
|
> to a lower initial starting
|
|
|
|
speed. Supported speeds include:</P
|
|
><P
|
|
></P
|
|
><UL
|
|
><LI
|
|
><P
|
|
> 64000</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
> 33600</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
> 14400</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
> 9600</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
> 2400</P
|
|
></LI
|
|
></UL
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="DETECTPORT">3.4. Dialer Application Cannot Detect Serial Port</H2
|
|
><P
|
|
>The startup script that executes the serial port setup works well with Red Hat, Debian, Slackware,
|
|
|
|
and SuSE. If you are not running one of these distributions, you may need to perform the following steps
|
|
|
|
in order to set up.</P
|
|
><P
|
|
> After inserting the mwave.o module and starting the <SPAN
|
|
CLASS="APPLICATION"
|
|
>mwavem</SPAN
|
|
>
|
|
|
|
application, you must run the <B
|
|
CLASS="COMMAND"
|
|
>setserial</B
|
|
> command in order for the serial port configuration to discover the
|
|
|
|
UART on the mwave hardware:</P
|
|
><TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>setserial /dev/ttySx autoconfig</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><P
|
|
>Replace ttySx with the serial port you have configured the ACP driver to use.</P
|
|
><P
|
|
>To test whether the serial port is setup correctly, run:</P
|
|
><TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>setserial /dev/ttySx</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><P
|
|
>The above command should return the following for serial port 1:</P
|
|
><TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
>/dev/ttyS1, UART: 16550A, Port: 0x2f8, IRQ: 3</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><P
|
|
>The port and IRQ numbers should match the information placed
|
|
|
|
in the syslog by the ACP module when it was loaded:</P
|
|
><TABLE
|
|
BORDER="0"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="PROGRAMLISTING"
|
|
>kernel: Mwave Modem, UART settings IRQ 0x3 IO 0x2f8</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><P
|
|
>If the information returned by <B
|
|
CLASS="COMMAND"
|
|
>setserial</B
|
|
> indicates that the UART is
|
|
|
|
'unknown' or if the IRQ and I/O resources do not match what you
|
|
|
|
have in the syslog, you will need to reconfigure. Check the <B
|
|
CLASS="COMMAND"
|
|
>setserial</B
|
|
>
|
|
|
|
man pages to learn how to setup the resources on your ttySx to
|
|
|
|
match what appears in the syslog output.</P
|
|
><P
|
|
>If you have problems running <B
|
|
CLASS="COMMAND"
|
|
>setserial</B
|
|
>, you may have a resource
|
|
|
|
conflict. Before using <B
|
|
CLASS="COMMAND"
|
|
>insmod mwave</B
|
|
>, check <TT
|
|
CLASS="FILENAME"
|
|
>/proc/ioports</TT
|
|
> and
|
|
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>/proc/interrupts</TT
|
|
> to make sure the resources you intend to claim
|
|
|
|
are not already in use.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="SECT2"
|
|
><H2
|
|
CLASS="SECT2"
|
|
><A
|
|
NAME="PPPERRORS">3.5. PPP Errors Using 2.4.0 Version of the Kernel</H2
|
|
><P
|
|
>When upgrading to the 2.4.0 version of the kernel be sure to read the
|
|
|
|
<TT
|
|
CLASS="FILENAME"
|
|
>./Documentation/Changes </TT
|
|
>file. Kernel 2.4.0 requires an upgraded
|
|
|
|
version of the pppd, gcc, and modutils (amoung other things).
|
|
|
|
Follow the instructions for setting up the new pppd daemon
|
|
|
|
carefully.</P
|
|
><P
|
|
>You may experience some initial problems getting ppp running with 2.4.0. One of the most
|
|
|
|
prevelant errors we received was, "Can't locate module tty-ldisc-3." However, we had no problems
|
|
|
|
once we rebuilt the kernel with the following options:</P
|
|
><TABLE
|
|
BORDER="0"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="100%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="PROGRAMLISTING"
|
|
>CONFIG_PPP=y
|
|
|
|
CONFIG_PPP_ASYNC=m
|
|
|
|
CONFIG_PPP_SYNC_TTY=m
|
|
|
|
CONFIG_PPP_DEFLATE=m
|
|
|
|
CONFIG_PPP_BSDCOM=m </PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="startup.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="debugging.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Compilation, Installation, and Startup</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Debugging Tips</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |