github-actions[bot]
commented
3 weeks ago 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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com 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:
- glxgears displays black screen, no gears (#7981), similarity score: 0.72
- Different GPU getting detected inside devcontainer and WSL2 Ubuntu distro (#9631), similarity score: 0.71
Closed similar issues:
- KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied (#9662), similarity score: 0.76
- No OpenGL acceleration on VEGA 8 igpu (#8937), similarity score: 0.74
- Microsoft Dev Kit 2023 Windows 11 ARM WSL2 - No Graphics Hardware Acceleration Support (#9154), similarity score: 0.71
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
Ailina0728
Windows Version
Microsoft Windows [版本 10.0.22621.3447]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
1.Newly installed WSL2 2.run
apt install vainfo mesa-utils3.runglxinfo -B4.runexport LIBVA_DRIVER_NAME=d3d125.runvainfo6:runvainfo --display drm --device /dev/dri/renderD128vainfo --display drm --device /dev/dri/card07.runglxgearsExpected Behavior
After running
glxinfo -Band confirming that the Device and OpenGL renderer are using D3D12 (Intel (R) UHD Graphics 770), running vainfo will provide complete support information for exampleActual Behavior
There was an error when entering 'vainfo'
But when I entered
vainfo -- display drm -- device/dev/dri/renderD128, there was no errorThe result of entering
vainfo -- display drm -- device/dev/dri/card0is the same as above After re-verifying and enteringglxgears, I observed the window in the process of rendering, and in the task manager, I noticed that about half of the Intel GPU's workload is attributed to 3D rendering.Why does entering 'vainfo' prompt 'd3d12 driver parameter error 18', and what other verification methods are available
Diagnostic Logs