Hej Nick!

According to https://cc-enabling.trustedservices.intel.com/intel-tdx-enabling-guide/03/hardware_selection/;

To enable Intel TDX, one of the following processor families is required:

* 5th Gen Intel® Xeon® Scalable Processor
* Intel® Xeon® 6 Processors

No such luck and is HIGHLY unlikely given the cost of ram these days. Luckily there is zero need for such a thing in this neck of the woods given my penchant to keep things minimalizeed ... especially power consumption.

Het leven is goed,
Maurice

-o -o -o -o -o o- o- o- -o o- -o o- o- o- -o o-
(\ (\ (\ (\ (\ /) /) /) (\ /) (\ /) /) /) (\ /)
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
... Eþel byþ oferleof æghwylcum men.
Home is very dear to every man.
--- GNU bash, version 5.3.12(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint @ (2:280/464.113)

Hey Maurice!

On Tue, 07 Jul 2026 22:54:26 , you wrote:

No such luck and is HIGHLY unlikely given the cost of ram these days. Luckily there is zero need for such a thing in this neck of the woods
given my penchant to keep things minimalizeed ... especially power consumption.

While it will probably continue to be a detection thing in most kernels that you don't actually configure yourself (supplied as a default configure to detect just about anything), the kernel version I have currently sends a red warning to my boot logs. I have a feeling the 'patch' would probably just make it a non-serious (or at least less, since I'm sure a lot of people freaked out and went to the forums to ask about it as soon as they saw it the first time) logged affair (ie white or gray).

All said and done, I don't think there's anything actually wrong with whatever it's actually doing, it was just the logging of it that wasn't very pleasant.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20260425
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)