From owner-freebsd-hardware Tue Mar 4 16:20:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA26646 for hardware-outgoing; Tue, 4 Mar 1997 16:20:44 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA26575 for ; Tue, 4 Mar 1997 16:20:37 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA18729; Wed, 5 Mar 1997 10:49:34 +1030 (CST) From: Michael Smith Message-Id: <199703050019.KAA18729@genesis.atrad.adelaide.edu.au> Subject: Re: Problems with 2.1 Probe? In-Reply-To: <331CA8C4.5058@kerris.com> from Mike Kerr at "Mar 4, 97 05:57:08 pm" To: mkerr@kerris.com (Mike Kerr) Date: Wed, 5 Mar 1997 10:49:34 +1030 (CST) Cc: freebsd-hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike Kerr stands accused of saying: > I've had, on occasion, difficulty with my system probing my modem. I've > gone through the following progression: > > 14.4K No problems detecting it. (100%) > 28.8K Occasional problems detecting it. (60%) > 33.6K Seems to refuse to detect it. (10%) > > The percentages is an estimate of how often it will work. Each time the > modem has been configured to COM3 (sio2) on IRQ 4, with the standard 3e8 > base address. > > It's getting *really* frustrating. I've even tried changing the IRQ on > this latest attempt to IRQ 3, but it still won't detect it. The machine > I'm running is a 386DX-40 with 8M RAM. Neither IRQ 3 nor 4 are available if you have sio0 or sio1 respectively configured; you will have to use a different interrupt in that case. > Is anybody aware of any incompatibilities with 386 motherboards and fast > COM ports, or if the probe has problems, or if there is a way I can > bypass the probe to get the thing to work? If your modem is an internal unit, and it does not have a _real_ UART on the board, it's likely that it is too _slow_, and the 2.1 sio probe is giving up on it. You could try booting a 2.2 installation disk to see if it finds it, once you have fixed your interrupt problem. > Oddly enough, if I boot into my DOS partition and use something like > Telemate, it works fine. DOS communications programs have very low expectations of serial hardware. You could probably jam a digestive biscuit into an ISA slot and log on to your favorite BBS with it, but that won't work too well with the BSD sio driver. > Mike. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[