mirror of
https://github.com/Kron4ek/Conty
synced 2024-11-16 19:50:06 +01:00
Update README.md
This commit is contained in:
parent
ff03775b24
commit
3b3b00e3c4
1 changed files with 3 additions and 1 deletions
|
@ -130,7 +130,7 @@ If you just want a sandboxing functionality but don't need a container with a fu
|
|||
|
||||
## Known issues
|
||||
|
||||
Nvidia users with the proprietary driver will experience graphics acceleration problems if their Nvidia kernel module version mismatches the version of the Nvidia libraries inside Conty. This applies only to the proprietary driver, Nouveau should work fine without any additional actions (of course, if your GPU is supported by it).
|
||||
Nvidia users with the proprietary driver will experience graphics acceleration problems (probably graphical applications won't work at all) if their Nvidia kernel module version mismatches the version of the Nvidia libraries inside Conty. This applies only to the proprietary driver, Nouveau should work fine without any additional actions (of course, if your GPU is supported by it).
|
||||
|
||||
For example, if the version of your Nvidia kernel module is 460.56 and the libraries inside the container are from 460.67 version, then graphics acceleration will not work.
|
||||
|
||||
|
@ -141,6 +141,8 @@ export NVIDIA_FIX=1
|
|||
./conty.sh glxgears
|
||||
```
|
||||
|
||||
Another and more reliable solution is to install the same driver version as included inside Conty, which is usually the latest non-beta version. You can see the exact driver version in pkg_list.txt attached to each Conty release.
|
||||
|
||||
## How to update
|
||||
|
||||
There are three main ways to update Conty and get the latest packages, use whichever works best for you.
|
||||
|
|
Loading…
Reference in a new issue