From owner-freebsd-questions Thu May 25 20:23:41 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mostgraveconcern.com (mostgraveconcern.com [216.82.145.240]) by hub.freebsd.org (Postfix) with ESMTP id BD91937B81C for ; Thu, 25 May 2000 20:23:36 -0700 (PDT) (envelope-from dan@mostgraveconcern.com) Received: from danco (danco.mostgraveconcern.com [10.0.0.2]) by mostgraveconcern.com (8.9.3/8.9.3) with SMTP id UAA82178 for ; Thu, 25 May 2000 20:23:32 -0700 (PDT) (envelope-from dan@mostgraveconcern.com) Message-ID: <05eb01bfc6c1$c4cfbe40$0200000a@danco> Reply-To: "Dan O'Connor" From: "Dan O'Connor" To: "freebsd-questions" Subject: Re: couldn't map ports/memory Date: Thu, 25 May 2000 20:23:29 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have a Linksys LNE100TX version 2.0 in a HP Brio Celeron 433. >I just installed 4.0 on it. > >At boot time, I get the messages: >dc0: at device 13.0 on pci1 >dc0: couldn't map ports/memory I had a similar problem with a Kinston KNE110TX (device 'dc0') card. Turns out my Promise Ultra33 IDE card was getting probed first and hogged the port address that the NIC card wanted. Swapping the two cards in their PCI slots cleared this up, the NIC was probed first, and assigned it's port address, and the Ultra33 card happily used an alternate port address. Try booting with the -v flag and closely looking for what device is conflicting with your NIC. --Dan -- Dan O'Connor On Matters of Most Grave Concern http://www.mostgraveconcern.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message