New error on boot uo w/new kernel

General system Kernel, boot, graphics & hardware
1

I am running a AMD 9600X and a Asus B850 motherboard and I have has zero issues . Just a few minutes ago I upgraded to the latest kernel then I noticed a issue on boot up in my log

“virt/tdx: TDX not supported by the host platform”

What is this ? can I blacklist it ? If so how ?

System:

Summary 
Kernel: 7.1.2-arch3-1 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1 clocksource: tsc
Desktop: Cinnamon v: 6.6.8 tk: GTK v: 3.24.52 wm: Muffin v: 6.6.3 vt: 7 dm: LightDM v: 1.32.0
Distro: EndeavourOS base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: 
Mobo: ASUSTeK model: TUF GAMING B850-PLUS WIFI v: Rev 1.xx serial: 
part-nu: SKU uuid:  Firmware: UEFI vendor: American Megatrends v: 1654
date: 04/02/2026
CPU:
Info: 6-core model: AMD Ryzen 5 9600X bits: 64 type: MT MCP smt: enabled arch: Zen 5 rev: 0
cache: L1: 480 KiB L2: 6 MiB L3: 32 MiB
Speed (MHz): avg: 3888 min/max: 628/5486 boost: enabled cores: 1: 3888 2: 3888 3: 3888 4: 3888
5: 3888 6: 3888 7: 3888 8: 3888 9: 3888 10: 3888 11: 3888 12: 3888 bogomips: 93602
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: NVIDIA AD103 \[GeForce RTX 4070 Ti SUPER\] vendor: ZOTAC driver: nvidia v: 610.43.02
arch: Lovelace pcie: speed: 2.5 GT/s lanes: 16 ports: active: none off: DP-3
empty: DP-1,DP-2,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:2705 class-ID: 0300
Display: x11 server: X.Org v: 21.1.23 with: Xwayland v: 24.1.12 driver: X: loaded: nvidia
unloaded: modesetting alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.70x13.46") s-diag: 692mm (27.26")
Monitor-1: DP-3 mapped: DP-4 note: disabled model: Dell S2721DGF serial:  res: N/A
dpi: 109 size: 597x336mm (23.5x13.23") diag: 685mm (27") modes: max: 2560x1440 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm:
drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 610.43.02 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 4070 Ti SUPER/PCIe/SSE2
Info: Tools: api: eglinfo,glxinfo gpu: nvidia-settings,nvidia-smi x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA AD103 High Definition Audio vendor: ZOTAC driver: snd_hda_intel v: kernel pcie:
speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22bb class-ID: 0403
Device-2: Creative Labs EMU20k2 \[Sound Blaster X-Fi Titanium Series\] driver: snd_ctxfi
v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 1102:000b class-ID: 0403
API: ALSA v: k7.1.2-arch3-1 status: kernel-api
Server-1: sndiod v: N/A status: off
Server-2: PipeWire v: 1.6.7 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 5 GT/s
lanes: 1 port: e000 bus-ID: 08:00.0 chip-ID: 10ec:8125 class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 
Drives:
Local Storage: total: 465.76 GiB used: 50.73 GiB (10.9%)
ID-1: /dev/nvme0n1 vendor: Crucial model: CT500T500SSD8 size: 465.76 GiB speed: 63.2 Gb/s
lanes: 4 tech: SSD serial:  fw-rev: P8CR004 temp: 34.9 C scheme: GPT
Partition:
ID-1: / size: 446.75 GiB used: 50.45 GiB (11.3%) fs: ext4 dev: /dev/nvme0n1p2
Swap:
ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -1 dev: /dev/nvme0n1p3
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s lanes: 1
chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 1-4:2 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1 speed: 480 Mb/s lanes: 1
power: 100mA chip-ID: 174c:2074 class-ID: 0900
Device-1: 1-4.4:4 info: Logitech Logitech Mechanical keyboard type: keyboard,HID
driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 250mA
chip-ID: 046d:c341 class-ID: 0300 serial: 
Device-2: 1-11:3 info: ASUSTek AURA LED Controller type: HID driver: hid-generic,usbhid
interfaces: 2 rev: 2.0 speed: 12 Mb/s lanes: 1 power: 16mA chip-ID: 0b05:19af class-ID: 0300
serial: 
Hub-3: 2-0:1 info: super-speed hub ports: 5 rev: 3.1 speed: 20 Gb/s lanes: 2 chip-ID: 1d6b:0003
class-ID: 0900
Hub-4: 2-4:2 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0 speed: 5 Gb/s lanes: 1
power: 8mA chip-ID: 174c:3074 class-ID: 0900
Hub-5: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s lanes: 1
chip-ID: 1d6b:0002 class-ID: 0900
Hub-6: 4-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s lanes: 1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-7: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s lanes: 1
chip-ID: 1d6b:0002 class-ID: 0900
Hub-8: 6-0:1 info: super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s lanes: 1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-9: 7-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s lanes: 1
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 7-1:2 info: Pixart Imaging Optical Mouse type: mouse driver: hid-generic,usbhid
interfaces: 1 rev: 1.1 speed: 1.5 Mb/s lanes: 1 power: 100mA chip-ID: 093a:2510 class-ID: 0301
Sensors:
System Temperatures: cpu: 44.8 C mobo: 37.5 C gpu: nvidia temp: 46 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%

Repos:

Summary 
Packages: pm: pacman pkgs: 1116
Active pacman repo servers in: /etc/pacman.d/endeavouros-mirrorlist
1: https: //mirrors.gigenet.com/endeavouros/repo/$repo/$arch
2: https: //mirror.rznet.fr/endeavouros/repo/$repo/$arch
3: https: //pkg.adfinis-on-exoscale.ch/endeavouros/repo/$repo/$arch
4: https: //mirror.moson.org/endeavouros/repo/$repo/$arch
5: https: //mirror.gofoss.xyz/endeavouros/repo/$repo/$arch
6: https: //mirror.retropc.se/endeavouros/repo/$repo/$arch
7: https: //mirror.alpix.eu/endeavouros/repo/$repo/$arch
8: https: //repo.c48.uk/endeavouros/repo/$repo/$arch
9: https: //fosszone.csd.auth.gr/endeavouros/repo/$repo/$arch
10: https: //distrohub.kyiv.ua/endeavouros/repo/$repo/$arch
11: https: //mirrors.c0urier.net/linux/endeavouros/repo/$repo/$arch
12: https: //mirror.funami.tech/endeavouros/repo/$repo/$arch
13: https: //mirrors.urbanwave.co.za/endeavouros/repo/$repo/$arch
14: https: //mirrors.tuna.tsinghua.edu.cn/endeavouros/repo/$repo/$arch
15: https: //mirrors.nxtgen.com/endeavouros-mirror/repo/$repo/$arch
16: https: //mirror.b-interactive.com.au/endeavouros/repo/$repo/$arch
17: https: //www.miraa.jp/endeavouros/repo/$repo/$arch
18: https: //ftp.rz.tu-bs.de/pub/mirror/endeavouros/repo/$repo/$arch
19: https: //ftp.belnet.be/mirror/endeavouros/repo/$repo/$arch
20: https: //mirror.diyarciftci.xyz/endeavouros/repo/$repo/$arch
21: https: //mirror.archlinux.tw/EndeavourOS/repo/$repo/$arch
22: https: //mirror.freedif.org/EndeavourOS/repo/$repo/$arch
23: https: //mirror.albony.in/endeavouros/repo/$repo/$arch
24: https: //mirror.sjtu.edu.cn/endeavouros/repo/$repo/$arch
25: https: //mirror.accum.se/mirror/endeavouros/repo/$repo/$arch
26: https: //mirrors.jlu.edu.cn/endeavouros/repo/$repo/$arch
27: https: //mirror.jingk.ai/endeavouros/repo/$repo/$arch
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https: //losangeles.mirror.pkgbuild.com/$repo/os/$arch
2: https: //mirror.givebytes.net/archlinux/$repo/os/$arch
3: https: //mirrors.lug.mtu.edu/archlinux/$repo/os/$arch
4: https: //plug-mirror.rcac.purdue.edu/archlinux/$repo/os/$arch
5: https: //mirror.zackmyers.io/archlinux/$repo/os/$arch
6: https: //arch.mirror.constant.com/$repo/os/$arch
7: https: //us.arch.niranjan.co/$repo/os/$arch
8: https: //us-mnz.soulharsh007.dev/archlinux/$repo/os/$arch
9: https: //mirror.akane.network/archmirror/$repo/os/$arch
10: https: //mirror2.givebytes.net/archlinux/$repo/os/$arch
11: https: //iad.mirrors.misaka.one/archlinux/$repo/os/$arch
12: https: //zxcvfdsa.com/arch/$repo/os/$arch
13: https: //mirrors.logal.dev/archlinux/$repo/os/$arch
14: https: //arch.mirror.marcusspencer.us:4443/archlinux/$repo/os/$arch
15: https: //us.mirrors.cicku.me/archlinux/$repo/os/$arch
16: https: //mirrors.rit.edu/archlinux/$repo/os/$arch
17: https: //arch.hu.fo/archlinux/$repo/os/$arch
18: https: //mirror.adectra.com/archlinux/$repo/os/$arch
19: https: //arch-mirror.brightlight.today/$repo/os/$arch
20: https: //mirror.tzulo.com/archlinux/$repo/os/$arch
Info:
Memory: total: 32 GiB available: 30.99 GiB used: 2.47 GiB (8.0%)
Processes: 284 Power: uptime: 14m states: freeze,mem,disk suspend: deep wakeups: 0
hibernate: platform Init: systemd v: 261 default: graphical
Compilers: gcc: 16.1.1 Client: Cinnamon v: 6.6.8 inxi: 3.3.40
2

It means your CPU doesn’t support Intel TDX (a server-grade security feature), which is normal for most consumer PCs. You can safely ignore it.

3

is their something I can blacklist and if so how ?

would like to get this out of my logs :slight_smile:

4

The system logs are for the system not to satisfy your ocd for removing any errors you don’t like from your logs as journaling is designed for being able to read back system information. Otherwise just try blacklisting the module if something in the kernel is trying to load it and if that doesn’t work just wipe your entire system log if it bothers you that much.

Lastly you don’t have to “fix” every error you see.

5

I have yet to encounter a human without quirks. I’m sure if I find a creature without any, that wouldn’t be a human.

6

sorry I asked , next time I will seek my answers elsewhere

7

Have a look here @brothergc :

The user twig noted that a patch is in the pipeline to remove the annoying message.

See:
https://patchew.org/linux/20260702043204.81741-1-jirislaby@kernel.org/

Before commit 165e77353831 below, the kernel did not print anything when
X86_FEATURE_TDX_HOST_PLATFORM was not present in a cpu.

After the commit, this is emitted to the log, with the error level:
virt/tdx: TDX not supported by the host platform

This is disturbing as it is not an error running CPUs without the
feature.

Drop the error message completely to revert to the state before
165e77353831.

8

The point is…it’s not a problem. Ir’s not an error, it’s just information.

9

You’ve been ceremonially sacrificed on the sacred “How dare you not already know every obscure Linux detail” altar. Classic rite of passage.

If you really want to troll the high priests of Linux Knowledge, you can always invoke one of the forbidden incantations :man_mage:

  • Praising Edge on Linux - bonus points if you call it faster than Firefox and more stable than Chrome.

  • Using VS Code instead of Vim - “I just want my editor to work” is the ultimate heresy.

  • Installing Flatpak on Arch - or Snap anywhere outside Ubuntu.

  • Running GNOME and saying it’s better than KDE - eternal war, eternal suffering.

  • Using sudo in scripts - or defending chmod 777 as “just a quick fix.”

  • Saying systemd is good, actually - prepare for ritual exile.

  • Using ZFS on Linux - and ignoring licensing drama.

  • Mounting NTFS and saying it’s fine - especially if you dual‑boot.

  • Using proprietary NVIDIA drivers - or praising Proton for outperforming Windows.

10

And that if the error isn’t causing a real problem on your system there’s nothing to fix. @brothergc Sorry if I came off a bit too harsh that wasn’t the intent, I should have left out the irrelevant comment and that would have sounded nicer and still given you an answer so my apologies.

11

Just stumbled upon a topic in the Arch forum that might be of intrest to you.
https://bbs.archlinux.org/viewtopic.php?id=314157

12

I do. It’s better than KDE. Period.

I do. Period.

So bring it on! :rofl:

13

Anybody can have a bad day and have a “momentary lapse of reason”. I know I have… a lot.

So please don’t bother. You are entitled to ask any question you want. Stay around!

14

please use code tags at least.

15

Please be nice to each other!

this is in my view a legit question about something in the system log that concerns a user, if that something is actually a problem or not is not the question.

16

I have no idea what a “code tag” is

17

Ya know I was hoping for a workaround , But what I found is people giving opinions ( not all) instead of helping to solve a issue . I do post in other forums and My own personal rule is if I cant provide a solution for a issue then I do not post .

I also do not assume that everyone is up to my level as I have found on other Arch forums . I have been on Arch, and manjaro Linux forums and lets just say to be kind they leave much to be desired when treating people who are not up to their level . Not everyone was born with a masters degree in Linux . Which is why I like Linux mint forums , kind people .

so ,in closing I dought I will post again and if a moderator is reading this please just delete my account . Thanks and have a great day ! :slight_smile:

18

As said before, the journal or system logs are designed to read back system information, not to exclude something you don’t want to see. It’s possible to blacklist a module to prevent it from loading but it seems for your specific thing they are already working on a fix so that what you don’t want to see in the system logs will not be seen anymore.

I apoligize again for being having responded as a bit of an asshole earlier, but everyone has their days sometimes.

19

I don’t mind, but I prefer KDE.

Also because I have to customize GNOME to make it the way I need and like it, so I might as well use KDE directly, which already does what I want natively.

If GNOME had better support for extensions, I could use it instead of ignoring them. But since that’s not the case, I’m sticking with KDE.

At the beginning I did it too, but then I realized that for the software I use I don’t need a flatpak on Arch or EOS, it’s already there in the repo, or in the AUR.

On other distros like Debian, or other flatpaks, however, I use it, since not all the software I want is present in the repositories, or can be added.

20

Well I would say there is not always a workaround for a problem and in this case it appears to be a bug, and someone is working on a patch. Also if this is only about a clean looking journal and nothing more, like there a possible problem with your system, I would not worry about it. Not sure exactly what you mean with being up to your level, because we just don’t know what level this would be.