From owner-freebsd-questions@FreeBSD.ORG Mon Jan 15 11:10:22 2007 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9B98B16A4A0 for ; Mon, 15 Jan 2007 11:10:22 +0000 (UTC) (envelope-from weiwu@sdf.lonestar.org) Received: from bossdog.realss.com (bossdog.realss.com [211.157.108.128]) by mx1.freebsd.org (Postfix) with ESMTP id 3D01B13C4BA for ; Mon, 15 Jan 2007 11:10:22 +0000 (UTC) (envelope-from weiwu@sdf.lonestar.org) Received: from localhost (unknown [127.0.0.1]) by bossdog.realss.com (Postfix) with ESMTP id 0964D4CBD5B for ; Mon, 15 Jan 2007 18:44:26 +0800 (CST) Received: from bossdog.realss.com ([127.0.0.1]) by localhost (bossdog.realss.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15045-08 for ; Mon, 15 Jan 2007 18:44:22 +0800 (CST) Received: from [218.193.55.195] (unknown [59.57.239.56]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by bossdog.realss.com (Postfix) with ESMTP id C669D4CBCFF for ; Mon, 15 Jan 2007 18:44:21 +0800 (CST) From: Zhang Weiwu To: questions@freebsd.org Content-Type: text/plain Date: Mon, 15 Jan 2007 18:43:09 +0800 Message-Id: <1168857789.5592.12.camel@joe.realss.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at bossdog.realss.com Cc: Subject: how do I tell if my sio0 port is broken? 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: Mon, 15 Jan 2007 11:10:22 -0000 Hello List. I guess my sio0 port is broken on my Thinkpad, OS is FreeBSD-6.1. Reason: 1) I have tested a null-modem serial cable is working by using it on a dumb-terminal and a headless server. With the same cable and same headless server, but replace dumb-terminal with my thinkpad, run $ tip com1 connected Then, whatever key I press, nothing happens. Usually I should see login prompt after I pressed "Enter" key. Test was done with FreeBSD Generic kernel. 2) I have plugged a modem (with ordinary serial cable, not the null-modem one) on it and run minicom. If I type 'at' I should get 'OK' as prompt, but I didn't. The same modem and same cable work for another Linux box. 3) I go to BIOS and do a serial port test, test result is "OK", but I think bios have no knowledge if a port is broken when it's not connected to anything at all. So, I think next morning I should go and check if there are PCMCIA card that can provide an extra COM port, but before that I think I should write this letter to the list to see what you guys would do in this case: do you also think this looks like COM1 port is broken? Thank you very much for advices. Zhang Weiwu