I figured it may have been a problem specific to the wireless card you had instead of the mobo so I did a bunch of digging on the model of the BT card when looking for bugs and found this
I’m not sure if this guy is a kernel dev that just happened to be browsing the forums, and this is the ONLY mention I’ve found of this but it sort of makes sense in a twisted sort of way.
TLDR, go to your bios/uefi and disable secure boot and disable fast boot.
Try BT again.
I also found this to be an interesting read and descriptive.
It’s possible your WiFi drivers are signed but the BT driver may not be
I disabled secure boot and fast boot and no dice. Fast boot in ASUS bios was easy to disable, secure boot was kinda sketchy (it isn’t on or off but “standard” or “Other OS”) but I found a command to indicate that I did turn off secure boot
[naive@nixos:~]$ sudo bootctl | cat
System:
Firmware: UEFI 2.80 (American Megatrends 5.27)
Firmware Arch: x64
Secure Boot: disabled
TPM2 Support: yes
Measured UKI: no
Boot into FW: supported
Current Boot Loader:
Product: systemd-boot 256.8
Features: ✓ Boot counting
✓ Menu timeout control
✓ One-shot menu timeout control
✓ Default entry control
✓ One-shot entry control
✓ Support for XBOOTLDR partition
✓ Support for passing random seed to OS
✓ Load drop-in drivers
✓ Support Type #1 sort-key field
✓ Support @saved pseudo-entry
✓ Support Type #1 devicetree field
✓ Enroll SecureBoot keys
✓ Retain SHIM protocols
✓ Menu can be disabled
✓ Boot loader sets ESP information
ESP: /dev/disk/by-partuuid/7f401586-cddf-4fda-94ef-4f9c0dfe18db
File: └─/EFI/systemd/systemd-bootx64.efi
Random Seed:
System Token: set
Exists: yes
Available Boot Loaders on ESP:
ESP: /boot (/dev/disk/by-partuuid/7f401586-cddf-4fda-94ef-4f9c0dfe18db)
File: ├─/EFI/systemd/systemd-bootx64.efi (systemd-boot 256.8)
└─/EFI/BOOT/BOOTX64.EFI (systemd-boot 256.8)
Boot Loaders Listed in EFI Variables:
Title: Linux Boot Manager
ID: 0x0002
Status: active, boot-order
Partition: /dev/disk/by-partuuid/7f401586-cddf-4fda-94ef-4f9c0dfe18db
File: └─/EFI/systemd/systemd-bootx64.efi
Title: UEFI OS
ID: 0x0003
Status: active, boot-order
Partition: /dev/disk/by-partuuid/7f401586-cddf-4fda-94ef-4f9c0dfe18db
File: └─/EFI/BOOT/BOOTX64.EFI
Title: Windows Boot Manager
ID: 0x0000
Status: active, boot-order
Partition: /dev/disk/by-partuuid/b429a9b0-6401-477d-ad31-8f6171d129d2
File: └─/EFI/Microsoft/Boot/bootmgfw.efi
Boot Loader Entries:
$BOOT: /boot (/dev/disk/by-partuuid/7f401586-cddf-4fda-94ef-4f9c0dfe18db)
token: nixos
Default Boot Loader Entry:
type: Boot Loader Specification Type #1 (.conf)
title: NixOS (Generation 28 NixOS Vicuna 24.11.711815.1807c2b91223 (Linux 6.8.9-zen1), built on 2025-01-03)
id: nixos-generation-28.conf
source: /boot//loader/entries/nixos-generation-28.conf
sort-key: nixos
version: Generation 28 NixOS Vicuna 24.11.711815.1807c2b91223 (Linux 6.8.9-zen1), built on 2025-01-03
machine-id: c4ffda5dad814e16883baa67a32ae521
linux: /boot//EFI/nixos/8rrjakh605hmr5rz4n726y1xg07z7ll4-linux-6.8.9-zen1-bzImage.efi
initrd: /boot//EFI/nixos/swbdhgsvvng4apapza5mpxinv2wjkxwj-initrd-linux-6.8.9-zen1-initrd.efi
options: init=/nix/store/4rrpa6x6gz6cp0gcxxc5pvcq2270a9bb-nixos-system-nixos-24.11.711815.1807c2b91223/init loglevel=4
That said, this link you provided is literally someone with my exact wireless/bluetooth card getting bluetooth to work Bluetooth not discovering devices, driver current (Kubuntu 24.04) - Ask Ubuntu
So I am going to dig in and try and figure out how to try what was done there on NixOS, because it SHOULD work. I am fully on team “this is possible” now
Like this has near exact results as that post, notice the rtw89_8851be driver
uname -a; lspci -nnk | grep -iA2 net; lsusb | grep -i 'blue'; sudo dmesg | grep -i firmware; lsmod | grep bluetooth
Linux nixos 6.8.9-zen1 #1-NixOS ZEN SMP PREEMPT_DYNAMIC Thu May 2 17:47:44 UTC 2024 x86_64 GNU/Linux
08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
DeviceName: RTL8111H 1GbE Controller
Subsystem: ASUSTeK Computer Inc. Onboard RTL8111H Ethernet [1043:8677]
Kernel driver in use: r8169
Kernel modules: r8169
09:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:b851]
Subsystem: Foxconn International, Inc. Device [105b:e100]
Kernel driver in use: rtw89_8851be
Bus 001 Device 008: ID 0489:e112 Foxconn / Hon Hai Bluetooth Radio
[ 2.830766] [drm] Loading DMUB firmware via PSP: version=0x02020020
[ 2.831033] [drm] Found VCN firmware Version ENC: 1.33 DEC: 4 VEP: 0 Revision: 3
[ 2.831037] amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware
[ 22.663162] systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
[ 22.929857] rtw89_8851be 0000:09:00.0: loaded firmware rtw89/rtw8851b_fw.bin
[ 22.931436] rtw89_8851be 0000:09:00.0: Firmware version 0.29.41.3 (65cefb31), cmd version 0, type 5
[ 22.931439] rtw89_8851be 0000:09:00.0: Firmware version 0.29.41.3 (65cefb31), cmd version 0, type 3
bluetooth 1097728 42 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
ecdh_generic 16384 2 bluetooth
rfkill 40960 8 asus_wmi,bluetooth,cfg80211
crc16 12288 2 bluetooth,ext4
My idea is as follows:
{ USB_DEVICE(0x0489, 0xe112), .driver_info = BTUSB_REALTEK |
BTUSB_WIDEBAND_SPEECH },
This line right here is for a github repository that purports to be " bluetooth for ubuntu 6.8 kernel "
I can see in the result of my command in the previous post that the id of my device is in the code (0489, e112)
ID 0489:e112 Foxconn / Hon Hai Bluetooth Radio
So I want to see if I can figure out if the version of btusb I am running has this code too…I think that would settle if I have actually have a driver explicitly
If I look at
and search
“0x0489, 0xe112”
I get no results.
but if I remove the 2, there are some interesting lines.
Lines 650-656 are almost what it seems like the file needs,
and more interestingly lines 484-540 call out the realtek 8852 (which my device is NOT) that I kept finding in google search results.
I think that the problem is that there is no line in btusb for my specific bluetooth. I am not sure if the solution is as simple as adding this line or if there are other related things in other files, this is far above my personal knowledge. But I will continue reading
{ USB_DEVICE(0x0489, 0xe112), .driver_info = BTUSB_REALTEK |
BTUSB_WIDEBAND_SPEECH }
Worst case I can install ubuntu on a separate drive and see if I can get bluetooth working to convince myself this is really possible.
With alot of kernel stuff it can be that simple actually, alot of times theres already a function or variable buried in the code that just isnt called or built during src compilation and simply adding a line before recompiling is all thats needed to fix it.
Also, given that it seems to be calling the driver for your device, it may really be as simple as its only getting half the driver.
I’m going to get a copy of the src code for the nixos 24.11 kernel, you mentioned earlier things worked fine in the previous now deprecated version of nixos.
Im going to get a copy of the kernel for the prior version and do an A - B comparison and see if we can narrow it down, if its something really as simple as a compilation option in the btusb file, we should be able to add that in as an argument for a kernel pin in the config and rebuild from the top level instead of doing an imperative edit
This is also worth a read too, it mentions this file in conjunction with a kernel updating breaking connectivity with nixos unstable, this was a few months ago and the unstable version is about what we have now for nixos stable.
We are not the only ones sniffing a kernel bug, take a look at this thread too.
I’m going to get a copy of the src code for the nixos 24.11 kernel, you mentioned earlier things worked fine in the previous now deprecated version of nixos.
I didn’t say that, you might be mixing up one of the referenced threads in this topic with my problem. Bluetooth has never worked for me on NixOS and my install is < 1 month old, only windows BT worked after installing a driver. This is a new build so I haven’t ran anything but Nix on this hardware.
I really appreciate the continued research, yes I do think basically trying a fork of btusb.c is the best next step but I need to read your links…
Do’ly noted, thank you for that, i can subtract prior functionality from the equation
and no problem, i like debugging hardware issues, something really satisfying about it
I found another interesting connection. A comment from the above mention on github references a power state mismanagement, the device more or less goes to sleep on boot and then refuses to wake. Work around was to disable low energy mode in the controller.
i took another look at your dmesg logs, line 1143: [ 0.000000] microcode: updated early: 0x34 -> 0x37, date = 2024-05-29[ 0 - Pastebin.com
[ 30.962569] r8169 0000:08:00.0: can't disable ASPM; OS doesn't have ASPM control
There might be a connection here, ASPM is automatic state power management.
I also double checked the code for the driver your kernel is loading and this option is available for that driver, so despite the option not technically being listed in the nixpkg options repo, i think its still worth trying.
hardware.bluetooth.settings.General.ControllerMode = "bredr";
EDIT: Disregard this, your BT device driver (realtek) dont include Low Energy state as an available option to the controller so setting this wont effect anything. Refer to drivers/bluetooth/btusb.c and read the statements for the MEDIATEK drivers which were mentioned in github post DO include a controller option for LE states but the realtek devices do not
Alright.
I forked the zen kernel im using and patched in the device for your BT module and ran a rebuild on my own machine with success. Heres that snip, give it a whirl. its building from src, so it wil take a while to fully complete. Do a full reboot after using this command:
sudo shutdown -r now
Heres the custom kernel package that should just drop into your config.
EDIT: Copied wrong snip, updated
boot.kernelPackages = let
linux_zen_pkg = { fetchurl, buildLinux, ...}@args:
buildLinux (args // rec{
version = "6.8.9-zen1";
modDirVersion = version;
src = pkgs.fetchurl {
url =
"https://github.com/Mephist0phel3s/zen1-6.8.9/archive/refs/tags/v6.8.9-zen1.tar.gz";
sha256 =
"sha256-8bAzJ2us4swMTZ4c4DAEqbpAj98cjgxUe8vBouUdjDU=";
};
} // (args.argsOverride or { }));
linux_zen = pkgs.callPackage linux_zen_pkg { };
in pkgs.recurseIntoAttrs (pkgs.linuxPackagesFor linux_zen);
Trying now
Quick question (while I wait for the kernel to build)
{ USB_DEVICE(0x0489, 0xe112), .DRIVER_INFO = BTUSB_REALTEK |
BTUSB_WIDEBAND_SPEECH },
will it cause problems that .DRIVER_INFO is capitalized?
Will it get interpreted the same way as .driver_info?
Fuck i didnt even notice that, and yeah probably. Let me fix that
Thanks, if you weren’t around I was about to fork your fork. I’ll wait a few mins
Fixed, heres the new snip
boot.kernelPackages = let
linux_zen_pkg = { fetchurl, buildLinux, ...}@args:
buildLinux (args // rec{
version = "6.8.9-zen1-rev1"; #EDIT: Forgot to add the -rev1 at the end on the first post, this one builds
modDirVersion = version;
src = pkgs.fetchurl {
url =
"https://github.com/Mephist0phel3s/zen1-6.8.9/archive/refs/tags/v6.8.9-zen1-rev1.tar.gz";
sha256 =
"sha256-5JL0B6b9o5bx9M8viaiN4RKCvuON/b3pMZ8yfDjH25Y=";
};
} // (args.argsOverride or { }));
linux_zen = pkgs.callPackage linux_zen_pkg { };
in pkgs.recurseIntoAttrs (pkgs.linuxPackagesFor linux_zen);
and yeah, we had the same thought. Same page club xD
Well, now its not building. Give me a minute i need to figure out why its suddenly wanting to fail building
Edit: Sigh. Github.
Edit 2: for whatever reason my commit didnt make it to the release so im doing it AGAIN.
ALRIGHT.
This one DEFINITELY builds AND has the patch. Fuck i need to read the github manual again
boot.kernelPackages = let
linux_zen_pkg = { fetchurl, buildLinux, ...}@args:
buildLinux (args // rec{
version = "6.8.9-zen1-mephi";
modDirVersion = version;
src = pkgs.fetchurl {
url =
"https://github.com/Mephist0phel3s/zen1-6.8.9/archive/refs/tags/v6.8.9-zen1-mephi.tar.gz";
sha256 =
"sha256-OFjUz997M23kU2LJ5oNshzWiE2njRQDKRefsXBnfprw=";
};
} // (args.argsOverride or { }));
linux_zen = pkgs.callPackage linux_zen_pkg { };
in pkgs.recurseIntoAttrs (pkgs.linuxPackagesFor linux_zen);
Ok that failed to build for me,
GOT:
QUESTION: Support for tracing block IO actions, NAME: BLK_DEV_IO_TRACE, ALTS: Y/n/?, ANSWER:
GOT:
QUESTION: Support BTF function arguments for probe events, NAME: PROBE_EVENTS_BTF_ARGS, ALTS: Y/n/?, ANSWER:
GOT:
QUESTION: Enable kprobes-based dynamic events, NAME: KPROBE_EVENTS, ALTS: Y/n/?, ANSWER:
GOT:
QUESTION: Do NOT protect notrace function from kprobe events, NAME: KPROBE_EVENTS_ON_NOTRACE, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Enable uprobes-based dynamic events, NAME: UPROBE_EVENTS, ALTS: Y/n/?, ANSWER: y
GOT: y
QUESTION: Synthetic trace events, NAME: SYNTH_EVENTS, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: User trace events, NAME: USER_EVENTS, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Histogram triggers, NAME: HIST_TRIGGERS, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Trace event injection, NAME: TRACE_EVENT_INJECT, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Add tracepoint that benchmarks tracepoints, NAME: TRACEPOINT_BENCHMARK, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Ring buffer benchmark stress tester, NAME: RING_BUFFER_BENCHMARK, ALTS: N/m/y/?, ANSWER: n
GOT: n
QUESTION: Show eval mappings for trace events, NAME: TRACE_EVAL_MAP_FILE, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Record functions that recurse in function tracing, NAME: FTRACE_RECORD_RECURSION, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Validate RCU is on during ftrace execution, NAME: FTRACE_VALIDATE_RCU_IS_WATCHING, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Perform a startup test on ftrace, NAME: FTRACE_STARTUP_TEST, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Verify compile time sorting of ftrace functions, NAME: FTRACE_SORT_STARTUP_TEST, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Ring buffer startup self test, NAME: RING_BUFFER_STARTUP_TEST, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Verify ring buffer time stamp deltas, NAME: RING_BUFFER_VALIDATE_TIME_DELTAS, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Test module to create a preempt / IRQ disable delay thread to test latency tracers, NAME: PREEMPTIRQ_DELAY_TEST, ALTS: M/n/?, ANSWER:
GOT:
QUESTION: Test module for in-kernel kprobe event generation, NAME: KPROBE_EVENT_GEN_TEST, ALTS: M/n/?, ANSWER:
GOT:
GOT: *
GOT: * Runtime Verification
GOT: *
QUESTION: Runtime Verification, NAME: RV, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Remote debugging over FireWire early on boot, NAME: PROVIDE_OHCI1394_DMA_INIT, ALTS: Y/n/?, ANSWER:
GOT:
GOT: *
GOT: * Sample kernel code
GOT: *
QUESTION: Sample kernel code, NAME: SAMPLES, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Filter access to /dev/mem, NAME: STRICT_DEVMEM, ALTS: Y/n/?, ANSWER: y
GOT: y
QUESTION: Filter I/O access to /dev/mem, NAME: IO_STRICT_DEVMEM, ALTS: Y/n/?, ANSWER: y
GOT: y
GOT: *
GOT: * x86 Debugging
GOT: *
QUESTION: Enable verbose x86 bootup info messages, NAME: X86_VERBOSE_BOOTUP, ALTS: Y/n/?, ANSWER:
GOT:
QUESTION: Early printk, NAME: EARLY_PRINTK, ALTS: Y/n/?, ANSWER:
GOT:
QUESTION: Early printk via EHCI debug port, NAME: EARLY_PRINTK_DBGP, ALTS: Y/n/?, ANSWER:
GOT:
QUESTION: Early printk via the xHCI debug port, NAME: EARLY_PRINTK_USB_XDBC, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Dump the EFI pagetable, NAME: EFI_PGT_DUMP, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Set upper limit of TLB entries to flush one-by-one, NAME: DEBUG_TLBFLUSH, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: x86 instruction decoder selftest, NAME: X86_DECODER_SELFTEST, ALTS: N/y/?, ANSWER:
GOT:
GOT: IO delay type
GOT: > 1. port 0x80 based port-IO delay [recommended] (IO_DELAY_0X80)
GOT: 2. port 0xed based port-IO delay (IO_DELAY_0XED)
GOT: 3. udelay based port-IO delay (IO_DELAY_UDELAY)
GOT: 4. no port-IO delay (IO_DELAY_NONE)
CHOICE: 1-4?, ANSWER:
GOT:
QUESTION: Debug boot parameters, NAME: DEBUG_BOOT_PARAMS, ALTS: Y/n/?, ANSWER:
GOT:
QUESTION: CPA self-test code, NAME: CPA_DEBUG, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Debug low-level entry code, NAME: DEBUG_ENTRY, ALTS: Y/n/?, ANSWER:
GOT:
QUESTION: NMI Selftest, NAME: DEBUG_NMI_SELFTEST, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Debug the x86 FPU code, NAME: X86_DEBUG_FPU, ALTS: Y/n/?, ANSWER:
GOT:
QUESTION: ATOM Punit debug driver, NAME: PUNIT_ATOM_DEBUG, ALTS: M/n/y/?, ANSWER:
GOT:
GOT: Choose kernel unwinder
GOT: > 1. ORC unwinder (UNWINDER_ORC)
GOT: 2. Frame pointer unwinder (UNWINDER_FRAME_POINTER)
CHOICE: 1-2?, ANSWER:
GOT:
GOT: *
GOT: * Kernel Testing and Coverage
GOT: *
GOT: *
GOT: * KUnit - Enable support for unit tests
GOT: *
QUESTION: KUnit - Enable support for unit tests, NAME: KUNIT, ALTS: N/m/y/?, ANSWER: n
GOT: n
QUESTION: Notifier error injection, NAME: NOTIFIER_ERROR_INJECTION, ALTS: N/m/y/?, ANSWER: n
GOT: n
QUESTION: Fault-injections of functions, NAME: FUNCTION_ERROR_INJECTION, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Fault-injection framework, NAME: FAULT_INJECTION, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Code coverage for fuzzing, NAME: KCOV, ALTS: N/y/?, ANSWER:
GOT:
GOT: *
GOT: * Runtime Testing
GOT: *
QUESTION: Runtime Testing, NAME: RUNTIME_TESTING_MENU, ALTS: N/y/?, ANSWER: n
GOT: n
QUESTION: Memtest, NAME: MEMTEST, ALTS: Y/n/?, ANSWER: y
GOT: y
QUESTION: Microsoft Hyper-V driver testing, NAME: HYPERV_TESTING, ALTS: N/y/?, ANSWER:
GOT:
GOT: *
GOT: * Rust hacking
GOT: *
GOT: #
GOT: # configuration written to .config
GOT: #
GOT: make[1]: Leaving directory '/build/zen1-6.8.9-6.8.9-zen1-mephi/build'
GOT: make: Leaving directory '/build/zen1-6.8.9-6.8.9-zen1-mephi'
error: unused option: DAMON_DBGFS
error: unused option: DRM_DP_AUX_CHARDEV
error: unused option: DRM_DP_CEC
error: unused option: MODULE_COMPRESS_XZ
warning: unused option: POWER_RESET_GPIO
warning: unused option: POWER_RESET_GPIO_RESTART
error: unused option: SLS
error: unused option: ZRAM_DEF_COMP_ZSTD
error: builder for '/nix/store/dvr9b70afwg6343j60ljwy4m5zaayvxd-linux-config-6.8.9-zen1-mephi.drv' failed with exit code 255;
last 25 log lines:
> GOT: *
> GOT: * Runtime Testing
> GOT: *
> QUESTION: Runtime Testing, NAME: RUNTIME_TESTING_MENU, ALTS: N/y/?, ANSWER: n
> GOT: n
> QUESTION: Memtest, NAME: MEMTEST, ALTS: Y/n/?, ANSWER: y
> GOT: y
> QUESTION: Microsoft Hyper-V driver testing, NAME: HYPERV_TESTING, ALTS: N/y/?, ANSWER:
> GOT:
> GOT: *
> GOT: * Rust hacking
> GOT: *
> GOT: #
> GOT: # configuration written to .config
> GOT: #
> GOT: make[1]: Leaving directory '/build/zen1-6.8.9-6.8.9-zen1-mephi/build'
> GOT: make: Leaving directory '/build/zen1-6.8.9-6.8.9-zen1-mephi'
> error: unused option: DAMON_DBGFS
> error: unused option: DRM_DP_AUX_CHARDEV
> error: unused option: DRM_DP_CEC
> error: unused option: MODULE_COMPRESS_XZ
> warning: unused option: POWER_RESET_GPIO
> warning: unused option: POWER_RESET_GPIO_RESTART
> error: unused option: SLS
> error: unused option: ZRAM_DEF_COMP_ZSTD
For full logs, run 'nix-store -l /nix/store/dvr9b70afwg6343j60ljwy4m5zaayvxd-linux-config-6.8.9-zen1-mephi.drv'.
error: 1 dependencies of derivation '/nix/store/slvx02ngnwxzixpzfys9aq8sijblj4i6-linux-6.8.9-zen1-mephi.drv' failed to build
error: 1 dependencies of derivation '/nix/store/74awgykyc8hs49f004wmc59m4r3nlb6y-nixos-system-nixos-24.11.711815.1807c2b91223.drv' failed to build
going to try and figure out how to get full logs