Date: Sat, 22 Nov 2008 08:09:31 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: hamtilla <tangel@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Integrated RTL8168/8111 NIC not assigned interface Message-ID: <20081121210931.GY51761@server.vk2pj.dyndns.org> In-Reply-To: <20616760.post@talk.nabble.com> References: <20616760.post@talk.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--PZYVFYZbFYjzBslI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Nov-21 00:07:26 -0800, hamtilla <tangel@gmail.com> wrote: >I'm running 7.0-RELEASE-i386 on Jetway's NC92-N230 mainboard. The board has >one integrated RTL8168/8111 gigabit NIC as well as an expansion board with >three RTL8168/8111 NICs. Why would the three NICs work while the onboard N= IC >does not?=20 > >none2@pci0:1:0:0: class=3D0x020000 card=3D0x816810ec chip=3D0x816810= ec >rev=3D0x02 hdr=3D0x00 > vendor =3D 'Realtek Semiconductor' > device =3D 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class =3D network > subclass =3D ethernet >re0@pci0:2:4:0: class=3D0x020000 card=3D0x10ec16f3 chip=3D0x816710ec rev= =3D0x10 >hdr=3D0x00 > vendor =3D 'Realtek Semiconductor' > device =3D 'RTL8169/8110 Family Gigabit Ethernet NIC' > class =3D network > subclass =3D ethernet =2E.. The on-board NIC is a different type to your expansion cards (note the different 'chip=3D' values. Looking at the code, it appears that only some variants of the RTL8168 are supported in 7.x. Unfortunately, pciconf doesn't report the actual hardware revision, so you can't tell from the pciconf output whether it's supported or not. Can you report the output of 'pciconf -r pci0:1:0:0 0x40' (which should report the hw revision) and 'pciconf -r pci0:2:4:0 0x40' (which gives me a double-check). You could try booting -current and see if the on-board NIC works there - the range of supported NICs has changed. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --PZYVFYZbFYjzBslI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkknI4sACgkQ/opHv/APuIcFwQCgm+za+8ePHH4wrk1IcpFbtqw8 s/sAoLafpFaKXwRU4X4/dJ1vc5kIs/fJ =A0ap -----END PGP SIGNATURE----- --PZYVFYZbFYjzBslI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081121210931.GY51761>