From owner-freebsd-questions Tue Feb 7 19:14:39 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id TAA19521 for questions-outgoing; Tue, 7 Feb 1995 19:14:39 -0800 Received: from netcom7.netcom.com (fod@netcom7.netcom.com [192.100.81.115]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id TAA19512 for ; Tue, 7 Feb 1995 19:14:26 -0800 Received: by netcom7.netcom.com (8.6.9/Netcom) id TAA02199; Tue, 7 Feb 1995 19:12:42 -0800 Date: Tue, 7 Feb 1995 19:12:42 -0800 From: fod@netcom.com (Frank O'Donnell) Message-Id: <199502080312.TAA02199@netcom7.netcom.com> To: questions@FreeBSD.org Subject: Problem with third serial port Sender: questions-owner@FreeBSD.org Precedence: bulk I recently installed FreeBSD 2.0 on a 486DX2-66 equipped with a no-name multifunction card with two serial ports at what MS-DOS calls COM1 and COM2, plus a Hayes Accura 144 internal modem card at COM3. All three serial ports use the standard addresses; COM1 and COM3 share IRQ 4. COM1 is unused, while the Microsoft mouse is on COM2. All three serial ports are reported by the AMI BIOS on bootup, and none of my DOS/Windows programs has any trouble finding and using the internal modem card on COM3. A couple of days ago I posted a message to this list reporting that FreeBSD was not finding the modem on the third serial port (i.e. sio2) on bootup. Per a suggestion here, I recompiled the kernel after adding a line "options ALLOW_CONFLICT-IRQ" to the source and changing the irq in the "device sio2" line from irq5 to 4. However, it still didn't find the modem. I then deleted the line for sio0 and recompiled the kernel another time; still no luck. I'm surprised that it still isn't finding it, given that DOS programs don't have any trouble with it. Short of changing out the hardware, is there anything else I can try? The modem will _not_ let me reset the IRQ or address, although it will let me choose between COM1-2-3-4. The multifunction card also doesn't allow selection of IRQ or address on the serial ports, and although it theoretically lets you disable COM1 this doesn't seem to be working right. Thanks for any suggestions, Frank fod@netcom.com