From owner-freebsd-questions Mon Aug 28 15:14:33 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mercure.IRO.UMontreal.CA (mercure.IRO.UMontreal.CA [132.204.24.67]) by hub.freebsd.org (Postfix) with ESMTP id 0F04D37B424 for ; Mon, 28 Aug 2000 15:14:31 -0700 (PDT) Received: from phobos.IRO.UMontreal.CA (IDENT:root@phobos.IRO.UMontreal.CA [132.204.20.20]) by mercure.IRO.UMontreal.CA (8.9.3/8.9.3) with ESMTP id SAA11481; Mon, 28 Aug 2000 18:14:20 -0400 Received: from localhost (beaupran@localhost) by phobos.IRO.UMontreal.CA (8.9.3/8.9.3) with ESMTP id SAA06782; Mon, 28 Aug 2000 18:14:19 -0400 Full-Name: Antoine Beaupre Date: Mon, 28 Aug 2000 18:14:19 -0400 (EDT) From: Antoine Beaupre To: Siegbert Baude Cc: freebsd-questions@freebsd.org Subject: Re: ed0 device timeout without conflict In-Reply-To: <39AADDD2.C01BC6FB@gmx.de> Message-ID: MIME-Version: 1.0 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 Then I would have a problem in windows as well... Or at least, windows should give me warning about the conflict, shouldn't it? :) But thining of it , this might just be it since I had a battery (CMOS) failure recently and lost all my BIOS settings...=20 A. On Mon, 28 Aug 2000, Siegbert Baude wrote: > Hi Antoine, >=20 > > PS/2 support is not compiled in the kernel... > >=20 > > I don't even have a PS/2 port on my machine! >=20 > 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. >=20 > Ciao > Siegbert >=20 Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message