Date: Sun, 24 Aug 1997 16:38:00 +1000 (EST) From: Andrew <perrya@python.shoal.net.au> To: bob olbrich <rjob@gulftel.com> Cc: freebsd-questions@freebsd.org Subject: Internal modem - can't install FreeBSD Message-ID: <Pine.BSI.3.95.970824162802.5314A-100000@python.shoal.net.au> In-Reply-To: <33FF8B97.17E8713D@gulftel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
ahhh, the penny drops, an internal modem. It looks like there is some kind of conflict preventing your internal modem from being detected. The only thing I can think of is disabling the other two com ports and seeing if it detects the si0 (com port 1) then. I unfortunately have no experience with internal modems. Does anyone know how to help Bob? Apparently when he boots the freebsd install disk it fails to detect the com ports (sio0 not found at 0x3f8) and he is subsequently unable to use the modem to dial up and install FreeBSD. thanks in advance Andrew Perry On Sat, 23 Aug 1997, bob olbrich wrote: > Date: Sat, 23 Aug 1997 20:17:12 -0500 > From: bob olbrich <rjob@gulftel.com> > Reply-To: 11923@gtc.gulftel.com, village@gtc.gulftel.com, > green@gtc.gulftel.com, drive@gtc.gulftel.com, > magnolia@gtc.gulftel.com, springs@gtc.gulftel.com, al@gtc.gulftel.com > To: perrya@python.shoal.net.au > Subject: com ports and setup utility > > Andrew, > > Yes, there is a way to change the addresses for the com ports. > But, as I said com1 is definitely the internal modem (3F8).The addresses > that show up > for the only other two ports (A & B) look like com2 and com3 (2F8 and > 3E8) > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.970824162802.5314A-100000>