From owner-freebsd-questions Sat Nov 13 18:54: 5 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mail.kersur.net (mail.kersur.net [199.79.199.3]) by hub.freebsd.org (Postfix) with ESMTP id DBA9115225 for ; Sat, 13 Nov 1999 18:54:00 -0800 (PST) (envelope-from bcohen@bpecreative.com) Received: from mojomatic (nas-41-59.boston.navinet.net [216.67.41.59]) by mail.kersur.net (8.9.1/8.9.1) with SMTP id VAA03621; Sat, 13 Nov 1999 21:56:57 -0500 (EST) Reply-To: From: "Bob Cohen" To: "freebsd-questions" , "Christopher Michaels" , , Subject: RE: PnP Modem Question Date: Sat, 13 Nov 1999 21:54:59 -0500 Message-ID: <002d01bf2e4b$a40a0c10$0100a8c0@mojomatic> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <6C37EE640B78D2118D2F00A0C90FCB4401105D77@site2s1> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I second this. FWIW, I use the PnP USR 56K > faxmodem with no problems on > > cuaa4. > > I set up the interface with the /stand/sysinstall > > utility; I selected ppp0 on /dev/cuaa4 (COM5). > I did not do anything > > to my kernel to make it work, nor did I use MAKEDEV. It turns out that everyone had something relevant to bring to the table. cuaa4 WAS the correct device to specify in my com software but I did have to perform a MAKEDEV to enable cuaa4. Go figure. The weird thing was that I began the process with cuaa4 but got an error message stating that the device wasn't enabled. I assumed it had something to do with the serial ports as named sioX which in turn sent me off on a wild goose chase. cuaa4 is now enabled and my modem seems to work. Thanks to everyone for the help. Bob Cohen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message