Getting boot error after latest update

[invalid_user_name]

Tech noob here. For the 2nd time I’m getting a boot up error after running sudo zypper dup. See link for screenshot and details. Any way to fix this? How to diagnose this? How can I determine which module in the update is causing the error. The update size is 2.4GB total which is a bigger than usual update.

https://paste.opensuse.org/pastes/f854ea612683

I’m running an AMD Ryzen laptop with TW Gnome Wayland.

Anyone else having this issue after the recent update?

PS: I did a snapshot rollback to get back to a bootable working system.

[marel]

Good you did a roll-back.

The error text (handy for searching) is “amdgpu SECUREDISPLAY query secured isplay TA failed. ret 0x0”

Probably good to disable secure boot and try again. I checked my system and although I never enabled it it is on. You can change the setting in Yast, Boot Loader Settings.

[arvidjaar]

@marel

good to disable secure boot and try again. … You can change the setting in Yast, Boot Loader Settings.

No, you cannot change this setting in YaST. If Secure Boot is enabled, system will simply fail to boot.

[marel]

Thanks @arvidjaar, good to know.

Interesting design choice, to provide the option to disable “Secure Boot Support” while secure boot is enabled, mokutil --sb-state and disabling it will break the system.

I see there is an possibility to disable secure boot using mokutil but it looks to me the correct way of doing this is to disable it in the bios.

[invalid_user_name]

@marel

Probably good to disable secure boot and try again.

advait@localhost:~> mokutil --sb-state
SecureBoot disabled
advait@localhost:~> 

Nate on Linux Out Loud seemed to say that the recent TW update is messing up some systems. So my plan is to wait until this bug is fixed.

advait@localhost:~> uname -srm
Linux 6.11.2-1-default x86_64
advait@localhost:~> 

Is there a website where I can look and see the repair status of this bug? I’m a tech noob. Anyone know the name or designation of this bug?

Sorry for my noob questions.

[marel]

@invalid_user_name

Is there a website where I can look and see the repair status of this bug?

I would first check https://bugzilla.opensuse.org, use the words from the error text (“handy for testing”), I did so and could not find a relevant problem.

Searching for the text using the search engine and limiting to max 1 year old gives multiple hits including the exact message, I did not look further.

[invalid_user_name]

@marel

I would first check https://bugzilla.opensuse.org, use the words from the error text (“handy for testing”), I did so and could not find a relevant problem.

Thanks for the link. I submitted a bug report with a CC to me.

[marel]

Always good to post the link to the issue so others can easily chime in.

[invalid_user_name]

@marel
“Always good to post the link to the issue so others can easily chime in.”

Yes, good reminder. Thanks.

[invalid_user_name]

post deleted removed. Is there anyway to delete a post?

[invalid_user_name]

Problem fixed. I hired a remote Linux expert. He found that one of my USB drives was specified as auto-mount in the FSTAB file. We have no idea how this happened. He removed it from fstab and then I installed the big TW update (4GB!). My system rebooted fine (took about 15 minutes to reboot as TW processed 4GB of updates). Now I’m back to normal and all good.