From owner-freebsd-questions@FreeBSD.ORG Tue Apr 6 01:59:18 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F1A2106567A for ; Tue, 6 Apr 2010 01:59:18 +0000 (UTC) (envelope-from jhall@socket.net) Received: from mf5.socket.net (mf5j.socket.net [216.106.26.218]) by mx1.freebsd.org (Postfix) with ESMTP id 1083A8FC08 for ; Tue, 6 Apr 2010 01:59:17 +0000 (UTC) Received: from [10.129.40.204] (216.106.19.47.reverse.socket.net [216.106.19.47]) by mf5.socket.net (Postfix) with ESMTP id ABC426C810 for ; Mon, 5 Apr 2010 20:59:16 -0500 (CDT) Message-Id: <64467532-26D9-4AB6-8B73-7F892AB82B3B@socket.net> From: Jay Hall To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 5 Apr 2010 20:59:15 -0500 X-Mailer: Apple Mail (2.936) Subject: ttyu0 link down X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Apr 2010 01:59:18 -0000 Ladies and Gentlemen, Earlier today, I had to dial into a server to check a link from both sides (a router was down). This evening, when I connected to the server I am not able to connect to the modem. From dmesg uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] Using cu -l /dev/ttyu0 I receive a message stating "link down". I have issued a kill -HUP 1 to restart the ttys and receive the same message. The same thing happens when rebooting the server. Trying to open the port with minicom, I receive the following message minicom: cannot open /dev/cuau0: Operation not permitted If I change the port to /dev/ttyu0, I receive the following message minicom: cannot open /dev/ttyu0: Permission denied Permissions on /dev/ttyu0 and /dev/cuau0 are as follows crw------- 1 root wheel 0, 41 Apr 5 20:03 /dev/ttyu0 crw-rw---- 1 uucp dialer 0, 44 Apr 5 20:03 /dev/cuau0 Is this a hardware issue or am I missing something else? Thanks, Jay