From owner-freebsd-questions Sat Mar 14 13:20:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03297 for freebsd-questions-outgoing; Sat, 14 Mar 1998 13:20:12 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from bbs.mpcs.com (bbs.mpcs.com [204.215.226.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03274; Sat, 14 Mar 1998 13:20:04 -0800 (PST) (envelope-from hgoldste@bbs.mpcs.com) Received: (from hgoldste@localhost) by bbs.mpcs.com (8.8.8/8.8.7/MPCS spamzap) id QAA19198; Sat, 14 Mar 1998 16:19:56 -0500 Date: Sat, 14 Mar 1998 16:19:56 -0500 From: Howard Goldstein Message-Id: <199803142119.QAA19198@bbs.mpcs.com> To: freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Cc: efinley@castlenet.com, lauralyng@rocket.comtrol.com, tomm@comtrol.com Subject: Re: Rocketport DTR, 2.2.5R, mgetty - RESOLVED In-Reply-To: <199803141730.MAA09924@bbs.mpcs.com> Reply-To: hgoldste@bbs.mpcs.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In previous episodes I wrote: : : Under 2.2.5R? comtrol's August drivers fail to diddle DTR under : 2.2.5R, and -current drivers under 2.2.5R with enough patching so : they'll build get stuck in ioctl() forever. This turned out to be woefully incorrect. More verbose logging of mgetty's activities revealed that the real culprit was mgetty's attempted use of vtime. That mgetty didn't have a problem with vtime in operating on the standard cuaa ports, and too-terse logging, conspired to lead to an erroneous conclusion about broken DTR control. Rebuilding mgetty with BROKEN_VTIME (and reassigning the August comtrol driver's idea of major device #s to the one assigned in -current (i.e., 81), but this reassigment might not have been necessary under 2.2.5R...) fixed the problem. To the folks on the Cc: list, thank you for your advice and comments. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message