From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 17 08:40:28 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C055A16A401; Fri, 17 Mar 2006 08:40:28 +0000 (UTC) (envelope-from ckern1@twcny.rr.com) Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5E9943D5A; Fri, 17 Mar 2006 08:40:26 +0000 (GMT) (envelope-from ckern1@twcny.rr.com) Received: from reddwarf.local (cpe-69-202-106-69.twcny.res.rr.com [69.202.106.69]) by ms-smtp-02.nyroc.rr.com (8.13.4/8.13.4) with ESMTP id k2H8eOhK029188; Fri, 17 Mar 2006 03:40:24 -0500 (EST) Received: from reddwarf.local (localhost [127.0.0.1]) by reddwarf.local (8.13.4/8.13.4) with ESMTP id k2H8eOwb001190; Fri, 17 Mar 2006 03:40:24 -0500 (EST) (envelope-from ckern1@reddwarf.local) Received: (from ckern1@localhost) by reddwarf.local (8.13.4/8.13.4/Submit) id k2H8eNLf001189; Fri, 17 Mar 2006 03:40:23 -0500 (EST) (envelope-from ckern1) Date: Fri, 17 Mar 2006 03:40:23 -0500 From: Clayton Scott Kern To: John Baldwin Message-ID: <20060317084023.GA731@reddwarf.local> References: <20060316184128.GA12770@reddwarf.local> <200603161555.41213.jhb@freebsd.org> <20060316222407.GA727@reddwarf.local> <200603162158.02027.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200603162158.02027.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Unable to get SIIG PCI serial card to work X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 08:40:29 -0000 on 03-16-2006, John Baldwin wrote: > On Thursday 16 March 2006 05:24 pm, Clayton Scott Kern wrote: > > on 03-16-2006, John Baldwin wrote: > > > Ok, can you get a dmesg from a boot with your custom kernel with puc in > > > it and the output from kldstat -v with that kernel booted? > > > > Here's the info you requested. When not loading the puc module in > > /boot/loader.conf, the puc device isn't found, though pciconf -lv shows > > the device. I added the output of pciconf -lv at the end. > > > > Output of dmesg > > > > Copyright (c) 1992-2005 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights reserved. > > FreeBSD 6.0-RELEASE-p5 #0: Sat Mar 11 12:12:08 EST 2006 > > root@reddwarf.local:/usr/obj/usr/src/sys/GENERIC > > This kernel doesn't have 'device puc' in it. If it did, it would have the > 'pci/puc' and 'puc/sio' modules listed in the kldstat -v output. Make sure > you have built a custom kernel with 'device puc' enabled, installed it, and > are booting from it. > > > Output of kldstat -v > > > > Id Refs Address Size Name > > 1 11 0xc0400000 63072c kernel > > Contains modules: > > Id Name > > 26 xpt > > 27 probe > > 28 cam > > ... > > No puc this list tells me 'device puc' isn't in this kernel. :) > Thank you for all your help. I thought I had built and installed the new kernel. This time I did both and now dmesg shows: puc0: port 0x9000-0x901f,0x9400-0x941f mem 0xe30 04000-0xe3004fff,0xe3000000-0xe3000fff irq 16 at device 8.0 on pci0 sio1: on puc0 sio1: type 16550A sio1: unable to activate interrupt in fast mode - using normal mode sio2: on puc0 sio2: type 16550A sio2: unable to activate interrupt in fast mode - using normal mode sio3: on puc0 sio3: type 16550A sio3: unable to activate interrupt in fast mode - using normal mode sio4: on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode and kldstat -v | fgrep puc yields: 174 pccard/puc 175 pci/puc 176 cardbus/puc 187 puc/sio 337 puc/ppc Now when I run tip using sio1 - sio4 (aliases for /dev/cuad1-4), I get a message saying connected, but when I press enter, instead of getting my firewall's menu, I get nothing. I rebooted the system into Windoze and it works fine using TerraTerm Pro. -- Clayton Scott Kern ckern1@twcny.rr.com | The software stated it required Firewall/UNIX System Administrator | Microsoft Windows 98SE or higher, PIX, FreeBSD, Linux, Solaris & HP-UX | so I installed FreeBSD