wlan0 No such device
up vote
0
down vote
favorite
I am trying to run these two commands in an attempt to fix my intermittent wireless connection
iwconfig wlan0
sudo iwconfig wlan0 power off
But I get this error
wlan0 No such device
networking drivers wireless lan
asked Nov 24 at 13:40
stackinator
460114
add a comment |
up vote
0
down vote
favorite
I am trying to run these two commands in an attempt to fix my intermittent wireless connection
iwconfig wlan0
sudo iwconfig wlan0 power off
But I get this error
wlan0 No such device
networking drivers wireless lan
asked Nov 24 at 13:40
stackinator
460114
1
Please edit to add results forlsusb; lspci -nnk | grep -iA3 net; iwconfig
– Jeremy31
Nov 24 at 13:51
@Jeremy31 updated per your recommendation
– stackinator
Nov 24 at 13:56
sounds like you're using the wrong name for the network device use ifconfig to see what your network device name is(it will be on the left hand side along with lo)
– N. Phip
Nov 24 at 14:01
updated per your recommendation. Does that change anything?
– stackinator
Nov 24 at 14:06
whatever name you get on the left top of the command ifconfig is your network device name and should be used instead of wlan0 (wlp4s0 in your case)
– N. Phip
Nov 24 at 14:09
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am trying to run these two commands in an attempt to fix my intermittent wireless connection
iwconfig wlan0
sudo iwconfig wlan0 power off
But I get this error
wlan0 No such device
networking drivers wireless lan
asked Nov 24 at 13:40
stackinator
460114
I am trying to run these two commands in an attempt to fix my intermittent wireless connection
iwconfig wlan0
sudo iwconfig wlan0 power off
But I get this error
wlan0 No such device
networking drivers wireless lan
networking drivers wireless lan
asked Nov 24 at 13:40
stackinator
460114
asked Nov 24 at 13:40
stackinator
460114
edited 2 days ago
asked Nov 24 at 13:40
stackinator
460114
asked Nov 24 at 13:40
stackinator
460114
asked Nov 24 at 13:40
stackinator
460114
460114
1
Please edit to add results forlsusb; lspci -nnk | grep -iA3 net; iwconfig
– Jeremy31
Nov 24 at 13:51
@Jeremy31 updated per your recommendation
– stackinator
Nov 24 at 13:56
sounds like you're using the wrong name for the network device use ifconfig to see what your network device name is(it will be on the left hand side along with lo)
– N. Phip
Nov 24 at 14:01
updated per your recommendation. Does that change anything?
– stackinator
Nov 24 at 14:06
whatever name you get on the left top of the command ifconfig is your network device name and should be used instead of wlan0 (wlp4s0 in your case)
– N. Phip
Nov 24 at 14:09
add a comment |
1
Please edit to add results forlsusb; lspci -nnk | grep -iA3 net; iwconfig
– Jeremy31
Nov 24 at 13:51
@Jeremy31 updated per your recommendation
– stackinator
Nov 24 at 13:56
sounds like you're using the wrong name for the network device use ifconfig to see what your network device name is(it will be on the left hand side along with lo)
– N. Phip
Nov 24 at 14:01
updated per your recommendation. Does that change anything?
– stackinator
Nov 24 at 14:06
whatever name you get on the left top of the command ifconfig is your network device name and should be used instead of wlan0 (wlp4s0 in your case)
– N. Phip
Nov 24 at 14:09
1
1
Please edit to add results for
lsusb; lspci -nnk | grep -iA3 net; iwconfig– Jeremy31
Nov 24 at 13:51
Please edit to add results for
lsusb; lspci -nnk | grep -iA3 net; iwconfig– Jeremy31
Nov 24 at 13:51
@Jeremy31 updated per your recommendation
– stackinator
Nov 24 at 13:56
@Jeremy31 updated per your recommendation
– stackinator
Nov 24 at 13:56
sounds like you're using the wrong name for the network device use ifconfig to see what your network device name is(it will be on the left hand side along with lo)
– N. Phip
Nov 24 at 14:01
sounds like you're using the wrong name for the network device use ifconfig to see what your network device name is(it will be on the left hand side along with lo)
– N. Phip
Nov 24 at 14:01
updated per your recommendation. Does that change anything?
– stackinator
Nov 24 at 14:06
updated per your recommendation. Does that change anything?
– stackinator
Nov 24 at 14:06
whatever name you get on the left top of the command ifconfig is your network device name and should be used instead of wlan0 (wlp4s0 in your case)
– N. Phip
Nov 24 at 14:09
whatever name you get on the left top of the command ifconfig is your network device name and should be used instead of wlan0 (wlp4s0 in your case)
– N. Phip
Nov 24 at 14:09
add a comment |
2 Answers
2
active
oldest
votes
up vote
2
down vote
accepted
The answer to your question is to use sudo iwconfig wlp4s0 power off
But I doubt if it will fix your issue as the ath9k module blocks power management changes unless you
sudo modprobe -r ath9k
sudo modprobe -r ath9k ps_enable=1You may actually want to try
sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
systemctl restart network-manager.serviceanswered Nov 24 at 13:57
Jeremy31
8,20521364
1
The issue with using wlan0 is that it doesn't exist, your wifi interface is wlp4s0. The ps_enable will switch back to default on a reboot and the sudo sed command can be reversed by changing where the 2 and 3 are
– Jeremy31
Nov 24 at 14:04
add a comment |
up vote
1
down vote
Your wlan0 name adapter is wlp4s0.
Correct use of wlp4s0:
iwconfig wlp4s0
sudo iwconfig wlp4s0 power off
answered Nov 24 at 14:10
kukulo
1,270418
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
The answer to your question is to use sudo iwconfig wlp4s0 power off
But I doubt if it will fix your issue as the ath9k module blocks power management changes unless you
sudo modprobe -r ath9k
sudo modprobe -r ath9k ps_enable=1You may actually want to try
sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
systemctl restart network-manager.serviceanswered Nov 24 at 13:57
Jeremy31
8,20521364
1
The issue with using wlan0 is that it doesn't exist, your wifi interface is wlp4s0. The ps_enable will switch back to default on a reboot and the sudo sed command can be reversed by changing where the 2 and 3 are
– Jeremy31
Nov 24 at 14:04
add a comment |
up vote
2
down vote
accepted
The answer to your question is to use sudo iwconfig wlp4s0 power off
But I doubt if it will fix your issue as the ath9k module blocks power management changes unless you
sudo modprobe -r ath9k
sudo modprobe -r ath9k ps_enable=1You may actually want to try
sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
systemctl restart network-manager.serviceanswered Nov 24 at 13:57
Jeremy31
8,20521364
1
The issue with using wlan0 is that it doesn't exist, your wifi interface is wlp4s0. The ps_enable will switch back to default on a reboot and the sudo sed command can be reversed by changing where the 2 and 3 are
– Jeremy31
Nov 24 at 14:04
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
The answer to your question is to use sudo iwconfig wlp4s0 power off
But I doubt if it will fix your issue as the ath9k module blocks power management changes unless you
sudo modprobe -r ath9k
sudo modprobe -r ath9k ps_enable=1You may actually want to try
sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
systemctl restart network-manager.serviceanswered Nov 24 at 13:57
Jeremy31
8,20521364
The answer to your question is to use sudo iwconfig wlp4s0 power off
But I doubt if it will fix your issue as the ath9k module blocks power management changes unless you
sudo modprobe -r ath9k
sudo modprobe -r ath9k ps_enable=1You may actually want to try
sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
systemctl restart network-manager.serviceanswered Nov 24 at 13:57
Jeremy31
8,20521364
answered Nov 24 at 13:57
Jeremy31
8,20521364
answered Nov 24 at 13:57
Jeremy31
8,20521364
answered Nov 24 at 13:57
Jeremy31
8,20521364
8,20521364
1
The issue with using wlan0 is that it doesn't exist, your wifi interface is wlp4s0. The ps_enable will switch back to default on a reboot and the sudo sed command can be reversed by changing where the 2 and 3 are
– Jeremy31
Nov 24 at 14:04
add a comment |
1
The issue with using wlan0 is that it doesn't exist, your wifi interface is wlp4s0. The ps_enable will switch back to default on a reboot and the sudo sed command can be reversed by changing where the 2 and 3 are
– Jeremy31
Nov 24 at 14:04
1
1
The issue with using wlan0 is that it doesn't exist, your wifi interface is wlp4s0. The ps_enable will switch back to default on a reboot and the sudo sed command can be reversed by changing where the 2 and 3 are
– Jeremy31
Nov 24 at 14:04
The issue with using wlan0 is that it doesn't exist, your wifi interface is wlp4s0. The ps_enable will switch back to default on a reboot and the sudo sed command can be reversed by changing where the 2 and 3 are
– Jeremy31
Nov 24 at 14:04
add a comment |
up vote
1
down vote
Your wlan0 name adapter is wlp4s0.
Correct use of wlp4s0:
iwconfig wlp4s0
sudo iwconfig wlp4s0 power off
answered Nov 24 at 14:10
kukulo
1,270418
add a comment |
up vote
1
down vote
Your wlan0 name adapter is wlp4s0.
Correct use of wlp4s0:
iwconfig wlp4s0
sudo iwconfig wlp4s0 power off
answered Nov 24 at 14:10
kukulo
1,270418
add a comment |
up vote
1
down vote
up vote
1
down vote
Your wlan0 name adapter is wlp4s0.
Correct use of wlp4s0:
iwconfig wlp4s0
sudo iwconfig wlp4s0 power off
answered Nov 24 at 14:10
kukulo
1,270418
Your wlan0 name adapter is wlp4s0.
Correct use of wlp4s0:
iwconfig wlp4s0
sudo iwconfig wlp4s0 power off
answered Nov 24 at 14:10
kukulo
1,270418
answered Nov 24 at 14:10
kukulo
1,270418
answered Nov 24 at 14:10
kukulo
1,270418
answered Nov 24 at 14:10
kukulo
1,270418
1,270418
add a comment |
add a comment |
draft saved
draft discarded
draft saved
draft discarded
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%2faskubuntu.com%2fquestions%2f1095647%2fwlan0-no-such-device%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
1
Please edit to add results for
lsusb; lspci -nnk | grep -iA3 net; iwconfig– Jeremy31
Nov 24 at 13:51
@Jeremy31 updated per your recommendation
– stackinator
Nov 24 at 13:56
sounds like you're using the wrong name for the network device use ifconfig to see what your network device name is(it will be on the left hand side along with lo)
– N. Phip
Nov 24 at 14:01
updated per your recommendation. Does that change anything?
– stackinator
Nov 24 at 14:06
whatever name you get on the left top of the command ifconfig is your network device name and should be used instead of wlan0 (wlp4s0 in your case)
– N. Phip
Nov 24 at 14:09