From owner-freebsd-questions Mon Jul 15 21:23:34 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA29972 for questions-outgoing; Mon, 15 Jul 1996 21:23:34 -0700 (PDT) Received: from gdi.uoregon.edu ([128.223.186.250]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA29963 for ; Mon, 15 Jul 1996 21:23:32 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id VAA02477; Mon, 15 Jul 1996 21:23:30 -0700 (PDT) Date: Mon, 15 Jul 1996 21:23:30 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Steve Emmert cc: questions@FreeBSD.ORG Subject: Re: Comm port trouble in 2.1.5 install In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Jul 1996, Steve Emmert wrote: > When I selected FTP install and COM 2 (/dev/cuaa1) then went to iij-ppp > the modem would not respond to "at". I then did a "show modem" and found > the device set to COM 1 (/dev/cuaa0). No amount of hacking with the option > selections or "set device" in iij-ppp would work to get the modem on-line > even when "show modem" displayed /dev/cuaa1. I took the disk back home and > tried it on my system with the same results. I even FTP'ed a new boot.flp > but nothing seems to work. My old 2.1 boot floppy works but a 2.2 -SNAP > boot floppy fails too. > > Any ideas?? Make sure sio0 is being probed. I just changed that option on my 2.1.5 installed machine, no problems. Did you check baudrate and data bits also? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major