From: "Michael Niewöhner" <linux@mniewoehner.de>
To: Mimi Zohar <zohar@linux.ibm.com>,
peterhuewe@gmx.de, jarkko.sakkinen@linux.intel.com, jgg@ziepe.ca,
arnd@arndb.de, linux-integrity@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] Nuvoton NCPT650 TPM 2.0 mode not working
Date: Sun, 11 Nov 2018 19:51:01 +0100 [thread overview]
Message-ID: <b1f403b78da6d70ae493272fd7e9fede0714cf30.camel@mniewoehner.de> (raw)
In-Reply-To: <1541961216.3734.60.camel@linux.ibm.com>
Hi Mimi,
On Sun, 2018-11-11 at 13:33 -0500, Mimi Zohar wrote:
> On Sun, 2018-11-11 at 18:55 +0100, Michael Niewöhner wrote:
> > Hi all,
> >
> > Nuvoton NCPT650 does not work in TPM 2.0 mode with tpm_tis / tpm_i2c_nuvoton
> > while it works in TPM 1.2 mode (I can reflash it via UEFI setup).
> > Kernel version is 4.19.1
> >
> > Kernel config:
> >
> > $ cat .config | egrep 'TCG|TPM|CRB|_TIS'
> > CONFIG_TCG_TPM=y
> > CONFIG_HW_RANDOM_TPM=y
> > CONFIG_TCG_TIS_CORE=y
> > CONFIG_TCG_TIS=y
> > CONFIG_TCG_TIS_SPI=y
> > # CONFIG_TCG_TIS_I2C_ATMEL is not set
> > # CONFIG_TCG_TIS_I2C_INFINEON is not set
> > CONFIG_TCG_TIS_I2C_NUVOTON=y
> > # CONFIG_TCG_NSC is not set
> > # CONFIG_TCG_ATMEL is not set
> > # CONFIG_TCG_INFINEON is not set
> > CONFIG_TCG_CRB=y
> > # CONFIG_TCG_VTPM_PROXY is not set
> > # CONFIG_TCG_TIS_ST33ZP24_I2C is not set
> > # CONFIG_TCG_TIS_ST33ZP24_SPI is not set
> >
> >
> > TPM 1.2 mode dmesg:
> >
> > $ dmesg | egrep -i tis\|tpm\|crb
> > [ 3.210040] tpm_tis 00:0a: 1.2 TPM (device-id 0xFE, rev-id 2)
> >
> >
> > TPM 2.0 mode dmesg:
> >
> > $ dmesg | egrep -i tis\|tpm\|crb
> > [ 0.000000] efi: ACPI
> > 2.0=0x9e457000 ACPI=0x9e457000 SMBIOS=0x9ec44000 SMBIOS
> > 3.0=0x9ec43000 TPMEventLog=0x9711f018
> > [ 0.003517] ACPI: TPM2 0x000000009E490ED8 000034 (v03 LENOVO TC-
> > S06 00001300 AMI 00000000)
> > [ 4.071550] ima: No TPM chip found, activating TPM-bypass!
>
> It's possible that eventually the TPM is initialized, but not in time
> for IMA. Could you you check to see if the TPM is responding to
> userspace commands after boot?
No it isn't even detected. There is no /dev/tpm0 and /sys/class/tpm is empty.
>
> Mimi
>
next prev parent reply other threads:[~2018-11-11 18:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 17:55 [BUG] Nuvoton NCPT650 TPM 2.0 mode not working Michael Niewöhner
2018-11-11 18:24 ` James Bottomley
2018-11-11 18:50 ` Michael Niewöhner
2018-11-11 18:57 ` James Bottomley
2018-11-11 20:09 ` Michael Niewöhner
2018-11-11 20:29 ` James Bottomley
2018-11-11 20:34 ` Michael Niewöhner
2018-11-11 21:11 ` Michael Niewöhner
2018-11-11 21:42 ` Mimi Zohar
2018-11-14 20:46 ` Michael Niewöhner
2018-11-16 21:06 ` Michael Niewöhner
2018-11-18 8:18 ` Jarkko Sakkinen
2018-11-18 14:10 ` Michael Niewöhner
2018-11-19 13:49 ` Jarkko Sakkinen
2018-11-25 20:06 ` Michael Niewöhner
2018-11-26 19:15 ` Michael Niewöhner
2018-11-26 21:13 ` Jarkko Sakkinen
2018-11-13 10:50 ` Jarkko Sakkinen
2019-01-11 15:40 ` Mimi Zohar
2019-01-12 9:52 ` Michael Niewöhner
2019-01-12 10:49 ` Michael Niewöhner
2018-11-11 18:33 ` Mimi Zohar
2018-11-11 18:51 ` Michael Niewöhner [this message]
2018-11-13 10:28 ` Jarkko Sakkinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b1f403b78da6d70ae493272fd7e9fede0714cf30.camel@mniewoehner.de \
--to=linux@mniewoehner.de \
--cc=arnd@arndb.de \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).