I confirm this is the same version I get 14e4:4312 I worked with ndiswrapper in feisty but it won't work on fwcutter or ndiswrapper in gutsy.
On 26/10/2007, Miłosz Kosobucki <[EMAIL PROTECTED]> wrote: > > I have the same problem. I tried both amd64 and i386 versions of gutsy > and used bcm43xx-fwcutter (through restricted-manager) to get the > firmware. My computer is HP notebook (dv6510ew). In fwcutter I used the > firmware from internet link that was provided. I also tried several > other firmwares (like this: > http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o from > http://linuxwireless.org/en/users/Drivers/b43 and > bcm43xx_compwiz18.1-all.deb firmware (got it somewhere on forum)) with > the same result. I also tried extracting firmware from windows vista > driver (bcmwl6.sys) but fwcutter told me that this file doesn't contain > any firmware. > > I don't know what the problem may be, because the card is listed as > compatibile with the bcm43xx driver. So maybe firmware is incorrect, if > so restricted-manager should check it and point proper firmware to me. > > With these errors card is listed in iwconfig but can't find any network > (and network is present because on windows it gets detected with about > 80% strenght). > > This is lspci outpu about my card: > > 03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11a/b/g > [14e4:4312] (rev 02) > Subsystem: Hewlett-Packard Company Unknown device [103c:1371] > Flags: bus master, fast devsel, latency 0, IRQ 16 > Memory at b0200000 (64-bit, non-prefetchable) [size=16K] > Capabilities: <access denied> > > Dmesg output about wifi card is exactly the same as in reporter's > attachment. > > ** Attachment added: "lspci-v-nn" > http://launchpadlibrarian.net/10176806/lspci-v-nn > > -- > bcm43xx cannot suspend mac > https://bugs.launchpad.net/bugs/153358 > You received this bug notification because you are a direct subscriber > of the bug. > -- bcm43xx cannot suspend mac https://bugs.launchpad.net/bugs/153358 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
