From owner-freebsd-hardware Thu Jun 26 16:28:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA19007 for hardware-outgoing; Thu, 26 Jun 1997 16:28:16 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA19002 for ; Thu, 26 Jun 1997 16:28:13 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id QAA28217; Thu, 26 Jun 1997 16:28:40 -0700 (PDT) To: "Jin Guojun[ITG]" cc: freebsd-hardware@FreeBSD.ORG, jinouye@cse.ogi.edu Subject: Re: IRQ assignment for PII motherboards In-reply-to: Your message of "Thu, 26 Jun 1997 12:30:11 PDT." <199706261930.MAA09301@george.lbl.gov> Date: Thu, 26 Jun 1997 16:28:39 -0700 Message-ID: <28213.867367719@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This is no a real BIOS problem. Two ways to solve it: > (1) boot -c > irq xxx # For a pair of PCI devices? That would be an interesting trick. I don't think you read his message in enough detail. :-) > (2) recompile your kernel. Please refer the freebsd manual. Won't help either - see above. The bigger issue here for me at least is why this doesn't work with a shared IRQ. I've had, for example, my SMC (PCI) ethernet card and my Adaptec 2940 on the same IRQ and it worked just fine. No problems. What are the symptoms of failure with the shared IRQ this person is having? Are they sure it's because of IRQ sharing that this problem exists, or is it perhaps something else? Jordan