-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] initramfs changes cause critical nvidia bug to surface on turing, ampere, and maybe pascal #285
Comments
Ok, I've done a bunch of testing and I'm convinced we need this fix. What @qoijjj has done here https://github.com/secureblue/secureblue/blob/live/files/scripts/setearlyloading.sh should be what we do in our nvidia build. Edit: corrected URL. originally had this incorrect URL: |
I have to double check how we implement, but would be ideal if we can fix this here in the |
@bsherman for reference of others, I believe you meant to link https://github.com/secureblue/secureblue/blob/live/files/scripts/setearlyloading.sh |
Fixed by #292 |
* fix: chromium browser use of hw accel on hybrid laptops Fixes: #285 * fix: use default nvidia driver power management This fixes power management on optimus laptops, specifically for Ampere+ where the specified config was preventing D3cold state. Upstream negativo17 should be notified of this change, too. Fix: #290
The upstream issue: https://forums.developer.nvidia.com/t/550-54-14-cannot-create-sg-table-for-nvkmskapimemory-spammed-when-launching-chrome-on-wayland/284775
The ublue line that is likely causing this to surface: https://github.com/ublue-os/hwe/blob/main/nvidia-install.sh#L59
This bug means that chromium-based browsers are unusable on all ublue nvidia images for certain architectures
Layering the ublue akmod without making that initramfs change fixes the issue.
The text was updated successfully, but these errors were encountered: