Ima error communicating to tpm chip

I am getting the following error message as a list of 4 or 5 lines with differing numbers at the beginning of each line during boot for a long while: ima: error communicating to tpm chip I am using

I am getting the following error message as a list of 4 or 5 lines with differing numbers at the beginning of each line during boot for a long while:

ima: error communicating to tpm chip

I am using Ubuntu 19.04 (though this error was existing for a while at the older versions) and my computer is a Toshiba Z930.

BeastOfCaerbannog's user avatar

asked Oct 3, 2019 at 8:58

alpakyuz's user avatar

It is simple: just enable TPM from the BIOS setup.

To change the BIOS settings you can hit F2 during boot before Ubuntu starts. Please be sure not to change anything else if your computer is working properly.

BeastOfCaerbannog's user avatar

answered Oct 3, 2019 at 9:04

alpakyuz's user avatar

alpakyuzalpakyuz

3771 gold badge2 silver badges7 bronze badges

5

If you couldn’t find TPM, it appears as Intel Platform Trust Technology in the Security section of the BIOS. I had to disable that setting in order to get rid of that error.

answered Mar 25, 2020 at 18:37

dilver's user avatar

dilverdilver

911 silver badge2 bronze badges

1

TPM may not be named clearly in the BIOS settings. In my BIOS, it definitely was not. The setting was initially disabled and required setting a password before it could be enabled. There was a sub-setting to allow the Operating System to make changes.

If you don’t have a configuration password, check for security settings that are disabled and can not be changed. Try setting a password and enable the configuration.

answered Jul 25, 2020 at 11:59

BillThor's user avatar

BillThorBillThor

4,55818 silver badges22 bronze badges

1

I had to boot into my motherboard Bios Setup by pressing esc to get into the Startup Menu then F10 to get into Computer setup or cut it short by pressing F10 before the OS boots up . After getting into the Bios Setup -and that primarily applies to my bios UI version and other similar ones- just

  1. Move to Security tab
  2. Navigate down to select the System Security menu option
  3. Another popup menu with the Embedded Security Device option would be most probably disabled.
  4. Escape back out of the menu then navigate up to Setup Password
  5. Set up a new password
  6. sway back to the Embedded Security Device to get it enabled.
  • Also make sure to enable all the options -or at least the one you want to enable- at the Device Security option .

Just as a side note, this error is somehow interconnected with Ata comreset failed (errno=-16). So if by any chance someone googled this otherwise different error message and landed on this page, then then this solution might resolve the issue at this particular case .

answered Feb 19, 2022 at 14:37

polendina's user avatar

polendinapolendina

851 silver badge8 bronze badges

2

For my NUC it showed up under «Devices and Peripherals > Onboard Devices > Legacy Device Configuration > Trusted Platform Module»

answered Jan 12, 2022 at 5:12

Peter's user avatar

PeterPeter

3813 silver badges7 bronze badges

Not always the BIOS gives you the options for TPM for granted. So on my Elitebook 8570P it is simply NOT possible to alter the TPM settings in any way.
Of course you do not want the messages at the startup prompt during and in between the boot-splash. So you can do the following:

  1. In a terminal run:

    sudo nano /etc/default/grub
    
  2. Navigate with the arrow keys on your keyboard to the place where it says:

    quiet splash
    

    and change it to:

    quiet loglevel=0 splash
    
  3. Save the file and run:

    sudo update-grub 
    
  4. Reboot and you will see that there are no messages anymore of the TPM error.

This tip is mostly for people who do not want to mess in the BIOS. Tested this on a HP Elitebook 8570P with Jammy Jellyfish fresh installed.

BeastOfCaerbannog's user avatar

answered May 15, 2022 at 12:11

Joris Donders's user avatar

Как правильно задавать вопросы

Правильно сформулированный вопрос и его грамотное оформление способствует высокой вероятности получения достаточно содержательного и по существу ответа. Общая рекомендация по составлению тем: 1. Для начала воспользуйтесь поиском форума. 2. Укажите версию ОС вместе с разрядностью. Пример: LM 19.3 x64, LM Sarah x32 3. DE. Если вопрос касается двух, то через запятую. (xfce, KDE, cinnamon, mate) 4. Какое железо. (достаточно вывод inxi -Fxz в спойлере (как пользоваться спойлером смотрим здесь)) или же дать ссылку на hw-probe 5. Суть. Желательно с выводом консоли, логами. 6. Скрин. Просьба указывать 2, 3 и 4 независимо от того, имеет ли это отношение к вопросу или нет. Так же не забываем об общих правилах Как пример вот

Аватара пользователя

djultra

Сообщения: 10
Зарегистрирован: 23 сен 2018, 21:22
Откуда: ДНР
Благодарил (а): 1 раз

Ima: Error Communicating to TPM chip

11 июл 2020, 08:55

Здравствуйте. Подскажите, что за ошибка при загрузке LM 20 (на 19.3 такого не было) показывает ошибку в самом начале Ima: Error Communicating to TPM chip и впереди время в 0,7329487 ms и так несколько раз например почти как на фото с интернета. Системник HP8300SFF

Вложения
wnokB.jpg


Аватара пользователя

symon2014

Сообщения: 5136
Зарегистрирован: 16 дек 2017, 21:59
Решено: 29
Откуда: Феодосия
Благодарил (а): 31 раз
Поблагодарили: 646 раз
Контактная информация:

Ima: Error Communicating to TPM chip

#2

11 июл 2020, 09:00


Аватара пользователя

djultra

Сообщения: 10
Зарегистрирован: 23 сен 2018, 21:22
Откуда: ДНР
Благодарил (а): 1 раз

Ima: Error Communicating to TPM chip

#3

11 июл 2020, 09:16

Да нет с жесткого диска, один на 500 на нем lm, второй на 250 на нем WIN7. BOOT0 так и остался ? Может из-за GRUB ? т.к после обновления он слетел, восстановил через BOOT REPAIR DISK. установил на весь диск 500 гб, а не на раздел с LINUX. Вроде правильно же


Аватара пользователя

Ара Магеддон

Сообщения: 559
Зарегистрирован: 08 дек 2018, 01:08
Решено: 18
Благодарил (а): 35 раз
Поблагодарили: 135 раз

Ima: Error Communicating to TPM chip

#4

11 июл 2020, 10:04

Ну сначала можно перейти по ссылке и выполнить то что там написано:
Зайти в БИОС и если чип TPM включён — выключить, если выключен — то включить. Должно быть где-то в разделе «Security».

(Хотя убунте раньше было пофиг на все эти ТРМ-ы. Может что поменялось)


Аватара пользователя

Ара Магеддон

Сообщения: 559
Зарегистрирован: 08 дек 2018, 01:08
Решено: 18
Благодарил (а): 35 раз
Поблагодарили: 135 раз

Ima: Error Communicating to TPM chip

#5

11 июл 2020, 12:38

UPD: Хотя чисто интуитивно… этот чип — он для очень специфических корпоративных задач, и обычным юзерам сроду не нужен был. Так что не думаю, что проблемы с доступом к нему будут прерывать загрузку. Вероятно, проблема где-то ещё, просто сообщение не падает в лог.


I can not help, but I have the same problem (well, it might not be a real problem) and I’d like to point to it: viewtopic.php?f=48&t=327629 (it’s basically a different issue, but also the TPM error occurs)

I have to similar boards (ASRock J5005-ITX and J4105-ITX, both Intel Gemini Lake), both running with upgraded Linux Mint 20 XFCE.
The J4105-ITX has a newer Beta-BIOS.

On both systems Intel PPT (Intel Platform Trust Technology) is activated. I’ve checked it right now in the BIOS and this is the only option for TPM.

On one system (J5005) everything is fine and I don’t get an error.
On the other system (J4105, newer beta BIOS) I have the error «ima: Error Communicating to TPM chip» (8 times).

It looks like this error is new, since I’ve upgraded to Mint 20 now.

Code: Select all

user1@machine1:/var/log$ ll /var/log/syslog.1
-rw-r----- 1 syslog adm 144663 Aug 11 02:29 /var/log/syslog.1
user1@machine1:/var/log$
user1@machine1:/var/log$ grep TPM /var/log/syslog.1
Aug 11 02:24:27 venice kernel: [    0.000000] ACPI: TPM2 0x000000006D5C2000 000034 (v04 ALASKA A M I    00000001 AMI  00000000)
user1@machine1:/var/log$
user1@machine1:/var/log$ grep TPM /var/log/syslog
Aug 11 04:03:24 venice kernel: [    0.000000] ACPI: TPM2 0x000000006D5C2000 000034 (v04 ALASKA A M I    00000001 AMI  00000000)
Aug 11 12:49:05 venice kernel: [    0.000000] efi:  ACPI=0x6d64d000  ACPI 2.0=0x6d64d014  TPMFinalLog=0x6d61b000  SMBIOS=0x6d8f2000  SMBIOS 3.0=0x6d8f1000  MEMATTR=0x67ae1018  ESRT=0x67b05c98  TPMEventLog=0x617af018
Aug 11 12:49:05 venice kernel: [    0.010053] ACPI: TPM2 0x000000006D5C2000 000034 (v04 ALASKA A M I    00000001 AMI  00000000)
Aug 11 12:49:05 venice kernel: [    1.011262] ima: Error Communicating to TPM chip
Aug 11 12:49:05 venice kernel: [    1.012950] ima: Error Communicating to TPM chip
Aug 11 12:49:05 venice kernel: [    1.013497] ima: Error Communicating to TPM chip
Aug 11 12:49:05 venice kernel: [    1.014042] ima: Error Communicating to TPM chip
Aug 11 12:49:05 venice kernel: [    1.014588] ima: Error Communicating to TPM chip
Aug 11 12:49:05 venice kernel: [    1.015134] ima: Error Communicating to TPM chip
Aug 11 12:49:05 venice kernel: [    1.015679] ima: Error Communicating to TPM chip
Aug 11 12:49:05 venice kernel: [    1.016225] ima: Error Communicating to TPM chip
Aug 11 12:55:04 venice kernel: [    0.000000] efi:  ACPI=0x6d64d000  ACPI 2.0=0x6d64d014  TPMFinalLog=0x6d61b000  SMBIOS=0x6d8f2000  SMBIOS 3.0=0x6d8f1000  MEMATTR=0x67ae1018  ESRT=0x67b00e18  TPMEventLog=0x617af018
Aug 11 12:55:04 venice kernel: [    0.010545] ACPI: TPM2 0x000000006D5C2000 000034 (v04 ALASKA A M I    00000001 AMI  00000000)
Aug 11 12:55:04 venice kernel: [    1.019633] ima: Error Communicating to TPM chip
Aug 11 12:55:04 venice kernel: [    1.021338] ima: Error Communicating to TPM chip
Aug 11 12:55:04 venice kernel: [    1.021885] ima: Error Communicating to TPM chip
Aug 11 12:55:04 venice kernel: [    1.022432] ima: Error Communicating to TPM chip
Aug 11 12:55:04 venice kernel: [    1.022980] ima: Error Communicating to TPM chip
Aug 11 12:55:04 venice kernel: [    1.023527] ima: Error Communicating to TPM chip
Aug 11 12:55:04 venice kernel: [    1.024072] ima: Error Communicating to TPM chip
Aug 11 12:55:04 venice kernel: [    1.024620] ima: Error Communicating to TPM chip
Aug 11 14:41:08 venice kernel: [    0.000000] efi:  ACPI=0x6d64d000  ACPI 2.0=0x6d64d014  TPMFinalLog=0x6d61b000  SMBIOS=0x6d8f2000  SMBIOS 3.0=0x6d8f1000  MEMATTR=0x67ad8018  ESRT=0x67af7e18  TPMEventLog=0x617af018
Aug 11 14:41:08 venice kernel: [    0.010592] ACPI: TPM2 0x000000006D5C2000 000034 (v04 ALASKA A M I    00000001 AMI  00000000)
Aug 11 14:41:08 venice kernel: [    1.022445] ima: Error Communicating to TPM chip
Aug 11 14:41:08 venice kernel: [    1.024072] ima: Error Communicating to TPM chip
Aug 11 14:41:08 venice kernel: [    1.024639] ima: Error Communicating to TPM chip
Aug 11 14:41:08 venice kernel: [    1.025180] ima: Error Communicating to TPM chip
Aug 11 14:41:08 venice kernel: [    1.025750] ima: Error Communicating to TPM chip
Aug 11 14:41:08 venice kernel: [    1.026317] ima: Error Communicating to TPM chip
Aug 11 14:41:08 venice kernel: [    1.026884] ima: Error Communicating to TPM chip
Aug 11 14:41:08 venice kernel: [    1.027453] ima: Error Communicating to TPM chip 

Понравилась статья? Поделить с друзьями:
  • Im connect fail error code 30004 msg
  • Iis web config error
  • Ilsagaz ошибка lp как исправить
  • Iis service unavailable http error 503 the service is unavailable
  • Ilok server error