Date: Sun, 21 Jan 1996 16:34:26 +0100 (MET) From: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de> To: deasey@server1.netpath.net (Geoffrey Deasey) Cc: kuku@gilberto.physik.rwth-aachen.de, caleb@crl.com, freebsd-questions@freebsd.org Subject: Re: find sio3 Message-ID: <199601211534.QAA11389@gilberto.physik.rwth-aachen.de> In-Reply-To: <Pine.LNX.3.91.960121100344.19797A-100000@server1.netpath.net> from "Geoffrey Deasey" at Jan 21, 96 10:04:33 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > I thought the conflict address was 12e8, so would this not be com4 ? sio0==com1 .... sio3==com4 #define IO_COM4 0x2E8 /* COM4 i/o address */ > > ------------------------------------------------------------------ > FreeBSD / Linux | Netpath, Inc & Stratonet, Inc. | > ------------------+ 2466 Corporation Parkway | > Opinions are mine | Burlington, NC 27215 910-226-0425 | > not theirs +----------------------------------------------+ > > > On Sun, 21 Jan 1996, Christoph Kukulies wrote: > > > > > > > when RELEASE 2.1 boots it see's sio1 &sio2 > > > but not sio3. What do i need to edit so 2.1R see's my very > > > inexpensive internal(archtek,smartlink:v32) Modem > > > running on an AMD 486DX66, 8m ram, vesa vlb,512cache > > > > sio3 usually conflicts with S3 based graphics boards. So > > you cannot use it at the standard sio3 address. > > > > > > > > > > this modem works well in dos as comm 4 irq3(2e8) > > > > > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601211534.QAA11389>