search

microsoft / WSL

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

WSL2 Kernel Add Bluetooth Support to microsoft-standard-WSL2 #12234

Open yaplej opened 5 days ago

yaplej commented 5 days ago

I am trying to use the development environment for Home Assistant in VS Code using Docker Desktop. The Integration I am working on requires bluetooth connection to a piece of hardware. So the easiest way to get that working would be to pass a USB Bluetooth adapter to WSL.

That much works but once the USB bluetooth adapter is recognized by the container it wont load the bluetooth drivers/module because the WSL kernel does not have those enabled.

Once the USB bluetooth device is passed to the WSL container it should be able to use it.

Tried to build a custom kernel for using with WSL & Docker but didn't get it working.

(https://github.com/docker/for-win/issues/14284)

github-actions[bot] commented 5 days 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:

Closed similar issues:

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

yaplej commented 5 days ago

/feature

github-actions[bot] commented 5 days ago
Diagnostic information ``` Found '/feature', adding tag 'feature' ```
github-actions[bot] commented 5 days 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'.
yaplej commented 4 days ago

/emailed-logs

github-actions[bot] commented 4 days ago
Diagnostic information ``` Found '/emailed-logs', adding tag 'emailed-logs' ```
borjamunozf commented 1 day ago

Did you build a custom kernel with this config?

CONFIG_BT=y

which Bluetooh adapter/brand is it?

Build custom kernel:

sudo apt-get update
sudo apt-get install -y build-essential flex bison dwarves libssl-dev libelf-dev bc

git clone --branch linux-msft-wsl-5.15.167.4 https://github.com/microsoft/WSL2-Linux-Kernel.git --progress --depth 1

cd WSL2-Linux-Kernel

vim Microsoft/config-wsl

Finally:

echo n | make KCONFIG_CONFIG=Microsoft/config-wsl -j$(nproc) bzImage

Check again.