At 01:59 PM 3/21/99 -0500, Michael Stearne wrote [abridged]:
>Any ideas? Where in Linux is the modem handled besides at runtime,
>it is just a device that reacts to commands like a hard disk?
Yes and no. The serial ports are detected by the kernel, and the associated
/dev entries can be reconfigured using setserial. But the modem itself is an
external device (even an internal modem, if it works with Linux, *looks
like* an external device to the OS) so isn't itself considered by anything
except apps that are designed to do things with it.
>
>Also, this modem has worked before in the same distribution, I just
>reinstalled the
>dist. last night and haven't touched any of the config files throughout,
>so they should be just like the factory settings.
Michael, this comment illustrates a serious problem that occurs when people
ask for help, here or elsewhere. Why didn't you tell us this in the first
place? For that matter, why didn't you mention that the modem worked
properly under Win98 in your first message? Until now, I had assumed from
your questions that the modem had *never* worked with Linux. This wastes
both my time and yours. So please consider more carefully what information
to include when you ask questions in the future.
As to the specifics of your problem, something has obviously changed. Might
it be the phone line or the ISP? For instance, does Win98 still connect
correctly TODAY? How many times did the Linux connection fail in the way you
described (might it be an isolated bad port at the ISP end, for example)?
Hypertrm and the Win ppp app do use init strings, even if you didn't input
particular ones, and you might want to check what they are. But if the modem
used to work under Linux, this is less a priority than I thought before.
Unfortunately, your AT&Z command displays only the AT settings, not the S
register values, and they are what we need to see to find out if the modem
is misset. On my modems, AT&Z lists the registers as well, but your must use
a different command for that. See if you can find it in your manual, I guess
(or does anyone else know offhand?).
What /dev/ttyS* entry is the modem located on? What does setserial report
about that S* device? And BTW, what Linux distribution/version are you using?
The core question, as I see it, is where this 300 bps setting is coming
from, and all of my suggestions are oriented toward helping you figure that out.
Good luck.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
