topic Intel QST SDK Linux: Which drivers is needed HECI or AMT? in Intel® Business Client Software Development

Intel QST SDK Linux: Which drivers is needed HECI or AMT?

opperpanter — Fri, 24 Jun 2011 22:04:08 GMT

Hello,

I am trying to use the Intel QST SDK on my DH55TC motherboard. From Debian Squeeze.

The Intel QST SDK documentation talks about installing the heci driver from www.openamt.org.

This one is outdated, and needs some patches to get going on newer hardware. The patches are available in pdf documents, so not very smooth. See http://software.intel.com/en-us/forums/showthread.php?t=82888&o=a&s=lr

On the other side I understand that the new Intel AMT Open Source drivers contain the MEI drivers, which are basically successor of the HECI driver or a superset of HECI

drivers. These can be downloaded from http://software.intel.com/en-us/articles/download-the-latest-intel-amt-open-source-drivers/#comment-61037

This driver doesn't compile on Debian Squeeze, see http://software.intel.com/en-us/forums/showthread.php?t=83788&o=a&s=lr.

So I am kinda stuck here.

Would love to have someone shed some light on this.

Thanks!

Intel QST SDK Linux: Which drivers is needed HECI or AMT?

opperpanter — Sat, 25 Jun 2011 00:06:04 GMT

I solved my compilation problem (mentioned above), and got the AMT/MEI module loaded correctly.

The sample applications in the Intel QST SDK now run correctly.

So it seems that the HECI driver from www.openamt.org is no longer needed.

Would be good to have some official info from Intel though.

Intel QST SDK Linux: Which drivers is needed HECI or AMT?

thelexus — Tue, 19 Jul 2011 13:49:09 GMT

Hello opperpanter,

how did you solve your problem? If i run one of the example sdk programs i always get a ERRNO 19 (no such device). The mei and SDK does compile and the mei module is loaded.

I changed /dev/heci to /dev/mei in the device library sources, but this doesnt helped me.

Hopefully you can help me.

Bye

Intel QST SDK Linux: Which drivers is needed HECI or AMT?

opperpanter — Sat, 06 Aug 2011 20:53:32 GMT

I don't think you should (need to) change the device name. If I remember correctly, the QST SDK doesn't use the device by name so it wouldn't matter.

For me it just works If I add the one line to the MEI source and compile & load it.

Intel QST SDK Linux: Which drivers is needed HECI or AMT?

wehcgk — Wed, 17 Aug 2011 10:31:50 GMT

Hi,
I am having the exact same problem - ERRNO 19 (no such device).

I tried strace on the bustest program and it showed its trying to open /dev/heci. So I thought maybe I could symlink /dev/mei to /dev/heci. Now it shows

ioctl(3, HIDIOCGRDESCSIZE or HIDIOCGVERSION or SNDRV_HWDEP_IOCTL_INFO, 0x7fff63b5e290) = -1 EINVAL (Invalid argument)

Is it because the QST SDK was written to use the older HECI driver thats causing this problem?

I am not a programmer so I do not know what's the next step to take from here. Can anyone help me?

I am running Fedora 15 x86_64 on a Q35-based machine. The mei module compiles and loads fine.

Thanks.