From owner-freebsd-stable Thu Oct 24 21:53:45 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 C119E37B404 for ; Thu, 24 Oct 2002 21:53:42 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-165-226-88.dsl.lsan03.pacbell.net [64.165.226.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB8F043E3B for ; Thu, 24 Oct 2002 21:53:41 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2D04066C7B; Thu, 24 Oct 2002 21:53:41 -0700 (PDT) Date: Thu, 24 Oct 2002 21:53:40 -0700 From: Kris Kennaway To: The Gupta Age Cc: Ray Kohler , freebsd-stable@freebsd.org Subject: Re: configured irq not * in bitmap of probed irqs #,,, strange modem weirdness Message-ID: <20021025045340.GA62538@xor.obsecurity.org> References: <200210240657.09596.ataraxia@cox.net> <20021024173705.S475-100000@kashmir.etowns.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline In-Reply-To: <20021024173705.S475-100000@kashmir.etowns.net> User-Agent: Mutt/1.4i 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 --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 24, 2002 at 05:40:11PM -0700, The Gupta Age wrote: >=20 > On Thu, 24 Oct 2002, Ray Kohler wrote: >=20 > | > |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. > | > |- @ > | > | >=20 > 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 --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9uM5UWry0BWjoQKURAqCQAKDs6l04LabNfROH51DrpBeLq9WyigCgjskX EySe8dBn5dexZw9NeroBh0U= =bs+H -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message