scottk/secureblue
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/secureblue.git synced 2025-12-24 22:37:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: add FAQ item about known upstream proprietary nvidia driver bug

Browse Source
This commit is contained in:
qoijjj
2024-08-20 09:48:35 -07:00
committed by GitHub
parent 06c2883bb1
commit f86b2c49e1
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
FAQ.md
View File

@@ -84,3 +84,10 @@ For more technical detail, see [#268](https://github.com/secureblue/secureblue/i
#### Why is DNS broken on my secureblue VM?
The DNSSEC setting we set in `/etc/systemd/resolved.conf.d/securedns.conf` causes known issues with network connectivity when secureblue is used in a VM. To fix it, comment out `DNSSEC=allow-downgrade` in that file and manually set a dns provider in network settings.
#### Why does chromium take a long time to open?
This is a [known issue](https://forums.developer.nvidia.com/t/550-54-14-cannot-create-sg-table-for-nvkmskapimemory-spammed-when-launching-chrome-on-wayland/284775) with the proprietary nvidia drivers. Your options are:
- (Recommended if available for your hardware) switch to a `-main` image and use Nouveau with NVK and [GSP](https://nouveau.freedesktop.org/PowerManagement.html)
- Enable xwayland with `ujust toggle-xwayland` and then set ozone-platform to x11 in `chrome://flags`