How to check whether module is loaded with custom configurations?Why is my network interface named enp0s25...

For which categories of spectra is there an explicit description of the fibrant objects via lifting properties?

Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?

Having the player face themselves after the mid-game

Trig Subsitution When There's No Square Root

Can't make sense of a paragraph from Lovecraft

What do you call someone who likes to pick fights?

How exactly does an Ethernet collision happen in the cable, since nodes use different circuits for Tx and Rx?

Rationale to prefer local variables over instance variables?

Why couldn't the separatists legally leave the Republic?

How do we create new idioms and use them in a novel?

Can I negotiate a patent idea for a raise, under French law?

What materials can be used to make a humanoid skin warm?

Whose blood did Carol Danver's receive, Mar-vell's or Yon-Rogg's in the movie?

Street obstacles in New Zealand

Does "Until when" sound natural for native speakers?

Recommendation letter by significant other if you worked with them professionally?

Conservation of Mass and Energy

What do *foreign films* mean for an American?

I can't die. Who am I?

Can we track matter through time by looking at different depths in space?

Specifying a starting column with colortbl package and xcolor

Which situations would cause a company to ground or recall a aircraft series?

How can I get players to focus on the story aspect of D&D?

Signed and unsigned numbers



How to check whether module is loaded with custom configurations?


Why is my network interface named enp0s25 instead of eth0?How do I create a system file /etc/modprobe.d/ath9k.conf?`qdbus` returns an error. Ubuntu 18.04How (recipe) to build only one kernel module?Cannot get my N300 (DWA-130) D-link wireless USB to work on Ubuntu 14.04I have a Sony Vaio SVT131Aiil. The wireless does not show up as an option in network managerinstalled ubuntu 16.04 on hp laptop - wifi not workingubuntu 16.04 hotspot. Client has no internetwl module is loaded but not workingwireless ath9k suddenly stopped working on ubuntu 16.04UbuntuStudio will connect to one of two routersASUS laptop - wifi not connecting after upgrading to 18.04Kernel can't see Atheros Communications Inc. AR9462 Wireless Network Adapter













2















In the answer by Chili555 for How do I create a system file /etc/modprobe.d/ath9k.conf? it is shown that you can create a config file for a kernel module . Now the question is how do I verify that the options set in that config file have taken effect after sudo modprobe ath9k ?



Specific option that I am trying to check is ps_enable. However, doing the following



$ modinfo ath9k | grep ps_enable
parm: ps_enable:Enable WLAN PowerSave (int)


only explains what the parameter is and not its current value.










share|improve this question





























    2















    In the answer by Chili555 for How do I create a system file /etc/modprobe.d/ath9k.conf? it is shown that you can create a config file for a kernel module . Now the question is how do I verify that the options set in that config file have taken effect after sudo modprobe ath9k ?



    Specific option that I am trying to check is ps_enable. However, doing the following



    $ modinfo ath9k | grep ps_enable
    parm: ps_enable:Enable WLAN PowerSave (int)


    only explains what the parameter is and not its current value.










    share|improve this question



























      2












      2








      2








      In the answer by Chili555 for How do I create a system file /etc/modprobe.d/ath9k.conf? it is shown that you can create a config file for a kernel module . Now the question is how do I verify that the options set in that config file have taken effect after sudo modprobe ath9k ?



      Specific option that I am trying to check is ps_enable. However, doing the following



      $ modinfo ath9k | grep ps_enable
      parm: ps_enable:Enable WLAN PowerSave (int)


      only explains what the parameter is and not its current value.










      share|improve this question
















      In the answer by Chili555 for How do I create a system file /etc/modprobe.d/ath9k.conf? it is shown that you can create a config file for a kernel module . Now the question is how do I verify that the options set in that config file have taken effect after sudo modprobe ath9k ?



      Specific option that I am trying to check is ps_enable. However, doing the following



      $ modinfo ath9k | grep ps_enable
      parm: ps_enable:Enable WLAN PowerSave (int)


      only explains what the parameter is and not its current value.







      networking drivers configuration system






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 2 hours ago







      Sergiy Kolodyazhnyy

















      asked 3 hours ago









      Sergiy KolodyazhnyySergiy Kolodyazhnyy

      73.9k9154323




      73.9k9154323






















          1 Answer
          1






          active

          oldest

          votes


















          2














          Apparently such information is contained within /sys filesystem. According to Gilles's answer on the relevant post, in order to find the driver in use by interface you would execute



          readlink /sys/class/net/wlan0/device/driver


          which would provide the relative path as in



          ../../../../bus/pci/drivers/ath5k


          In my case due to systemd and predictive interface naming, the interface is named differently and produces



          $  readlink /sys/class/net/wlp2s0/device/driver
          ../../../../bus/pci/drivers/ath9k


          The resulting directory path contains subdirectories module/parameters/ where there will be files for each parameter containing their current value. Thus, if I edit the /etc/modprobe/ath9k.conf file and reinsert the module, the result is as follows:



          # After editing the conf file to set parameter to 1
          $ sudo sh -c 'modprobe -r ath9k ; sleep 3; modprobe ath9k'
          $ sudo cat /sys/class/net/wlp2s0/device/driver/../../../../bus/pci/drivers/ath9k/module/parameters/ps_enable
          1
          # after editing the file and setting parameter to 0
          $ sudo sh -c 'modprobe -r ath9k ; sleep 3; modprobe ath9k'
          $ sudo cat /sys/class/net/wlp2s0/device/driver/../../../../bus/pci/drivers/ath9k/module/parameters/ps_enable
          0


          The command can be combined as well.



          $ cat  "$(readlink -f /sys/class/net/wlp2s0/device/driver/)"/module/parameters/ps_enable
          0


          If you do have desktop environment and dbus running, as well as qdbus or dbus-send installed, such information can be queried via Network Manager's dbus interface ( though it requires figuring out the object path of each individual device, and probably would be better written in Python or C )



          $ qdbus --system org.freedesktop.NetworkManager /org/freedesktop/NetworkManager/Devices/14 org.freedesktop.NetworkManager.Device.Driver
          ath9k





          share|improve this answer

























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1124641%2fhow-to-check-whether-module-is-loaded-with-custom-configurations%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









            2














            Apparently such information is contained within /sys filesystem. According to Gilles's answer on the relevant post, in order to find the driver in use by interface you would execute



            readlink /sys/class/net/wlan0/device/driver


            which would provide the relative path as in



            ../../../../bus/pci/drivers/ath5k


            In my case due to systemd and predictive interface naming, the interface is named differently and produces



            $  readlink /sys/class/net/wlp2s0/device/driver
            ../../../../bus/pci/drivers/ath9k


            The resulting directory path contains subdirectories module/parameters/ where there will be files for each parameter containing their current value. Thus, if I edit the /etc/modprobe/ath9k.conf file and reinsert the module, the result is as follows:



            # After editing the conf file to set parameter to 1
            $ sudo sh -c 'modprobe -r ath9k ; sleep 3; modprobe ath9k'
            $ sudo cat /sys/class/net/wlp2s0/device/driver/../../../../bus/pci/drivers/ath9k/module/parameters/ps_enable
            1
            # after editing the file and setting parameter to 0
            $ sudo sh -c 'modprobe -r ath9k ; sleep 3; modprobe ath9k'
            $ sudo cat /sys/class/net/wlp2s0/device/driver/../../../../bus/pci/drivers/ath9k/module/parameters/ps_enable
            0


            The command can be combined as well.



            $ cat  "$(readlink -f /sys/class/net/wlp2s0/device/driver/)"/module/parameters/ps_enable
            0


            If you do have desktop environment and dbus running, as well as qdbus or dbus-send installed, such information can be queried via Network Manager's dbus interface ( though it requires figuring out the object path of each individual device, and probably would be better written in Python or C )



            $ qdbus --system org.freedesktop.NetworkManager /org/freedesktop/NetworkManager/Devices/14 org.freedesktop.NetworkManager.Device.Driver
            ath9k





            share|improve this answer






























              2














              Apparently such information is contained within /sys filesystem. According to Gilles's answer on the relevant post, in order to find the driver in use by interface you would execute



              readlink /sys/class/net/wlan0/device/driver


              which would provide the relative path as in



              ../../../../bus/pci/drivers/ath5k


              In my case due to systemd and predictive interface naming, the interface is named differently and produces



              $  readlink /sys/class/net/wlp2s0/device/driver
              ../../../../bus/pci/drivers/ath9k


              The resulting directory path contains subdirectories module/parameters/ where there will be files for each parameter containing their current value. Thus, if I edit the /etc/modprobe/ath9k.conf file and reinsert the module, the result is as follows:



              # After editing the conf file to set parameter to 1
              $ sudo sh -c 'modprobe -r ath9k ; sleep 3; modprobe ath9k'
              $ sudo cat /sys/class/net/wlp2s0/device/driver/../../../../bus/pci/drivers/ath9k/module/parameters/ps_enable
              1
              # after editing the file and setting parameter to 0
              $ sudo sh -c 'modprobe -r ath9k ; sleep 3; modprobe ath9k'
              $ sudo cat /sys/class/net/wlp2s0/device/driver/../../../../bus/pci/drivers/ath9k/module/parameters/ps_enable
              0


              The command can be combined as well.



              $ cat  "$(readlink -f /sys/class/net/wlp2s0/device/driver/)"/module/parameters/ps_enable
              0


              If you do have desktop environment and dbus running, as well as qdbus or dbus-send installed, such information can be queried via Network Manager's dbus interface ( though it requires figuring out the object path of each individual device, and probably would be better written in Python or C )



              $ qdbus --system org.freedesktop.NetworkManager /org/freedesktop/NetworkManager/Devices/14 org.freedesktop.NetworkManager.Device.Driver
              ath9k





              share|improve this answer




























                2












                2








                2







                Apparently such information is contained within /sys filesystem. According to Gilles's answer on the relevant post, in order to find the driver in use by interface you would execute



                readlink /sys/class/net/wlan0/device/driver


                which would provide the relative path as in



                ../../../../bus/pci/drivers/ath5k


                In my case due to systemd and predictive interface naming, the interface is named differently and produces



                $  readlink /sys/class/net/wlp2s0/device/driver
                ../../../../bus/pci/drivers/ath9k


                The resulting directory path contains subdirectories module/parameters/ where there will be files for each parameter containing their current value. Thus, if I edit the /etc/modprobe/ath9k.conf file and reinsert the module, the result is as follows:



                # After editing the conf file to set parameter to 1
                $ sudo sh -c 'modprobe -r ath9k ; sleep 3; modprobe ath9k'
                $ sudo cat /sys/class/net/wlp2s0/device/driver/../../../../bus/pci/drivers/ath9k/module/parameters/ps_enable
                1
                # after editing the file and setting parameter to 0
                $ sudo sh -c 'modprobe -r ath9k ; sleep 3; modprobe ath9k'
                $ sudo cat /sys/class/net/wlp2s0/device/driver/../../../../bus/pci/drivers/ath9k/module/parameters/ps_enable
                0


                The command can be combined as well.



                $ cat  "$(readlink -f /sys/class/net/wlp2s0/device/driver/)"/module/parameters/ps_enable
                0


                If you do have desktop environment and dbus running, as well as qdbus or dbus-send installed, such information can be queried via Network Manager's dbus interface ( though it requires figuring out the object path of each individual device, and probably would be better written in Python or C )



                $ qdbus --system org.freedesktop.NetworkManager /org/freedesktop/NetworkManager/Devices/14 org.freedesktop.NetworkManager.Device.Driver
                ath9k





                share|improve this answer















                Apparently such information is contained within /sys filesystem. According to Gilles's answer on the relevant post, in order to find the driver in use by interface you would execute



                readlink /sys/class/net/wlan0/device/driver


                which would provide the relative path as in



                ../../../../bus/pci/drivers/ath5k


                In my case due to systemd and predictive interface naming, the interface is named differently and produces



                $  readlink /sys/class/net/wlp2s0/device/driver
                ../../../../bus/pci/drivers/ath9k


                The resulting directory path contains subdirectories module/parameters/ where there will be files for each parameter containing their current value. Thus, if I edit the /etc/modprobe/ath9k.conf file and reinsert the module, the result is as follows:



                # After editing the conf file to set parameter to 1
                $ sudo sh -c 'modprobe -r ath9k ; sleep 3; modprobe ath9k'
                $ sudo cat /sys/class/net/wlp2s0/device/driver/../../../../bus/pci/drivers/ath9k/module/parameters/ps_enable
                1
                # after editing the file and setting parameter to 0
                $ sudo sh -c 'modprobe -r ath9k ; sleep 3; modprobe ath9k'
                $ sudo cat /sys/class/net/wlp2s0/device/driver/../../../../bus/pci/drivers/ath9k/module/parameters/ps_enable
                0


                The command can be combined as well.



                $ cat  "$(readlink -f /sys/class/net/wlp2s0/device/driver/)"/module/parameters/ps_enable
                0


                If you do have desktop environment and dbus running, as well as qdbus or dbus-send installed, such information can be queried via Network Manager's dbus interface ( though it requires figuring out the object path of each individual device, and probably would be better written in Python or C )



                $ qdbus --system org.freedesktop.NetworkManager /org/freedesktop/NetworkManager/Devices/14 org.freedesktop.NetworkManager.Device.Driver
                ath9k






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 2 hours ago

























                answered 3 hours ago









                Sergiy KolodyazhnyySergiy Kolodyazhnyy

                73.9k9154323




                73.9k9154323






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • 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%2faskubuntu.com%2fquestions%2f1124641%2fhow-to-check-whether-module-is-loaded-with-custom-configurations%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

                    VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

                    Couldn't open a raw socket. Error: Permission denied (13) (nmap)Is it possible to run networking commands...

                    Why not use the yoke to control yaw, as well as pitch and roll? Announcing the arrival of...