It looks like 6.4.6 is working on Fedora 38 on my 13th gen.
If you go into Software Center->Updates, click on the 3 bars and select Software Repositories you can add the Fedora 38 - x86_64 - Test Updates repo. After that, you can run a dnf update or check for updates in the Software Center.
After downloading the updates, It requires a restart, and will again hang at boot. If you power off and then reboot into the earlier kernel version you were using, It should finish the update.
I don’t typically run test updates, so I disabled the repo after the update, and would recommend doing so too if you don’t want early software versions.
1 Like
This is the way. 
I’ve disabled TPM through the BIOS until the update hits stable. This is not the ideal solution, but it made all the problems disappear.
Fedora 38 kernel 6.4.6 is now in stable. Booted fine without “tpm_tis.interrupts=0” in the kernel args.
4 Likes
confirmed here too. Got 6.4.6-200.fc38.x86_64 (no boot params, and no waiting) this AM and lappy (not a framework, but similar) started to boot-behave nicely.
Shout out to this community: it has been extremely helpful sorting thru a myriad of issues I have with FC36,37,38 on my Alder Lake laptop (not a framework guy, yet but will be soon).
1 Like
Confirming here as well. 6.4.6-200.fc38.x86_64. TPM is working as expected. Thanks all for keeping track of this one!
1 Like
Hi folks, reporting from Debian testing here. Looks like I’m facing this same issue. linux-image-6.4.0-1-amd64 wouldn’t boot for me. linux-image-6.3.0-1-amd64 Version 6.3.7-1 booted fine. I temporarily added the tpm_tis.interrupts=0 argument following these instructions and am able to run my 6.4.4-1 kernel. Thanks, all!
2 Likes
openSUSE Tumbleweed with 6.4.6 and everything is now fine without the parameter.
On Fedora 37 kernel 6.4.7-100.fc37 works fine again. Problem solved I guess.
Yeah, they caught it in .6 and the resolution has progressed through .7
So things are looking good. That said, because it’s resolved in these two current kernels, marking this resolved.
Should it crop up again, this thread is open to track again.
1 Like
Chiming in to mention debian unstable. Kernel package versions 6.4.0-1 and 6.4.0-2 (these are debian versions, not kernel versions) were failing as everyone else described above. Adding tpm_tis.interrupts=0 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/defaults/grub then sudo update-grub allowed booting.
This is on a 12th gen laptop.
2 Likes
Cool, thanks for that, I added this to one of our pinned Debian guides a community member put together.
This is fixed with linux-image-6.4.0-3-amd64 Version 6.4.11-1
2 Likes
This is correct.
I think the kernel has regressed. I’m unable to shutdown on arch with 6.5.3-arch1-1 and a FW 12th gen. I tried the flag (using systemd-boot) with no success. I realize that this is not a supported setup. The issue is present when using a live image and when exiting the bios too. I don’t even use the TPM for anything (that I am aware of); is there a way to outright disable it?
1 Like
It came back to me at some linux6.4 release (forgot the patchlevel) but was able to disable it via the tpm_tis.interrupts=0 boot parameter.
Will report back when I rebooted with linux6.5.
1 Like
I am now on a fresh install of fedora 38. Still didn’t work so I updated. Current grub options “BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.4.15-200.fc38.x86_64 root=UUID=7bd081c4-38ea-427c-b924-125b6b8a1af7 ro rootflags=subvol=root nomodeset rhgb quiet tpm_tis.interrupts=0”. I have restored bios settings. I am going to give Windows 11 a go. At this point I am starting to think that this is a separate issue.
1 Like
Definitely not the kernel. I am now running Windows with no success. Opened a support ticket 
1 Like
Okay, thank you very much for keeping this thread in the loop and also opening a ticket. Updates like this save us so much time, really appreciate it.
Hm. My kernel has updated once since I reported me being fixed and I’m still good. I’m on linux-image-6.4.0-4-amd64 Version 6.4.13-1 on Debian testing.
2 Likes