Linux ACP Modem (Mwave) mini-HOWTO, page 9 by Mike Sullivan
<< Return to Title Details & Download10
serial 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 setserial man pages to learn how to setup the resources on your ttySx to match what appears in the syslog output.
If you have problems running setserial, you may have a resource conflict. Before using insmod mwave, check /proc/ioports and /proc/interrupts to make sure the resources you intend to claim are not already in use.
-----
3.5. PPP Errors Using 2.4.0 Version of the Kernel
When upgrading to the 2.4.0 version of the kernel be sure to read the ./ Documentation/Changes 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.
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: CONFIGPPP=y CONFIGPPPASYNC=m CONFIGPPPSYNCTTY=m CONFIGPPPDEFLATE=m CONFIGPPPBSDCOM=m
-----
4. Debugging Tips
4.1. Error Logs
Errors encountered by the ACP Modem device driver or application are logged using the syslog utility.
-----
4.2. Tracing
The ACP device driver supports a debug argument to enable the generation of trace information. The command for this debug is listed below. You can also access several of the variables listed below in the mwaved script. +---------------------------------------------------------------------------+ |insmod mwave mwavedebug=0x0f | +---------------------------------------------------------------------------+
Where the following debug trace information is selectable: 0x01 ACP Modem Device driver entry points 0x02 Systems Management API(SMAPI) 0x04 Hardware Interfac