I installed Storm Linux last night on my P100. It's running great with the exception of one detail. When I try to connect to the internet (56k), if I have /dev/modem as my modem, my computer freezes, all I can do is drop to the command line. If I have /dev/tty# (# = 0 - 3) as my modem, it wont do anything. I think it may be a conflict somewhere between my modem and my mouse, but I don't know where to check or change this. Any help would greatly be appreciated.
CyPHoN
I suppose that your modem is one of type "WinModem", hwich I personally hate, because they waste a lot of CPU cycles and when connecting the system freezes for about one second... That kind of modem has a "small" problem: they're half hardware, and the other half software, and the manufacturers offers only drivers for Win32. I think that you should use a modem which is made in the "old style", I mean a modem which actually has built-in the communications port, and that port configures as standard serial port [dev/cuaa0, dev/cuaa1 etc, depending on what OS you use]
At this point you should have no problem...
A good replacement for your modem is an external one, is a guaranteed solution.
The modem I have is listed on linux.com under hardware, "Works fine, fast and very easy to install. This is a must have for any linux user."
it's a hardware modem, the AOpenUSA FM56
Check /var/log/messages (it may be in a different place, or named differently such as syslog) for clues to whats going on...
ARGH!!!
ok... I decided to install Mandrake instead of Storm Linux, and I'm still having the same problem. Depending on the type of flow control I have, when I query the modem I will either get "The modem is not responding " (CRTSCTS), or It will go through everything and then have blank for all the response fields (XOn/XOff and None).
If I choose any other devices as the modem, I get "Sorry, the modem is busy"
I'm wondering if perhaps you are linking /dev/modem to the wrong device. If you link it to something like ttyS01 (COM 2 in Redhat), and you happen to have a mouse or some other device attached, that will definitely cause problems...
I little trick I was able to use once was to
echo "ATDT5551212" > /dev/ttyS01
You should hear it dial. If not, try another
echo "ATDT5551212" > /dev/ttyS1
echo "ATDT5551212" > /dev/ttyS[0]2
You may have to chenga the example I gave here to suit your specific system...
A simple resource is here:
http://www.westga.edu/~stu7440/linux/modem.txt