Linmodems Mailing list Archives

	Web archives.linmodems.org

Return-Path: <goldberg@phep2.technion.ac.il>
Mailing-List: contact discuss-help@linmodems.org; run by ezmlm
Delivered-To: mailing list discuss@linmodems.org
Received: (qmail 676 invoked from network); 4 Sep 2001 18:18:10 -0000
Received: from mailgw2.technion.ac.il (132.68.238.35)
  by www.linmodems.org with SMTP; 4 Sep 2001 18:18:10 -0000
Received: from phep2.technion.ac.il (phep2.technion.ac.il [132.68.64.53])
	by mailgw2.technion.ac.il (Postfix) with ESMTP
	id 3A7A436D16; Tue,  4 Sep 2001 21:17:59 +0300 (IDT)
Date: Tue, 4 Sep 2001 21:17:48 +0300 (IDT)
From: Jacques Goldberg <goldberg@phep2.technion.ac.il>
Reply-To: Jacques Goldberg <Jacques.Goldberg@cern.ch>
To: Ker Nulov <ker@null.net>
Cc: "Trandahl, Steve" <steve.trandahl@cotelligent.com>,
	"'discuss@linmodems.org'" <discuss@linmodems.org>
Subject: Re: Ltmodem.html update Attached, Re: LTModem Unresol
In-Reply-To: <20010904134257.4560.qmail@qis>
Message-ID: <Pine.LNX.4.05_heb2.08.10109042054300.21087-100000@phep2.technion.ac.il>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 4 Sep 2001, Ker Nulov wrote:

> Hi jaques
> 
> Trandahl, Steve writes:
> 
> > Jacques,
> >
> > I am interested if and when you get the result of your testing.I am still
> > unable to connect without getting the NoEC under Linux.Everything runs
> 
> I hadn't followed your previus messages, but I cant tell you for sure that
> you get this error because your kernel isn't enabling your lucent modem on
> startup.

  Ker,

  First, thanks for taking the time to comment.
  Second, "for sure" is never certitude, because this error message
happens after the modems have gone through handshaking. If the modem would
not have been enabled, in addition to ATDT or any other AT command which
indeed does not need enabling to do something (on that common knowledge I
of course agree with you), the modem would not actually dial, cause the
other hand to go off hook, and negotiate a protocole.
  The problem is more subtle than that. It comes from wrong assignment of
one of the resources (IRQ, ports), probably but not for sure some
conflict. 
  Either the local modem does not transmit significant bits or it does not
receive bits sent by the remote modem. 
  Indeed after I connect to my ISP (reading CONNECT NoEC on my screen)
which expects a carriage return, nothing happens, so either it is not sent
out or the reply (logon prompt)  is not received.
  I would need two machines and two phone lines to determine which
direction is failing: enough to see if what I try to type appears or not
on a dumb terminal emulator at the other end. I am willing to bet a very
small amount of money that the local modem does not receive. Not sure at
all.

  Finally, here is how this develops:
  I first set my BIOS to non-PnP OS. The BIOS sets the registers in the
modem (mine is PCI not ISA by the way, but Steve too sees the same
problem). Ltmodem works perfectly. The kernel and ltmodem correctly
autodetect the IRQ and the two ports.
  Then I reset my BIOS to PnP OS. The BIOS does not set the registers in
tge modem. Forcing the priorily detected parameters fails completely (NO
DIALTONE which IS what happens when the modem is not enabled). With the
same IRQ and ports used under Windows, I get actual dialling, actual
handshaking, and the CONNECT NoEC message, after which nothing passes
along.
  My understanding is that NoEC reflects the failure of the modems to talk
between them although the analog part of the line is definitely working.

  I personally do not mind working as no-PNP OS, but clearing out this
problem might be of interest to other users, less lucky then me, without
the possibility to set their BIOS as I happily can.

                                                 Jacques