8.3.1. I get a /dev/modem no such device error.
First of all, check if you really have the drivers loaded. You can do this by the command
This command lists all the modules that you have loaded, and if you see something like
Module Size Used by
ptserial 47472 0 (unused)
pctel 1211808 0 [ptserial]
then, the modules are correctly loaded.
If not, just load them and retry.
Also check whether the file /dev/modem is symlinked to /dev/ttyS15
Remember, even if msdos or Microsoft Windows tells you that the modem is in com 3 or com 4, in GNU/Linux the driver makes it appear in
/dev/ttyS15 (the Microsoft equivalent of which will be com 16!!)
If you are in doubt, I suggest that you re-create the device files by the commands
bash$ rm /dev/ttyS15 /dev/modem
mknod /dev/ttyS15 c 62 79
NOTE: the numbers after /devttyS15 are distribution specific, and the c 62 79 works for Red Hat
Linux and derivatives. If you have any other distribution, please check your documentations.
chgrp uucp /dev/ttyS15
chmod 666 /dev/ttyS15
ln -s /dev/ttyS15 /dev/modem
8.3.2. My dialer gives a No Carrier error
This is a bug with the drivers for the kernel 2.4x series
Refer to section 7.6 for more information.
8.3.3. I get a No Dialtone message.
This is usually solved by adding ATX3 to your modem init strings.
The process of adding the ATX3 init string varies depending on the dialer you are using.
For example, if you are using wvdial, you need to add X3 at the end
of the Init2 line in the file /etc/wvdial.conf.
On the other hand, if you are using KPPP, you will have to add ATX3 in
the Initialization String 1 field, which can be found in the
Modem Commands section of the Modem
of the Setup dialogue box of KPPP.
8.3.4. I get a Modem Busy error.
First of all, check if the drivers are loaded or not and then see, if any program is using the modem.
If everything seems to be all right, try to find out the irq of your modem with the command
If the irq listed is obviously incorrect (like 0) (or does not tally with your M$-Windows configuration) then either use the setserial command
setserial /dev/ttyS15 irq * (where * is the irq of your modem)
or fiddle with the BIOS settings (see section 7.8)
Another possibilty may be that your sound modules are conflicting with the PCTel modules. Refer to section 7.10 for this.