Re: RTL8168/8111 Not Being Assigned to Interface
I upgraded to 7.1-PRERELEASE and now it works. Thank you! Pieter de Goeje wrote: On Friday 21 November 2008, hamtilla 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. [EMAIL PROTECTED]:1:0:0: class=0x02 card=0x816810ec chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet This NIC requires FreeBSD 7-STABLE or -CURRENT. You can probably copy the if_re driver from -STABLE to your source tree and recompile the kernel, or simply update to 7-STABLE. Hope this helps, Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/RTL8168-8111-Not-Being-Assigned-to-Interface-tp20621867p20662169.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RTL8168/8111 Not Being Assigned to Interface
On Friday 21 November 2008, hamtilla 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. [EMAIL PROTECTED]:1:0:0: class=0x02 card=0x816810ec chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet This NIC requires FreeBSD 7-STABLE or -CURRENT. You can probably copy the if_re driver from -STABLE to your source tree and recompile the kernel, or simply update to 7-STABLE. Hope this helps, Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RTL8168/8111 Not Being Assigned to Interface
hamtilla 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. [EMAIL PROTECTED]:1:0:0: class=0x02 card=0x816810ec chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet [EMAIL PROTECTED]:2:4:0: class=0x02 card=0x10ec16f3 chip=0x816710ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169/8110 Family Gigabit Ethernet NIC' class = network subclass = ethernet [EMAIL PROTECTED]:2:6:0: class=0x02 card=0x10ec16f3 chip=0x816710ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169/8110 Family Gigabit Ethernet NIC' class = network subclass = ethernet [EMAIL PROTECTED]:2:7:0: class=0x02 card=0x10ec16f3 chip=0x816710ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169/8110 Family Gigabit Ethernet NIC' class = network subclass = ethernet Why would the three NICs work while the onboard NIC does not? I would imagine the same driver services both controllers. Do I need to assign an interface to the device somehow? Thank you! Aloha, I use the same PCI cards in a number of servers. All work fine. But on board ones are only 100 so I dont use them. However I notice that the on board nic in your case uses a different chipset: chip=0x816810ec is onboard. chip=0x816710ec is slot pci's. I dont know what this means in respect to operation problems though. -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
