> Well, the good news is that /var/log/messages contains an error > message that the ALW page you cite suggests a solution for. The bad > news is that the solution is "remove all power sources to force the > device to reload the firmware". This box is a laptop, and it doesn't > look like disconnecting the battery is going to be any straightforward > operation. Unless: the Bluetooth controller I'm trying to use is a USB > dongle, can I achieve the same effect by just pulling it out of the > USB port?
It's difficult to say for certain. But somehow I think you did try replugging the usb dongle as a troubleshooting step? If not, that would be a one thing to try to fix the issue. The thing is, It's not exactly clear to me if the firmware is loaded or not and I'm a bit out of scope at this point. One interesting thing I've read some time ago and it might be of use here, was that you can force a cold-boot (Should have the same effect as with waiting a bit without power completely) by editing kernel parameters. https://www.kernel.org/doc/html/v6.11/admin-guide/kernel-parameters.html ``` reboot= [KNL] Format (x86 or x86_64): [w[arm] | c[old] | h[ard] | s[oft] | g[pio]] | d[efault] \ [[,]s[mp]#### \ [[,]b[ios] | a[cpi] | k[bd] | t[riple] | e[fi] | p[ci]] \ [[,]f[orce] Where reboot_mode is one of warm (soft) or cold (hard) or gpio (prefix with 'panic_' to set mode for panic reboot only), reboot_type is one of bios, acpi, kbd, triple, efi, or pci, reboot_force is either force or not specified, reboot_cpu is s[mp]#### with #### being the processor to be used for rebooting. ``` And if I'm not wrong (would love some input from others who edited their kernel command-line arguments) it should be possible to do with: (kernel-arguments) Example for how kernel-arguments is used: https://guix.gnu.org/manual/en/html_node/Using-the-Configuration-System.html Also it might be possible that during startup of pc, there is a way to also for the time being use one or another parameter. -- Hope that helps, Ignas
