Date: Fri, 25 Oct 2002 06:29:17 -0400 From: "Patrick Cable II" <freebsd@slaudiovis.org> To: <freebsd-stable@freebsd.org> Subject: RE: configured irq not * in bitmap of probed irqs #,,, strange modem weirdness Message-ID: <GEEGJMKEOCMNOBOAHIOMEEOBCAAA.freebsd@slaudiovis.org> In-Reply-To: <20021025045340.GA62538@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?GEEGJMKEOCMNOBOAHIOMEEOBCAAA.freebsd>