From owner-freebsd-questions@FreeBSD.ORG Fri Apr 8 06:51:26 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A61616A4CE for ; Fri, 8 Apr 2005 06:51:26 +0000 (GMT) Received: from wizard.online.ee (wizard.online.ee [194.106.96.27]) by mx1.FreeBSD.org (Postfix) with SMTP id A998543D3F for ; Fri, 8 Apr 2005 06:51:24 +0000 (GMT) (envelope-from jani@soundflows.com) Received: (qmail 5886 invoked by uid 79); 8 Apr 2005 09:51:23 +0300 Received: from 194.106.123.34 by wizard (envelope-from , uid 78) with qmail-scanner-1.24st (clamdscan: 0.81/704. spamassassin: 3.0.2. perlscan: 1.24st. Clear:RC:0(194.106.123.34):SA:0(0.0/5.0):. Processed in 0.224928 secs); 08 Apr 2005 09:51:23 +2000 X-Spam-Status: No, hits=0.0 required=5.0 Received: from unknown (HELO ?194.106.123.34?) (194.106.123.34) by wizard.online.ee with SMTP; 8 Apr 2005 09:51:23 +0300 Message-ID: <4256298D.7080704@soundflows.com> Date: Fri, 08 Apr 2005 09:49:49 +0300 From: Jani Luukkanen User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jonathan Chen References: <4254EE05.8000302@soundflows.com> <20050407192714.GA3678@osiris.chen.org.nz> In-Reply-To: <20050407192714.GA3678@osiris.chen.org.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: Serial console connection problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2005 06:51:26 -0000 Hi Jonathan and thanks for reply! Jonathan Chen wrote: >I have an issue with serial console connection with two FreeBSD machines >(Both with Intel SE7210TP1-E motherboard, other configured as "host" >from bios and other has ordinary com ports which are connected with >normal tested serial cable). > >Host machine is running FreeBSD 5.3 and the "client" one 4.10. > >Problem is that when trying to open the serial connection with tip, >error occurs as; > >/root@mos root # tip com1 >tip: /dev/cuaa0: Device busy >link down > > > > > Weird, fstat shows nothing on the port; root@mos root # fstat /dev/cuaa0 USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME root@mos root # And yes, this is problem is on the 4.10 machine which is connecting to the 5.3 one. >Try running fstat(1) against /dev/cuaa0 to try to find out what's >holding the device. If I understand you correctly, you're doing this >on the 4.10 machine. > > > >>Main question is that how to get access first to the com1 port generally >>and second to get ahold of the remote screen on the other end of the >>serial cable? >> >> > > > Might be this is the problem, here is all gettys running on the 4.10 machine: root 246 0.0 0.1 956 516 v7 Is+ 16Mar05 0:00.00 /usr/libexec/getty Pc ttyv7 root 245 0.0 0.1 956 516 v6 Is+ 16Mar05 0:00.00 /usr/libexec/getty Pc ttyv6 root 244 0.0 0.1 956 516 v5 Is+ 16Mar05 0:00.00 /usr/libexec/getty Pc ttyv5 root 243 0.0 0.1 956 516 v4 Is+ 16Mar05 0:00.00 /usr/libexec/getty Pc ttyv4 root 242 0.0 0.1 956 516 v3 Is+ 16Mar05 0:00.00 /usr/libexec/getty Pc ttyv3 root 241 0.0 0.1 956 516 v2 Is+ 16Mar05 0:00.00 /usr/libexec/getty Pc ttyv2 root 240 0.0 0.1 956 516 v1 Is+ 16Mar05 0:00.00 /usr/libexec/getty Pc ttyv1 root 239 0.0 0.1 956 516 v0 Is+ 16Mar05 0:00.00 /usr/libexec/getty Pc ttyv0 root 238 0.0 0.1 956 516 d0 Is 16Mar05 0:00.00 /usr/libexec/getty std.9600 console The last one (console) does not appear on the 5.3 machines processlist, would it be safe to kill that one just like that with kill -9 238 (If that is the process locking the port)? The connection is ordinary serial cable, do you mean that should specify from BSD side what kind of connection is it? >Make sure that you haven't got a getty running at the same time on >both sides, and that you've got a null-modem connection between the two >hosts instead of a straight thru'. > >Cheers. > > Thanks and Cheers, Jani