WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: mei and mei_me modules in TCore.  (Read 796 times)

Offline madmax

  • WikiUser
  • *
  • Posts: 44
mei and mei_me modules in TCore.
« on: October 20, 2018, 03:47:54 AM »

While checking out the list of loaded modules, I came across something that caught my eye: mei and mei_me modules in that list.
This is  the Intel(R) Management Engine Interface.

I have IME turned off in BIOS (yes, I know ... )

But ...
Why is it being loaded?
What is its purpose in TCore?

Thanks in advance.


Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6830
Re: mei and mei_me modules in TCore.
« Reply #1 on: October 20, 2018, 07:41:16 AM »
Hi madmax
In this document:
it states:
Intel(R) Management Engine Interface (Intel(R) MEI)


The Intel Management Engine (Intel ME) is an isolated and protected computing
resource (Co-processor) residing inside certain Intel chipsets. The Intel ME
provides support for computer/IT management features. The feature set
depends on the Intel chipset SKU.
The kernel is probably detecting one of those Intel chipsets and loading those modules as a result.

Running modinfo:
Code: [Select]
tc@box:~$ modinfo mei_me
filename:       /lib/modules/4.14.10-tinycore/kernel/drivers/misc/mei/mei-me.ko.gz
author:         Intel Corporation
description:    Intel(R) Management Engine Interface
license:        GPL v2
alias:          pci:v00008086d0000A2BBsv*sd*bc*sc*i*
alias:          pci:v00008086d0000A2BAsv*sd*bc*sc*i*
alias:          pci:v00008086d0000319Asv*sd*bc*sc*i*
alias:          pci:v00008086d00005A9Asv*sd*bc*sc*i*
alias:          pci:v00008086d00001A9Asv*sd*bc*sc*i*
alias:          pci:v00008086d0000A1BAsv*sd*bc*sc*i*
alias:          pci:v00008086d0000A13Bsv*sd*bc*sc*i*
alias:          pci:v00008086d0000A13Asv*sd*bc*sc*i*
alias:          pci:v00008086d00009D3Bsv*sd*bc*sc*i*
alias:          pci:v00008086d00009D3Asv*sd*bc*sc*i*
alias:          pci:v00008086d00009CBBsv*sd*bc*sc*i*
alias:          pci:v00008086d00009CBAsv*sd*bc*sc*i*
alias:          pci:v00008086d00008CBAsv*sd*bc*sc*i*
alias:          pci:v00008086d00009C3Asv*sd*bc*sc*i*
alias:          pci:v00008086d00008D3Asv*sd*bc*sc*i*
alias:          pci:v00008086d00008C3Asv*sd*bc*sc*i*
alias:          pci:v00008086d00001DBAsv*sd*bc*sc*i*
alias:          pci:v00008086d00001CBAsv*sd*bc*sc*i*
alias:          pci:v00008086d00001E3Asv*sd*bc*sc*i*
alias:          pci:v00008086d00001D3Asv*sd*bc*sc*i*
alias:          pci:v00008086d00001C3Asv*sd*bc*sc*i*
alias:          pci:v00008086d00003B65sv*sd*bc*sc*i*
alias:          pci:v00008086d00003B64sv*sd*bc*sc*i*
alias:          pci:v00008086d00002E34sv*sd*bc*sc*i*
alias:          pci:v00008086d00002E24sv*sd*bc*sc*i*
alias:          pci:v00008086d00002E14sv*sd*bc*sc*i*
alias:          pci:v00008086d00002E04sv*sd*bc*sc*i*
alias:          pci:v00008086d00002A74sv*sd*bc*sc*i*
alias:          pci:v00008086d00002A64sv*sd*bc*sc*i*
alias:          pci:v00008086d00002A54sv*sd*bc*sc*i*
alias:          pci:v00008086d00002A44sv*sd*bc*sc*i*
alias:          pci:v00008086d000028F4sv*sd*bc*sc*i*
alias:          pci:v00008086d000028E4sv*sd*bc*sc*i*
alias:          pci:v00008086d000028D4sv*sd*bc*sc*i*
alias:          pci:v00008086d000028C4sv*sd*bc*sc*i*
alias:          pci:v00008086d000028B4sv*sd*bc*sc*i*
alias:          pci:v00008086d000029F4sv*sd*bc*sc*i*
alias:          pci:v00008086d000029E4sv*sd*bc*sc*i*
alias:          pci:v00008086d000029D4sv*sd*bc*sc*i*
alias:          pci:v00008086d000029C4sv*sd*bc*sc*i*
alias:          pci:v00008086d000029B4sv*sd*bc*sc*i*
alias:          pci:v00008086d00002A14sv*sd*bc*sc*i*
alias:          pci:v00008086d00002A04sv*sd*bc*sc*i*
alias:          pci:v00008086d000029A4sv*sd*bc*sc*i*
alias:          pci:v00008086d00002994sv*sd*bc*sc*i*
alias:          pci:v00008086d00002984sv*sd*bc*sc*i*
alias:          pci:v00008086d00002974sv*sd*bc*sc*i*
depends:        mei
intree:         Y
vermagic:       4.14.10-tinycore SMP mod_unload 486
shows that  mei  is a dependency of  mei_me.

If you check:
it states:
module_blacklist=  [KNL] Do not load a comma-separated list of
      modules.  Useful for debugging problem modules.

So adding the following boot code should block them both from loading:
Code: [Select]

Offline madmax

  • WikiUser
  • *
  • Posts: 44
Re: mei and mei_me modules in TCore.
« Reply #2 on: October 21, 2018, 02:52:38 PM »
Thanks for taking the time to write back.

I was wondering why TCore was loading it and a while after I posted I realised that it was the kernel that loads it and it is not a distro packaging option, so to speak.   

If you check ...
So adding the following boot code should ...
Thanks for the know-how.  =-)