[Help]: bluetoothctl scan on: No default controller available #507
Comments
|
Hi @HamzaHajeir You are doing some things that I have no experience with. A quick look and the only thing that stands out is the following: That tells me you have probably updated the firmware but having two versions of each firmware file may or may not be bad but I have not tested it. You might want to delete the .zst files. I'll ponder this issue. |
|
@morrownr Thanks for your quick response. AFAIK the zst files are just compressed files, not executable ones, therefore I don't see an issue (But maybe I'm wrong?). What I'm wondering is the question what triggers btmtk module? Is it these firmware files or another source? In the Ubuntu that runs over VMBox (And as I've seen in other issues while searching), btmtk presents when running |
Yes, compressed binary files. The kernel reads compressed and non-compressed binary files. You have both. Tell me which one the kernel is using? |
I've just renamed the .bin files and here's:
It seems the fail line is reduced by one :). UPDATE: Even when flipping the active one (renaming back the .bin files and renaming .zst files), produces the same error line. |
The firmware issue I mentioned is likely not the source of your problem. I'll do some more research on that and update my firmware guide but let's drop that issue for now.
I do not know what WSL is. Can you enlighten me? FYI: This site does have heavy traffic but it is not a social media site so it can take some time for replies on specific topics... especially on a topic like this. Why? My history started with learning to program with FORTRAN, My history of small computer operating systems is: CP/M. PC-DOS, DR-DOS, OS/2 and Linux. I have almost no experience with Windows. There are a lot of very smart people, including Linux kernel devs, that stop by at times and some may have Windows experience but this may not be the optimal place for you to get help... but I don't know that for sure. |
It's Windows Subsystem for Linux. I'm also new into using this. I'm new to it. But the experience is too much better than VM. I might consider immigrating into Linux sometime in future, not ready for that atm. Setup another OS? my memory is almost full :.
I see your point, I appreciate your trying to help out. Bue me also don't know where the most suitable place to ask. WSL2 repository have issues section disabled. Update, I've just found a place to raise the issue (microsoft/WSL#12048). Hope they come with real help. |
I understand. Maybe this is a good place if you are not in a hurry. Where would I go if I want to learn more about WSL?
I've been using Linux since 1994 so I have some experience... kidding. Something to consider: One of the best ways to learn Linux is to grab an old desktop or laptop that is still functional but not used anymore... those can usually be found found in many places for nothing... maybe in your closet. My main dev box here is 11 years old and it is faster than I need. My point being is that we can get you going with Linux on a system that would not support Windows 11, 10 or ever 8... probably 7. That could save you the trouble of messing with WSL. |
Thank you for your patience and help. I'm not in a hurry. Per anything new to me, I personally prefer to watch an introductory video, here's a top on search on Youtube: https://www.youtube.com/watch?v=qYlgUDKKK5A&t=9s . Ofcourse there's more. And here's an official document for WSL: https://learn.microsoft.com/en-us/windows/wsl/about. It also provides some videos.
I see, I have another PC but I have one monitor now, that PC keeps an old state of files there :). I'll check if a too old laptop is working xD. But per the project I work on, yet speed of compilation matters, but more importantly the apparently new Bluetooth standard (BLE) is supported. |
|
What is your status? I have not run across anything that appears to be of use. |
It should be something with WSL, however the assigned person closed the issue with unreasonable argument. microsoft/WSL#12048 |
That means "This would take a lot of work and I don't feel like messing with it." |
Checklist
uname
lsusb
rfkill
dkms
iw
What happened?
I have WSL and want to manage bluetooth from within it.
I've followed this instruction to build the custom WSL, including all the required checks into .config file.
Here's the latest .config file content that built the latest WSL firmware: https://pastebin.com/5CBrBf7c
And have used usbipd to share and attach the bluetooth device through:
usbipd bind --busid={BUSID}usbipd attach --wsl --busid={BUSID}Where both run successfully, and:
usbipd listgives:However, running
bluetoothctl scan onresult inNo default controller available.My finding concludes that btmtk module is missing within the system. And I don't know how to find/have/run it.
From my research I've registered many useful commands, here's the outputs of them:
uname -a:lsb_release -asystemctl status bluetooth:sudo dmesg | grep firmware:Note I've followed this procedure (#3) to include
BT_RAM_CODE_MT7961_1_2_hdr.binand other files, adding all files.Therefore:
ls -a /lib/firmware/mediatek | grep MT7961:lsusb -v -s 001:003(Note 003 is the corresponding device ID):hciconfig -a:rfkillShows unblocked hard and software:lsmod | grep -i bt- This one which shows me that the module MTK module is missing:And finally:
journalctl --dmesg --boot=-0 --grep blueWhat could be the issue? And how to solve it?
Note that I've tried running the bluetooth within Ubuntu from VMBox and it does work from within. Ofcourse when the bluetooth adapter not attached to WSL.
The text was updated successfully, but these errors were encountered: