search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.18k stars 805 forks source link

Custom kernel not being recognized. #11779

Closed anshium closed 3 weeks ago

anshium commented 1 month ago

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

  1. Custom kernel located at C:\Sources\vmlinux
  2. Modify .wslconfig (in C:\Users\Admin) to: 
    [wsl2]
kernel=C:\\Sources\\vmlinux
  3. Open Powershell.
  4. wsl --shutdown
  5. wsl -d Ubuntu-20.04
  6. 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

github-actions[bot] commented 1 month 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 scipt will output the path of the log file once done. 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!

Closed similar issues:

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

anshium commented 1 month ago

WslLogs-2024-07-14_20-22-15.zip

github-actions[bot] commented 1 month ago
Diagnostic information ``` .wslconfig found Custom kernel found: 'C:\Sources\vmlinux' Detected appx version: 2.2.4.0 ```
zcobol commented 1 month ago

@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.

0xbadfca11 commented 1 month ago

5.15.153.1-microsoft-standard-WSL2+ is not original kernel. Microsoft original kernel version strings have not a +.

craigloewen-msft commented 1 month ago

@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!

anshium commented 1 month ago

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.