Date: Mon, 21 Mar 2005 11:43:23 -0800 From: Andrew Robinson <andrewr@uidaho.edu> To: Charles Swiger <cswiger@mac.com> Cc: freebsd-questions@freebsd.org Subject: Re: NIC won't DHCP or configure Message-ID: <b940fbb920c1.b920c1b940fb@uidaho.edu>
next in thread | raw e-mail | index | archive | help
Hi Chuck,
Thanks for the suggestion - that's beyond my exerptise, but here is the (hopefully relevant) output of pciconf
###########################################
none4@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
none5@pci10:5:0: class=0x028000 card=0x68331462 chip=0x02011814 rev=0x01 hdr=0x00
vendor = 'Ralink Technology Corp'
class = network
###########################################
I would appreciate any further advice or assistance,
Andrew
----- Original Message -----
From: Charles Swiger <cswiger@mac.com>
Date: Monday, March 21, 2005 11:12 am
Subject: Re: NIC won't DHCP or configure
> Hi, Andrew--
>
> On Mar 21, 2005, at 1:54 PM, Andrew Robinson wrote:
> > It makes me wonder if FreeBSD is identifying the card as
> something
> > different than it is. Is that possible? What next steps might
> be
> > useful for me to take?
>
> Take a look at the output of "pciconf -v -l". The odds are that
> it
> lists a PCI ID for your NIC that the FreeBSD driver doesn't know
> about.
> Use that information to update /usr/src/sys/pci/if_rlreg.h and
> /usr/src/sys/dev/re/if_re.c, and see whether that gets you a
> working
> driver. If you're not sure how to do this, post the pciconf info
> for
> just your NIC so that others can try to update the code and get
> you a
> working driver...
>
> --
> -Chuck
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b940fbb920c1.b920c1b940fb>