Answer the question
In order to leave comments, you need to log in
Where do network devices disappear in standby mode and what happens with FN + F2 (wi-fi)?
Attempts were made on different kernels: 3.2-3.8rc4
We have Mint 13, aka Ubuntu 12.04 and a modern laptop with wi-fi on an atheros chip (02:00.0 Network controller: Atheros Communications Inc. Device 0037 (rev 01))
We click “go to standby”, we get a pop-up message “connection is broken, going offline”. The light on the panel goes out and the PC goes into hibernation. After waking up, the light does not light up and ifconfig does not show wlan1, but it is visible in ifconfig -a.
After pressing FN-F2 everything falls into place. When you connect an external USB adapter, absolutely the same thing happens.
Where might the problem lie? How can I add the FN+F2 key combination to some script for /etc/pm/sleep.d?
Replacing network-manager with wicd didn't change anything.
Answer the question
In order to leave comments, you need to log in
When hibernating, some kernel modules are unloaded, as they do not work correctly after waking up. In your case, these are wifi device modules. Re-enabling the adapter via FN forces the modules to be loaded. You need to deal with pm, add modprobe for wifi adapter modules to the script that is executed after waking up.
Can you help me figure it out further?
cat /etc/acpi/events/asus-wireless-on
event=hotkey (ATKD|HOTK) 0000005f
action=/etc/acpi/asus-wireless.sh on
#!/bin/sh
# Find and toggle wireless devices on Asus laptops
test -f /usr/share/acpi-support/state-funcs || exit 0
. /usr/share/acpi-support/state-funcs
toggleAllWirelessStates
Add asus-wireless.sh to the end
echo "used" >> /tmp/wifi.log
Somewhere, after all, there must be a file for switching to standby mode? Well, that is, the script for immersion in sleep. I would like to look at him, because he knows how to turn off the light bulb. It would be possible to simply remove the desired line.
Is it possible to execute scripts step by step? Although, most likely, it will be enough just to read it.
Maybe your WiFi card is killed via rfkill when it goes to sleep, and then it forgets to set the correct status to the corresponding variable in the /sys/class/rfkill/rfkill[x]/state branch? check the contents of this variable when Wi-Fi is on, and after it stops working.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question