Comment 104 for bug 1283589

Revision history for this message
In , w.and.gvb (w.and.gvb-linux-kernel-bugs) wrote :

(In reply to Sebastian Riemer from comment #74)
> @Jan: No wonder, it is the same chipset, the "Intel HM76". Have you
> installed the HECI driver from Samsung to your Windows?
> After installing it, it should work if the doc from Intel is correct that
> the embedded controller and therefore lid, power and battery are controlled
> via HECI/MEI instead of SMBus.
>
> Can you check your Linux kernel >= 3.5 config for CONFIG_INTEL_MEI and
> CONFIG_INTEL_MEI_ME please?
>
> Locations:
> -> Device Drivers -> Misc devices -> Intel Management Engine Interface
> -> Device Drivers -> Misc devices -> ME Enabled Intel Chipsets
>
> You should have a /dev/mei device then. The other driver provides MEI
> support for the following Intel chipsets:
>
> 7 Series Chipset Family
> 6 Series Chipset Family
> 5 Series Chipset Family
> 4 Series Chipset Family
> Mobile 4 Series Chipset Family
> ICH9
> 82946GZ/GL
> 82G35 Express
> 82Q963/Q965
> 82P965/G965
> Mobile PM965/GM965
> Mobile GME965/GLE960
> 82Q35 Express
> 82G33/G31/P35/P31 Express
> 82Q33 Express
> 82X38/X48 Express
>
> The HM76 belongs to the 7 Series Chipset Family.
>
> There is also kernel documentation: Documentation/misc-devices/mei/
> Sending an email to <email address hidden> could also help.
>
> Intel AMT (Active Management Technology) is required in the user-space it
> seems:
>
> http://software.intel.com/en-us/blogs/2009/08/21/working-with-intel-amt-and-
> linux
>
> There are "Power Packages" and the LMS (Local Manageability Service).
> OpenAMT seems to be legacy.
>
> This is the place for latest Open Source Intel AMT downloads:
> http://software.intel.com/en-us/articles/download-the-latest-intel-amt-open-
> source-drivers
> http://software.intel.com/en-us/articles/intel-active-management-technology-
> start-here-guide-intel-amt-9
>
> Please check that out if you get it working with that!

I've followed your tips and compiled INTEL_MEI into the kernel. The lid event has been working properly ever since. For me the issue seems solved, but I can only speak for myself.