We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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:
No branches or pull requests
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: