From owner-freebsd-questions Mon Aug 28 17:43:45 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 E8A8137B423 for ; Mon, 28 Aug 2000 17:43:42 -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 CAA13089; Tue, 29 Aug 2000 02:43:40 +0200 (MEST) Message-ID: <39AB073F.C20C127C@gmx.de> Date: Tue, 29 Aug 2000 02:43:43 +0200 From: Siegbert Baude 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 , freebsd-questions@freebsd.org Subject: Re: ed0 device timeout without conflict References: 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 Antoine Beaupre wrote: > = > Then I would have a problem in windows as well... Or at least, windows > should give me warning about the conflict, shouldn't it? :) > = The problem is NOT compiling in appropriate kernel options. If the modules for PS/2 and USB are present, the kernel will use the information, which it gathers on bootup about the IRQs, to solve the PnP problems. Not having those modules forces the kernel to blindly ignore the otherwise used IRQs, so there can occur IRQ conflicts. Windows always has all modules so this problem won=B4t happen. Another point to your NIC. Is it a combo version with 10base-2 and 10base-T ? Then mabe it=B4s adjusted to listen to the 10base-2 port or th= e autosensing doesn=B4t work properly. Get vendor=B4s DOS-tool to check thi= s out. Ciao Siegbert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message