From 08e8b75168f37e484b7f99583b8e60828a9b22c2 Mon Sep 17 00:00:00 2001 From: gferg <> Date: Sun, 29 Apr 2001 21:46:11 +0000 Subject: [PATCH] updated --- .../linuxdoc/Winmodems-and-Linux-HOWTO.sgml | 142 +++++++++++------- 1 file changed, 88 insertions(+), 54 deletions(-) diff --git a/LDP/howto/linuxdoc/Winmodems-and-Linux-HOWTO.sgml b/LDP/howto/linuxdoc/Winmodems-and-Linux-HOWTO.sgml index 3bfdc125..85e74096 100644 --- a/LDP/howto/linuxdoc/Winmodems-and-Linux-HOWTO.sgml +++ b/LDP/howto/linuxdoc/Winmodems-and-Linux-HOWTO.sgml @@ -4,36 +4,36 @@
-
-A Winmodem, like other modems, is used for accessing to phone services, as BBS, Internet, Voice Phone, Fax, etc. It is raccorded to a phone line and is caracterized by its speed. If you want to learn more about modems, I report you to the Modems-HOWTO.
+ A Winmodem, like other modems, is used for accessing to phone services, as BBS, Internet, Voice Phone, Fax, etc. It is raccorded to a phone line and is caracterized by its speed. If you want to learn more about modems, I report you to the Modems-HOWTO.
-But they are WINmodems. That is, they need Windows to work. Why ? Simply because they are stupid. They need a special software, a driver, to accomplice their complete task. Who says software says OS, and the drivers included with the modem are, at 99%, exclusively for the MS-Windows platform. But with the democratization of Linux, some manufacturers, like LT or Motorola, decided to create a linux driver for their modems. But they have not understand linux philosophy: the drivers they provide works, of course, but they are 'Closed Source'. They are free, at the sense of the price, but not under the GPL. It means that the sources are not available.
-So, some 'hackers' decided to make an Open Source driver, but they do not know a lot about their modems, because manufacturers don't want to communicate the specifications of their modems, so the OpenSource drivers are often in the alpha or beta status.
-
-1. Try to get the name of the serial port where your modem is connected (under Windows or MSDOS, example: COM1 COM2, ...).
-The name of your modem under Linux is /dev/ttySx, where x is the number of the serial port under DOS, - 1. <
-Example: Under DOS: COM1, under Linux ttySx, with x=1-1, so ttyS0
-2nd example: Under DOS: COM3, under Linux ttyS2
-and so on
-
+But they are WINmodems. That is, they need Windows to work. Why ? Simply because they are stupid. They need a special software, a driver, to accomplice their complete task. Who says software says OS, and the drivers included with the modem are, at 99%, exclusively for the MS-Windows platform. But with the democratization of Linux, some manufacturers, like LT or Motorola, decided to create a linux driver for their modems. But they have not understand linux philosophy: the drivers they provide works, of course, but they are 'Closed Source'. They are free, at the sense of the price, but not under the GPL. It means that the sources are not available.
+ So, some 'hackers' decided to make an Open Source driver, but they do not know a lot about their modems, because manufacturers don't want to communicate the specifications of their modems, so the OpenSource drivers are often in the alpha or beta status.
+ 1. Try to get the name of the serial port where your modem is connected (under Windows or MSDOS, example: COM1 COM2, ...).
+ The name of your modem under Linux is /dev/ttySx, where x is the number of the serial port under DOS, - 1. <
+Example: Under DOS: COM1, under Linux ttySx, with x=1-1, so ttyS0
+ 2nd example: Under DOS: COM3, under Linux ttyS2
+and so on
+
2. Make a symlink from /dev/ttySx to /dev/modem, by typing
ln -s /dev/ttySx /dev/modem
-Choose 'Serial Port Setup', type 'A' for setting 'Serial Device', delete all the line, and type '/dev/modem'. Then validate by [Enter]. Type [Esc], and choose 'save setup as dfl, then choose 'Exit'.
-Wait a little time, then type 'AT' if the modem answers 'OK' then you have NOT a Winmodem, you have a standard modem...
-If the initialisation time takes too long, then you have a Winmodem. Use this document for try making it useful. Log in as root.
+3. Download and install the minicom package. Then run 'minicom -s'.
+ Choose 'Serial Port Setup', type 'A' for setting 'Serial Device', delete all the line, and type '/dev/modem'. Then validate by [Enter]. Type [Esc], and choose 'save setup as dfl, then choose 'Exit'.
+Wait a little time, then type 'AT' if the modem answers 'OK' then you have NOT a Winmodem, you have a standard modem...
+ If the initialisation time takes too long, then you have a Winmodem. Use this document for try making it useful. Log in as root.
4. Exit from Minicom by typing CTRL+A, then X.
@@ -49,6 +49,7 @@ Ok, now we have a Winmodem... But there are two types of Winmodems: ISA or PCI.
Choose 'Any' in 'PCI Access Mode' (CONFIG_PCI_GOBIOS)
'PCI quirks' (CONFIG_PCI_QUIRKS)
'Backward compatible /proc/pci' (CONFIG_PCI_OLD_PROC)
+
'/proc filesystem support' (CONFIG_PROC_FS)
@@ -60,25 +61,37 @@ Now run 'cat /proc/pci'. If you see the name of your modem in the lines returned
If you don't find it, maybe you have an ISA modem. How to be sure ?
-ISA support is not assumed by the Kernel (the 2.4.* kernel will do it, but it is yet in a not-stable version...). It is a third-party software, named isapnp, who does it. First you must be sure that you have this package installed. If not install it by downloading the isapnptools package.
-Once isapnptools is installed, we'll run a special program, pnpdump, who inspects your computer for finding ISA devices. Then it tries to guess the resources used by the devices and prints them to a file, /etc/isapnp.conf. Then you edit this file and run an other program, isapnp, which reads the isapnp.conf file and auto configure your devices.
-
-Eh ? It sounds hard ? Then follow these steps:
-
-1. Run 'pnpdump > /etc/isapnp.conf'.
-2. Edit it with your favourite text editor
-3. Locate the section where your modem is described.
-4. Uncomment some lines in the file (Remove the # at the beginning of the line. You need:
-1 line '(IO 0 ...)'
-1 line '(INT 0 ...)'
-1 line '(DMA 0 ...)'
-1 line '(DMA 1 ...)'
-1 line '(IO 1...)'
-5. Remove the '(CHECK)' in all uncommented IO lines
-6. Run 'isapnp /etc/isapnp.conf'. If you get errors, edit the file isapnp.conf and try changing parameters, help you with the error message. If you get no errors, edit isapnp.conf and uncomment the '(ACT Y)' line in the secton of your modem. Then re-run 'isapnp /etc/isapnp.conf'. It must answer you " [[Name of your modem]] Enabled OK"
-7. Add 'isapnp /etc/isapnp.conf' to your /etc/rc.d/rc.local, by typing 'echo "isapnp /etc/isapnp.conf" >> /etc/rc.d/rc.local'. It is useful for auto-configuring your devices at each startup
-
-If it can help , here is an extract of my /etc/isapnp.conf file (I have commented this file, and original file comments are preceded by ##)
+ISA support is not assumed by the Kernel (UPDATED: if you have a
+2.4.x kernel, the kernel can do it automagically for you, if so, skip this
+section and read the next). It is a third-party software, named isapnp, who does
+it. First you must be sure that you have this package installed. If not install
+it by downloading the isapnptools package. Once isapnptools is installed,
+we'll run a special program, pnpdump, who inspects your computer
+for finding ISA devices. Then it tries to guess the
+resources used by the devices and prints them to a file,
+/etc/isapnp.conf. Then you edit this file and run an other
+program, isapnp, which reads the isapnp.conf file and auto
+configure your devices. Eh ? It sounds hard ? Then
+follow these steps: 1. Run 'pnpdump >
+/etc/isapnp.conf'. 2. Edit it with your favourite text
+editor 3. Locate the section where your modem is
+described. 4. Uncomment some lines in the file (Remove
+the # at the beginning of the line. You need: 1 line
+'(IO 0 ...)' 1 line '(INT 0 ...)' 1 line '(DMA 0
+...)' 1 line '(DMA 1 ...)' 1 line '(IO 1...)' 5.
+Remove the '(CHECK)' in all uncommented IO lines 6. Run
+'isapnp /etc/isapnp.conf'. If you get errors, edit the file
+isapnp.conf and try changing parameters, help you with the
+error message. If you get no errors, edit isapnp.conf and
+uncomment the '(ACT Y)' line in the secton of your modem.
+Then re-run 'isapnp /etc/isapnp.conf'. It must answer you "
+[[Name of your modem]] Enabled OK" 7. Add 'isapnp
+/etc/isapnp.conf' to your /etc/rc.d/rc.local, by typing
+'echo "isapnp /etc/isapnp.conf" >> /etc/rc.d/rc.local'. It
+is useful for auto-configuring your devices at each
+startup If it can help , here is an extract of my
+/etc/isapnp.conf file (I have commented this file, and
+original file comments are preceded by ##)
+If you have a 2.4 kernel (launch 'uname -r' to get your kernel version), you don't have to do this tricky textfile-based and third-party package installation, since 2.4 series introduce a method similar to the PCI, and obsoletes the isapnptools package. To get this feature, you have to say 'Y' or 'M' to the 'Plug and Play support' (CONFIG_PNP) and 'ISA Plug and Play support' (CONFIG_ISAPNP) during kernel configuration (it is in 'Plug and Play configuration' section). Again, recompile your kernel and install it. If you said 'M' to ISA Plug-and-Play support, it should be good to do a 'modprobe isapnp'. You have to have a driver compliant with this new device access method (eg. the ltmodem 5.78, read the next section).
+
+
+
You have not to read this section entirely; just read one matching with your modem. For the moment, it just describes how to install a LT Modem, using the Lucent and OpenSource driver. If you have written or used an other Winmodem driver, Open or Closed Source, you can email me (alexandre12@mageos.com), and I will include it in this section.
-
-URL:
+
+URL: http://www.tux.org/pub/dclug/marvin/ltmodem-5.78e.tar.gz
+Author: Lucent
+License: Non-GPL
+Supports: ISA/PCI modem, with a Lucent chipset (Mars family)
+Features: Kernel module; simulate a serial port. Does PPP, Fax and Voice
+Current Version: 5.78e
+Documentation: README-1ST
+Requires: 2.2.x or 2.4.x; ISA PNP Support; Loadable module support; C Compiler
+How-to-use: Read README-1ST. It is very clear.
+Problems:
+
+URL: http://www.linmodems.org/linux568.zip
Author: Lucent Technologies
License: Non-GPL
-Supports: ISA/PCI modems, with a Lucent chipsets (Mars family)
+Supports: ISA/PCI modems, with a Lucent chipset (Mars family)
Features: Kernel module; simulate a serial port. Does PPP, Fax and Voice
Current version (as far as I know): 5.68
Documentation: README
@@ -155,12 +190,12 @@ Problems:
-URL:
+URL: http://www.close.u-net.com
Authors: Richard Close and Pavel Machek
License: GPL
Supports: ISA/PCI modems, with Lucent chipsets (Mars family)
Feature: User-space driver; does Voice calls; does not PPP (V90)
-Current version (as far as I know): 0.9.2
+Current version (as far as I know): 0.99
Documentation: README
Requires: GNU C Compiler, automake
How-to-use:
@@ -180,9 +215,9 @@ Problems:
-
-
- Copyright (C) 2000 Alexandre J.
+
+ Copyright (C) 2000, 2001 Alexandre J.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
@@ -198,16 +233,15 @@ Problems:
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
-If you have any ideas about this document, pleace email me: alexandre12@mageos.com.
-
+If you have any ideas about this document, please email me:
+alexandre12@mageos.com.
-
-
-
-
-
+
+
+
+
+
+
rm -f /dev/modem
-3. Download and install the minicom package. Then run 'minicom -s'.
@@ -117,7 +130,7 @@ If it can help , here is an extract of my /etc/isapnp.conf file (I have commente
(IO 1 (SIZE 8) (BASE 0x0100) )
# Name of the card
(NAME "GVC5005/256[0]{LT Win Modem }")
-# Activitate it
+# Activate it
(ACT Y)
# End configuration
))
@@ -129,14 +142,36 @@ If it can help , here is an extract of my /etc/isapnp.conf file (I have commente
+