Find out why linux kernel module was loaded
Multi tool use
The debian backports 4.8 standard kernel loads the module fjes
on my thinkpad T460s.
How can I find out why this module is loaded, i.e. which hardware triggers loading this module?
linux-kernel kernel-modules
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
The debian backports 4.8 standard kernel loads the module fjes
on my thinkpad T460s.
How can I find out why this module is loaded, i.e. which hardware triggers loading this module?
linux-kernel kernel-modules
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Kernel will detect new hardware and load this module on the boot. When kernel didnt enable this module.Kernel didnt load this module. Even kernel detected new hardware on the boot.
– supriady
Jan 6 '17 at 11:24
Actually you can run # lsmod to check all modules loaded. And you can check fjes module info with # modinfo fjes.ko.If I am not mistaken.Another users also post the question about fjes module.It called Fujitsu device.
– supriady
Jan 6 '17 at 11:35
add a comment |
The debian backports 4.8 standard kernel loads the module fjes
on my thinkpad T460s.
How can I find out why this module is loaded, i.e. which hardware triggers loading this module?
linux-kernel kernel-modules
The debian backports 4.8 standard kernel loads the module fjes
on my thinkpad T460s.
How can I find out why this module is loaded, i.e. which hardware triggers loading this module?
linux-kernel kernel-modules
linux-kernel kernel-modules
asked Jan 5 '17 at 21:01
JanJan
5,3491828
5,3491828
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Kernel will detect new hardware and load this module on the boot. When kernel didnt enable this module.Kernel didnt load this module. Even kernel detected new hardware on the boot.
– supriady
Jan 6 '17 at 11:24
Actually you can run # lsmod to check all modules loaded. And you can check fjes module info with # modinfo fjes.ko.If I am not mistaken.Another users also post the question about fjes module.It called Fujitsu device.
– supriady
Jan 6 '17 at 11:35
add a comment |
Kernel will detect new hardware and load this module on the boot. When kernel didnt enable this module.Kernel didnt load this module. Even kernel detected new hardware on the boot.
– supriady
Jan 6 '17 at 11:24
Actually you can run # lsmod to check all modules loaded. And you can check fjes module info with # modinfo fjes.ko.If I am not mistaken.Another users also post the question about fjes module.It called Fujitsu device.
– supriady
Jan 6 '17 at 11:35
Kernel will detect new hardware and load this module on the boot. When kernel didnt enable this module.Kernel didnt load this module. Even kernel detected new hardware on the boot.
– supriady
Jan 6 '17 at 11:24
Kernel will detect new hardware and load this module on the boot. When kernel didnt enable this module.Kernel didnt load this module. Even kernel detected new hardware on the boot.
– supriady
Jan 6 '17 at 11:24
Actually you can run # lsmod to check all modules loaded. And you can check fjes module info with # modinfo fjes.ko.If I am not mistaken.Another users also post the question about fjes module.It called Fujitsu device.
– supriady
Jan 6 '17 at 11:35
Actually you can run # lsmod to check all modules loaded. And you can check fjes module info with # modinfo fjes.ko.If I am not mistaken.Another users also post the question about fjes module.It called Fujitsu device.
– supriady
Jan 6 '17 at 11:35
add a comment |
1 Answer
1
active
oldest
votes
You can use lspci -v. You will need to grep (probably with -i to ignore case) for your module shown in lsmod. e.g. to find r8169:
lspci -v |grep -i -A 4 -B 4 r8169
You can change the number of lines before and after (A, B) to your liking/needs.
I found another user had the same question. There is a script here to find out.
No result, not withlspci -nk
, too.
– Jan
Jan 5 '17 at 21:41
Check with lspci -v by itself. Question: is fjes showing up in lsmod? I think fjes is a Fujitsu Extended Network Device Driver. Did you check your ethernets/wifis/networks in the lspci output?
– number9
Jan 5 '17 at 21:48
lspci
only shows Intel devices and a Realtek one (SD card reader).
– Jan
Jan 5 '17 at 21:54
That's... pretty odd. Got on my debian machine, lspci shows everything. Are you doing this as root/elevated privileges? I will admit, I am not on a laptop, and do not have your kernel installed (I bet). I think the script on the link I posted could be modified to search all directories in /sys/class and print them. That may or may not help your cause.
– number9
Jan 5 '17 at 22:16
My bet is that the module is loaded but not needed at all...
– Jan
Jan 5 '17 at 22:22
|
show 3 more comments
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
});
}
});
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%2funix.stackexchange.com%2fquestions%2f335196%2ffind-out-why-linux-kernel-module-was-loaded%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
You can use lspci -v. You will need to grep (probably with -i to ignore case) for your module shown in lsmod. e.g. to find r8169:
lspci -v |grep -i -A 4 -B 4 r8169
You can change the number of lines before and after (A, B) to your liking/needs.
I found another user had the same question. There is a script here to find out.
No result, not withlspci -nk
, too.
– Jan
Jan 5 '17 at 21:41
Check with lspci -v by itself. Question: is fjes showing up in lsmod? I think fjes is a Fujitsu Extended Network Device Driver. Did you check your ethernets/wifis/networks in the lspci output?
– number9
Jan 5 '17 at 21:48
lspci
only shows Intel devices and a Realtek one (SD card reader).
– Jan
Jan 5 '17 at 21:54
That's... pretty odd. Got on my debian machine, lspci shows everything. Are you doing this as root/elevated privileges? I will admit, I am not on a laptop, and do not have your kernel installed (I bet). I think the script on the link I posted could be modified to search all directories in /sys/class and print them. That may or may not help your cause.
– number9
Jan 5 '17 at 22:16
My bet is that the module is loaded but not needed at all...
– Jan
Jan 5 '17 at 22:22
|
show 3 more comments
You can use lspci -v. You will need to grep (probably with -i to ignore case) for your module shown in lsmod. e.g. to find r8169:
lspci -v |grep -i -A 4 -B 4 r8169
You can change the number of lines before and after (A, B) to your liking/needs.
I found another user had the same question. There is a script here to find out.
No result, not withlspci -nk
, too.
– Jan
Jan 5 '17 at 21:41
Check with lspci -v by itself. Question: is fjes showing up in lsmod? I think fjes is a Fujitsu Extended Network Device Driver. Did you check your ethernets/wifis/networks in the lspci output?
– number9
Jan 5 '17 at 21:48
lspci
only shows Intel devices and a Realtek one (SD card reader).
– Jan
Jan 5 '17 at 21:54
That's... pretty odd. Got on my debian machine, lspci shows everything. Are you doing this as root/elevated privileges? I will admit, I am not on a laptop, and do not have your kernel installed (I bet). I think the script on the link I posted could be modified to search all directories in /sys/class and print them. That may or may not help your cause.
– number9
Jan 5 '17 at 22:16
My bet is that the module is loaded but not needed at all...
– Jan
Jan 5 '17 at 22:22
|
show 3 more comments
You can use lspci -v. You will need to grep (probably with -i to ignore case) for your module shown in lsmod. e.g. to find r8169:
lspci -v |grep -i -A 4 -B 4 r8169
You can change the number of lines before and after (A, B) to your liking/needs.
I found another user had the same question. There is a script here to find out.
You can use lspci -v. You will need to grep (probably with -i to ignore case) for your module shown in lsmod. e.g. to find r8169:
lspci -v |grep -i -A 4 -B 4 r8169
You can change the number of lines before and after (A, B) to your liking/needs.
I found another user had the same question. There is a script here to find out.
edited Apr 13 '17 at 12:36
Community♦
1
1
answered Jan 5 '17 at 21:10
number9number9
55026
55026
No result, not withlspci -nk
, too.
– Jan
Jan 5 '17 at 21:41
Check with lspci -v by itself. Question: is fjes showing up in lsmod? I think fjes is a Fujitsu Extended Network Device Driver. Did you check your ethernets/wifis/networks in the lspci output?
– number9
Jan 5 '17 at 21:48
lspci
only shows Intel devices and a Realtek one (SD card reader).
– Jan
Jan 5 '17 at 21:54
That's... pretty odd. Got on my debian machine, lspci shows everything. Are you doing this as root/elevated privileges? I will admit, I am not on a laptop, and do not have your kernel installed (I bet). I think the script on the link I posted could be modified to search all directories in /sys/class and print them. That may or may not help your cause.
– number9
Jan 5 '17 at 22:16
My bet is that the module is loaded but not needed at all...
– Jan
Jan 5 '17 at 22:22
|
show 3 more comments
No result, not withlspci -nk
, too.
– Jan
Jan 5 '17 at 21:41
Check with lspci -v by itself. Question: is fjes showing up in lsmod? I think fjes is a Fujitsu Extended Network Device Driver. Did you check your ethernets/wifis/networks in the lspci output?
– number9
Jan 5 '17 at 21:48
lspci
only shows Intel devices and a Realtek one (SD card reader).
– Jan
Jan 5 '17 at 21:54
That's... pretty odd. Got on my debian machine, lspci shows everything. Are you doing this as root/elevated privileges? I will admit, I am not on a laptop, and do not have your kernel installed (I bet). I think the script on the link I posted could be modified to search all directories in /sys/class and print them. That may or may not help your cause.
– number9
Jan 5 '17 at 22:16
My bet is that the module is loaded but not needed at all...
– Jan
Jan 5 '17 at 22:22
No result, not with
lspci -nk
, too.– Jan
Jan 5 '17 at 21:41
No result, not with
lspci -nk
, too.– Jan
Jan 5 '17 at 21:41
Check with lspci -v by itself. Question: is fjes showing up in lsmod? I think fjes is a Fujitsu Extended Network Device Driver. Did you check your ethernets/wifis/networks in the lspci output?
– number9
Jan 5 '17 at 21:48
Check with lspci -v by itself. Question: is fjes showing up in lsmod? I think fjes is a Fujitsu Extended Network Device Driver. Did you check your ethernets/wifis/networks in the lspci output?
– number9
Jan 5 '17 at 21:48
lspci
only shows Intel devices and a Realtek one (SD card reader).– Jan
Jan 5 '17 at 21:54
lspci
only shows Intel devices and a Realtek one (SD card reader).– Jan
Jan 5 '17 at 21:54
That's... pretty odd. Got on my debian machine, lspci shows everything. Are you doing this as root/elevated privileges? I will admit, I am not on a laptop, and do not have your kernel installed (I bet). I think the script on the link I posted could be modified to search all directories in /sys/class and print them. That may or may not help your cause.
– number9
Jan 5 '17 at 22:16
That's... pretty odd. Got on my debian machine, lspci shows everything. Are you doing this as root/elevated privileges? I will admit, I am not on a laptop, and do not have your kernel installed (I bet). I think the script on the link I posted could be modified to search all directories in /sys/class and print them. That may or may not help your cause.
– number9
Jan 5 '17 at 22:16
My bet is that the module is loaded but not needed at all...
– Jan
Jan 5 '17 at 22:22
My bet is that the module is loaded but not needed at all...
– Jan
Jan 5 '17 at 22:22
|
show 3 more comments
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.
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%2funix.stackexchange.com%2fquestions%2f335196%2ffind-out-why-linux-kernel-module-was-loaded%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
E,y7cO7P,FOxlAUEw 7Lz,4kvl6Kw,dc pNW2SuLtZkDj819ekO75ZVgYAzNIoOoHy,ikYZdimg7 5ZW
Kernel will detect new hardware and load this module on the boot. When kernel didnt enable this module.Kernel didnt load this module. Even kernel detected new hardware on the boot.
– supriady
Jan 6 '17 at 11:24
Actually you can run # lsmod to check all modules loaded. And you can check fjes module info with # modinfo fjes.ko.If I am not mistaken.Another users also post the question about fjes module.It called Fujitsu device.
– supriady
Jan 6 '17 at 11:35