From owner-freebsd-questions Tue Jul 16 17:32:00 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA23150 for questions-outgoing; Tue, 16 Jul 1996 17:32:00 -0700 (PDT) Received: from phs.k12.ar.us (garman@phs.k12.ar.us [165.29.117.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA23127 for ; Tue, 16 Jul 1996 17:31:52 -0700 (PDT) Received: from localhost (garman@localhost) by phs.k12.ar.us (8.6.12/8.6.12) with SMTP id TAA24545; Tue, 16 Jul 1996 19:31:33 -0500 Date: Tue, 16 Jul 1996 19:31:33 -0500 (CDT) From: Jason Garman 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: > Hi, > > Made a boot floppy of 2.1.5 -RELEASE to show my buddy how cool FreeBSD is! > 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. > I got bitten by his one too. A workaround that I found was to select "com 1" from the install menu, and do a set device /dev/cuaa1 from iij-ppp. It took me several hours of continuous head-banging to figure this out :-) It seems that if you do a 'term' with one device open and then change it with "set device" it ignores the change, which was really annoying me at the beginning... -- Jason