Bug 48121 - iwlwifi can't connect to router after resuming from suspend.
Summary: iwlwifi can't connect to router after resuming from suspend.
Status: CLOSED OBSOLETE
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: networking_wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-01 15:08 UTC by Dan Carpenter
Modified: 2014-05-08 05:39 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.6-rc7
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Dan Carpenter 2012-10-01 15:08:18 UTC
Subject    : Re: iwlwifi can't connect to router after resuming from suspend.
Submitter  : Kevin Cruz <skate_ops@yahoo.com>
Date       : Mon, 1 Oct 2012 07:44:01 -0700 (PDT)
Message-ID : <1349102641.41622.YahooMailNeo@web164005.mail.gq1.yahoo.com>
References : https://lkml.org/lkml/2012/10/1/253

> You can compile it under ubuntu.<A0> I looked on google to find

> directions but everyone had bad advice.<A0> This might work:

> apt-get build-dep linux-image-$(uname -r)
> download and unpack the kernel from kernel.org
> make localmodconfig
> make
> make modules_install install
> reboot

> If it doesn't then having the dmesg from Sabayon live disk will have
> to be enough.<A0> We can open a bug for that on bugzilla and CC the
> wireless people.

I was able to build and install the kernel (3.6-rc7) successfully but I
still can't connect after suspend.<A0> I'm not sure it matters but for the
`make localmodconfig` I just answered each request with whichever was
capital, and for the multi options I just answered whichever had `>` which
was always 1.<A0> The letter that is capital (like `N/y` or `Y/n`) is the
recommended answer, correct?<A0> If needed I don't mind retrying to build it
with different configurations.

For right now, I'm gonna give some [boot options][1] I found a shot.

[the dmesg doesn't look good cut and pasted.  Follow the link to lkml.org]
Comment 1 Emmanuel Grumbach 2014-03-18 11:06:01 UTC
still an issue?

Note You need to log in before you can comment on or make changes to this bug.