Date: Tue, 16 Jul 1996 19:31:33 -0500 (CDT) From: Jason Garman <garman@phs.k12.ar.us> To: Steve Emmert <steve@emmert.com> Cc: questions@FreeBSD.ORG Subject: Re: Comm port trouble in 2.1.5 install Message-ID: <Pine.LNX.3.92.960716192910.24455A-100000@phs.k12.ar.us> In-Reply-To: <Pine.BSI.3.94.960715184357.320B-100000@free.emmert.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.3.92.960716192910.24455A-100000>