Koozali.org: home of the SME Server

internal modems

Gerald Jansen

internal modems
« on: November 30, 1999, 12:06:55 AM »
I am setting up an e-smith server with an internal modem. I have used a Creative Labs,pnp,pic non Win modem and a generic 56k v.90 jumpered ISA with a cirrus logic cchip set both dial out but fail to "latch on". I have a feeling it is a handshake problem with the ISP. However, since e-smith generates no error messages I really can't tell. Does anyone have any ideas, or a favorite modem that almost always works. I am leaning toward a 3Com US robotics because they are usually sure fire. However I don't know which models work well with linus, Any idea? tia  :-)

Charlie Brady

RE: internal modems
« Reply #1 on: November 30, 1999, 10:49:23 AM »
Gerald Jansen wrote:

> I am setting up an e-smith server with an internal modem. I
> have used a Creative Labs,pnp,pic non Win modem and a generic
> 56k v.90 jumpered ISA with a cirrus logic cchip set both dial
> out but fail to "latch on". I have a feeling it is a
> handshake problem with the ISP. However, since e-smith
> generates no error messages I really can't tell.

I wouldn't go buying another modem into I had diagnosed the
problem some more.

Get to the login prompt using Alt-F3, then login as "root"
using your admin password. Look for messages related to
dialup in /var/log/messages. Report back to us here if you are
none the wiser after doing that.

Charlie

John Powell

RE: internal modems
« Reply #2 on: December 01, 1999, 02:54:11 AM »
I would agree with Charlie, you might be jumping to conclusions,
but then you might be right :)

If the logs don't show you anything obvious... try listening to
the train.  Does it sound wierd, perhaps constantly retraining?
If you can't hear it, try adding a M2 to the dial string, that will
force the speaker on, even after they connect.  If you want, stick
a mic up to the speaker and make a sound file (WAV, au, etc.) of
the training and email it to me (make it a med/low sample rate so
it isn't huge).

The other thing you can try is to use a term program and dial
your ISP manually (atdt.....).  Does it train then return a connect
message?  If all works well, at least on most ISP NASs, it will
return a login screen a few seconds after connect, and there
should not be any "garbage" on the screen (lots of garbage is
usually a sign of trouble negotiating error correction between
the modems and a sign of trouble).  Do note, garbage can also
be caused by PPP negotiation, and not be a problem, but most
NASs won't do that without client initiation, so it is a valid
warning sign.

If you do find it is a handshake problem, the first thing to try
is to disable V.90 (the command varies modem to modem).  If
that solves it (but you only get V.34), then yes, a 3Com/USR
modem is an excellent choice.  Might I recommend the 3Com/USR
PCI Internal Data/fax, it has been an excellent modem for me.

Also, and this should be obvious in the logs, look for authentication
problems.  Your symptoms so far could point to that to.

Hope this helps,
JP

David Crowe

RE: internal modems
« Reply #3 on: December 04, 1999, 04:44:44 PM »
I had the same problem with an ISA modem with cirrus chipset. It works fine under other distibutions so I know it is not a hardware problem. Nothing shows up in the logs either. The login seems to time out before completing. I am still searching for a solution. Perhaps the next point upgrade will allow more control over the modem.

Charlie Brady

RE: internal modems
« Reply #4 on: December 05, 1999, 11:36:01 AM »
David Crowe wrote:

> I had the same problem with an ISA modem with cirrus chipset.
> It works fine under other distibutions so I know it is not a
> hardware problem. Nothing shows up in the logs either. The
> login seems to time out before completing. I am still searching
> for a solution. Perhaps the next point upgrade will allow more
> control over the modem.

It's very hard to provide more options without knowing what possible
changes you want or need.  It's particularly strange that you say
that the modem works with other distributions, but not with e-smith,
since e-smith is using identical software. The dial string e-smith uses
is "ATL0M0DTnnnnnn" using the standard chat timeout.

I'm sure that there is *something* in the logs.  If there is any change that you'd like to make, see the documentation on http://www.e-smith.org.
Feel free to email me if you want help.

Charlie