diff options
| author | Simon Rettberg | 2016-10-20 15:26:36 +0200 |
|---|---|---|
| committer | Simon Rettberg | 2016-10-20 15:26:36 +0200 |
| commit | 27594b6b603b8d1a10c398c21b6a0c8958b5b477 (patch) | |
| tree | 4dcaa24712c91d37d00f25ecb41b81003aeb73bb /remote/modules/debug-report-bwlp/data/opt/openslx/bin/debug_report | |
| parent | [run-virt] More cleanup; kill legacy support, rename and move includes, kill ... (diff) | |
| download | tm-scripts-27594b6b603b8d1a10c398c21b6a0c8958b5b477.tar.gz tm-scripts-27594b6b603b8d1a10c398c21b6a0c8958b5b477.tar.xz tm-scripts-27594b6b603b8d1a10c398c21b6a0c8958b5b477.zip | |
[rfs-stage32] Check for nvidia.ko first, then for whitelisted pciids
We might have a supported onboard card AND a whitelisted nvidia card.
Stage 3.1 will load the nvidia kernel modules all right, but then
stage 3.2 sees the whitelisted onboard card, enables "force 3d" for
vmware and skips the part where it will load the nvidia user space libs,
resulting in an unusable client.
Check for the nvidia kernel module first and only check for a supported
onboard card if none was found to prevent this situation from occuring.
Diffstat (limited to 'remote/modules/debug-report-bwlp/data/opt/openslx/bin/debug_report')
0 files changed, 0 insertions, 0 deletions