JuliaGPU
No post-Meteor Lake support via WSL2
For my device (Lunar Lake ARC 140V) I am able to get basic functionality in native windows. However, my impression that full usage via WSL2 is currently not possible? WSL2 natively installs Linux Kernel 5.15 (I believe); I have tried to manually compile a more updated kernel, but the latest offered by Microsoft at this moment is 6.6 (see releases of https://github.com/microsoft/WSL2-Linux-Kernel) whereas it appears Lunar Lake requires 6.11. (Symptomatically, WSL just does not recognize my system as having any GPU.) This would appear to affect devices starting with Meteor Lake, which requires 6.7.
Is there a workaround to utilize a more recent kernel for WSL? If not, I thought it might be worth having this incompatibility documented while waiting for WSL to update.
@maleadt Do we have workaround for this, I have tried WSL2 in the past tests that fail are specific to single/double precision types etc., but rest of them use to work fine.
I do not have a workaround. Microsoft seems to document that using a v6 kernel is possible if you compile it yourself, as you probably did: https://learn.microsoft.com/en-us/community/content/wsl-user-msft-kernel-v6
Native (i.e. non-WSL) use of oneAPI.jl is possible, but limited due to the lack of vendor libraries. Adding support for those is a nontrivial amount of work, and not something I have time for right now. I was waiting for the new Julia C++ FFI to mature so that we can do away with the vendor library wrappers, hopefully extending support of vendor libraries to native Windows. But that is similarly not for the immediate future.
So I'd still try to upgrade the kernel in your WSL2 install.
Hi Tim, thank you for the quick response. Indeed, those Microsoft instructions point to the same repo I linked above. That repo contains WSL Linux kernel sources only up to 6.6 (at the time of writing). Having tried 6.6, it does not resolve my issue. I'm happy to try again once the Microsoft repo makes available a more up-to-date kernel. (Whenever that is, hopefully with the next LTS kernel?)