Still if not for you, all efforts would have been futile. Thank you for your valuable inputs.
Yash Raj
I am yashraj (snaps a finger)
- 1 Post
- 11 Comments
Thank you everyone for your valuable time. Cheers!
Went ahead and explained it even, also posted on the original arch forum.
Brother guess what? It actually fixed it. OMG I am soo happy, at last it got fixed, i was trying it for the last week and didn’t work, but you swoop and in an instant fixed it. I just can’t thank you enough really. I am really greatful to you.

I’ll do that. Thank you so much 🤗
So fast. Wow I couldn’t even find that resource in all my searching. So Nows the tough part, I hoped I was an expert nixos user. I will try to implement this somehow (cough vibe code), but any more hints would be appreciated. One thing I know the direction to go is patching kernel, which I have seen a repo do, so I will try to copy that.
First of all thank you. So yes I have a dual boot system, with windows and nixos.
I tried turning the bluetooth off in windows and booting into nixos, but it didn’t work. And I am sure it’s not a hardware issue because bluetooth works in windows.
I tried cold booting as well with same results.
There are no proper logs as well that suggest anything, in lsmod, lsusb, hciconfig, dmesg (hci capabilities -22 was only one, which I think is just cosmetic).
The scan on in bluetoothctl only shows the laptop’s mac address which means bluetooth does work but somehow it’s not finding the devices to connect to.
This is my exact model: FX608JH ASUS TUF Gaming F16 (2025)
So I tried that and bluetooth also didn’t work there. I even went ahead and tried multiple distros to see if it was specific to nixos with same results.



So turns out making this patch upstream so it gets into the Linux kernel is not as easy as to open to pull request. There’s this setting up of git email and what not, but with my searches it seems this patch is already made by someone and should be implemented in the kernel 6.19, but take this with a grain of salt. I will update this post if I find the patch file but for now I am assuming this fixed in 6.19. And yes I was hesitant to to try this but the desperation got over me, as I just can’t have anything “not work” it irks me the wrong way, so I just went ahead with it.