From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 21:11:00 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 89FF116A402; Fri, 2 Mar 2007 21:11:00 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp2.utdallas.edu (smtp2.utdallas.edu [129.110.10.33]) by mx1.freebsd.org (Postfix) with ESMTP id 6CF5B13C461; Fri, 2 Mar 2007 21:11:00 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) by smtp2.utdallas.edu (Postfix) with ESMTP id 1D96A5C2EF; Fri, 2 Mar 2007 14:37:50 -0600 (CST) Date: Fri, 02 Mar 2007 14:37:50 -0600 From: Paul Schmehl To: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org Message-ID: <0596BF936C9E2F724954C223@utd59514.utdallas.edu> In-Reply-To: <20070302084747.GA80114@libero.sunshine.ale> References: <20070302084747.GA80114@libero.sunshine.ale> X-Mailer: Mulberry/4.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========9CE1C0190F08AECC356A==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: two problems with broadcom NICs X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2007 21:11:00 -0000 --==========9CE1C0190F08AECC356A========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Friday, March 02, 2007 09:47:47 +0100 Alessandro de Manzano=20 wrote: > Hello, > > I've got a bunch of new Dell PowerEdge SC440 machines, but I've some > problems running FreeBSD on them. > > OS: FreeBSD 6.2-RELEASE (but also -stable of yesterday), SMP (but tried > also GENERIC monoprocessor), both i386 and amd64, always same results. > > Situation: Two Broadcom NICs, one on the motherboard and one on > PCI-express bus, here is a snippet of pciconf -lv (as you can see I had > to add a 3COM PCI card in order to have connectivity) > > > bge0@pci3:0:0: class=3D0x020000 card=3D0x165914e4 chip=3D0x165914e4 = rev=3D0x21 > hdr=3D0x00 vendor =3D 'Broadcom Corporation' > device =3D 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' > class =3D network > subclass =3D ethernet > none1@pci4:0:0: class=3D0x020000 card=3D0x01df1028 chip=3D0x167a14e4 = rev=3D0x02 > hdr=3D0x00 vendor =3D 'Broadcom Corporation' > class =3D network > subclass =3D ethernet > xl0@pci5:2:0: class=3D0x020000 card=3D0x100010b7 chip=3D0x920010b7 = rev=3D0x74 > hdr=3D0x00 vendor =3D '3COM Corp, Networking Division' > device =3D '3C905C-TX Fast EtherLink for PC Management NIC' > class =3D network > subclass =3D ethernet > Shouldn't you be using the bce driver? This is an i386 machine, but amd64=20 should work the same (you're using the same chipset): bce0@pci9:0:0: class=3D0x020000 card=3D0x01b31028 chip=3D0x164c14e4 = rev=3D0x11=20 hdr=3D0x00 vendor =3D 'Broadcom Corporation' class =3D network subclass =3D ethernet bce1@pci5:0:0: class=3D0x020000 card=3D0x01b31028 chip=3D0x164c14e4 = rev=3D0x11=20 hdr=3D0x00 vendor =3D 'Broadcom Corporation' class =3D network subclass =3D ethernet This is a Dell 1950, from dmesg.boot: bce0: mem=20 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci9 bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz bce1: mem=20 0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci5 bce1: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========9CE1C0190F08AECC356A==========--