From owner-freebsd-hardware Sat Sep 9 15:29:27 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id 5BA6337B42C for ; Sat, 9 Sep 2000 15:29:24 -0700 (PDT) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with esmtp (Exim 1.92 #8) for hardware@freebsd.org id 13Xt7j-0005e0-00; Sat, 9 Sep 2000 15:29:23 -0700 Received: from localhost (localhost [127.0.0.1]) by asimov.phoenix.volant.org (8.9.3+Sun/8.9.3) with SMTP id PAA17145 for ; Sat, 9 Sep 2000 15:29:22 -0700 (PDT) From: patl@Phoenix.Volant.ORG Date: Sat, 9 Sep 2000 15:29:22 -0700 (PDT) Reply-To: patl@Phoenix.Volant.ORG Subject: Resolved: Re: dc0: couldn't map ports/memory To: hardware@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Back in April I posted the following problem: On 28-Apr-00 at 00:12, patl@phoenix.volant.org (patl@phoenix.volant.org) wrote: > I've just installed FreeBSD 4.0R on an Hitachi VisionBook Pro 7590. > During the boot, when the probe checks the builtin NIC, it reports: > > dc0: irq 11 at device 11.0 on pci0 > dc0: couldn't map ports/memory > device_probe_and_attach: dc0 attach returned 6 > > Windows98 lists this device as: > > Class: Network adapters > Device: PCI Fast Ethernet DEC 21143 Based Adapter > Resources: > IRQ: 11 > I/O: 1080h-10FFh > MEM: 09043000h-090433FFh > > What do I need to do to get FreeBSD to correctly handle this device? I didn't recieve any replies; so I left it as a Windows-only machine. Now that I have 4.1R in hand, and a few spare cycles; I thought I'd give it another try in the hope that 4.1 would give me better results. It didn't. And it also reported a "could not map" problem for the UHCI controller. (4.0 may have also done that - I didn't really notice.) But this time I tried a few more things. It turns out that turning 'Plug and Play OS' OFF in the BIOS fixed both problems. The Hitachi is now happily CVSupping -stable via it's built-in Ethernet port. So I thought I'd follow up to my original question in case it is of help to anyone else. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message