From owner-freebsd-questions@FreeBSD.ORG Tue Nov 16 04:58:46 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 206D4106564A for ; Tue, 16 Nov 2010 04:58:46 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id CE5258FC13 for ; Tue, 16 Nov 2010 04:58:45 +0000 (UTC) Received: by gwj20 with SMTP id 20so118739gwj.13 for ; Mon, 15 Nov 2010 20:58:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=XjaifTVWkrgvNOgc1dJvc4KLybhEygsJ0vX6JnAXBUM=; b=rQ5lRs2lmUUQCjM2Gnr1l5ZF0tptzjosvHgkGj2Jd1XOnsQubiOKcX0NDBIKpWKl8v aHClkwV6TST9dcFd+jbssHNnl6Vm8b5noxumNz2w45QofTmKbFgZOk9yrW0zjRXSd0kM D0HW8YAfJYPa2qkEgGP4qCu14ba9swPk2nkT0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=wGbyQHJgZlfTROePqnOio80lLWQYotN0q3Jw7bAFzkznCf2Fdcovs2cvRT5IJI1e49 U9NoCxGwNu2u0mPbsSldGdf6XR7iC79HARrBQntbLBa1CARxnd2d6uh7lXs+Qy9TxY3V UtxK6by2afJHPqf9MjLD0Dn8DbnxJiZPj3zQg= MIME-Version: 1.0 Received: by 10.91.17.5 with SMTP id u5mr8929494agi.165.1289883524995; Mon, 15 Nov 2010 20:58:44 -0800 (PST) Received: by 10.236.41.170 with HTTP; Mon, 15 Nov 2010 20:58:44 -0800 (PST) In-Reply-To: References: Date: Tue, 16 Nov 2010 04:58:44 +0000 Message-ID: From: "b. f." To: Chris Brennan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-questions@freebsd.org Subject: Re: 'Broadcom Wireless b/g (BCM4315/BCM22062000)' X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2010 04:58:46 -0000 On 11/16/10, Chris Brennan wrote: > On Mon, Nov 15, 2010 at 11:17 PM, b. f. wrote: > >> Chris Brennan wrote: >> ... >> >My Hiccup as the subject suggests is about my Wireless Card. >> >I have been following the handbook ( >> >http://www.freebsd.org/doc/handbook/config-network-setup.html) on how to >> use >> >64-bit Windows drivers coupled w/ ndisgen to get my wireless card >> > working. >> I >> >got ndisgen to generate a kernel module but it immediately caused my >> laptop >> >to reboot when the kernel was loaded. This left me scratching my head. I >> >think I might need firmware (I remember having to extract firmware from >> the >> >driver for linux). >> > >> >pciconf shows the following: >> > >> >[root at BlackDragon [~]# pciconf -lv | grep -A3 0x4315 >> >none8 at pci0:8:0:0: class=0x028000 card=0x137c103c chip=0x431514e4 >> >rev=0x01 hdr=0x00 >> > vendor = 'Broadcom Corporation' >> > device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' >> > class = network >> >[root at BlackDragon [~]# >> > >> >The laptop is an HP dv2845SE and it's running FreebSD64-8.1. Let me know >> if >> >I missed anything. >> >> I'm assuming that by "FreebSD64", you mean the amd64 version of >> FreeBSD. Have you tried using a recent version of the native bwn(4) >> driver, together with the net/bwn-firmware-kmod port, rather than >> ndis(4)? >> >> >> b. >> > > Yes, by FreeBSD64 I am implying amd64, an oversight on my part. I was told > the native bwn/bwn-firmware-kmod non-functional currently. Was I misinformed > about this? > I don't use it myself, but I have seen exchanges on the mailing lists from time to time that would suggest that it is working, at least for some hardware. The only PR that I can see in the database from someone using a card similar to yours was a report of a problem that only arose in a specific configuration, and that problem seems to have been solved: ttp://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/144724 However, you could ask weongyo@ (the developer who has done most of the work on it) directly. If you are feeling bold, you could try 9-CURRENT, where you will be able to use the latest versions of the driver and associated wireless infrastructure. b.