-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wireless network - Does not resume after suspend to SSD #2
Comments
|
Hibernate is not really a problem though IMHO because hibernation is bad for SSD's, or so they say. So it's better to disable it anyway. |
@Vistaus because the hardware buttons don't respond to ACPI, suspend to ram doesn't work at all. Are you planning to just reboot all the time? |
Same issue - WiFi doesn't work after hibernate, bluetooth not works too (bluetooth adapter is not visible at all after hibernate) |
Which is why I disabled hibernate. It's bad for SSD's anyway. |
I think it is ok for modern SSD drives... |
apparently this issue is pretty common to all wireles drivers. I haven't tested it but see https://wiki.archlinux.org/index.php/pm-utils#Standby.2Fsuspend_to_RAM to disable the driver if you use pm-utils |
Seems like this is due to Hyper-V: http://winsupersite.com/mobile-devices/surface-pro-3-tip-hyper-v-vs-connected-standby |
Seems like removing and probing back the module works : https://www.reddit.com/r/SurfaceLinux/comments/3nhjkn/hibernate_on_surface_pro_3/ |
not works for me, module not works after reboot |
@orion78fr 's method works for me. Just execute:
|
Wifi worked out of the box with the mwifiex driver. I had none of the flakiness issues experienced by the Ubuntu users. The firmware was updated via windows on 2014-08-07 and has not been updated since. The latest marvell firmware has been installed via https://github.com/nuclearsandwich/mwifiex-firmware-git
Regardless of whether netctl or Network Manager is used wifi fails to work after resuming from hibernate via systemd. I tried manually disabling wifi via
but it failed to come back up nonetheless after restart.
The text was updated successfully, but these errors were encountered: