The concept of “Airplane Mode” in Linux





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







-1















When installing a Ubuntu, Manjaro or other Graphical Linux distro on laptop, when press the airplane mode button on laptop, Airplane mode can be enabled.



How the concept of airplane mode works in Linux distro?



Is it just a set of rule toward Bluetooth, and wifi and other wireless stuff?



Does the implementation of airplane mode control appears in window manager, network manager or x11 or somewhere else?



If there is a problem in airplane mode control what part should I focus to figure out the problem?



Is there any one who can provide a explanation (high level) of the mechanism of airplane mode control in a specific system (KDE/Linux, Gnome/Linux or the other common system)?










share|improve this question

























  • What is the make, model, and serial number of your system? This issue is most likely extremely dependent on your hardware info. Without it, we can do very little to assist.

    – 0xSheepdog
    16 hours ago











  • @0xSheepdog, I am just trying to figure out the high level (general) stuff instead of detailed hardware operation. I am focused on the structure of how the software works.

    – davmos
    16 hours ago


















-1















When installing a Ubuntu, Manjaro or other Graphical Linux distro on laptop, when press the airplane mode button on laptop, Airplane mode can be enabled.



How the concept of airplane mode works in Linux distro?



Is it just a set of rule toward Bluetooth, and wifi and other wireless stuff?



Does the implementation of airplane mode control appears in window manager, network manager or x11 or somewhere else?



If there is a problem in airplane mode control what part should I focus to figure out the problem?



Is there any one who can provide a explanation (high level) of the mechanism of airplane mode control in a specific system (KDE/Linux, Gnome/Linux or the other common system)?










share|improve this question

























  • What is the make, model, and serial number of your system? This issue is most likely extremely dependent on your hardware info. Without it, we can do very little to assist.

    – 0xSheepdog
    16 hours ago











  • @0xSheepdog, I am just trying to figure out the high level (general) stuff instead of detailed hardware operation. I am focused on the structure of how the software works.

    – davmos
    16 hours ago














-1












-1








-1








When installing a Ubuntu, Manjaro or other Graphical Linux distro on laptop, when press the airplane mode button on laptop, Airplane mode can be enabled.



How the concept of airplane mode works in Linux distro?



Is it just a set of rule toward Bluetooth, and wifi and other wireless stuff?



Does the implementation of airplane mode control appears in window manager, network manager or x11 or somewhere else?



If there is a problem in airplane mode control what part should I focus to figure out the problem?



Is there any one who can provide a explanation (high level) of the mechanism of airplane mode control in a specific system (KDE/Linux, Gnome/Linux or the other common system)?










share|improve this question
















When installing a Ubuntu, Manjaro or other Graphical Linux distro on laptop, when press the airplane mode button on laptop, Airplane mode can be enabled.



How the concept of airplane mode works in Linux distro?



Is it just a set of rule toward Bluetooth, and wifi and other wireless stuff?



Does the implementation of airplane mode control appears in window manager, network manager or x11 or somewhere else?



If there is a problem in airplane mode control what part should I focus to figure out the problem?



Is there any one who can provide a explanation (high level) of the mechanism of airplane mode control in a specific system (KDE/Linux, Gnome/Linux or the other common system)?







linux networkmanager devices distributions






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 1 hour ago









sourcejedi

25.6k445113




25.6k445113










asked 16 hours ago









davmosdavmos

8817




8817













  • What is the make, model, and serial number of your system? This issue is most likely extremely dependent on your hardware info. Without it, we can do very little to assist.

    – 0xSheepdog
    16 hours ago











  • @0xSheepdog, I am just trying to figure out the high level (general) stuff instead of detailed hardware operation. I am focused on the structure of how the software works.

    – davmos
    16 hours ago



















  • What is the make, model, and serial number of your system? This issue is most likely extremely dependent on your hardware info. Without it, we can do very little to assist.

    – 0xSheepdog
    16 hours ago











  • @0xSheepdog, I am just trying to figure out the high level (general) stuff instead of detailed hardware operation. I am focused on the structure of how the software works.

    – davmos
    16 hours ago

















What is the make, model, and serial number of your system? This issue is most likely extremely dependent on your hardware info. Without it, we can do very little to assist.

– 0xSheepdog
16 hours ago





What is the make, model, and serial number of your system? This issue is most likely extremely dependent on your hardware info. Without it, we can do very little to assist.

– 0xSheepdog
16 hours ago













@0xSheepdog, I am just trying to figure out the high level (general) stuff instead of detailed hardware operation. I am focused on the structure of how the software works.

– davmos
16 hours ago





@0xSheepdog, I am just trying to figure out the high level (general) stuff instead of detailed hardware operation. I am focused on the structure of how the software works.

– davmos
16 hours ago










2 Answers
2






active

oldest

votes


















0















Is (Airplane mode) just a set of rule toward Bluetooth, and wifi and other wireless stuff?




Yes it just turns off networking. Read the Wikipedia artical.




Does the implementation of airmode control appears in window manager, network manager or x11 or somewhere else?




Desktop Environment.




If there is a problem in airmode control what part should I focus to figure out the problem?




It's a meta feature so you can ignore the issue and disable/enable networks directly.



Comments from Gnome, and KDE.






share|improve this answer































    0














    Mostly, "Airplane mode" means to disconnect any radio ("wireless") connections, AND stop sending any active probes to find possible connections.



    On most Linux systems, Wi-Fi network connections are managed through NetworkManager. Other wireless network connection managers are available.



    Additionally, there is a concept called RFKILL. RFKILL means to cut off a certain radio transmitter. In some cases, upper layers such as a Wi-Fi driver might recognize this, and return the specific error code ERFKILL, "Operation not possible due to RF-kill". For example the command iw dev wlp2s0 scan might return this error.



    Airplane Mode in Gnome Shell, or other GUI systems, will activate RFKILL if the hardware supports it. However, your GUI might let you enable Airplane mode even if you do not have RFKILL controls for all your radios... Partly because the GUI cannot reliably tell the association between RFKILL controls and radio devices :-).



    In Gnome shell, the Airplane mode button on the keyboard is just a keyboard shortcut to toggle Airplane mode. When Airplane mode is enabled, I can also see a button in the corner menu which allows to turn it back off.



    Some other GUIs use nm-applet to provide their GUI for NetworkManager, including for Airplane mode.



    Additionally, RFKILL might be a physical switch which the Operating System can only read, i.e. the hardware/firmware might not allow it to be overridden. This is called "hard rfkill". When the Operating System has control, it is called "soft rfkill".



    As the above link explains, you can use the rfkill command. rfkill list, or simply rfkill, will let you see if a hard rfkill is active, and what the device name is.



    You can also look in /sys/class/rfkill/. If you know how to inspect /sys/, you can find the name of the driver which exposes a given RFKILL control. E.g.



    $ cd /sys/class/rfkill
    $ ls
    rfkill1 rfkill2 rfkill3 rfkill8
    $ grep -H . */name
    rfkill1/name:dell-wifi
    rfkill2/name:dell-bluetooth
    rfkill3/name:phy0
    rfkill8/name:hci0
    $ ls -l
    total 0
    lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill1 -> ../../devices/platform/dell-laptop/rfkill/rfkill1
    lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill2 -> ../../devices/platform/dell-laptop/rfkill/rfkill2
    lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill3 -> ../../devices/pci0000:00/0000:00:1c.3/0000:02:00.0/ieee80211/phy0/rfkill3
    lrwxrwxrwx. 1 root root 0 Apr 6 15:53 rfkill8 -> ../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/rfkill8
    $ readlink rfkill8
    ../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/rfkill8
    $ cd rfkill8
    $ readlink device
    ../../hci0
    $ cd device
    $ readlink driver
    $ cd device
    $ readlink driver
    ../../../../../../../bus/usb/drivers/btusb
    $ cd driver
    $ readlink module
    ../../../../module/btusb


    Historically, the most common problem with Airplane mode is that you accidentally enabled Airplane mode e.g. by pressing a button. Then your Wi-Fi does not work, and you might not know why or how to fix it. However, my current Gnome shell is pretty good about soft rfkill. If Airplane mode is enabled, the Wi-Fi menu shows "Wi-Fi off". Clicking on "select a network" in the Wi-Fi menu shows a big notice that Airplane mode is enabled, and gives you a button to immediately disable Airplane mode.






    share|improve this answer


























      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%2f510830%2fthe-concept-of-airplane-mode-in-linux%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0















      Is (Airplane mode) just a set of rule toward Bluetooth, and wifi and other wireless stuff?




      Yes it just turns off networking. Read the Wikipedia artical.




      Does the implementation of airmode control appears in window manager, network manager or x11 or somewhere else?




      Desktop Environment.




      If there is a problem in airmode control what part should I focus to figure out the problem?




      It's a meta feature so you can ignore the issue and disable/enable networks directly.



      Comments from Gnome, and KDE.






      share|improve this answer




























        0















        Is (Airplane mode) just a set of rule toward Bluetooth, and wifi and other wireless stuff?




        Yes it just turns off networking. Read the Wikipedia artical.




        Does the implementation of airmode control appears in window manager, network manager or x11 or somewhere else?




        Desktop Environment.




        If there is a problem in airmode control what part should I focus to figure out the problem?




        It's a meta feature so you can ignore the issue and disable/enable networks directly.



        Comments from Gnome, and KDE.






        share|improve this answer


























          0












          0








          0








          Is (Airplane mode) just a set of rule toward Bluetooth, and wifi and other wireless stuff?




          Yes it just turns off networking. Read the Wikipedia artical.




          Does the implementation of airmode control appears in window manager, network manager or x11 or somewhere else?




          Desktop Environment.




          If there is a problem in airmode control what part should I focus to figure out the problem?




          It's a meta feature so you can ignore the issue and disable/enable networks directly.



          Comments from Gnome, and KDE.






          share|improve this answer














          Is (Airplane mode) just a set of rule toward Bluetooth, and wifi and other wireless stuff?




          Yes it just turns off networking. Read the Wikipedia artical.




          Does the implementation of airmode control appears in window manager, network manager or x11 or somewhere else?




          Desktop Environment.




          If there is a problem in airmode control what part should I focus to figure out the problem?




          It's a meta feature so you can ignore the issue and disable/enable networks directly.



          Comments from Gnome, and KDE.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 15 hours ago









          user1133275user1133275

          3,7641924




          3,7641924

























              0














              Mostly, "Airplane mode" means to disconnect any radio ("wireless") connections, AND stop sending any active probes to find possible connections.



              On most Linux systems, Wi-Fi network connections are managed through NetworkManager. Other wireless network connection managers are available.



              Additionally, there is a concept called RFKILL. RFKILL means to cut off a certain radio transmitter. In some cases, upper layers such as a Wi-Fi driver might recognize this, and return the specific error code ERFKILL, "Operation not possible due to RF-kill". For example the command iw dev wlp2s0 scan might return this error.



              Airplane Mode in Gnome Shell, or other GUI systems, will activate RFKILL if the hardware supports it. However, your GUI might let you enable Airplane mode even if you do not have RFKILL controls for all your radios... Partly because the GUI cannot reliably tell the association between RFKILL controls and radio devices :-).



              In Gnome shell, the Airplane mode button on the keyboard is just a keyboard shortcut to toggle Airplane mode. When Airplane mode is enabled, I can also see a button in the corner menu which allows to turn it back off.



              Some other GUIs use nm-applet to provide their GUI for NetworkManager, including for Airplane mode.



              Additionally, RFKILL might be a physical switch which the Operating System can only read, i.e. the hardware/firmware might not allow it to be overridden. This is called "hard rfkill". When the Operating System has control, it is called "soft rfkill".



              As the above link explains, you can use the rfkill command. rfkill list, or simply rfkill, will let you see if a hard rfkill is active, and what the device name is.



              You can also look in /sys/class/rfkill/. If you know how to inspect /sys/, you can find the name of the driver which exposes a given RFKILL control. E.g.



              $ cd /sys/class/rfkill
              $ ls
              rfkill1 rfkill2 rfkill3 rfkill8
              $ grep -H . */name
              rfkill1/name:dell-wifi
              rfkill2/name:dell-bluetooth
              rfkill3/name:phy0
              rfkill8/name:hci0
              $ ls -l
              total 0
              lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill1 -> ../../devices/platform/dell-laptop/rfkill/rfkill1
              lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill2 -> ../../devices/platform/dell-laptop/rfkill/rfkill2
              lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill3 -> ../../devices/pci0000:00/0000:00:1c.3/0000:02:00.0/ieee80211/phy0/rfkill3
              lrwxrwxrwx. 1 root root 0 Apr 6 15:53 rfkill8 -> ../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/rfkill8
              $ readlink rfkill8
              ../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/rfkill8
              $ cd rfkill8
              $ readlink device
              ../../hci0
              $ cd device
              $ readlink driver
              $ cd device
              $ readlink driver
              ../../../../../../../bus/usb/drivers/btusb
              $ cd driver
              $ readlink module
              ../../../../module/btusb


              Historically, the most common problem with Airplane mode is that you accidentally enabled Airplane mode e.g. by pressing a button. Then your Wi-Fi does not work, and you might not know why or how to fix it. However, my current Gnome shell is pretty good about soft rfkill. If Airplane mode is enabled, the Wi-Fi menu shows "Wi-Fi off". Clicking on "select a network" in the Wi-Fi menu shows a big notice that Airplane mode is enabled, and gives you a button to immediately disable Airplane mode.






              share|improve this answer






























                0














                Mostly, "Airplane mode" means to disconnect any radio ("wireless") connections, AND stop sending any active probes to find possible connections.



                On most Linux systems, Wi-Fi network connections are managed through NetworkManager. Other wireless network connection managers are available.



                Additionally, there is a concept called RFKILL. RFKILL means to cut off a certain radio transmitter. In some cases, upper layers such as a Wi-Fi driver might recognize this, and return the specific error code ERFKILL, "Operation not possible due to RF-kill". For example the command iw dev wlp2s0 scan might return this error.



                Airplane Mode in Gnome Shell, or other GUI systems, will activate RFKILL if the hardware supports it. However, your GUI might let you enable Airplane mode even if you do not have RFKILL controls for all your radios... Partly because the GUI cannot reliably tell the association between RFKILL controls and radio devices :-).



                In Gnome shell, the Airplane mode button on the keyboard is just a keyboard shortcut to toggle Airplane mode. When Airplane mode is enabled, I can also see a button in the corner menu which allows to turn it back off.



                Some other GUIs use nm-applet to provide their GUI for NetworkManager, including for Airplane mode.



                Additionally, RFKILL might be a physical switch which the Operating System can only read, i.e. the hardware/firmware might not allow it to be overridden. This is called "hard rfkill". When the Operating System has control, it is called "soft rfkill".



                As the above link explains, you can use the rfkill command. rfkill list, or simply rfkill, will let you see if a hard rfkill is active, and what the device name is.



                You can also look in /sys/class/rfkill/. If you know how to inspect /sys/, you can find the name of the driver which exposes a given RFKILL control. E.g.



                $ cd /sys/class/rfkill
                $ ls
                rfkill1 rfkill2 rfkill3 rfkill8
                $ grep -H . */name
                rfkill1/name:dell-wifi
                rfkill2/name:dell-bluetooth
                rfkill3/name:phy0
                rfkill8/name:hci0
                $ ls -l
                total 0
                lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill1 -> ../../devices/platform/dell-laptop/rfkill/rfkill1
                lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill2 -> ../../devices/platform/dell-laptop/rfkill/rfkill2
                lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill3 -> ../../devices/pci0000:00/0000:00:1c.3/0000:02:00.0/ieee80211/phy0/rfkill3
                lrwxrwxrwx. 1 root root 0 Apr 6 15:53 rfkill8 -> ../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/rfkill8
                $ readlink rfkill8
                ../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/rfkill8
                $ cd rfkill8
                $ readlink device
                ../../hci0
                $ cd device
                $ readlink driver
                $ cd device
                $ readlink driver
                ../../../../../../../bus/usb/drivers/btusb
                $ cd driver
                $ readlink module
                ../../../../module/btusb


                Historically, the most common problem with Airplane mode is that you accidentally enabled Airplane mode e.g. by pressing a button. Then your Wi-Fi does not work, and you might not know why or how to fix it. However, my current Gnome shell is pretty good about soft rfkill. If Airplane mode is enabled, the Wi-Fi menu shows "Wi-Fi off". Clicking on "select a network" in the Wi-Fi menu shows a big notice that Airplane mode is enabled, and gives you a button to immediately disable Airplane mode.






                share|improve this answer




























                  0












                  0








                  0







                  Mostly, "Airplane mode" means to disconnect any radio ("wireless") connections, AND stop sending any active probes to find possible connections.



                  On most Linux systems, Wi-Fi network connections are managed through NetworkManager. Other wireless network connection managers are available.



                  Additionally, there is a concept called RFKILL. RFKILL means to cut off a certain radio transmitter. In some cases, upper layers such as a Wi-Fi driver might recognize this, and return the specific error code ERFKILL, "Operation not possible due to RF-kill". For example the command iw dev wlp2s0 scan might return this error.



                  Airplane Mode in Gnome Shell, or other GUI systems, will activate RFKILL if the hardware supports it. However, your GUI might let you enable Airplane mode even if you do not have RFKILL controls for all your radios... Partly because the GUI cannot reliably tell the association between RFKILL controls and radio devices :-).



                  In Gnome shell, the Airplane mode button on the keyboard is just a keyboard shortcut to toggle Airplane mode. When Airplane mode is enabled, I can also see a button in the corner menu which allows to turn it back off.



                  Some other GUIs use nm-applet to provide their GUI for NetworkManager, including for Airplane mode.



                  Additionally, RFKILL might be a physical switch which the Operating System can only read, i.e. the hardware/firmware might not allow it to be overridden. This is called "hard rfkill". When the Operating System has control, it is called "soft rfkill".



                  As the above link explains, you can use the rfkill command. rfkill list, or simply rfkill, will let you see if a hard rfkill is active, and what the device name is.



                  You can also look in /sys/class/rfkill/. If you know how to inspect /sys/, you can find the name of the driver which exposes a given RFKILL control. E.g.



                  $ cd /sys/class/rfkill
                  $ ls
                  rfkill1 rfkill2 rfkill3 rfkill8
                  $ grep -H . */name
                  rfkill1/name:dell-wifi
                  rfkill2/name:dell-bluetooth
                  rfkill3/name:phy0
                  rfkill8/name:hci0
                  $ ls -l
                  total 0
                  lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill1 -> ../../devices/platform/dell-laptop/rfkill/rfkill1
                  lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill2 -> ../../devices/platform/dell-laptop/rfkill/rfkill2
                  lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill3 -> ../../devices/pci0000:00/0000:00:1c.3/0000:02:00.0/ieee80211/phy0/rfkill3
                  lrwxrwxrwx. 1 root root 0 Apr 6 15:53 rfkill8 -> ../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/rfkill8
                  $ readlink rfkill8
                  ../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/rfkill8
                  $ cd rfkill8
                  $ readlink device
                  ../../hci0
                  $ cd device
                  $ readlink driver
                  $ cd device
                  $ readlink driver
                  ../../../../../../../bus/usb/drivers/btusb
                  $ cd driver
                  $ readlink module
                  ../../../../module/btusb


                  Historically, the most common problem with Airplane mode is that you accidentally enabled Airplane mode e.g. by pressing a button. Then your Wi-Fi does not work, and you might not know why or how to fix it. However, my current Gnome shell is pretty good about soft rfkill. If Airplane mode is enabled, the Wi-Fi menu shows "Wi-Fi off". Clicking on "select a network" in the Wi-Fi menu shows a big notice that Airplane mode is enabled, and gives you a button to immediately disable Airplane mode.






                  share|improve this answer















                  Mostly, "Airplane mode" means to disconnect any radio ("wireless") connections, AND stop sending any active probes to find possible connections.



                  On most Linux systems, Wi-Fi network connections are managed through NetworkManager. Other wireless network connection managers are available.



                  Additionally, there is a concept called RFKILL. RFKILL means to cut off a certain radio transmitter. In some cases, upper layers such as a Wi-Fi driver might recognize this, and return the specific error code ERFKILL, "Operation not possible due to RF-kill". For example the command iw dev wlp2s0 scan might return this error.



                  Airplane Mode in Gnome Shell, or other GUI systems, will activate RFKILL if the hardware supports it. However, your GUI might let you enable Airplane mode even if you do not have RFKILL controls for all your radios... Partly because the GUI cannot reliably tell the association between RFKILL controls and radio devices :-).



                  In Gnome shell, the Airplane mode button on the keyboard is just a keyboard shortcut to toggle Airplane mode. When Airplane mode is enabled, I can also see a button in the corner menu which allows to turn it back off.



                  Some other GUIs use nm-applet to provide their GUI for NetworkManager, including for Airplane mode.



                  Additionally, RFKILL might be a physical switch which the Operating System can only read, i.e. the hardware/firmware might not allow it to be overridden. This is called "hard rfkill". When the Operating System has control, it is called "soft rfkill".



                  As the above link explains, you can use the rfkill command. rfkill list, or simply rfkill, will let you see if a hard rfkill is active, and what the device name is.



                  You can also look in /sys/class/rfkill/. If you know how to inspect /sys/, you can find the name of the driver which exposes a given RFKILL control. E.g.



                  $ cd /sys/class/rfkill
                  $ ls
                  rfkill1 rfkill2 rfkill3 rfkill8
                  $ grep -H . */name
                  rfkill1/name:dell-wifi
                  rfkill2/name:dell-bluetooth
                  rfkill3/name:phy0
                  rfkill8/name:hci0
                  $ ls -l
                  total 0
                  lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill1 -> ../../devices/platform/dell-laptop/rfkill/rfkill1
                  lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill2 -> ../../devices/platform/dell-laptop/rfkill/rfkill2
                  lrwxrwxrwx. 1 root root 0 Apr 6 10:03 rfkill3 -> ../../devices/pci0000:00/0000:00:1c.3/0000:02:00.0/ieee80211/phy0/rfkill3
                  lrwxrwxrwx. 1 root root 0 Apr 6 15:53 rfkill8 -> ../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/rfkill8
                  $ readlink rfkill8
                  ../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/rfkill8
                  $ cd rfkill8
                  $ readlink device
                  ../../hci0
                  $ cd device
                  $ readlink driver
                  $ cd device
                  $ readlink driver
                  ../../../../../../../bus/usb/drivers/btusb
                  $ cd driver
                  $ readlink module
                  ../../../../module/btusb


                  Historically, the most common problem with Airplane mode is that you accidentally enabled Airplane mode e.g. by pressing a button. Then your Wi-Fi does not work, and you might not know why or how to fix it. However, my current Gnome shell is pretty good about soft rfkill. If Airplane mode is enabled, the Wi-Fi menu shows "Wi-Fi off". Clicking on "select a network" in the Wi-Fi menu shows a big notice that Airplane mode is enabled, and gives you a button to immediately disable Airplane mode.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 6 mins ago

























                  answered 48 mins ago









                  sourcejedisourcejedi

                  25.6k445113




                  25.6k445113






























                      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%2f510830%2fthe-concept-of-airplane-mode-in-linux%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

                      宮崎県

                      濃尾地震

                      シテ島