Closed anshium closed 3 weeks ago
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.
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!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
@anshium to load the new kernel a wsl --shutdown
is required. You didn't specify this step, therefore sorry if you did restart the service already.
5.15.153.1-microsoft-standard-WSL2+
is not original kernel.
Microsoft original kernel version strings have not a +
.
@0xbadfca11 is correct! It looks like your custom kernel is being accurately loaded. You can change your kernel name to make it more obvious.
@anshium please confirm this is the case and I'll close this issue out. THanks for filing!
Thanks everyone for the insights.
I was trying to setup a depth camera on wsl and tried to remake the kernel with after changing certain settings with the hope of it being detected. Since the name was similar and hoped that the new kernel is named as the file location, I thought it is the same as original.
While the camera problem still exists, I think this issue is resolved.
Thanks again.
Windows Version
Microsoft Windows [Version 10.0.22631.3880]
WSL Version
0.0.0.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
wsl --shutdown
wsl -d Ubuntu-20.04
uname -r
(in wsl)The kernel is still the original
5.15.153.1-microsoft-standard-WSL2+
. This means that it did not pick up the custom kernel.Expected Behavior
I expected to see my own kernel to be listed after performing
uname -r
.Actual Behavior
The actual behavior was the original kernel being listed.
Diagnostic Logs
No response