12-21-2025, 07:40 PM
Hi and welcome! ?
At the moment, the second workaround mentioned in the blog post isn’t user-actionable yet — it requires kernel/driver changes that haven’t been packaged or documented for end users. Until those updates land, there’s unfortunately nothing specific you can try on your side beyond the first workaround. Hopefully clearer instructions or fixes will be shared in a future update.
At the moment, the second workaround mentioned in the blog post isn’t user-actionable yet — it requires kernel/driver changes that haven’t been packaged or documented for end users. Until those updates land, there’s unfortunately nothing specific you can try on your side beyond the first workaround. Hopefully clearer instructions or fixes will be shared in a future update.