4

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?

Jan
  • 7,772
  • 2
  • 35
  • 41
  • 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 06 '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 06 '17 at 11:35

1 Answers1

1

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.

number9
  • 1,064
  • No result, not with lspci -nk, too. – Jan Jan 05 '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 05 '17 at 21:48
  • lspci only shows Intel devices and a Realtek one (SD card reader). – Jan Jan 05 '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 05 '17 at 22:16
  • My bet is that the module is loaded but not needed at all... – Jan Jan 05 '17 at 22:22
  • I also have this module loaded. I think it is being loaded because it's alias is being associate with other hardware that you actually have. – giusti Jan 05 '17 at 22:59
  • That would be acpi*:PNP0C02:*... – Jan Jan 05 '17 at 23:39
  • 2
    There are more busses than just PCI, and other kernel subsystems that won't list modules in lspci. Try lsusb, lshw, lsmod for example. –  Jan 07 '17 at 08:43