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.
Check the Arch Linux site at the link below, specifically post 15 (post 17 explains) to see if that helps. If you try anything, make sure to note exactly what you did and results.
Check the Arch Linux site at the link below, specifically post 15 (post 17 explains) to see if that helps. If you try anything, make sure to note exactly what you did and results.
I was looking at the post you mention yesterday, just looked at it again, and can make as much sense of it the second time round as the first - none!
I timed it last night, it seems to last for 90 seconds approx. I was wondering if there is a config that has a time delay in it for udev that could be shortened.
The thread in the link I posted earlier indicates that adding "tpm_tis.interrupts=0" to the linux line in the menuentry in the grub.cfg file (without quotes of course). Make a backup copy of grub.cfg before making the change then save the change and do not update grub since this is only a test. You should show an entry in your BIOS firmware for TPM, likely under the Security tab. Check if it is enabled and disable and test boot. If that doesn't help, change it back. And again, make note of changes you make.
The thread in the link I posted earlier indicates that adding "tpm_tis.interrupts=0" to the linux line in the menuentry in the grub.cfg file (without quotes of course). Make a backup copy of grub.cfg before making the change then save the change and do not update grub since this is only a test. You should show an entry in your BIOS firmware for TPM, likely under the Security tab. Check if it is enabled and disable and test boot. If that doesn't help, change it back. And again, make note of changes you make.
Hi
Again thanks for the reply.
Its a little clearer now - I saw that line/code, but had no idea where to place it; unfortunately I do not ise grub, I use slackwares lilo to boot, but i will place that code in lilo.
I will look at the bios for what you indicate.
Thanks
slackbat
Last edited by slackbat; 04-25-2024 at 07:22 AM.
Reason: typo
So I did it, I added an append to lilo, rebooted, then hey-presto then problem was reduced to about 7 seconds, from 90 seconds. I am still going to look to see if there is a time component to the code.
Thanks...slackbat
Last edited by slackbat; 04-27-2024 at 04:48 AM.
Reason: typo
With Lilo there should be an append line in lilo.conf where the parameter is placed and if not, create it. Not sure if the TPM option in the BIOS will do anything. I have found that my Linux systems (including Slackware) boot without problem with TPM enabled or disabled.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.