Hi all,
I'm looking for help with some strange behavior that I have been
getting from my wireless adapter. This has been going on for quite
some time but only now am I able to see a pattern.
The behavior seems to be the following: Start up, connects to network
and work fine until I suspend my machine. On wake up, it works again
but after a seemingly random amount of time the connection is lost and
I can no longer find any networks.
Attached is dmesg output after startup and connecting to a wireless
network (dmesgAfterConecting.txt) and the same after the connection
has been lost (dmesgAfterConnectLost.txt). I get the "mac is in deep
sleep" error.
Normal iwconfig outup while connected:
jeremi@linux64:~$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11abgn ESSID:"NaosJena-SO53"
Mode:Managed Frequency:2.422 GHz Access Point: 02:16:01:58:DF:43
Bit Rate=54 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=60/70 Signal level=-50 dBm Noise level=-93 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
pan0 no wireless extensions.
and after it drops off:
jeremi@linux64:~$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11abgn ESSID:"NaosJena-SO53"
Mode:Managed Frequency:2.422 GHz Access Point: Not-Associated
Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
pan0 no wireless extensions.
I've tried the following:
1. disabling hardware scan by creating /etc/modprobe.d/local with the
following in it:
options iwlagn disable_hw_scan=1
2. running this:
sudo rmmod iwlagn && sudo modprobe iwlagn
after the connection drops. This usually results in the system no
longer recognizing that there is a wireless network adapter.
3. Toggling the wireless on/off switch.
None of these solutions have worked. Also of note is the random
behaviour of the wireless LED that is supposed to tell me if wireless
is on or not. After wake up it is on or off, in either state wireless
has been working or not.
I've also tried WICD 1.6.1 and Network Manager.
Environment:
I have an Asus F3Sv laptop with the following:
jeremi@linux64:~$ lspci | grep Network
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or
AGN [Kedron] Network Connection (rev 61)
and am running:
jeremi@linux64:~$ uname -a
Linux linux64 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC
2010 x86_64 GNU/Linux
with Ubuntu Karmic 64 bit.
As a temporary solution, does anyone know if it posible to "reboot"
just the wireless adapter. I though if this was possible it could be a
stopgap measure since it works well after a fresh start up.
Also if this is not the right place to post this, please let me know
and suggest where else to post it.
Thanks
Jeremi
Hi Jeremi,
On Tue, 2010-03-30 at 22:43 -0700, Jeremi Thebeau wrote:
> jeremi@linux64:~$ uname -a
> Linux linux64 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC
> 2010 x86_64 GNU/Linux
>
> with Ubuntu Karmic 64 bit.
Is it possible to give the latest driver code a try to ensure we are
dealing with the latest features? compat-wireless may be an easy way for
you to do this.
We have seen some devices that essentially get disconnected from the
platform, which seems to be happening here. We prepared a patch for this
a while ago, but nobody with this issue has yet been able to test it.
Perhaps you could? Please try
http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2037#c112 ...
hopefully it will still be straight forward to apply.
Reinette
Thanks Reinette,
I haven't played around much with ucode, linux modules, dirver and
applying patches. Do you have a suggestion for a good primer. I will
try to make sense of that ridiculously long bug when i get a chance.
Assuming I am able to install and patch, if the device drops off
again, are there any specific logs I should keep an eye on to help
test this patch?
Jeremi
On Wed, Mar 31, 2010 at 7:22 PM, reinette chatre
<[email protected]> wrote:
> Hi Jeremi,
>
> On Tue, 2010-03-30 at 22:43 -0700, Jeremi Thebeau wrote:
>
>> jeremi@linux64:~$ uname -a
>> Linux linux64 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC
>> 2010 x86_64 GNU/Linux
>>
>> with Ubuntu Karmic 64 bit.
>
> Is it possible to give the latest driver code a try to ensure we are
> dealing with the latest features? compat-wireless may be an easy way for
> you to do this.
>
> We have seen some devices that essentially get disconnected from the
> platform, which seems to be happening here. We prepared a patch for this
> a while ago, but nobody with this issue has yet been able to test it.
> Perhaps you could? Please try
> http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2037#c112 ...
> hopefully it will still be straight forward to apply.
>
> Reinette
>
>
>
On Thu, 2010-04-01 at 00:26 -0700, Jeremi Thebeau wrote:
> I haven't played around much with ucode, linux modules, dirver and
> applying patches. Do you have a suggestion for a good primer. I will
> try to make sense of that ridiculously long bug when i get a chance.
> Assuming I am able to install and patch, if the device drops off
> again, are there any specific logs I should keep an eye on to help
> test this patch?
There is no need to read the entire bug report. Only the comment linked
to at http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2037#c112
can be taken independently. You can read more about building and
patching the kernel in the README file that accompanies the kernel
source code. I believe http://www.kroah.com/lkn/ is also a good primer.
Hopefully that patch will return you a working system, if not then we
can look into which debugging to enable based on the symptoms you
experience at that time.
Reinette