really disable power save in linux wifi
up vote
2
down vote
favorite
I've got a laptop with an Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
(using iwlwifi
kernel module). Although power_save
(a module parameter) is disabled, I can see 802.11 control frames containing power management packets notifying the access point that it is going to sleep. The access point stops sending packets to the laptop until it sees another packet from the laptop.
How do I really stop the laptop from sending power save packets to the access point? (Or alternatively, how do I stop the access point from honouring them?)
I'm sure power_save
is disabled, as when I enabled it, power save packets are sent far more frequently (almost every second).
The access point is running hostapd
with an ath9k
driver. Both the access point and laptop are running debian wheezy with the 686-pae 3.2 kernel. I've tried putting the 3.10 iwlwifi driver on the laptop, but there is no change.
EDIT: I tried on another laptop with another iwlwifi
chipset Intel Corporation Centrino Ultimate-N 6300 (rev 35)
and it doesn't exactly have this problem. Every power save packet is followed by a non-power-save QoS null packet, so the access point presumably stops sending packets for a fraction of a second.
EDIT: I tried another mini PCIe wifi card in the first laptop, but it appears to be locked down so another mini PCIe card cannot be detected by the OS.
linux wireless-networking debian power-management hostapd
add a comment |
up vote
2
down vote
favorite
I've got a laptop with an Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
(using iwlwifi
kernel module). Although power_save
(a module parameter) is disabled, I can see 802.11 control frames containing power management packets notifying the access point that it is going to sleep. The access point stops sending packets to the laptop until it sees another packet from the laptop.
How do I really stop the laptop from sending power save packets to the access point? (Or alternatively, how do I stop the access point from honouring them?)
I'm sure power_save
is disabled, as when I enabled it, power save packets are sent far more frequently (almost every second).
The access point is running hostapd
with an ath9k
driver. Both the access point and laptop are running debian wheezy with the 686-pae 3.2 kernel. I've tried putting the 3.10 iwlwifi driver on the laptop, but there is no change.
EDIT: I tried on another laptop with another iwlwifi
chipset Intel Corporation Centrino Ultimate-N 6300 (rev 35)
and it doesn't exactly have this problem. Every power save packet is followed by a non-power-save QoS null packet, so the access point presumably stops sending packets for a fraction of a second.
EDIT: I tried another mini PCIe wifi card in the first laptop, but it appears to be locked down so another mini PCIe card cannot be detected by the OS.
linux wireless-networking debian power-management hostapd
Did you set power_level as well? By default, iwlwifi has power management disabled
– MariusMatutiae
Oct 21 '13 at 21:06
it's 0 while power save is N. I tried making it 5.
– Jayen
Oct 22 '13 at 0:40
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I've got a laptop with an Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
(using iwlwifi
kernel module). Although power_save
(a module parameter) is disabled, I can see 802.11 control frames containing power management packets notifying the access point that it is going to sleep. The access point stops sending packets to the laptop until it sees another packet from the laptop.
How do I really stop the laptop from sending power save packets to the access point? (Or alternatively, how do I stop the access point from honouring them?)
I'm sure power_save
is disabled, as when I enabled it, power save packets are sent far more frequently (almost every second).
The access point is running hostapd
with an ath9k
driver. Both the access point and laptop are running debian wheezy with the 686-pae 3.2 kernel. I've tried putting the 3.10 iwlwifi driver on the laptop, but there is no change.
EDIT: I tried on another laptop with another iwlwifi
chipset Intel Corporation Centrino Ultimate-N 6300 (rev 35)
and it doesn't exactly have this problem. Every power save packet is followed by a non-power-save QoS null packet, so the access point presumably stops sending packets for a fraction of a second.
EDIT: I tried another mini PCIe wifi card in the first laptop, but it appears to be locked down so another mini PCIe card cannot be detected by the OS.
linux wireless-networking debian power-management hostapd
I've got a laptop with an Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
(using iwlwifi
kernel module). Although power_save
(a module parameter) is disabled, I can see 802.11 control frames containing power management packets notifying the access point that it is going to sleep. The access point stops sending packets to the laptop until it sees another packet from the laptop.
How do I really stop the laptop from sending power save packets to the access point? (Or alternatively, how do I stop the access point from honouring them?)
I'm sure power_save
is disabled, as when I enabled it, power save packets are sent far more frequently (almost every second).
The access point is running hostapd
with an ath9k
driver. Both the access point and laptop are running debian wheezy with the 686-pae 3.2 kernel. I've tried putting the 3.10 iwlwifi driver on the laptop, but there is no change.
EDIT: I tried on another laptop with another iwlwifi
chipset Intel Corporation Centrino Ultimate-N 6300 (rev 35)
and it doesn't exactly have this problem. Every power save packet is followed by a non-power-save QoS null packet, so the access point presumably stops sending packets for a fraction of a second.
EDIT: I tried another mini PCIe wifi card in the first laptop, but it appears to be locked down so another mini PCIe card cannot be detected by the OS.
linux wireless-networking debian power-management hostapd
linux wireless-networking debian power-management hostapd
edited Oct 24 '13 at 1:34
asked Oct 21 '13 at 20:04
Jayen
328216
328216
Did you set power_level as well? By default, iwlwifi has power management disabled
– MariusMatutiae
Oct 21 '13 at 21:06
it's 0 while power save is N. I tried making it 5.
– Jayen
Oct 22 '13 at 0:40
add a comment |
Did you set power_level as well? By default, iwlwifi has power management disabled
– MariusMatutiae
Oct 21 '13 at 21:06
it's 0 while power save is N. I tried making it 5.
– Jayen
Oct 22 '13 at 0:40
Did you set power_level as well? By default, iwlwifi has power management disabled
– MariusMatutiae
Oct 21 '13 at 21:06
Did you set power_level as well? By default, iwlwifi has power management disabled
– MariusMatutiae
Oct 21 '13 at 21:06
it's 0 while power save is N. I tried making it 5.
– Jayen
Oct 22 '13 at 0:40
it's 0 while power save is N. I tried making it 5.
– Jayen
Oct 22 '13 at 0:40
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I took a look at the source code for iwlwifi. In the header iwl-modparams.h there is this bit of code:
* struct iwl_mod_params
*
* Holds the module parameters
*
* @sw_crypto: using hardware encryption, default = 0
* @disable_11n: disable 11n capabilities, default = 0,
* use IWL_DISABLE_HT_* constants
* @amsdu_size_8K: enable 8K amsdu size, default = 0
* @restart_fw: restart firmware, default = 1
* @wd_disable: enable stuck queue check, default = 0
* @bt_coex_active: enable bt coex, default = true
* @led_mode: system default, default = 0
* @power_save: disable power save, default = false
* @power_level: power level, default = 1
* @debug_level: levels are IWL_DL_*
* @ant_coupling: antenna coupling in dB, default = 0
*/
This suggests to me that the correct way to disable power saving is
insmod iwlwifi power_save=true
which is exactly the opposite of the output of modinfo. I would give it a try.
1) I'm sure power_save is disabled, as when I enabled it, power save packets are sent far more frequently (almost every second). 2) Both the access point and laptop are running debian wheezy with the 686-pae 3.2 kernel. 3) @power_save: enable power save, default = false
– Jayen
Oct 22 '13 at 10:21
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f663335%2freally-disable-power-save-in-linux-wifi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I took a look at the source code for iwlwifi. In the header iwl-modparams.h there is this bit of code:
* struct iwl_mod_params
*
* Holds the module parameters
*
* @sw_crypto: using hardware encryption, default = 0
* @disable_11n: disable 11n capabilities, default = 0,
* use IWL_DISABLE_HT_* constants
* @amsdu_size_8K: enable 8K amsdu size, default = 0
* @restart_fw: restart firmware, default = 1
* @wd_disable: enable stuck queue check, default = 0
* @bt_coex_active: enable bt coex, default = true
* @led_mode: system default, default = 0
* @power_save: disable power save, default = false
* @power_level: power level, default = 1
* @debug_level: levels are IWL_DL_*
* @ant_coupling: antenna coupling in dB, default = 0
*/
This suggests to me that the correct way to disable power saving is
insmod iwlwifi power_save=true
which is exactly the opposite of the output of modinfo. I would give it a try.
1) I'm sure power_save is disabled, as when I enabled it, power save packets are sent far more frequently (almost every second). 2) Both the access point and laptop are running debian wheezy with the 686-pae 3.2 kernel. 3) @power_save: enable power save, default = false
– Jayen
Oct 22 '13 at 10:21
add a comment |
up vote
0
down vote
I took a look at the source code for iwlwifi. In the header iwl-modparams.h there is this bit of code:
* struct iwl_mod_params
*
* Holds the module parameters
*
* @sw_crypto: using hardware encryption, default = 0
* @disable_11n: disable 11n capabilities, default = 0,
* use IWL_DISABLE_HT_* constants
* @amsdu_size_8K: enable 8K amsdu size, default = 0
* @restart_fw: restart firmware, default = 1
* @wd_disable: enable stuck queue check, default = 0
* @bt_coex_active: enable bt coex, default = true
* @led_mode: system default, default = 0
* @power_save: disable power save, default = false
* @power_level: power level, default = 1
* @debug_level: levels are IWL_DL_*
* @ant_coupling: antenna coupling in dB, default = 0
*/
This suggests to me that the correct way to disable power saving is
insmod iwlwifi power_save=true
which is exactly the opposite of the output of modinfo. I would give it a try.
1) I'm sure power_save is disabled, as when I enabled it, power save packets are sent far more frequently (almost every second). 2) Both the access point and laptop are running debian wheezy with the 686-pae 3.2 kernel. 3) @power_save: enable power save, default = false
– Jayen
Oct 22 '13 at 10:21
add a comment |
up vote
0
down vote
up vote
0
down vote
I took a look at the source code for iwlwifi. In the header iwl-modparams.h there is this bit of code:
* struct iwl_mod_params
*
* Holds the module parameters
*
* @sw_crypto: using hardware encryption, default = 0
* @disable_11n: disable 11n capabilities, default = 0,
* use IWL_DISABLE_HT_* constants
* @amsdu_size_8K: enable 8K amsdu size, default = 0
* @restart_fw: restart firmware, default = 1
* @wd_disable: enable stuck queue check, default = 0
* @bt_coex_active: enable bt coex, default = true
* @led_mode: system default, default = 0
* @power_save: disable power save, default = false
* @power_level: power level, default = 1
* @debug_level: levels are IWL_DL_*
* @ant_coupling: antenna coupling in dB, default = 0
*/
This suggests to me that the correct way to disable power saving is
insmod iwlwifi power_save=true
which is exactly the opposite of the output of modinfo. I would give it a try.
I took a look at the source code for iwlwifi. In the header iwl-modparams.h there is this bit of code:
* struct iwl_mod_params
*
* Holds the module parameters
*
* @sw_crypto: using hardware encryption, default = 0
* @disable_11n: disable 11n capabilities, default = 0,
* use IWL_DISABLE_HT_* constants
* @amsdu_size_8K: enable 8K amsdu size, default = 0
* @restart_fw: restart firmware, default = 1
* @wd_disable: enable stuck queue check, default = 0
* @bt_coex_active: enable bt coex, default = true
* @led_mode: system default, default = 0
* @power_save: disable power save, default = false
* @power_level: power level, default = 1
* @debug_level: levels are IWL_DL_*
* @ant_coupling: antenna coupling in dB, default = 0
*/
This suggests to me that the correct way to disable power saving is
insmod iwlwifi power_save=true
which is exactly the opposite of the output of modinfo. I would give it a try.
answered Oct 22 '13 at 5:06
MariusMatutiae
38k95195
38k95195
1) I'm sure power_save is disabled, as when I enabled it, power save packets are sent far more frequently (almost every second). 2) Both the access point and laptop are running debian wheezy with the 686-pae 3.2 kernel. 3) @power_save: enable power save, default = false
– Jayen
Oct 22 '13 at 10:21
add a comment |
1) I'm sure power_save is disabled, as when I enabled it, power save packets are sent far more frequently (almost every second). 2) Both the access point and laptop are running debian wheezy with the 686-pae 3.2 kernel. 3) @power_save: enable power save, default = false
– Jayen
Oct 22 '13 at 10:21
1) I'm sure power_save is disabled, as when I enabled it, power save packets are sent far more frequently (almost every second). 2) Both the access point and laptop are running debian wheezy with the 686-pae 3.2 kernel. 3) @power_save: enable power save, default = false
– Jayen
Oct 22 '13 at 10:21
1) I'm sure power_save is disabled, as when I enabled it, power save packets are sent far more frequently (almost every second). 2) Both the access point and laptop are running debian wheezy with the 686-pae 3.2 kernel. 3) @power_save: enable power save, default = false
– Jayen
Oct 22 '13 at 10:21
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f663335%2freally-disable-power-save-in-linux-wifi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you set power_level as well? By default, iwlwifi has power management disabled
– MariusMatutiae
Oct 21 '13 at 21:06
it's 0 while power save is N. I tried making it 5.
– Jayen
Oct 22 '13 at 0:40