wslg: cannot open display: :0 with "Illegal instruction at address 0x7f26b2a00c5c" at Intel GPU driver
Windows build number:
10.0.22621.675
Your Distribution version:
Ubuntu-22.04
Your WSL versions:
WSL-Version: 0.70.4.0 Kernelversion: 5.15.68.1 WSLg-Version: 1.0.45 MSRDC-Version: 1.2.3575 Direct3D-Version: 1.606.4 DXCore-Version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows Version: 10.0.22621.675
Steps to reproduce:
- system: Acer Swift 1 laptop with Intel Pentium Silver N6000 cpu Note: the N6000 doesn’t support avx or bmi2 instructions
- no X11 app is starting
- from the end of /mnt/wslg/stderr.log:
(EE) 39: /usr/bin/Xwayland (_start+0x25) [0x556f52a74265]
(EE)
(EE) Illegal instruction at address 0x7f26b2a00c5c
(EE)
Fatal server error:
(EE) Caught signal 4 (Illegal instruction). Server aborting
(EE)
[11:51:56:429] [10:10] [ERROR][com.freerdp.core.gcc] - Unknown GCC client data block: 0xC00C
WSL logs:
weston.log stderr.log pulseaudio.log
WSL dumps:
No response
Expected behavior:
X11 apps should start
Actual behavior:
Message “… cannot open display: :0” in terminal and Illegal instruction logged to /mnt/wslg/stderr.log:
(EE) Illegal instruction at address 0x7f26b2a00c5c
(EE)
Fatal server error:
(EE) Caught signal 4 (Illegal instruction). Server aborting
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 19 (2 by maintainers)
The old Intel GPU driver 27.20.100.9466 works for X11 apps with WSLg on my laptop.
Unfortunately this driver has a black screen issue after returing from powersave (after opening the laptop lid) .
But maybe usefull for people with desktop systems?!
Just come upon this, now see there is hope as of yesterday: https://community.intel.com/t5/Graphics/Illegal-instruction-with-Intel-GPU-driver/m-p/1439002/highlight/true#M112026
Looks like Intel will not investigate. They set the N600x iGPU (released in 2021!) to legacy support. Whatever caused the issue will not get fixed, only critical security bugs.
I posted a summary of the situation on Intels community at Reddit: https://www.reddit.com/r/intel/comments/z5cjsl/intel_does_not_fix_grafic_driver_issues_for/
You are very welcome to comment there.
If we can’t get help from Microsoft, who is able to escalate our problem inside Intel, then we are done IMO.
Thanks @gmsh for commenting at the Intel forum, shows them the issue is more common to the N600x.
@Microsoft: is there any conversation between developers at Microsoft and Intel about this issue?