From owner-freebsd-current Tue Jan 12 07:37:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03224 for freebsd-current-outgoing; Tue, 12 Jan 1999 07:37:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03217 for ; Tue, 12 Jan 1999 07:37:49 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id JAA74835; Tue, 12 Jan 1999 09:36:19 -0600 (CST) Date: Tue, 12 Jan 1999 09:36:19 -0600 From: Dan Nelson To: Andrzej Bialecki Cc: freebsd-current@FreeBSD.ORG Subject: Re: fxp0: can't map memory Message-ID: <19990112093619.A74560@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from "Andrzej Bialecki" on Tue Jan 12 10:27:34 GMT 1999 X-OS: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 12), Andrzej Bialecki said: > Using recent boot.flp (19990105-SNAP), on Intel Dakota MB, I get this > message from probing the on-board ethernet card. The card is then > unusable. Previous SNAP-s and -current (as of ca. Oct-Nov) had no > problems. I got this message after switching to a new motherboard (Micronics of some sort). After some investigating, it looked like the BIOS option "shadow system ROMs" was stomping on the EE/Pro's memory. I disabled all the shadowing and caching options and it worked. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message