Also, have you tried sudo modprobe bcm43xx? It could be of some help. If nothing helps, you could try searching launchpad if there is someone who has already reported a bug like this. Maybe they have also posted some workaround there. If it worked with earlier versions, it is most certainly a bug. Try searching there for broadcom, bcm, bcm43xx and so on. If you don't find any suitable bug, it'd be of help to the quality of Ubuntu if you reported this as a new bug. If you wish do so, the developers would be glad if you read through things like these first: <a href="https://wiki.ubuntu.com/DebuggingProcedures">https://wiki.ubuntu.com/DebuggingProcedures</a> <a href="https://wiki.ubuntu.com/KernelTeamBugPolicies">https://wiki.ubuntu.com/KernelTeamBugPolicies</a> <a href="https://wiki.ubuntu.com/Bugs/FindRightPackage"> https://wiki.ubuntu.com/Bugs/FindRightPackage</a> <a href="https://wiki.ubuntu.com/Bugs/">https://wiki.ubuntu.com/Bugs/</a> and links from those pages. Don't be surprised if it takes a long time before they answer, they are overwhelmed with bugreports, and has a lot of work to do. Hope it could be of some help. /pär <div>2008/1/2, Pär Lidén <<a href="mailto:par.liden@gmail.com">par.liden@gmail.com</a>>:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> grep -i does case independent search, might be useful for you when grepping for things. So grep -i broadcom would find all lines containg both Broadcom, broadCom, brOadcoM, and so on. So, you could also try lspci |grep -i bcm, might help. And, you don't need the " if it's just at single word, ie instead of grep "broadcom", grep broadcom can be used. Hope this is more help than it confuses you... ;-) /Pär </blockquote></div>