From owner-freebsd-questions@FreeBSD.ORG Tue Jun 1 08:52:11 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D2F816A4CE for ; Tue, 1 Jun 2004 08:52:11 -0700 (PDT) Received: from mailout1.informatik.tu-muenchen.de (mailout1.informatik.tu-muenchen.de [131.159.0.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id C05D043D49 for ; Tue, 1 Jun 2004 08:52:10 -0700 (PDT) (envelope-from barner@in.tum.de) Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000) id 9277D3F41; Tue, 1 Jun 2004 17:27:35 +0200 (CEST) Date: Tue, 1 Jun 2004 17:27:35 +0200 From: Simon Barner To: Wayne Pascoe Message-ID: <20040601152735.GD35382@zi025.glhnet.mhn.de> References: <20040601110940.GA65805@marvin.penguinpowered.org> <20040601134914.Q53545@gaff.hhhr.ision.net> <20040601143344.GB67057@marvin.penguinpowered.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zS7rBR6csb6tI2e1" Content-Disposition: inline In-Reply-To: <20040601143344.GB67057@marvin.penguinpowered.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: freebsd-questions@freebsd.org Subject: Re: Intel Ethernet card not being detected X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 15:52:11 -0000 --zS7rBR6csb6tI2e1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > I've tried installing 5.2.1 on the machine and it still doesn't work. > Now though, it's even worse, as the em0 device doesn't work either.=20 >=20 > I get something along these lines: > em0: Link is up 10Mbps Half Duplex > em0: watchdog timeout -- resetting=20 > em0: Link is up 10Mbps Half Duplex > em0: watchdog timeout -- resetting=20 I can recall from some older postings (and the archives. Hint, hint ;-) that this can be worked around by disabling ACPI. [...] > none3@pci3:8:0: class=3D0x020000 card=3D0x30108086 chip=3D0x10518086 rev= =3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82801EB/ER (ICH5/ICH5R) PRO/100 VE Network Connection' > class =3D network > subclass =3D ethernet Okay, that's your Intel NIC that is not detected (yet ;-> Add the following line to struct fxp_ident fxp_ident_table[] (in /usr/src/sys/dev/fxp/if_fxp.c) { 0x1051, -1, "Intel 82562ET (ICH5/ICH5R) Pro/100 VE Ethernet" }, and rebuild your kernel. This has already been added to -CURRENT, so you don't have to file a problem report. Simon P.S: 0x1051 are the first four letters of the chip id in the pciconfig output. -1 matches all chip revisions, i.e. if special hacks for a specific revision (0x02 in your case) were necessary, the would be an extra line for that particular chip. --zS7rBR6csb6tI2e1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAvKBnCkn+/eutqCoRAqw0AKCBJKXfcuDfNPnCOYt+PaK8+EtCnQCeKWVf fAdas27ng0MkrPEZlus3pss= =oBPH -----END PGP SIGNATURE----- --zS7rBR6csb6tI2e1--