The easiest way to get Bluetooth is to install all the proprietary Atheros firmware with these commands: wget http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-atheros_20190114-2_all.deb sudo dpkg -i firmware-atheros_20190114-2_all.deb
If you want to only install the proprietary firmware for the Atheros Bluetooth, you need to do it this way: sudo apt install git git clone https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
(Wait while it downloads 360MB) cd linux-firmware sudo cp -r ar3k /lib/firmware/
If you want to delete the 360MB that you downloaded: cd .. rm -r linux-firmware
true freedom ALSO includes the freedom to do your own research somewhere else ā¦
if that research takes you to some other distributionās wiki then that doesnāt mean you canāt apply said instructions retroactively in a RYF certified distribution ā¦ that being said PureOS is STILL a pure OS precisely because itās NOT named FreedomOS
First of all, get the terminology right. The RYF certification is for hardware that runs on 100% free software, and the Librem 13/14/15/Mini will never get this certification because they contain microcode, FSP and 9% of the ME, which is proprietary. Purism is only trying to get RYF certification for the Librem 5 phone, not for its PCs. You may be right that the FSF wonāt grant RYF certification for products that have official instructions on how to install proprietary software, but the RYF criteria page doesnāt explicitly say that.
However, we are not talking about the Librem 5 here (since its RS9116 doesnāt require proprietary firmware in the Linux file system to use Bluetooth).
The FSF officially endorses distributions that contain 100% free software, and PureOS has received that endorsement. It is an open question whether the FSF would have endorsed PureOS, if Purism had instructions on its web site how to install proprietary firmware. When I have asked the FSF questions like this in the past that are matters of interpretation, I havenāt received a reply.
Personally, I think that Purism should set up a general community wiki for all its devices (like it has for the Librem 5), where the community is encouraged to post āunofficialā documentation. I have answered questions on how to deal with WiFi/Bluetooth on Librem devices at least 3 different times, and this kind of information should be centralized somewhere, so we donāt have to keep repeating ourselves.
there are already distributions that are FAR better suited for this sort of hardware. such as Debian, Ubuntu, PopOS, Linux-Mint, Fedora, Suse and others that are more closely related to the LinuxFromScratch way of setting up an OS.
itās my impression that the majority of people who want to put PureOS on non-open-hardware only do so out of masochism or to brag to their audience that they are running a āPureā OS ā¦ there are legitimate exceptions though (as always)
people will always keep asking about what they are interested in mainly on forums because they feel itās more personal, direct and up-to-date that way and also because they want to relate to other ACTUAL people instead of just reading a community wiki that might very well be out-of-date or incomplete.
they also regularly post in multiple forums the SAME questions most of the time because ā¦ well ā¦ they ARE lazy/impatient
And yet a wiki is a better more efficient way to help people than spamming the same questions ad nauseum. The personal convenience of someone asking a question is not a relevant concern when it is someone else whose help you need.
I agree with @reC. There is a legitimate concern that a vast amount of information available on the internet about Linux is out of date, for the wrong distro, or both.
An ideal wiki (for a specific distro) would therefore have an indication of ārelease version last checked againstā - but would need that to be backed by people putting in the time to recheck information periodically against new releases.
Thanksā¦ Iāve been trying for hours and Finally! they are connected and workingā¦ It was soo longwinded but after a few hours it just seemed to recognise then finally connect them ā¦ sooo frustrating for a beginner