From owner-freebsd-current@FreeBSD.ORG Fri Aug 1 13:18:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 95A2C37B401; Fri, 1 Aug 2003 13:18:32 -0700 (PDT) In-Reply-To: <16169.55469.791014.669250@canoe.velocet.net> from David Gilbert at "Jul 31, 2003 11:04:13 pm" To: dgilbert@dclg.ca (David Gilbert) Date: Fri, 1 Aug 2003 13:18:32 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20030801201832.95A2C37B401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) cc: freebsd-current@freebsd.org Subject: Re: bge driver not recognising BCM 5705M X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 20:18:32 -0000 > I'm somewhat confused. So am I: where were you when I asked sent e-mail to this list asking for people to test the 5705 changes before I committed them? > On a recent 5.1-CURRENT, boot -v gives me: Actually, boot -v gives you much more, like the date when the kernel image was compiled. Too bad you decided not to show everything to us. > found-> vendor=0x14e4, dev=0x165d, revid=0x01 > bus=2, slot=0, func=0 > class=02-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0116, statreg=0x02b0, cachelnsz=8 (dwords) > lattimer=0x20 (960 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) > intpin=a, irq=11 > powerspec 2 supports D0 D3 current D0 > > followed by: > > pci2: at device 0.0 (no driver attached) > > This is the internal Gigabit ethernet on my Dell D800 laptop... but > it's not recognised, even though... > > static struct bge_type bge_devs[] = { > > ... > > { BCOM_VENDORID, BCOM_DEVICEID_BCM5705, > "Broadcom BCM5705 Gigabit Ethernet" }, > > ... > > }; > > and ... > > #define BCOM_VENDORID 0x14E4 > #define BCOM_DEVICEID_BCM5705M 0x165D > > ... so why doesn't the bge driver kick in? You'll need to investigate this one for yourself. Make *SURE* you booted from the right kernel image (strings -a /boot/kernel/kernel | grep 5705). A good way to experiment is compile your kernel _WITHOUT_ bge support, and then build if_bge.ko as a module: # cd /sys/modules/bge # make; make load -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= "If stupidity were a handicap, you'd have the best parking spot." =============================================================================