On 09/13/2016 04:23 AM, Bertram Scharpf wrote:
> Hi,
>
> after suspend, my wlan is dead and it cannot be restarted....
>
> What do I have to try?
I had this same problem with the ath5k driver (still do, I bet)
on my Thinkpad x61s. What happens if you run "sudo rfkill list"
after you resume from suspend? Does it show that the wireless is
"hard blocked"?
In my case, it was, so I tried something stupid. I patched my kernel
to answer "no" to the question "is rfkill enabled?"... and it worked!
--- a/drivers/net/wireless/ath/ath5k/rfkill.c 2012-05-28 21:16:04.000000000
-0400
+++ b/drivers/net/wireless/ath/ath5k/rfkill.c 2012-05-28 21:17:17.000000000
-0400
@@ -66,10 +66,8 @@
static bool
ath5k_is_rfkill_set(struct ath5k_hw *ah)
{
- /* configuring GPIO for input for some reason disables rfkill */
- /*ath5k_hw_set_gpio_input(ah, ah->rf_kill.gpio);*/
- return ath5k_hw_get_gpio(ah, ah->rf_kill.gpio) ==
- ah->rf_kill.polarity;
+ /* Hard code this to work around a stupid bug. */
+ return 0;
}
static void
Maybe you can do the same thing for your driver, if rfkill is actually the
issue.
I have a possibly outdated writeup of the issue here:
http://michael.orlitzky.com/articles/thinkpad_x61s_ath5k_rfkill_issues.php
