daily build 12.04 lts - cant connect to any types of wifi - asus u56e- wimax 6150

[christoper lavante banks]

daily build 12.04 lts - cant connect to any types of wifi - asus u56e- wimax 6150
daily build download was today 4/18/2012

[christoper lavante banks (dark-deity1)]

source: https://bbs.archlinux.org/viewtopic.php?id=136749

Here's what I found. Apparently there is some inerference from an attribute within the driver having to do with Bluetooth. My card does not have Bluetooth. You can reload it with the Bluetooth attribute forced off and check to see if the card will now associate wth an access point. I did this.

# modprobe -r iwlwifi
# modprobe -v iwlwifi bt_coex_active=0
Try to connect. If it works, create this file (if it doesn't already exist) /etc/modprobe.d/modprobe.conf
add this line to the file,

options iwlwifi bt_coex_active=0

reboot and voila

this fix worked for me im connected and having no issues... sorry im too noob to create a patch from it... but im sure its like 5 mins work for someone more experianced... also i upgraded from 11.04 and it didnt have this issue... but yeah ty for your help and gj on ubu and gl guys.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/985321/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[penalvch (penalvch)]

christopher lavante banks, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder, but the one all the way at the bottom) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]