[Bug 1034002]

2013-05-08 Thread Dennis New
I had a similar problem with my x700 (rv410) radeon, and fixed it with: radeontool light off   radeonreg regset 0x0284 0x1bd34208   radeonreg regset 0x02d0 0x003c00a1   radeonreg regset CL:03 0x001c0007   radeonreg regset CL:04 0x0002004a   radeonreg regset CL:05 0x0002004a  

[Bug 1097519] Re: Wrong driver used for older Broadcom chipsets

2013-07-31 Thread Dennis New
Sam Coffland's proposal from comment #29 seems to be the most sensible IMHO. I also have a BCM4313 on my Acer Aspire One, which has been broken with this upgraded wl.ko driver. brcmsmac is not an option for me since it doesn't support ad-hoc mode, which I require. -- You received this bug

[Bug 1097519] Re: Wrong driver used for older Broadcom chipsets

2013-07-31 Thread Dennis New
So, after a bit of hacking around, I was able to get my BCM4313 working with the latest bcmwl-6.30.223.30 and the latest kernel 3.10.0. I think the main problem that I originally had, and that others ( https://mail.gnome.org/archives/networkmanager-list/2013-February/msg00125.html ) started