How to check whether module is loaded with custom configurations?
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
add a comment |
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
add a comment |
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
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
networking drivers configuration system
edited 3 hours ago
Sergiy Kolodyazhnyy
asked 3 hours ago
Sergiy KolodyazhnyySergiy Kolodyazhnyy
73.9k9154323
73.9k9154323
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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
add a comment |
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
});
}
});
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%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
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
add a comment |
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
add a comment |
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
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
edited 3 hours ago
answered 3 hours ago
Sergiy KolodyazhnyySergiy Kolodyazhnyy
73.9k9154323
73.9k9154323
add a comment |
add a comment |
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.
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%2f1124641%2fhow-to-check-whether-module-is-loaded-with-custom-configurations%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