Strange issue with new messages on boot

I updated my TW/KDE systems (2 off) this week and they both behave differently now when booting to what happened prior to the update. I see some new messages appear very briefly after hitting enter on grub2 and they disappear and the display changes to the scrolling message display just as if I’d hit esc but by now the additional messages have gone from the screen. I have managed to spot at least a couple which relate to the SSDs these two systems have as boot devices. Now I can find no error messages when scanning the journal once the system is up and running so not sure why this happens of exactly what these messages are. I know the systems appear fine but I don’t like it when things change like this :wink:

So any ideas please? How might I capture these messages so I can actually see what they say? Anyone else noticed this?

Stuart

Hi
What about journalctl -b output? What about systemd-analyze blame, see anything different in the output?

I’ve not looked at either for a while but nothing jumps out at me right now. Booting is just as fast as normal and I’d probably not bother chasing this if I could read the messages!

Stuart

When this happens to me, and I can’t identify the messages in the logs (and I’m curious enough), I take a shot or record a video of the boot screen with a cell phone, and if a video I transfer it to the PC and watch frame by frame. Never failed yet.

The messages are always there. It’s just that ATM, the splash screen isn’t working as it should so instead of seeing a nice quiet splash you see noisy feedback from the boot messages
Part of the course in TW

I have a similar issue on my homeserver. Here, it’s an ACPI error which is not prompted at the boot screen any furhter.

The message on the screen vanishes too fast but I can find it in:

dmesg

If you got a glimpse of the message, maybe you remember it when seeing the dmesg post.