Linmodems Mailing list Archives

	Web archives.linmodems.org

Return-Path: <jcwren@jcwren.com>
Mailing-List: contact discuss-help@linmodems.org; run by ezmlm
Delivered-To: mailing list discuss@linmodems.org
Received: (qmail 181 invoked from network); 1 Feb 2002 19:32:47 -0000
Received: from dsl092-212-008.atl1.dsl.speakeasy.net (HELO jcwren.com) (66.92.212.8)
  by www.linmodems.org with SMTP; 1 Feb 2002 19:32:47 -0000
Received: from kd4dts (kd4dts.private.com [172.16.0.2])
	by jcwren.com (8.11.6/8.11.2) with SMTP id g11JWJA29240
	for <discuss@linmodems.org>; Fri, 1 Feb 2002 14:32:19 -0500
Reply-To: <jcwren@jcwren.com>
From: "John Chris Wren" <jcwren@jcwren.com>
To: <discuss@linmodems.org>
Subject: RE: COMPUSERVE issue, RE: Modem connects, won't negotiatate a protocol
Date: Fri, 1 Feb 2002 14:32:19 -0500
Message-ID: <NDBBKBJHGFJMEMHPOPEGCEIHDLAA.jcwren@jcwren.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <RELAY1XrbCZBnxEf1vn00003b52@relay1.softcomca.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal

	This is NOT a PPP protocol type problem.  Compuserve and Bellsouth.net are
nothing more than points to call into for testing.  Both give text login
prompts, and my other 3 analog modems all behave as expected.

	As I noted below, I used minicom to dial both.  On the other 3 modems,
after a carriage return or two, I get a text login prompt.  I change from
/dev/ttyS1 to /dev/modem (the Linmodem), make the *exact* same call, and I
get no data passed.

	As a further data point, I have a friend who set his modem up for me to
dial into.  When I connect to his modem with the other 3 modems, we can
carry on a keyboard conversation.  With the Linmodem, it connects, but no
data is passed.  And again, ATI11 reports that no protocol was established
(this is the internal modem protocol, such as MNP, V.34, etc, not PPP).

	--John

> -----Original Message-----
> From: stodolsk@rcn.com [mailto:stodolsk@rcn.com]
> Sent: Friday, February 01, 2002 14:06 PM
> To: jcwren@jcwren.com; discuss@linmodems.org
> Subject: COMPUSERVE issue, RE: Modem connects, won't negotiatate a
> protocol
>
>
> Would someone familar with the Compuserve specific issues please
> help John.
> This is a protocol, NOT a driver problem.
>
> A help may be to use wvdial, which I recall has an option
>  compuserve = yes
>
> THere is a  wvdial URL and Users list you could query,
> with the URL mentioned in DOCs/ltmodem.txt
>
> MarvS
>
>
> Original Message:
> -----------------
> From: John Chris Wren jcwren@jcwren.com
> Date: Thu, 31 Jan 2002 00:51:08 -0500
> To: discuss@linmodems.org
> Subject: Modem connects, won't negotiatate a protocol
>
>
> 	I've got a ThinkPad i1400 (2611-411) with a Lucent 'Luna'
> 1641B modem.  I'm
> running RH 7.2, kernel 2.4.9-21, and the ltmodem-600b14 code base from
> http://www.heby.de/ltmodem.
>
> 	The modem is configured, dials properly from minicom,
> negotiates, then
> never passes traffic.  A 'ATI11' command (report last connection status)
> indicates the modem connected with V.90, acceptable data rates,
> but that no
> protocol was ever negotiated.
>
> 	I've tried dialing into Bellsouth.net and a Compuserve
> local access number
> (which made me feel dirty afterwards...), same behavior.  I've
> tried various
> protocol limiting, such as only V22, V.34, V.90, etc, all with the same
> result.  The modem does eventually time out and produce a NO CARRIER
> message.
>
> 	I have found one other page
> (http://users.forthnet.gr/ath/goyiosn/linux/linux.html) about a
> fellow with
> a 2611-410, and except for we have slightly different interrupts allocated
> (my 11 vs his 3, since my PCMCIA ethercard is taking 3), we're
> basically the
> same as far as configuration.
>
> 	I'm hoping someone here has some insight.  The one
> possibility is that
> there may be some FLASH based firmware that needs upgrading, but
> I am unsure
> of this.  The IBM support site is unclear on this.  If I do need
> to re-flash
> the modem, I need a DOS only tool that will fit on a floppy
> (unless I could
> do it from WINE...).  I was under the impression that the
> firmware should be
> a function of the code uploaded into the modem when the ltmodem drivers
> load.
>
> 	While I may have missed something obvious, I've spent 5 or
> 6 hours hunting
> the 'net, trying various combinations.  Any recommendations would
> be greatly
> appreciated.
>
> 	--John
>
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
>
>