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

> 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


  reply	other threads:[~2024-11-18 14:15 UTC|newest]

Thread overview: 11+ 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
2024-11-18 14:15         ` Ignas Lapėnas [this message]
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
2024-11-24 10:53                   ` Ignas Lapėnas

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=87ed38ocgc.fsf@lapenas.dev \
    --to=ignas@lapenas.dev \
    --cc=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).