From owner-freebsd-bugs  Sat Jul 29 21:32:58 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id VAA15537
          for bugs-outgoing; Sat, 29 Jul 1995 21:32:58 -0700
Received: from arthur.cs.purdue.edu (arthur.cs.purdue.edu [128.10.2.1])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id VAA15531
          for <bugs@freebsd.org>; Sat, 29 Jul 1995 21:32:57 -0700
Received: from ector.cs.purdue.edu (dpm@ector.cs.purdue.edu [128.10.2.10])
    by arthur.cs.purdue.edu (8.6.10/PURDUE_CS-1.3) with ESMTP
    id <XAA21778> for <bugs@freebsd.org>; Sat, 29 Jul 1995 23:32:54 -0500
Received: (dpm@localhost)
    by ector.cs.purdue.edu (8.6.10/PURDUE_CS-1.3)
    id <XAA03231> for bugs@freebsd.org; Sat, 29 Jul 1995 23:32:51 -0500
Date: Sat, 29 Jul 1995 23:32:51 -0500
From: dpm@cs.purdue.edu (David Moffett)
Message-Id: <199507300432.XAA03231@ector.cs.purdue.edu>
To: bugs@freebsd.org
Subject: tip(1) & modems(5) problems
Content-Length: 2006
Sender: bugs-owner@freebsd.org
Precedence: bulk

I just installed FreeBSD 2.0.5R.  Someone has been working on the tip(1)
sources and has installed /etc/modems(5) as a generalized modem configuration
file for tip/cu, instead of using the inbedded dialers.  Some problems,
as a result, have appeared:

1) If I use the 'generic' dialer, the commands being sent to the modem
   appear on my screen, and after some time a "cannot synchronize with
   Hayes" message occurs.  If I'm unlucky, I send a control-C in here
   and end up with a terminal in raw mode (stty -sane is my friend).
   If I'm lucky I wait it out and after a few more lines of stuff, it
   gives up and quits.

2) I tried to back out the changes, by turning off the generic
   dialing code and turning the Hayes code back on in the .h
   file.  It times out after producing the 

   dialing...

   message.  Immediately after generating the time out message, the modem
   dials, connects and everything works just fine.


Now my questions:

A) who did it?
B) will they fix/undo what they have done before 2.1 gets out
   please?  Patches before then would be nice.
C) the man page for /etc/modems claims 4.4 origination.  I've looked in
   4.4BSD's printed URM and there seemingly is no hint of /etc/modems.
   Attribution of /etc/modems to 4.4BSD is not a good or wise thing to
   do in the man page if it really isn't from 4.4.  Perhaps some policy
   should be written about attribution of features implemented by the
   FreeBSD team?

Background.  2.0.5R has trouble, 2.0.0R worked fine.  The modem is a
Practical Peripherals Data/Fax PM144MT II connected through a classic
IBM brand serial/parallel card.  The serial port in question is /dev/cuaa0.

Thanks as always.  Having source makes this kind of problem a minor
nit, not a show stopping pain.  Further, the configuration file is
a good idea, it would appear it's just not quite done yet.

I'm a news group reader, but not a mailing list reader.  So email
me with questions/comments/fixes.  :-)

David Moffett
(dpm@cs.purdue.edu)