From owner-freebsd-questions@FreeBSD.ORG Thu Jul 31 22:37:57 2003 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 BB08E37B401 for ; Thu, 31 Jul 2003 22:37:57 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38F5343F3F for ; Thu, 31 Jul 2003 22:37:57 -0700 (PDT) (envelope-from jshamlet@comcast.net) Received: from [192.168.1.1] (pcp04633217pcs.gambrl01.md.comcast.net[68.49.68.116](untrusted sender)) by comcast.net (rwcrmhc12) with SMTP id <2003080105373501400k3pp7e>; Fri, 1 Aug 2003 05:37:36 +0000 From: "J. Seth Henry" To: stan In-Reply-To: <20030731171848.GA4365@teddy.fas.com> References: <1059662053.28758.8.camel@alexandria> <20030731171848.GA4365@teddy.fas.com> Content-Type: text/plain Organization: Message-Id: <1059716254.30080.4.camel@alexandria> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 01 Aug 2003 01:37:35 -0400 Content-Transfer-Encoding: 7bit cc: Free BSD Questions list Subject: Re: Help PLEASE! on proper kernel config file to use serial ports with puc driver 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, 01 Aug 2003 05:37:58 -0000 Stan, Could you describe your hardware in a bit more detail. I can't imagine why your system would hard lock, unless there is something seriously wrong. Also, I'm curious why puc is detecting your card as sio4 and sio5 (COM5 and COM6 respectively) Most mainboards only have sio0/COM1 and sio1/COM2. What is using sio2 and sio3? BTW - I would start from a generic kernel configuration if you don't remember what you did. Then, make the necessary changes to the copy of GENERIC, and go from there. Then, rebuild the kernel - it probably isn't necessary, but it will at least return your kernel to something closer to the baseline. Regards, Seth Henry On Thu, 2003-07-31 at 13:18, stan wrote: > On Thu, Jul 31, 2003 at 10:34:14AM -0400, J. Seth Henry wrote: > > All you need in your kernel config is 'device puc'. You already appear > > to have this in your config, as your system detected the adapter. > > > > Him > > I've made some "progress" on this ;-( > > I have created teh devices in /dev. I now have just the puc line in the > kernel config, and the ports are getting detected like this: > > puc0: port 0xfce0-0xfcff irq 11 at device 6.0 on pci0 > sio4: type 16550A > sio5: type 16550A > > That;s the good nes. The bad news is that when I do "cu -l cuaa4", the > computer locks up! No response to any keyboard input, no response to a ping > etc. I have to power cycle it to get it back :-( > > Sugestions?