From owner-freebsd-questions Thu Jun 4 21:32:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25252 for freebsd-questions-outgoing; Thu, 4 Jun 1998 21:32:17 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25122 for ; Thu, 4 Jun 1998 21:31:59 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id VAA26678; Thu, 4 Jun 1998 21:31:57 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Thu, 4 Jun 1998 21:31:57 -0700 (PDT) From: Doug White Reply-To: Doug White To: Marco Shaw cc: freebsd-questions@FreeBSD.ORG Subject: Re: Internal modem and cuaa1 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Jun 1998, Marco Shaw wrote: > No seriously, I'm running 2.2.6. I only have one physical COM port. I > checked 'dmesg' and it seems like the system is only activiating cua0 for > my mouse. When it can't find cua1 (sio1), it stops there and doesn't > start up sio2 or sio3 (kernel defaults to 4 COM ports). > > My intention was to setup my Internal USR 28.8 to cua2, irq 5, but since > the com port isn't activated then I certainly have a problem. My modem is > hardwire to cua2, irq 5 via the jumpers. > > How do I solve my problem? Can I change the jumpers to cua1, irq3 on my > modem and then bootup will 'find' cua1 or is my problem more complicated > then that since I only have one COM port? sio2 isn't configured into the kernel by default. Boot -c and enable it. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major NOTICE: gdi.uoregon.edu is going down, please use dwhite@resnet! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message