+
+mISDN is the successor of isdn4linux, and also consists of kernel modules
+that are part of the Linux kernel. The mISDN modules have been rewritten
+from scratch since the old isdn4linux modules were difficult to maintain.
+
+The new mISDN modules are based on the CAPI interface (see question
+[ for more details on the CAPI
+interface). Not all ISDN cards supported by isdn4linux have been/will be
+ported to mISDN. For the moment, isdn4linux can still be used in parallel
+with mISDN, but this may change in the future.
+
+For more technical and configuration information about the mISDN driver
+see question ][.
] general_hardware: What hardware is supported by isdn4linux?
@@ -1400,14 +1419,18 @@ If the interrupt for the card is shared with other devices and your card does
not work, then there could be an issue with the motherboard. See question
[ for this.
-One very interesting thing: the Fritz! card is currently the only passive card
-for which a capi driver exists. As a result, it can be configured to
+One very interesting thing: the Fritz! card was the first card
+for which a capi driver existed which can be configured to
fax. See question ][ and
]
for more information on this. Usage of the capi driver is completely optional,
you might as well stay with the standard driver if you do not need capi
support.
+In total three drivers exist: the old Hisax driver (part of isdn4linux), the
+new mISDN driver, and the binary AVM driver. Only the last one is prepared
+for sending faxes.
+
hardware_avmb1: What is special about the AVM B1 card?
@@ -1897,6 +1920,8 @@ howto (isdn.html) and a ISDN quick-install guide (isdnquick.html).
- Tips to configure Red Hat:
+- Tips to configure Debian with Fritz Card PCI and kernel 2.6 (in German):
+
- Tips to configure Mandrake:
- Tips to configure Gentoo:
@@ -5181,6 +5206,15 @@ for communicating, but can log outgoing calls from any device.
See also question
[
for using two ISDN cards for logging.
+] isdnlog_enoughdata: How can I check whether isdnlog receives enough
+information from the kernel drivers?
+
+First stop isdnlog (e.g. "killall isdnlog"), then run "cat /dev/isdnctrl0".
+When you trigger some activity on the isdn line (e.g. by initiating an
+incoming call) you should see lines starting with "HEX:" or "D2:" in the
+output of the cat command. If these lines are missing then check your
+configuration of the kernel drivers.
+