I was originally going to post "how do I enable TXT in Linux kernel
2.6.37?" but I figured it out. As the process was rather non-obvious,
I post here with hopes that this information will be useful.
Working with the vanilla linux-2.6.37.tar.bz2 from kernel.org...
Documentation/intel_txt.txt does
This patch makes the documentation slightly more explicit about how to
enable Intel TXT support in the kernel, and adds two dependencies to
the relevant option in Kconfig. Without this patch it is difficult to
determine how to enable Intel TXT support without some knowledge of
Kconfig.
Signed-off
Hi Joe et al.,
What is the thinking behind the HAVE_INTEL_TXT option? Is the
intention to disable all TXT-related code on non-x86 platforms?
Wouldn't it be cleaner to add a dependency such as CONFIG_X86 to the
CONFIG_INTEL_TXT line, instead of the pseudo-automatic HAVE_INTEL_TXT?
Thanks,
-Jon
Yes I can confirm that I was using the latest BIOS version (Latitude
E6500 System BIOS A24) and TPM firmware (Dell Control Vault 14.x.132.0,
A17). I pulled all the RAM and that didn't make a difference, according
to Dell there was no physical means of clearing the CMOS. A new
motherboard is on
I know that for the HP 8530p BIOS revision F.0B exhibits the problem,
and F.0E does not. I have not tried to disassemble / difference them.
-Jon
On Fri, Jan 21, 2011 at 3:16 PM, Jeff Cleveland wrote:
> Yes I can confirm that I was using the latest BIOS version (Latitude E6500
> System BIOS A24
The usual cause of BIOS reboot loops or boot failures is a BIOS that doesn't
correctly call the BIOS ACM to unlock memory. However, memory should only be
locked on boot if the system did an SENTER and set the secrets flag but then
didn't clear it on shutdown (or if the coin battery is removed).
On Fri, 21 Jan 2011 13:39:19 -0500 Jonathan McCune wrote:
> This patch makes the documentation slightly more explicit about how to
> enable Intel TXT support in the kernel, and adds two dependencies to
> the relevant option in Kconfig. Without this patch it is difficult to
> determine how to enab
