Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello -
I'm having a problem with booting up my computer that suddenly appeared yesterday. It's the error I posted in the subject line - ima: Error Communicating to TPM chip.
My computer is an HP Z-Book 15. The OS is Ubuntu 22.04, (the Kubuntu version). The computer uses the UEFI native boot mode when starting up.
I've gone into HP Computer Set-Up to try to adjust the TPM settings but the options are limited. The only place that I can make a TPM adjustment is under the "Security" tab. In the User Management I can select Set Security Level, then go to TPM Embedded Security which gives the options: Change|View|Hide. The setting was View, I changed the setting to Change but I still got the error.
Also under the Security Tab, there's a section called "Embedded Security" and "TPM Embedded Security" is listed there but the option is grayed-out. So the only place in HP Computer Set-Up to actually change the TPM setting is under User Management, like I described in the previous paragraph.
I've been diligent about installing the upgrades Ubuntu pushes out, seemingly everyday. Since this boot-up error appeared so suddenly, my suspicion is that an update somehow conflicted with the computer's boot-up settings.
Does anyone have any ideas on how to fix this?
Thanks.
To my mind, the LAST thing you want is UEFI Security because the cockeyed and paranoid way UEFI is done has simply moved people to hacking pcs when they are running. If windows is about, that's easy enough.
I'd go back into the BIOS, and see if you can back off security. Ignore errors that don't stop you running.
Thanks for the input about UEFI. I'll try resetting back to BIOS soon. Right now, I'm using my computer in one of the alternate versions that are available when the computer boots up - Ubuntu with Linux 5.15.0,56 generic and Ubuntu, (actually Kubuntu), is operating. (I have a Zoom meeting this evening, and getting this computer operating is top priority, so I plan to just use this version tonight.)
Similar to what you mentioned about going back to BIOS, when the alternate version loads, I get a screen showing the "communicating with the TMP chip error," but the OS finishes loading and is usable, unlike when using Kubuntu 22.04, where it stops on the error screen.
The reason I started using UEFI at all was that when I upgraded from Ubuntu 20.04 to Kubuntu 22.04, I couldn't get the OS to load properly when using the BIOS -- I don't remember if the problem was intermittent, (sometimes the OS loaded and sometimes not), or if Kubuntu just wouldn't load at all.
I'm guessing that I'm using Kubuntu with an older version of Linux -- is that right? Do you know if there will be obvious differences I'll run into?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.