Linux ACP Modem (Mwave) mini-HOWTO, Mike Sullivan [best summer reads .txt] 📗
- Author: Mike Sullivan
- Performer: -
Book online «Linux ACP Modem (Mwave) mini-HOWTO, Mike Sullivan [best summer reads .txt] 📗». Author Mike Sullivan
+---------------------------------------------------------------------------+
2.4. Runtime
An initialization script has been provided which may be used to to start,
stop, or check the status of the ACP Modem driver and application. It has
been successfully run on the Debian, Slackware, SuSE, and Red Hat
distributions and should run on any of their derivitives. If you are using
the runtime script, it will load the mwave device driver module, configure
the serial port, and start the mwave manager for you. All of the options
which can be passed to the device driver module, along with some options for
the script itself, can be configured by uncommenting and editing the
appropriate variables at the beginning of the script.
The mwaved startup script can be found in the src/mwavem directory of the
source distribution. If you are running the Red Hat distribution, you can
copy the script to your /etc/rc.d/init.d directory and issue the ntsysv
command in order to enable it at boot time. If not using Red Hat, see the
documentation for your distribution for information on how to set this up to
run at boot time.
It is recommended that you use the provided mwaved script. If you are not
using the script, however, the following sections will describe how to
manually start the device driver and application.
2.4.1. Loading the ACP device driver
To load the mwave device driver use
+---------------------------------------------------------------------------+
|insmod mwave |
+---------------------------------------------------------------------------+
or
+---------------------------------------------------------------------------+
|modprobe mwave |
+---------------------------------------------------------------------------+
The following arguments may be supplied with the insmod command:
Note NOTE
� The following arguments are not persistent from boot to boot (i.e. We
are not saving them in the BIOS).��*�mwave_3780i_irq=5/7/10/11/15
This parameter allows you to configure the IRQ used by the DSP if the DSP IRQ was not set and stored in BIOS by the Thinkpad?? configuration utility.��*�mwave_3780i_io=0x130/0x350/0x0070/0xDB0
This parameter allows you to configure the I/O range used by the DSP if the DSP I/O range was not set and stored in the BIOS by the Thinkpad?? configuration utility.��*�mwave_uart_irq=3/4
This parameter allows you to configure the IRQ used by the ACP UART if the Mwave's UART IRQ was not set and stored in BIOS by the Thinkpad?? configuration utility.��*�mwave_uart_io=0x3f8/0x2f8/0x3E8/0x2E8
This parameter allows you to configure the I/O range used by the ACP UART if the UART I/O range was not set and stored in BIOS by the Thinkpad?? configuration utility.The following code is an example of how to run DSP using ttyS1 resources:
+------------------------------------------------------------------------------------------+
|insmod mwave mwave_3780i_irq=10 mwave_3780i_io=0x0130 mwave_uart_irq=3 mwave_uart_io=0x2f8|
+------------------------------------------------------------------------------------------+
Note NOTE
� The mwave is unable to check for resource conflicts. It is your
responsibility to ensure that none of the resources specified conflict with other (commonly PCMCIA) devices.You can use the tpctl package on Linux or the Thinkpad?? configuration
utility on Windows NT or DOS to manage the configuration of Thinkpad??
related resources.
2.4.2. Running ACP Modem Application
Once the ACP device driver is loaded successfully, use the mwavem command
to execute the application.
Note NOTE
� The location of the mwavem.conf file can be specified as an
argument to the mwavem application. If not specified the default location is assumed to be /usr/local/etc/mwavem.conf unless otherwise changed during the build process.Setup the serial driver to recognize the UART provided by the ACP driver.
+---------------------------------------------------------------+
|setserial /dev/ttyS0 autoconfig |
+---------------------------------------------------------------+
Note NOTE
� Substitute /dev/ttyS0 to match the serial port you have
configured the DSP to use.Note NOTE
� You may wish to create a symbolic link from your modem
device to your serial device for convenience. Example: ln -s /dev/ttyS0 /dev/modemThe ACP Modem is now available for use by your favorite dialing application.
Resolving Installation and Configuration ProblemsThe following sections list solutions to possible problems you may
experience.
3.1. DSP Does Not Start
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 lilo.conf file. For example, if you had a
machine with 128 Meg you would type:
+---------------------------------------------------------------------------+
|append="mem=130496K" |
+---------------------------------------------------------------------------+
Note NOTE
� 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.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:
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
If you receive a message like the one above, check the command line arguments
you provided to insmod.
3.2. Resource Conflicts
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 insmod mwave command line
parameters listed in Section 2.4.1.
Typically the configured resources are:
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)For dual boot systems we recommeded that you use the Thinkpad?? Configuration
Utility on Windows NT or DOS to configure these system resources.
Windows NT Thinkpad Configuration Utility Notes: (Under the Internal Modem --
Advanced selection)
Set IRQ sharing to disabled
Set 1st IRQ to your DSP IRQ (10 is recommened)
Set 2nd IRQ to your UART IRQ (i.e. ttyS1 is equivalent to COM2)
Set the DSP I/O address (0x130 is recommended)
Set the internal modem I/O address to the UART I/O address (i.e. 0x2f8
for COM2)
The DMA address is unused and can be set to anything.
Note NOTE
� You may also specify parameters to use for the duration of the boot by
using the insmod mwave line parameters listed in section Section 2.4.1.3.3. Not Connecting at Specified Starting Speed
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
Comments (0)