Release Notes 93000351_5P for Digi DataFire RAS Digi AccelePort RAS Linux Driver Package dgdm-0.02-21.i386.rpm 11/05/99 Please reference the following number(s) when searching the Digi International web site (www.digi.com) or ftp site (ftp.digi.com) for the latest software package: RPM Part Number: 40002059_5P This Digi software package includes device drivers for the DataFire RAS and AccelePort RAS families of adapters. It is currently supported on the following hardware platforms: * Standard i386/Pentium PC and is currently supported on the following Linux distributions: * RedHat 5 * RedHat 6 * Debian Linux 2.1 This package requires tix and swig. If they are not installed on the target machine prior to installing this rpm, this rpm will refuse to install. Known Problems: * There is currently a problem with SMP locking such that if many ports are opened or closed in rapid succession, a user's system can lock up Changes in this release: * Fixed problem in firmware where high levels of traffic on the D-Channel could result in a hung channel. Never seen in a real-world environment, only while testing at Digi with a specific switch simulator - Q026, Vantive 3235 * Fixed problem in adapter firmware of modem showing RING messages after call had been abandoned * Fixed problem in adapter firmware to avoid adapter panic when we accessed non-allocated DSP. This resulted in the devices being inaccessible and hung PPP sessions. - Q023, Vantive 3232 * Fixed problem in adapter firmware of assigning a modem to take an incoming call before that modem was properly initialized. This problem had caused adapter panics and inaccessible devices. - Q025, Vantive 3234 * Fixed open/close bug that occured because opencnt and dxbchannel flags achieved a deadly embrace. Corrected the behaviour of both flags and added debug checking a self-repairing code. Results in hung ports - Q014, Vantive 3114 * Fixed improper interrupt clearing when dgdm adapter shares an IRQ with another adapter - Q024, Vantive 3233 * Fixes to correct spinlock problems with SMP installations - Q018, Vantive 3115 * Disabled line discipline OPOST processing since all OPOST processing is done by the adapter firmware * Fixed compile time error in dtrc.c * Enhanced dm_driver, dm_admin and dm_gui man pages * Enhanced dm_admin to allow jitter attenuation, numbering plan, address type and subaddress type to be specified * Corrected wrong NFAS ID display for port 2 * Reduced CPU utilization by fixing improper behaviour in select() calls * Changed dm_gui so that configuration commands are issued to adapters only if changes are made Software limitations: * The maximum combined number of Acceleport RAS and DataFire RAS adapters in one system is currently set to 4. * Although there are numerous places within the rpm that might imply support for additional hardware platforms, this release is valid only for i386 * The ISDN adapters supported by this release of the driver package can send and receive analog calls and also 64Kbs and 56Kbs digital ISDN calls. This driver package DOES NOT support the isdn4linux interface. In the case of ISDN calls, the firmware assumes the caller begins data transfer in sync PPP mode, and received sync PPP packets are translated into async PPP packets and passed up through the standard asynchronous devices. Transmitted async PPP packets are likewise translated into sync PPP packets before being transmitted over the ISDN link. This mode is initiated by either an incoming ISDN digital call or by a dialout with the AT dial command "ATDIXXXX" where XXXX is the phone number to dial. Additional Notes: * The dgdm driver is installed when the rpm is installed, i.e., the rpm dgdm.spec file does a "cd /usr/src/dg/dgdm/drv/linux" and a "make install". In order to make the driver available for use, you must cause the driver to be loaded. This can be accomplished by doing a "chkconfig --add dgdm" to cause the driver rc scripts enabled for start and stop, and then reboot the system. You can also do a "insmod dgdm" to cause the driver to be loaded without having to reboot. By combining these two steps, you can cause to driver to be loaded immediately and whenver the system is rebooted. Once the driver has been loaded, you must create device nodes before you can configure the dgdm adapters. To create device nodes, do a "/proc/dgdm/mknod". You must run this command any time adapters are added or changed. It creates device nodes for all dgdm adapters found on your system. It will not, however, remove any device nodes that do not match your current hardware configuration. In order to remove device nodes before creating new ones, do a "/proc/dgdm/mknod -d". This will remove ALL dgdm device nodes. Then do a "/proc/dgdm/mknod" to create device nodes that match your hardware configuration. NOTE that all device nodes are made with permissions equal to 664 and group/owner equal to root. Once device nodes have been created, you can configure the adapters that have been found on your system by the dgdm driver. See dm_driver(4) for additional details on the dgdm driver. * This package includes several support and configuration utilites including dm_admin, a command line utility, and dm_gui, a graphical utility. Both can be used to configure adapters as well as to display adapter configuration and status information. Refer to the man pages for these utilities for additional information. A copy of these release notes can be found in: /usr/src/dg/dgdm/drv/linux/release.notes after the rpm has been installed.