From owner-freebsd-stable Fri Oct 25 3:30:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 211E937B401 for ; Fri, 25 Oct 2002 03:30:49 -0700 (PDT) Received: from gis.net (home.gis.net [208.218.130.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F3FF43E42 for ; Fri, 25 Oct 2002 03:30:43 -0700 (PDT) (envelope-from freebsd@slaudiovis.org) Received: from symplexity ([63.214.66.54]) by mail.gis.net; Fri, 25 Oct 2002 06:30:28 -0400 From: "Patrick Cable II" To: Subject: RE: configured irq not * in bitmap of probed irqs #,,, strange modem weirdness Date: Fri, 25 Oct 2002 06:29:17 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20021025045340.GA62538@xor.obsecurity.org> Importance: Normal X-Rcpt-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On a related note, I have a similar problem that i think may be causing a parallel port not to show up in CUPS. (Or that seems to be my only error on startup - perhaps you can tell me if im way off and looking in the very wrong direction?) Patrick Cable II -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Kris Kennaway Sent: Friday, October 25, 2002 12:54 AM To: The Gupta Age Cc: Ray Kohler; freebsd-stable@freebsd.org Subject: Re: configured irq not * in bitmap of probed irqs #,,, strange modem weirdness On Thu, Oct 24, 2002 at 05:40:11PM -0700, The Gupta Age wrote: > > On Thu, 24 Oct 2002, Ray Kohler wrote: > > | > |Go into your BIOS and turn off plug and play, if you haven't already. I seem > |to recall this being the solution to that problem in the past. > | > |- @ > | > | > > Didnt make any difference. it was actually off originally > turning it on produced the exact same dmesg(as far as devices go). > any other suggestion/input will be very appreciated. I deleted the original mail in this thread, but I've seen this on two FIC VA-503+ mobos, for which the serial ports apparently just do not work properly (there was a BIOS update that allegedly fixed this for some version of windows, but Windows 89 still fails to detect them). No matter what I do, the serial ports just do not generate interrupts. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message