From owner-freebsd-questions  Mon Aug 28 14:47: 3 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from mail.rz.uni-ulm.de (sirius-giga.rz.uni-ulm.de [134.60.241.36])
	by hub.freebsd.org (Postfix) with ESMTP id 7B0F237B422
	for <freebsd-questions@freebsd.org>; Mon, 28 Aug 2000 14:47:00 -0700 (PDT)
Received: from gmx.de (lilith.wohnheim.uni-ulm.de [134.60.106.64])
	by mail.rz.uni-ulm.de (8.9.3/8.9.3) with ESMTP id XAA18997;
	Mon, 28 Aug 2000 23:46:56 +0200 (MEST)
Message-ID: <39AADDD2.C01BC6FB@gmx.de>
Date: Mon, 28 Aug 2000 23:46:58 +0200
From: Siegbert Baude <siegbert.baude@gmx.de>
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-9mdkfb i686)
X-Accept-Language: de, en
MIME-Version: 1.0
To: Antoine Beaupre <beaupran@IRO.UMontreal.CA>,
	freebsd-questions@freebsd.org
Subject: Re: ed0 device timeout without conflict
References: <Pine.LNX.4.21.0008281536250.31920-100000@phobos.IRO.UMontreal.CA>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi Antoine,

> PS/2 support is not compiled in the kernel...
> =

> I don't even have a PS/2 port on my machine!

Nevertheless, if your motherboard=B4s chips are able to support PS/2
(which is true for a motherboard with Intel PIIX4, I suppose) this
interrupt conflict actually can be there. Look into your BIOS with
onboard components are activated and switch off everything you won=B4t
need.

Ciao
Siegbert


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message