Wifi stopped working without apparent reason The 2019 Stack Overflow Developer Survey Results...

What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?

Why Did Howard Stark Use All The Vibranium They Had On A Prototype Shield?

Monty Hall variation

Deadlock Graph and Interpretation, solution to avoid

What do the Banks children have against barley water?

Are there any other methods to apply to solving simultaneous equations?

Why is the maximum length of openwrt’s root password 8 characters?

Lethal sonic weapons

Can't find the latex code for the ⍎ (down tack jot) symbol

What tool would a Roman-age civilization have to grind silver and other metals into dust?

Can I write a for loop that iterates over both collections and arrays?

Extreme, unacceptable situation and I can't attend work tomorrow morning

Why can Shazam do this?

Feasability of miniature nuclear reactors for humanoid cyborgs

Limit the amount of RAM Mathematica may access?

Inflated grade on resume at previous job, might former employer tell new employer?

What are the motivations for publishing new editions of an existing textbook, beyond new discoveries in a field?

Which Sci-Fi work first showed weapon of galactic-scale mass destruction?

How to answer pointed "are you quitting" questioning when I don't want them to suspect

It's possible to achieve negative score?

Spanish for "widget"

"To split hairs" vs "To be pedantic"

How can I fix this gap between bookcases I made?

Springs with some finite mass



Wifi stopped working without apparent reason



The 2019 Stack Overflow Developer Survey Results Are InMultiple USB wireless devices?Pinguy OS 11.04 WiFi and Wired Networking is not workingwireless is disabled by hardware switch even when notWhat driver is being used by a wireless usb adapter?Making a usb wifi device work an a PowerPC Debian computer (iBook G4)Problems with connecting to wifiSetup wifi configurations for Broadcom43142Broadcom wireless undetected in Fedora 27Broadcom Wireless PCI Card BMC4360 14e4:43a0 cannot get drivers workingwifi not working, lenovo G50-70





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















I'm using Linux Mint 17.3 Rosa in a Dell Inspiron 1525 laptop. Wireless connection has been working for years in this laptop in different linux distros with proprietary Broadcom driver. I formated my computer 14 days ago, and wireless was working fine after that. I have been alternating between cabled and wireless connection. Yesterday, after disconnecting my cable connection, suddenly I could not use wireless anymore. The wifi networks are listed, but I cannot connect to them. I have confirmed (with other computer) that the network is working properly. I checked the packages that were installed or updated since last time wifi was working, and there were none.
My kernel version is



$ uname -a
Linux mycomputer 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:37:25 UTC 2015 i686 i686 i686 GNU/Linux


Here is my wireless card:



$ lspci -knn | grep Net -A2
0b:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
Subsystem: Dell Wireless 1395 WLAN Mini-Card [1028:000b]
Kernel driver in use: wl


Here is my dmesg output:



$ dmesg | grep wl
[ 11.216767] wl: module license 'MIXED/Proprietary' taints kernel.
[ 11.225409] wl: module verification failed: signature and/or required key missing - tainting kernel
[ 11.476882] wlan0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 6.30.223.248 (r487574)


Here is the output of iwconfig:



$ iwconfig
wlan0 IEEE 802.11abg ESSID:"housenet"
Mode:Managed Frequency:2.462 GHz Access Point: 20:CF:30:C6:32:A5
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off

lo no wireless extensions.

eth0 no wireless extensions.


Here is ip output (I don't know why it has state DORMANT and mode DORMANT):



$ ip link show wlan0
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DORMANT mode DORMANT group default qlen 1000
link/ether 00:23:4d:a8:e4:77 brd ff:ff:ff:ff:ff:ff


Also, rfkill seems to show no problem.



$ rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: brcmwl-0: Wireless LAN
Soft blocked: no
Hard blocked: no


I've tried changing the driver from bcmwl-kernel-source to firmware-b43-installer, reboot the computer, but the problem persists. Strangely, the same problem is now happening in the USB-live version of LM 17.3.










share|improve this question















migrated from askubuntu.com Jun 25 '16 at 14:31


This question came from our site for Ubuntu users and developers.



















  • Check what I posted half an hour ago: askubuntu.com/questions/791287/… Can you connect to any network with another distro?

    – Digital Dracula
    Jun 25 '16 at 14:09











  • I don't have another distro on this machine, only Windows.

    – Jack Antares
    Jun 25 '16 at 14:18











  • But does it work there? Because if it does that would indicate a non-hardware problem - if you read my own thread, I've tried using other distros, including a completely fresh, live USB and it still failed. For the life of me, I can't imagine how a non-hardware issue can appear like that in different distros, including one booting from a live USB

    – Digital Dracula
    Jun 25 '16 at 14:24











  • @DigitalDracula it could also be a driver issue, not necessarily hardware.

    – nixpower
    Jun 25 '16 at 14:26











  • @DigitalDracula I've tried in the live-USB of LM 17.3 and the problem is also happening there.

    – Jack Antares
    Jun 25 '16 at 14:43


















1















I'm using Linux Mint 17.3 Rosa in a Dell Inspiron 1525 laptop. Wireless connection has been working for years in this laptop in different linux distros with proprietary Broadcom driver. I formated my computer 14 days ago, and wireless was working fine after that. I have been alternating between cabled and wireless connection. Yesterday, after disconnecting my cable connection, suddenly I could not use wireless anymore. The wifi networks are listed, but I cannot connect to them. I have confirmed (with other computer) that the network is working properly. I checked the packages that were installed or updated since last time wifi was working, and there were none.
My kernel version is



$ uname -a
Linux mycomputer 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:37:25 UTC 2015 i686 i686 i686 GNU/Linux


Here is my wireless card:



$ lspci -knn | grep Net -A2
0b:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
Subsystem: Dell Wireless 1395 WLAN Mini-Card [1028:000b]
Kernel driver in use: wl


Here is my dmesg output:



$ dmesg | grep wl
[ 11.216767] wl: module license 'MIXED/Proprietary' taints kernel.
[ 11.225409] wl: module verification failed: signature and/or required key missing - tainting kernel
[ 11.476882] wlan0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 6.30.223.248 (r487574)


Here is the output of iwconfig:



$ iwconfig
wlan0 IEEE 802.11abg ESSID:"housenet"
Mode:Managed Frequency:2.462 GHz Access Point: 20:CF:30:C6:32:A5
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off

lo no wireless extensions.

eth0 no wireless extensions.


Here is ip output (I don't know why it has state DORMANT and mode DORMANT):



$ ip link show wlan0
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DORMANT mode DORMANT group default qlen 1000
link/ether 00:23:4d:a8:e4:77 brd ff:ff:ff:ff:ff:ff


Also, rfkill seems to show no problem.



$ rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: brcmwl-0: Wireless LAN
Soft blocked: no
Hard blocked: no


I've tried changing the driver from bcmwl-kernel-source to firmware-b43-installer, reboot the computer, but the problem persists. Strangely, the same problem is now happening in the USB-live version of LM 17.3.










share|improve this question















migrated from askubuntu.com Jun 25 '16 at 14:31


This question came from our site for Ubuntu users and developers.



















  • Check what I posted half an hour ago: askubuntu.com/questions/791287/… Can you connect to any network with another distro?

    – Digital Dracula
    Jun 25 '16 at 14:09











  • I don't have another distro on this machine, only Windows.

    – Jack Antares
    Jun 25 '16 at 14:18











  • But does it work there? Because if it does that would indicate a non-hardware problem - if you read my own thread, I've tried using other distros, including a completely fresh, live USB and it still failed. For the life of me, I can't imagine how a non-hardware issue can appear like that in different distros, including one booting from a live USB

    – Digital Dracula
    Jun 25 '16 at 14:24











  • @DigitalDracula it could also be a driver issue, not necessarily hardware.

    – nixpower
    Jun 25 '16 at 14:26











  • @DigitalDracula I've tried in the live-USB of LM 17.3 and the problem is also happening there.

    – Jack Antares
    Jun 25 '16 at 14:43














1












1








1








I'm using Linux Mint 17.3 Rosa in a Dell Inspiron 1525 laptop. Wireless connection has been working for years in this laptop in different linux distros with proprietary Broadcom driver. I formated my computer 14 days ago, and wireless was working fine after that. I have been alternating between cabled and wireless connection. Yesterday, after disconnecting my cable connection, suddenly I could not use wireless anymore. The wifi networks are listed, but I cannot connect to them. I have confirmed (with other computer) that the network is working properly. I checked the packages that were installed or updated since last time wifi was working, and there were none.
My kernel version is



$ uname -a
Linux mycomputer 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:37:25 UTC 2015 i686 i686 i686 GNU/Linux


Here is my wireless card:



$ lspci -knn | grep Net -A2
0b:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
Subsystem: Dell Wireless 1395 WLAN Mini-Card [1028:000b]
Kernel driver in use: wl


Here is my dmesg output:



$ dmesg | grep wl
[ 11.216767] wl: module license 'MIXED/Proprietary' taints kernel.
[ 11.225409] wl: module verification failed: signature and/or required key missing - tainting kernel
[ 11.476882] wlan0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 6.30.223.248 (r487574)


Here is the output of iwconfig:



$ iwconfig
wlan0 IEEE 802.11abg ESSID:"housenet"
Mode:Managed Frequency:2.462 GHz Access Point: 20:CF:30:C6:32:A5
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off

lo no wireless extensions.

eth0 no wireless extensions.


Here is ip output (I don't know why it has state DORMANT and mode DORMANT):



$ ip link show wlan0
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DORMANT mode DORMANT group default qlen 1000
link/ether 00:23:4d:a8:e4:77 brd ff:ff:ff:ff:ff:ff


Also, rfkill seems to show no problem.



$ rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: brcmwl-0: Wireless LAN
Soft blocked: no
Hard blocked: no


I've tried changing the driver from bcmwl-kernel-source to firmware-b43-installer, reboot the computer, but the problem persists. Strangely, the same problem is now happening in the USB-live version of LM 17.3.










share|improve this question
















I'm using Linux Mint 17.3 Rosa in a Dell Inspiron 1525 laptop. Wireless connection has been working for years in this laptop in different linux distros with proprietary Broadcom driver. I formated my computer 14 days ago, and wireless was working fine after that. I have been alternating between cabled and wireless connection. Yesterday, after disconnecting my cable connection, suddenly I could not use wireless anymore. The wifi networks are listed, but I cannot connect to them. I have confirmed (with other computer) that the network is working properly. I checked the packages that were installed or updated since last time wifi was working, and there were none.
My kernel version is



$ uname -a
Linux mycomputer 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:37:25 UTC 2015 i686 i686 i686 GNU/Linux


Here is my wireless card:



$ lspci -knn | grep Net -A2
0b:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
Subsystem: Dell Wireless 1395 WLAN Mini-Card [1028:000b]
Kernel driver in use: wl


Here is my dmesg output:



$ dmesg | grep wl
[ 11.216767] wl: module license 'MIXED/Proprietary' taints kernel.
[ 11.225409] wl: module verification failed: signature and/or required key missing - tainting kernel
[ 11.476882] wlan0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 6.30.223.248 (r487574)


Here is the output of iwconfig:



$ iwconfig
wlan0 IEEE 802.11abg ESSID:"housenet"
Mode:Managed Frequency:2.462 GHz Access Point: 20:CF:30:C6:32:A5
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off

lo no wireless extensions.

eth0 no wireless extensions.


Here is ip output (I don't know why it has state DORMANT and mode DORMANT):



$ ip link show wlan0
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state DORMANT mode DORMANT group default qlen 1000
link/ether 00:23:4d:a8:e4:77 brd ff:ff:ff:ff:ff:ff


Also, rfkill seems to show no problem.



$ rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: brcmwl-0: Wireless LAN
Soft blocked: no
Hard blocked: no


I've tried changing the driver from bcmwl-kernel-source to firmware-b43-installer, reboot the computer, but the problem persists. Strangely, the same problem is now happening in the USB-live version of LM 17.3.







wifi broadcom






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 25 '16 at 14:42







Jack Antares

















asked Jun 25 '16 at 14:05









Jack AntaresJack Antares

92




92




migrated from askubuntu.com Jun 25 '16 at 14:31


This question came from our site for Ubuntu users and developers.









migrated from askubuntu.com Jun 25 '16 at 14:31


This question came from our site for Ubuntu users and developers.















  • Check what I posted half an hour ago: askubuntu.com/questions/791287/… Can you connect to any network with another distro?

    – Digital Dracula
    Jun 25 '16 at 14:09











  • I don't have another distro on this machine, only Windows.

    – Jack Antares
    Jun 25 '16 at 14:18











  • But does it work there? Because if it does that would indicate a non-hardware problem - if you read my own thread, I've tried using other distros, including a completely fresh, live USB and it still failed. For the life of me, I can't imagine how a non-hardware issue can appear like that in different distros, including one booting from a live USB

    – Digital Dracula
    Jun 25 '16 at 14:24











  • @DigitalDracula it could also be a driver issue, not necessarily hardware.

    – nixpower
    Jun 25 '16 at 14:26











  • @DigitalDracula I've tried in the live-USB of LM 17.3 and the problem is also happening there.

    – Jack Antares
    Jun 25 '16 at 14:43



















  • Check what I posted half an hour ago: askubuntu.com/questions/791287/… Can you connect to any network with another distro?

    – Digital Dracula
    Jun 25 '16 at 14:09











  • I don't have another distro on this machine, only Windows.

    – Jack Antares
    Jun 25 '16 at 14:18











  • But does it work there? Because if it does that would indicate a non-hardware problem - if you read my own thread, I've tried using other distros, including a completely fresh, live USB and it still failed. For the life of me, I can't imagine how a non-hardware issue can appear like that in different distros, including one booting from a live USB

    – Digital Dracula
    Jun 25 '16 at 14:24











  • @DigitalDracula it could also be a driver issue, not necessarily hardware.

    – nixpower
    Jun 25 '16 at 14:26











  • @DigitalDracula I've tried in the live-USB of LM 17.3 and the problem is also happening there.

    – Jack Antares
    Jun 25 '16 at 14:43

















Check what I posted half an hour ago: askubuntu.com/questions/791287/… Can you connect to any network with another distro?

– Digital Dracula
Jun 25 '16 at 14:09





Check what I posted half an hour ago: askubuntu.com/questions/791287/… Can you connect to any network with another distro?

– Digital Dracula
Jun 25 '16 at 14:09













I don't have another distro on this machine, only Windows.

– Jack Antares
Jun 25 '16 at 14:18





I don't have another distro on this machine, only Windows.

– Jack Antares
Jun 25 '16 at 14:18













But does it work there? Because if it does that would indicate a non-hardware problem - if you read my own thread, I've tried using other distros, including a completely fresh, live USB and it still failed. For the life of me, I can't imagine how a non-hardware issue can appear like that in different distros, including one booting from a live USB

– Digital Dracula
Jun 25 '16 at 14:24





But does it work there? Because if it does that would indicate a non-hardware problem - if you read my own thread, I've tried using other distros, including a completely fresh, live USB and it still failed. For the life of me, I can't imagine how a non-hardware issue can appear like that in different distros, including one booting from a live USB

– Digital Dracula
Jun 25 '16 at 14:24













@DigitalDracula it could also be a driver issue, not necessarily hardware.

– nixpower
Jun 25 '16 at 14:26





@DigitalDracula it could also be a driver issue, not necessarily hardware.

– nixpower
Jun 25 '16 at 14:26













@DigitalDracula I've tried in the live-USB of LM 17.3 and the problem is also happening there.

– Jack Antares
Jun 25 '16 at 14:43





@DigitalDracula I've tried in the live-USB of LM 17.3 and the problem is also happening there.

– Jack Antares
Jun 25 '16 at 14:43










1 Answer
1






active

oldest

votes


















1














I solved my similar issue, maybe this applies to you too.



It appears I had accidentally pressed Fn + F2, which in this Fujitsu Siemens turns off the wifi. And, surprise-surprise, it remembers the choice even after a shutdown.



Check to make sure there isn't a physical button or shortcut combo like mine which deactivates your wifi. Apparently this persists between reboots.






share|improve this answer


























  • But in this case you shouldn't be seeing the networks, right?

    – Jack Antares
    Jul 1 '16 at 16:40











  • Good question. Apparently you can. Maybe the shortcut blocks the card from connecting, but allows scanning.

    – Digital Dracula
    Jul 2 '16 at 14:27











  • On my version (v30 in Ubuntu 16.04) iwconfig also shows the TxPower. It says off when in airplane mode, and 13dBm when enabled.

    – xenoid
    Apr 8 '18 at 20:59











  • It is usually a physical cut-off switch, so persisting across reboots is expected behaviour.

    – Rui F Ribeiro
    yesterday












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f292068%2fwifi-stopped-working-without-apparent-reason%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









1














I solved my similar issue, maybe this applies to you too.



It appears I had accidentally pressed Fn + F2, which in this Fujitsu Siemens turns off the wifi. And, surprise-surprise, it remembers the choice even after a shutdown.



Check to make sure there isn't a physical button or shortcut combo like mine which deactivates your wifi. Apparently this persists between reboots.






share|improve this answer


























  • But in this case you shouldn't be seeing the networks, right?

    – Jack Antares
    Jul 1 '16 at 16:40











  • Good question. Apparently you can. Maybe the shortcut blocks the card from connecting, but allows scanning.

    – Digital Dracula
    Jul 2 '16 at 14:27











  • On my version (v30 in Ubuntu 16.04) iwconfig also shows the TxPower. It says off when in airplane mode, and 13dBm when enabled.

    – xenoid
    Apr 8 '18 at 20:59











  • It is usually a physical cut-off switch, so persisting across reboots is expected behaviour.

    – Rui F Ribeiro
    yesterday
















1














I solved my similar issue, maybe this applies to you too.



It appears I had accidentally pressed Fn + F2, which in this Fujitsu Siemens turns off the wifi. And, surprise-surprise, it remembers the choice even after a shutdown.



Check to make sure there isn't a physical button or shortcut combo like mine which deactivates your wifi. Apparently this persists between reboots.






share|improve this answer


























  • But in this case you shouldn't be seeing the networks, right?

    – Jack Antares
    Jul 1 '16 at 16:40











  • Good question. Apparently you can. Maybe the shortcut blocks the card from connecting, but allows scanning.

    – Digital Dracula
    Jul 2 '16 at 14:27











  • On my version (v30 in Ubuntu 16.04) iwconfig also shows the TxPower. It says off when in airplane mode, and 13dBm when enabled.

    – xenoid
    Apr 8 '18 at 20:59











  • It is usually a physical cut-off switch, so persisting across reboots is expected behaviour.

    – Rui F Ribeiro
    yesterday














1












1








1







I solved my similar issue, maybe this applies to you too.



It appears I had accidentally pressed Fn + F2, which in this Fujitsu Siemens turns off the wifi. And, surprise-surprise, it remembers the choice even after a shutdown.



Check to make sure there isn't a physical button or shortcut combo like mine which deactivates your wifi. Apparently this persists between reboots.






share|improve this answer















I solved my similar issue, maybe this applies to you too.



It appears I had accidentally pressed Fn + F2, which in this Fujitsu Siemens turns off the wifi. And, surprise-surprise, it remembers the choice even after a shutdown.



Check to make sure there isn't a physical button or shortcut combo like mine which deactivates your wifi. Apparently this persists between reboots.







share|improve this answer














share|improve this answer



share|improve this answer








edited yesterday









Rui F Ribeiro

42k1483142




42k1483142










answered Jun 26 '16 at 12:16









Digital DraculaDigital Dracula

14516




14516













  • But in this case you shouldn't be seeing the networks, right?

    – Jack Antares
    Jul 1 '16 at 16:40











  • Good question. Apparently you can. Maybe the shortcut blocks the card from connecting, but allows scanning.

    – Digital Dracula
    Jul 2 '16 at 14:27











  • On my version (v30 in Ubuntu 16.04) iwconfig also shows the TxPower. It says off when in airplane mode, and 13dBm when enabled.

    – xenoid
    Apr 8 '18 at 20:59











  • It is usually a physical cut-off switch, so persisting across reboots is expected behaviour.

    – Rui F Ribeiro
    yesterday



















  • But in this case you shouldn't be seeing the networks, right?

    – Jack Antares
    Jul 1 '16 at 16:40











  • Good question. Apparently you can. Maybe the shortcut blocks the card from connecting, but allows scanning.

    – Digital Dracula
    Jul 2 '16 at 14:27











  • On my version (v30 in Ubuntu 16.04) iwconfig also shows the TxPower. It says off when in airplane mode, and 13dBm when enabled.

    – xenoid
    Apr 8 '18 at 20:59











  • It is usually a physical cut-off switch, so persisting across reboots is expected behaviour.

    – Rui F Ribeiro
    yesterday

















But in this case you shouldn't be seeing the networks, right?

– Jack Antares
Jul 1 '16 at 16:40





But in this case you shouldn't be seeing the networks, right?

– Jack Antares
Jul 1 '16 at 16:40













Good question. Apparently you can. Maybe the shortcut blocks the card from connecting, but allows scanning.

– Digital Dracula
Jul 2 '16 at 14:27





Good question. Apparently you can. Maybe the shortcut blocks the card from connecting, but allows scanning.

– Digital Dracula
Jul 2 '16 at 14:27













On my version (v30 in Ubuntu 16.04) iwconfig also shows the TxPower. It says off when in airplane mode, and 13dBm when enabled.

– xenoid
Apr 8 '18 at 20:59





On my version (v30 in Ubuntu 16.04) iwconfig also shows the TxPower. It says off when in airplane mode, and 13dBm when enabled.

– xenoid
Apr 8 '18 at 20:59













It is usually a physical cut-off switch, so persisting across reboots is expected behaviour.

– Rui F Ribeiro
yesterday





It is usually a physical cut-off switch, so persisting across reboots is expected behaviour.

– Rui F Ribeiro
yesterday


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f292068%2fwifi-stopped-working-without-apparent-reason%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Hudson River Historic District Contents Geography History The district today Aesthetics Cultural...

The number designs the writing. Feandra Aversely Definition: The act of ingrafting a sprig or shoot of one...

Ayherre Geografie Demografie Externe links Navigatiemenu43° 23′ NB, 1° 15′ WL43° 23′ NB, 1°...