From: Hal F. <hal...@gm...> - 2008-08-04 00:32:55
|
Hi Ram - No, it looks like it is the TPM chip that is wrong, it is returning bad data. Even though the other TPM functions work OK, that does not mean that this one does. I was going to suggest some workarounds that might get Trousers to use TPM_CertifyKey2 instead of TPM_CertifyKey, or at least to have the TPM chip use TPM_CERTIFY_INFO2 instead of TPM_CERTIFY_INFO, but it looks like Trousers does not support either of those right now. http://trousers.sourceforge.net/trousers12support.html claims to support Tcsip_CertifyKey2, but actually I do not see it in the Trousers CVS source code, or any related functions. It's possible that it is just your TPM which is at fault - maybe you could persuade Dell to exchange your motherboard, then you would have a new TPM and it might work better. I don't have that model so I can't test to see if the problem happens with all Broadcom TPMs. I would hope that Broadcom would have tested this kind of functions so hopefully it is not a design problem that would be common across many chips. Hal On Sun, Aug 3, 2008 at 2:48 AM, Ram Krishnan <pro...@ya...> wrote: > Hi Hal - Tough luck :-( I cleared the TPM like you suggested and the error > persists. I believe it is not a hardware problem because all the other > functionalities seem to work fine. For example, TPM_QUOTE which is does a > similar operation works! Could it be the driver that came with Kernel > 2.6.25.4-10.fc8? > > --Ram |