From owner-freebsd-questions Sun Nov 4 2:44:14 2001 Delivered-To: freebsd-questions@freebsd.org Received: from packet.mtc.dhs.org (das-01-169-237-54-119.das.ucdavis.edu [169.237.54.119]) by hub.freebsd.org (Postfix) with ESMTP id 7880D37B409 for ; Sun, 4 Nov 2001 02:44:11 -0800 (PST) Received: (from jimmy@localhost) by packet.mtc.dhs.org (8.11.6/8.11.6) id fA4Ainu86284; Sun, 4 Nov 2001 02:44:49 -0800 (PST) Date: Sun, 4 Nov 2001 02:44:45 -0800 (PST) From: Terminator To: Ted Mittelstaedt Cc: Subject: RE: NIC memory corrupt In-Reply-To: <002e01c1650f$2ab36800$1401a8c0@tedm.placo.com> Message-ID: <20011104024117.R86272-100000@packet.mtc.dhs.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm not sure about the network adapter. dmesg gives me such information: ed0: port 0xee80-0xee9f irq 11 at device 5. 0 on pci0 ed0: address 00:80:c6:f4:55:f0, type NE2000 (16 bit) BTW, I recompiled the kernel and enabled PNP BIOS option, then I got something like the following in booting: unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources Perhaps this is the reason and I shall turn this option off in kernel? How to do it? Is there anyway to do it without recompile kernel again? Thanks a lot! Jimmy On Sun, 4 Nov 2001, Ted Mittelstaedt wrote: > this is often due to some other adapter card in the system that has > option rom or ram that's stomping on the shared memory allocated by > your adapter card. > > For example you might have a SCSI card that has bios at c800 and your > system boots off this, but once the system is up this BIOS is unused. > Later on when the kernel is loading your card on ed allocated c800 > for it's shared ram and now you got 2 devices fighting over the same > memory location. > > I've also seen this happen with bad cabling too. > > Either way this is a problem that you need to look at. what ethernet card > are you using? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjvlHCAACgkQVieKrU8Jxnm5CwCcC4H/4UBWoZzyoEmEu9udf2Hd X6UAn1ahjsYmdQxhU0zrN8YtadjR2EXH =LLMS -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message