Date: Thu, 24 Mar 2005 07:26:11 -0800 From: Andrew Robinson <andrewr@uidaho.edu> To: des@des.no (=?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?=) Cc: jason henson <jason@ec.rr.com> Subject: Re: NIC detected, but won't DHCP or configure Message-ID: <ea9155ea8d2e.ea8d2eea9155@uidaho.edu>
index | next in thread | raw e-mail
Excellent! The interface is now up:
bash-2.05b$ ifconfig
fwe0: flags=108802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
options=8<VLAN_MTU>
ether 02:90:f5:40:24:d8
ch 1 dma -1
re0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
ether 00:90:f5:3f:08:d8
media: Ethernet autoselect (100baseTX)
status: no carrier
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
And:
bash-2.05b$ pciconf -lv
re0@pci10:3:0: class=0x020000 card=0x09001558 chip=0x816910ec rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8169 Gigabit Ethernet Adapter'
class = network
subclass = ethernet
I am not able to check the viability of the network connection until tomorrow. I will report back.
Again, thanks.
Andrew
----- Original Message -----
From: des@des.no (Dag-Erling Smørgrav)
Date: Wednesday, March 23, 2005 9:42 am
Subject: Re: NIC detected, but won't DHCP or configure
> Andrew Robinson <andrewr@uidaho.edu> writes:
> > re_probe(): vid 10ec did 8169 hwrev 10000000
>
> That's an 8169SB, which is supported in -CURRENT. Try the attached
> patch. I'll try to get it merged before 5.4-RELEASE.
>
> DES
> --
> Dag-Erling Smørgrav - des@des.no
>
>
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ea9155ea8d2e.ea8d2eea9155>