unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Hatton <dan.hatton@btinternet.com>
To: GUIX help list <help-guix@gnu.org>
Subject: Re: How to diagnose Bluetooth trouble?
Date: Mon, 18 Nov 2024 13:48:23 +0000	[thread overview]
Message-ID: <20222fe3-5612-4ffb-9dc9-543545b1084b@btinternet.com> (raw)
In-Reply-To: <87jzd0ojub.fsf@lapenas.dev>


[-- Attachment #1.1: Type: text/plain, Size: 857 bytes --]

On 18/11/2024 11:35, Ignas Lapėnas wrote:


> https://wiki.archlinux.org/title/Bluetooth#bluetoothctl:_No_default_controller_available
> Since you're with guix, journalctl command should be replaced with
> something like this.
> sudo cat /var/log/messages | grep hci
> to check if you're blocked by rfkill the command should simply be rfkill

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?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2024-11-18 13:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16 10:39 How to diagnose Bluetooth trouble? Daniel Hatton
2024-11-18  7:57 ` Ignas Lapėnas
2024-11-18  9:53   ` Daniel Hatton
2024-11-18 11:35     ` Ignas Lapėnas
2024-11-18 13:48       ` Daniel Hatton [this message]
2024-11-18 14:15         ` Ignas Lapėnas
2024-11-20 13:02           ` Daniel Hatton
2024-11-21 12:13             ` Daniel Hatton
2024-11-21 12:37               ` Ignas Lapėnas
2024-11-21 18:26                 ` Daniel Hatton

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=20222fe3-5612-4ffb-9dc9-543545b1084b@btinternet.com \
    --to=dan.hatton@btinternet.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).