From owner-freebsd-stable@FreeBSD.ORG Tue Nov 29 13:39:34 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B734A16A420 for ; Tue, 29 Nov 2005 13:39:34 +0000 (GMT) (envelope-from sebastian.ssmoller@gmx.net) Received: from sigma.informatik.hu-berlin.de (sigma.informatik.hu-berlin.de [141.20.20.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6A0843D6E for ; Tue, 29 Nov 2005 13:39:29 +0000 (GMT) (envelope-from sebastian.ssmoller@gmx.net) Received: from tyrael.linnet (p54BCEA8C.dip.t-dialin.net [84.188.234.140]) (authenticated bits=0) by sigma.informatik.hu-berlin.de (8.13.4+Sun/8.13.4/INF-2.0-MA-SOLARIS-2.10) with ESMTP id jATDd4M6002778 for ; Tue, 29 Nov 2005 14:39:25 +0100 (CET) Date: Tue, 29 Nov 2005 14:37:45 +0100 From: sebastian ssmoller To: freebsd-stable@freebsd.org Message-Id: <20051129143745.64788cd5.sebastian.ssmoller@gmx.net> In-Reply-To: <1133247949.1071.11.camel@leguin> References: <1133247949.1071.11.camel@leguin> X-Mailer: Sylpheed version 1.0.5 (GTK+ 1.2.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Status: No (sigma) X-Spam-Status: No, score=1.8 required=5.0 tests=FORGED_RCVD_HELO, RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on rabe Subject: trouble with cuad0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 13:39:34 -0000 hi, yesterday i updated one of my dev boxes from 5.3 to 6.0. this box has two serial ports. i use "cu -l cuadX -s 38400" to connect some external "devices". this works perfectly fine with cuad1 but not with cuad0. on cuad0 i only get "connected" from cu but then the line is not usable (no echo, no input seems to reach the other end). on 5.3 both serial ports worked perfectly fine this way. anyone any idea what happend? is there some special handling for cuad0? btw: the same happens on my laptop (running an older -current) when using cuaU0 ... thx regards, seb