Skip to content
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

Switching MESA_D3D12_DEFAULT_ADAPTER_NAME to NVIDIA defaults to llvmpipe rendering #12412

Open
1 of 2 tasks
Kulsgam opened this issue Dec 26, 2024 · 3 comments
Open
1 of 2 tasks

Comments

@Kulsgam
Copy link

Kulsgam commented Dec 26, 2024

Windows Version

Microsoft Windows [Version 10.0.26100.2605]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 24.04

Other Software

No response

Repro Steps

Steps were followed from here
sudo apt install mesa-utils
nvidia-smi
MESA_D3D12_DEFAULT_ADAPTER_NAME=NVIDIA glxinfo | grep "OpenGL renderer"

Expected Behavior

The following output should be present:

MESA: error: ZINK: failed to choose pdev
glx: failed to create drisw screen
OpenGL renderer string: D3D12 (NVIDIA GeForce RTX 4060 Laptop GPU)

Actual Behavior

The following output is given by running the glxinfo command as outlined in "Repro Steps":

MESA: error: ZINK: failed to choose pdev
glx: failed to create drisw screen
OpenGL renderer string: llvmpipe (LLVM 17.0.6, 256 bits)

Running the same command without the env variable gives the following:

MESA: error: ZINK: failed to choose pdev
glx: failed to create drisw screen
OpenGL renderer string: D3D12 (Intel(R) Arc(TM) Graphics)

It uses the integrated graphics card but refuses to use the Nvidia Graphics card despite nvidia-smi detecting it.
How can I get it to use the Nvidia Graphics card?

Diagnostic Logs

WslLogs-2024-12-26_17-48-04.zip

Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Copy link

Diagnostic information
Issue was edited and new log file was found: https://github.com/user-attachments/files/18250383/WslLogs-2024-12-26_17-48-04.zip
Detected appx version: 2.3.26.0

@Kulsgam
Copy link
Author

Kulsgam commented Dec 28, 2024

I've already attached the log file, why does it still have the label "needs-author-feedback?"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant