From owner-freebsd-newbies Wed Jul 8 19:41:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08616 for freebsd-newbies-outgoing; Wed, 8 Jul 1998 19:41:15 -0700 (PDT) (envelope-from owner-freebsd-newbies@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08555 for ; Wed, 8 Jul 1998 19:40:55 -0700 (PDT) (envelope-from chrisc@vmunix.com) Received: from localhost (chrisc@localhost) by vnode.vmunix.com (8.8.8/8.8.8) with SMTP id WAA20702; Wed, 8 Jul 1998 22:40:40 -0400 (EDT) (envelope-from chrisc@vmunix.com) Date: Wed, 8 Jul 1998 22:40:40 -0400 (EDT) From: Chris Coleman X-Sender: chrisc@vnode Reply-To: Chris Coleman To: Ken Seggerman cc: FreeBSD Newbies Mailing List Subject: Re: more modem trouble In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Will this require a kernel re-build? It shouldn't, the serial drivers should be in your kernel. type: dmesg | grep sio This will tell you if the sio0 (COM1) driver is in your kernel. If this reveals nothing, you can try talking to the COM port using cu. cu -l /dev/cuaa0 This will connect you to the modem. You can try the other different com ports cuaa1 cuaa2 etc.. If the device is there, but not configured, you can try this. cd /dev sh MAKEDEV cuaa0 This will rebuild your COM port device. -Chris > > Thanks, > Ken > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-newbies" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message