I don't think that's necessary, and may even be counterproductive while you are trying to enable the bluetooth functionality.ktat wrote:before entering rfkill list, I clicked on the bluetooth icon to turn the daemon on.
This sounds like a case of problematic inbuilt bluetooth devices, as I mentioned in the first post. Comparing the Puppy/Fedora lsmod results, I see one significant one which is absent in Puppy - hp_wireless
Apparently this kernel module supports the hardware wifi switch on HP laptops.
In Tahrpup6 I can see that the hp_wireless module was not enabled in the kernel configuration. So it's feasible you could lobby one of the Tahrpup developers (rcrsn51 springs to mind) to compile this module for you and provide it as a dotpet.
But before you do this, try the fixes mentioned here -
https://forums.gentoo.org/viewtopic-p-7 ... ml#7499484
You will see that one of the suggested fixes is to cycle the wireless switch, which adds additonal weight to my suspicion that the hp_wireless module may be required.
And I still think the "btcoex_enable=1" parameter should be used.