From: Jesse Gibbons <jgibbons2357@gmail.com>
To: help-guix@gnu.org
Subject: help with USB bluetooth driver
Date: Fri, 26 Jun 2020 18:45:03 -0600 [thread overview]
Message-ID: <58de57d2-6c62-06c2-8815-90445b57b3e5@gmail.com> (raw)
I recently purchased the device described here
<https://h-node.org/bluetooth/view/en/2005/Broadcom-BCM20702A0-Bluetooth/1/1/undef/undef/undef/undef/bluetooth-works/asus>
H-node says it should work without nonfree drivers. But when I plug it
in, the kernel says non-free firmware was disabled. Do I need to setup
anything to get the kernel to load the driver?
H-node says that it was tested on PureOS. I know that PureOS does not
disable firmware, they simply don't install them on the distro by
default and don't provide any way to install them. So this could be
something for Purism to investigate.
I've searched the linux-libre source, including the deblob script, but I
can't find where it disables that particular device, so it's safe to
assume that it is not known to require blobs. Furthermore, the device
itself is documented in the deblobbed source, so it's reasonable to
expect the device to work.
I confirmed that lsusb -v is almost identical to what's on h-node, where
the only difference is the serial number. I can't find the hwinfo
package, so I can't compare the other data. What package contains hwinfo?
If I can get it to load on another gnu/linux-libre operating system,
it's a problem with guix. Else it is a linux-libre bug and I should
report it upstream. What linux-libre distro should I check?
reply other threads:[~2020-06-27 0:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58de57d2-6c62-06c2-8815-90445b57b3e5@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).