From owner-freebsd-questions@FreeBSD.ORG Fri Aug 1 07:42:15 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 1B51F37B401 for ; Fri, 1 Aug 2003 07:42:15 -0700 (PDT) Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4845443FA3 for ; Fri, 1 Aug 2003 07:42:14 -0700 (PDT) (envelope-from stanb@panix.com) Received: from panix.com (brillig.panix.com [166.84.1.76]) by mail1.panix.com (Postfix) with ESMTP id 96DAA49166; Fri, 1 Aug 2003 10:42:13 -0400 (EDT) Received: from teddy.fas.com (pcp01010374pcs.mplsnt01.sc.comcast.net [68.58.176.69]) by panix.com (Postfix) with ESMTP id 4970A2AA10; Fri, 1 Aug 2003 10:42:13 -0400 (EDT) Received: from stan by teddy.fas.com with local (Exim 3.36 #1 (Debian)) id 19ib6i-0007yA-00; Fri, 01 Aug 2003 10:42:12 -0400 Date: Fri, 1 Aug 2003 10:42:12 -0400 From: stan To: "J. Seth Henry" Message-ID: <20030801144212.GC30259@teddy.fas.com> Mail-Followup-To: "J. Seth Henry" , Free BSD Questions list References: <1059662053.28758.8.camel@alexandria> <20030731171848.GA4365@teddy.fas.com> <1059716254.30080.4.camel@alexandria> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1059716254.30080.4.camel@alexandria> X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.21 X-Uptime: 10:29:33 up 3 days, 1:02, 1 user, load average: 0.09, 0.03, 0.01 User-Agent: Mutt/1.5.4i Sender: Stan Brown 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 14:42:15 -0000 On Fri, Aug 01, 2003 at 01:37:35AM -0400, J. Seth Henry wrote: > 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. > The card is a generic PCI card, it's labeled "Mercury" on the box, and has a Sun chip on it. I see it's detected as a Dolphin card, and I _assume_ that is correct. The weirdness with it being COM5 and COM6 had to do with weirdness in my kernel conf file. I suspect the problem is that I need to pass certain flags in the kernel conf, but I don't know which ones. The good news is, after having spent a couple of days fighting this, and getting to the point I was locking up the computer with it, it dawned on me that I had started out there. So I went back and found out that I probably had the IO address for the on-board CO<1 chip wrong originally. Now it seems to be working, which will let me deploy the machine! Thanks for your help on this. I still plan on putting the PCI card in another machine and trying to get it to work, but that may take a while to get to. -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin