[clug] Intel Active Management Technology

Scott Ferguson scott.ferguson.clug at gmail.com
Mon May 15 14:07:06 UTC 2017



On 15/05/17 22:51, Bryan Kilgallin (iiNet) via linux wrote:
> I tried again in bash shell.
> 
> {
> make "CC := $(CROSS_COMPILE)gcc
>>
>> PROGS := mei-amt-check
>>
>> all: $(PROGS)
>>
>> clean:
>> rm -fr $(PROGS)"
> }
> 
> Resulting in the following quoted error report.
> "CROSS_COMPILE: command not found
> PROGS: command not found
> PROGS: command not found
> make: *** No targets specified and no makefile found. Stop."


'make' means (shorthand) "build package from source"
which can mean - build a package from source, and install... (make, make
install) or, build a debian package from source (make a debian package,
install a debian package). The former requires the packages covered by
"build-essential" (meta package for package building software), the
latter, "build-essential and checkinstall".

checkinstall builds a (very) basic debian package, and allows
installing/deinstalling using the Debian package management system
(dpkg). Note that Ubuntu uses the Debian package management system.

First run the command "sudo apt-get install build-essential"

Then read these:-
Refs:http://www.tldp.org/HOWTO/Software-Building-HOWTO-3.html
https://wiki.ubuntu.com/ubuntu-make
https://askubuntu.com/questions/161104/how-do-i-install-make
https://help.ubuntu.com/community/CheckInstall
http://www.linuxjournal.com/content/using-checkinstall-build-packages-source

To find out if a package/file is included in $Something:-
install "apt-file":-
sudo apt-get -y install apt-file

Then update the apt-file datebase:-
sudo apt-file update (updates database with full list of files and paths
used by installable packages in your repositories)

You can then use apt-file to search for files that are part of a package...
e.g. sudo apt-file search mei|grep -i amt|grep
'kernel\|image\|source\|header'
which yields... nothing.
But.. apt-file search mei|grep ".ko$"
linux-image-4.9.0-2-amd64:
/lib/modules/4.9.0-2-amd64/kernel/drivers/media/rc/keymaps/rc-gadmei-rm008z.ko
linux-image-4.9.0-2-amd64:
/lib/modules/4.9.0-2-amd64/kernel/drivers/misc/mei/mei-me.ko
linux-image-4.9.0-2-amd64:
/lib/modules/4.9.0-2-amd64/kernel/drivers/misc/mei/mei.ko
linux-image-4.9.0-2-amd64:
/lib/modules/4.9.0-2-amd64/kernel/drivers/nfc/mei_phy.ko
linux-image-4.9.0-2-amd64:
/lib/modules/4.9.0-2-amd64/kernel/drivers/nfc/pn544/pn544_mei.ko
linux-image-4.9.0-2-amd64-unsigned:
/lib/modules/4.9.0-2-amd64/kernel/drivers/media/rc/keymaps/rc-gadmei-rm008z.ko
linux-image-4.9.0-2-amd64-unsigned:
/lib/modules/4.9.0-2-amd64/kernel/drivers/misc/mei/mei-me.ko
linux-image-4.9.0-2-amd64-unsigned:
/lib/modules/4.9.0-2-amd64/kernel/drivers/misc/mei/mei.ko
linux-image-4.9.0-2-amd64-unsigned:
/lib/modules/4.9.0-2-amd64/kernel/drivers/nfc/mei_phy.ko
linux-image-4.9.0-2-amd64-unsigned:
/lib/modules/4.9.0-2-amd64/kernel/drivers/nfc/pn544/pn544_mei.ko
linux-image-4.9.0-2-rt-amd64:
/lib/modules/4.9.0-2-rt-amd64/kernel/drivers/media/rc/keymaps/rc-gadmei-rm008z.ko
linux-image-4.9.0-2-rt-amd64:
/lib/modules/4.9.0-2-rt-amd64/kernel/drivers/misc/mei/mei-me.ko
linux-image-4.9.0-2-rt-amd64:
/lib/modules/4.9.0-2-rt-amd64/kernel/drivers/misc/mei/mei.ko
linux-image-4.9.0-2-rt-amd64:
/lib/modules/4.9.0-2-rt-amd64/kernel/drivers/nfc/mei_phy.ko
linux-image-4.9.0-2-rt-amd64:
/lib/modules/4.9.0-2-rt-amd64/kernel/drivers/nfc/pn544/pn544_mei.ko
linux-image-4.9.0-2-rt-amd64-unsigned:
/lib/modules/4.9.0-2-rt-amd64/kernel/drivers/media/rc/keymaps/rc-gadmei-rm008z.ko
linux-image-4.9.0-2-rt-amd64-unsigned:
/lib/modules/4.9.0-2-rt-amd64/kernel/drivers/misc/mei/mei-me.ko
linux-image-4.9.0-2-rt-amd64-unsigned:
/lib/modules/4.9.0-2-rt-amd64/kernel/drivers/misc/mei/mei.ko
linux-image-4.9.0-2-rt-amd64-unsigned:
/lib/modules/4.9.0-2-rt-amd64/kernel/drivers/nfc/mei_phy.ko
linux-image-4.9.0-2-rt-amd64-unsigned:
/lib/modules/4.9.0-2-rt-amd64/kernel/drivers/nfc/pn544/pn544_mei.ko

Conclusion:- in my case, the kernel modules exists, I'd just need to
load it (if I hadn't already killed Intel Management long ago).


tl;dr?
If the instructions say:- "make, config, make install", install your
"build essential" (gcc, kernel source, kernel headers),
"make" the software, configure the software, then use "checkinstall" to
build a basic debian package, then install the debian package (see the
quoted references or this mailing list for hints).

make, config, make install is for "any" Linux distribution.
make, config, checkinstall is the variation to be used for any
distribution based on Debian.


Kind regards

-- 
    A: Because we read from top to bottom, left to right.
    Q: Why should I start my reply below the quoted text?

    A: Because it messes up the order in which people normally read text.
    Q: Why is top-posting such a bad thing?

    A: The lost context.
    Q: What makes top-posted replies harder to read than bottom-posted?

    A: Yes.
    Q: Should I trim down the quoted part of an email to which I'm reply

http://www.idallen.com/topposting.html



More information about the linux mailing list