supporting broadcom gig BCM5751

[John Kennedy]

On Fri, Sep 17, 2004 at 05:23:32PM -0400, Peter Radcliffe wrote:
> John Kennedy <jk at jk.homeunix.net> probably said:
> >   I have a few Dell 2650s at work and I had to load FreeBSD 5.2.1 (vs.
> > 4.x-STABLE, which at the time was 4.9).  They've all been up to long so I
> > don't have any handy dmesg output to compare to yours.
> > 
> >   pciconf gives me this, which may be of some help:
> > 
> > 	bge0 at pci3:6:0:  class=0x020000 card=0x01211028 chip=0x16a714e4 rev=0x02 hdr=0x00
> > 	    vendor   = 'Broadcom Corporation'
> > 	    device   = 'BCM5703X NetXtreme Gigabit Ethernet'
> > 	    class    = network
> > 	    subclass = ethernet
> > 
> >   The "chip" field is close to yours, but not an exact match.
> 
> I have other machines with Broadcom gig ether cards, including another
> Dell, but it's this exact chipset I'm having trouble with not anything
> that is close.

  Daniel O'Connor suggested I look in /var/run/dmesg.boot (I was looking in
/var/log/dmesg.*).  I looked on my 2nd 2650 box which apparently has a
slightly different chipset in it, and it should be older than the 1st.  The
device as identified there is a bit different:

	bge0: <Broadcom BCM5701 Gigabit Ethernet, ASIC rev. 0x105> mem 0xfcf10000-0xfcf1ffff irq 28 at device 6.0 on pci3
	bge0: Ethernet address: 00:06:5b:f0:7d:c3
	miibus0: <MII bus> on bge0

	bge0 at pci3:6:0:  class=0x020000 card=0x01211028 chip=0x164514e4 rev=0x15 hdr=0x00
	    vendor   = 'Broadcom Corporation'
	    device   = 'BCM5701 NetXtreme Gigabit Ethernet'
	    class    = network
	    subclass = ethernet

  Still, not your exact chipset (presumably 0x14e4 is vendor and 0x1677 is
version, the chip= field has them swapped, and my two machines straddle
your chip.

  I have another 5.3-BETA4 box with a BCM5788 (chip=0x169c14e4) but that
isn't the right chip either, and it isn't a Dell.

  Doesn't really help you, but if I were you I would try booting up under
5.2.1 (if only via CD-ROM), seeing what it reports about the chipset and if
it seems to be supported, and then chasing driver-code differences.