From owner-freebsd-questions Mon Apr 24 12:32:37 2000 Delivered-To: freebsd-questions@freebsd.org Received: from fedde.littleton.co.us (fedde.littleton.co.us [216.17.174.44]) by hub.freebsd.org (Postfix) with ESMTP id 9A35C37B531 for ; Mon, 24 Apr 2000 12:32:33 -0700 (PDT) (envelope-from cfedde@fedde.littleton.co.us) Received: from fedde.littleton.co.us (localhost [127.0.0.1]) by fedde.littleton.co.us (8.10.0/8.10.0) with ESMTP id e3OJWUb05230; Mon, 24 Apr 2000 13:32:30 -0600 (MDT) Message-Id: <200004241932.e3OJWUb05230@fedde.littleton.co.us> To: Bill Richter Cc: questions@FreeBSD.ORG Subject: Re: sio2 inop after 3.4R -> 4.0R upgrade In-Reply-To: From: Chris Fedde Date: Mon, 24 Apr 2000 13:32:30 -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 19 Apr 2000 19:23:01 -0700 (PDT) Bill Richter wrote: +------------------ | After migrating to 4.0R, with a GENERIC kernel, sio2 enabled | or manually configured using the boot floppy setting sio2/IO_COM3/irq9 | I'm rewarded with | sio2: configured irq 9 not in bitmap of probed irqs 0 +------------------ I had a similar problem. I found that after upgrading the kernel was allocating irq 9 to another purpose: $ dmesg | grep 'irq 9' unknown2: at port 0x300-0x301 irq 9 on isa0 After I moved my serial port controler to an unused irq the problem went away. Good luck chris -- Chris Fedde 303 773 9134 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message