Hi folks, I have a yocto-built system running on a Kontron (arch is i686). I explicitly instructed the yocto to bring in tpm-tools and TrouSerS. And I know they are installed. I set my BIOS to clear the tpm, brought up the system again, and noticed /sys/class/misc/tpm0/device/pubek is empty. That was to be expected. Next I enabled the TPM in bios and reset the Kontron. After the power came up I noticed pubek was not empty. Moreover, I could do the tpm_version but my tpm_takeownership failed.
I did a lot of looking through search engines and saw earlier this year in February someone suggested to rebuild TrouSerS with debug and see what is happening. That rebuild seemed to work for him. But in my case I am wondering if a previous private key was installed in Kontron's TPM chip, which would make the tpm_takeonership useless? Here's what I got... root@crownbay-noemgd:~# tpm_takeownership -l debug Tspi_Context_Create success Enter owner password: Confirm password: Enter SRK password: Confirm password: Tspi_Context_Connect success Tspi_Context_GetTpmObject success Tspi_GetPolicyObject success Tspi_Policy_SetSecret success Tspi_Context_CreateObject success Tspi_GetPolicyObject success Tspi_Policy_SetSecret success Tspi_TPM_TakeOwnership failed: 0x00002004 - layer=tcs, code=0004 (4), Internal software error Tspi_Context_CloseObject success Tspi_Context_FreeMemory success Tspi_Context_Close success thanks in advance Bill Martin ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ TrouSerS-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/trousers-users
