latest update consequences or just my paranoia

foe · 2025-10-02 15:53:14

Hello there,

After installing latest updates from pacman I noticed some weird boot sequence changes.
For example my desktop pc now at every boot does: "performing fsck on "..." on real root". What's that all about? Wasn't there before.
Laptop (thinkpad) started "amdgpu: Secure display: Generic Failure. SECUREDISPLAY: query securedisplay T A failed. ret 0x0". This is right after "Running hook [udev]".
Were there some additions to checks or verbose output in those updates or whatnot?
I am 100% certain that these messages showed up right after update.

twelveeighty · 2025-10-02 18:03:07

Do a clean restart, log in, wait 2-3 minutes and then post the journal from the current boot/login by runing `journalctl -b` as root. Before posting the journal, please look through the messages yourself and see if you can spot any possible concerns.

foe · 2025-10-02 20:21:29

Here it is:

Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: [drm] Loading DMUB firmware via PSP: version=0x0101002B
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: Found VCN firmware Version ENC: 1.24 DEC: 8 VEP: 0 Revision: 5
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: reserve 0x400000 from 0xf41f800000 for PSP TMR
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode is not available
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx command LOAD_TA(0x1) failed and response st
atus is (0x7)
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: psp gfx command INVOKE_CMD(0x3) failed and response
 status is (0x4)
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: SMU is initialized successfully!
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: [drm] Display Core v3.2.334 initialized on DCN 2.1
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: [drm] DP-HDMI FRL PCON supported
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x0101002B
Oct 02 23:08:02 smol kernel: amdgpu 0000:04:00.0: amdgpu: [drm] Using ACPI provided EDID for eDP-1

Well, from what I understood from chatgpt these are harmless. Though I am little bit confused why they are showing up at all since before these recent updates they didn't.
Though I booted xubuntu live usb one time yesterday...could it have meddled with some firmware stuff?

seth · 2025-10-02 20:57:35

A bunch of those have been there forever™ - archlinux.org/packages/core/any/linux-firmware-amdgpu/ was updated ~2 weeks ago - no idea whether your HW was affected or you're supposed to have _ta binary:
https://gitlab.com/kernel-firmware/linu … type=heads

Have you checked older journals to make sure they *really* where not there?

foe · 2025-10-02 21:25:54

I am 100% sure they were not logged out on boot. I can't really check past journals if they were specifically there since I already did a clean reinstall. I am assuming boot time logs are handled by different functions than those that log out journal entries since they little bit differ. So either some alterations were made to firmware stuff or idk just wild guessin...or some boot log output verbosity or something got an update maybe?

seth · 2025-10-03 08:21:57

since I already did a clean reinstall

Why?
Were the messages there before or as consequence of the re-installation?

You did (re-)install linux-firmware-amdgpu?

foe · 2025-10-03 10:38:01

Messages were there before, after updating and they are there after fresh install.
Did firmware reinstall and it didn’t change anything.

seth · 2025-10-03 14:02:24

https://wiki.archlinux.org/title/Silent_boot
As you figured, the messages are harmless and w/o previous records there's no way to figure what might have changed (they're not new unless you've skipped updates over the past two years or so)

foe · 2025-10-03 16:20:46

I usually update every day.
Somehow this coincided with me booting xubuntu live usb the same evening so at first I thought that it did some meddling with some boot records or firmware stuff. But yea, at this point I guess it's not much use to try to chase ghosts.
Since it's harmless I'll just leave it as is and will see what happens in the futere.

Last edited by foe (2025-10-03 16:21:38)

Arch Linux

#1 2025-10-02 15:53:14

latest update consequences or just my paranoia

#2 2025-10-02 18:03:07

Re: latest update consequences or just my paranoia

#3 2025-10-02 20:21:29

Re: latest update consequences or just my paranoia

#4 2025-10-02 20:57:35

Re: latest update consequences or just my paranoia

#5 2025-10-02 21:25:54

Re: latest update consequences or just my paranoia

#6 2025-10-03 08:21:57

Re: latest update consequences or just my paranoia

#7 2025-10-03 10:38:01

Re: latest update consequences or just my paranoia

#8 2025-10-03 14:02:24

Re: latest update consequences or just my paranoia

#9 2025-10-03 16:20:46

Re: latest update consequences or just my paranoia

Board footer