The OpenNET Project / Index page

[ новости /+++ | форум | теги | ]

Поиск:  Каталог документации

2. Compilation, Installation, and Startup

2.1. Prerequisites

If you are building the ACP Modem driver along with the user space application, you need to have a complete Linux source tree for your kernel, not just an up-to-date kernel image.

2.2. Building and Installing Source

  1. Use tar xzvf mwavem-yyyymmdd.tar.gz to unpack the distribution.

  2. Change directories with cd mwavem-yyyymmdd

  3. Use the ./configure command to configure the build options. Issue ./configure --help to view all of the options. The defaults are probably okay though.


    As of mwavem-1.0.3 you must give ./configure the --enable-mwavedd argument in order to build the driver with the user space application.

  4. Use the make command to build all of the ACP Modem binaries.


    Your gcc package should be at least at the 2.7.x level. Check your /usr/src/linux/Documentation/Changes file for the minimum version information.

  5. Use make install to install the mwavem binary, mwavem.conf configuration, the extra binary (mostly .dsp) files, and module device driver (if you specified that it must be built) and to create the /dev/modems/mwave device node.

2.3. Setting Things Up

In the [WORLDTRADE] section of your mwavem.conf file, set the Country= parameter to your country access code.


The mwavem.conf file is installed in the /usr/local/etc directory unless you specified otherwise during the build process

Country information (including access codes) are listed in the mwavem.conf file. For example, for France the following section is present:

[Telephony\Country List\33]






To set France to be your configured country in the [WORLDTRADE] section of mwavem.conf,
set Country=33

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
modprobe mwave

The following arguments may be supplied with the insmod command:


The following arguments are not persistent from boot to boot (i.e. We are not saving them in the BIOS).

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


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

  1. Once the ACP device driver is loaded successfully, use the mwavem command to execute the application.


    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.

  2. Setup the serial driver to recognize the UART provided by the ACP driver.

    setserial /dev/ttyS0 autoconfig


    Substitute /dev/ttyS0 to match the serial port you have configured the DSP to use.


    You may wish to create a symbolic link from your modem device to your serial device for convenience. Example: ln -s /dev/ttyS0 /dev/modem

The ACP Modem is now available for use by your favorite dialing application.

Inferno Solutions
Hosting by

Закладки на сайте
Проследить за страницей
Created 1996-2024 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру