1 |
On Saturday 14 August 2010 11:18:17 you wrote: |
2 |
> On Friday 13 August 2010 19:24:08 Bill Longman wrote: |
3 |
> > On 08/13/2010 10:58 AM, BRM wrote: |
4 |
> > > ----- Original Message ---- |
5 |
> > > |
6 |
> > >> On 13 August 2010 09:08, Neil Bothwick <neil@××××××××××.uk> wrote: |
7 |
> > >>> On Thu, 12 Aug 2010 22:10:02 -0700 (PDT), BRM wrote: |
8 |
> > >>>> but even so - they are saying this has to be done on every reboot, |
9 |
> > >>>> and that's not much of a solution. |
10 |
> > >>> |
11 |
> > >>> Put the commands in /etc/conf.d/local.start, or the start section |
12 |
> > >>> of /etc/conf.d/local if using baselayout2. |
13 |
> > >> |
14 |
> > >> Have you been through the guidance in this page to find out which |
15 |
> > >> kernel driver you ought to use with your card? |
16 |
> > >> http://linuxwireless.org/en/users/Drivers/b43 |
17 |
> > > |
18 |
> > > Yes. Unfortunately it's a 14e4:4320/ with BCM4306/2 Chip set (4306 Rev |
19 |
> > > 2), so it requires the b43-legacy driver, and only firmware version |
20 |
> > > FW10 supports the hardware from what I can tell. |
21 |
> > > |
22 |
> > > It just seems to me that I went from a working wireless on 2.6.30 to a |
23 |
> > > non-working wireless on 2.6.34. I'd really like to get back to a |
24 |
> > > working wireless card, and be on the newer kernel. |
25 |
> > |
26 |
> > I feel your pain, Ben. I remember about three years ago having my laptop |
27 |
> > working great with all manner of 802.11 cards. I could do my work |
28 |
> > anywhere in the house. And then it all just kind of melted. A new kernel |
29 |
> > for one thing but somehow something else fell apart. I've pretty much |
30 |
> > written off any wireless on Linux now. My time is worth more than the |
31 |
> > hours of troubleshooting. Keep plugging, you just might get it. |
32 |
> |
33 |
> Well, there's always ndiswrapper and the MSWindows driver to consider, when |
34 |
> all Linux solutions fail or don't work that well. |
35 |
> |
36 |
> I see on kernel v2.6.34-gentoo-r1 that CONFIG_B43LEGACY will now use V3 |
37 |
> firmware, which must be installed separately using b43-fwcutter. |
38 |
> |
39 |
> Has the OP tried that? |
40 |
> |
41 |
> PS. The kernel help is also recommending that b43legacy is installed as a |
42 |
> module. |
43 |
|
44 |
I read again your original post. I think that you have been trying to use the |
45 |
wrong firmware. The link I suggested recommends that you use b43_fwcutter to |
46 |
install this firmware: |
47 |
|
48 |
http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o |
49 |
|
50 |
Alternatively, you may want to experiment with whatever is the latest firmware |
51 |
in Broadcom's website and see if any of those work. |
52 |
-- |
53 |
Regards, |
54 |
Mick |