Thank you, Mario. I noticed I am behind on 2 updates for NVME solid state firmware. Just out of curiosity, could updating that potentially solve the issue?
I’m thinking no, but just wanted to check
Thank you, Mario. I noticed I am behind on 2 updates for NVME solid state firmware. Just out of curiosity, could updating that potentially solve the issue?
I’m thinking no, but just wanted to check
Nope. The fix for AMD SB-7033 is in the BIOS.
Hey guys, if any of you are still having issues because of the missing fix in BIOS update:
Could I ask you to take a minute to add to my thread on Lenovo’s forums, please? I feel like if there are more people complaining about it, maybe they will take notice.
@phillipleblanc sorry to call you out, but since you’re having the same issue/seeing the same logs as me, just wanted to check if there was any changes on your system since your last post? Cheers
Unfortunately no, ASUS hasn’t released a BIOS update yet for my laptop.
I mitigated the LUKS password entry issue by setting amdgpu.dcdebugmask=0x10 on the kernel command line, which has been good enough for me.
If I get around to calling ASUS support I’ll reference your Lenovo thread, so thanks for that!
Thank you! I am sorry, I don’t know how I missed seeing that you’re on an ASUS Zephyrus from your original comment, you literally state that in the opening sentence. I must be tired. Thanks for being kind ![]()
I’m curious to know if/how this needs to change in the future. From my understanding, the latest Linux firmware clears the RDSEED32 bit, forcing applications to use another method. This is until AMD release the appropriate AGESA update, followed by motherboard manufacturers distributing this in their BIOS releases. Looks like for the 9800X3D this is AGESA 1.2.0.3i (link). The latest BIOS for my motherboard is only on 1.2.0.3f so I have a while to wait… (thanks MSI!).
So, do we think the plan would be to eventually stop clearing the RDSEED32 bit automatically in Linux firmware? If so I imagine we’ll need to wait a reasonable time longer to allow for a reasonable proportion of the affected population to update BIOS.
Sorry for just dropping this in, I am helping a guy with a similar problem (on Manjaro, Ryzen 9 9900X3D).
I have not read every single message.
I just want to cross-link this comment I found here: