From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id cDSFKx1MO2eI9AAAe85BDQ:P1 (envelope-from ) for ; Mon, 18 Nov 2024 14:15:57 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id cDSFKx1MO2eI9AAAe85BDQ (envelope-from ) for ; Mon, 18 Nov 2024 15:15:57 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1731939357; a=rsa-sha256; cv=none; b=MxWeYJdZ4MJRdfeJ4p2w1txoZcsQaa8KCA6NtIe3nHpc0h54XcvHCiERRireikbT/5qP7V FkTmI1KG+ipWRVsMKlel+rhLEPfB4J51ZisTPApskKdReQ6RnE9a7sBon53SUO+L7vYes2 HQu5IArUBkOPtdp/g9uP7/lNBrhorfOWasAMFGJ6/gzv9UwC0+TQLG5MTctORsNnLxXxP8 lNHmOOnWFBg2o3itI0oUULn2sHKVTac7y15Xjk9ja3R5W3TZiDBg8sZcPziAVrTqd45B5F 9mwW7NPx2ZVSc8JqURdMbm0Nskaq+WAWC4p5jauM8I308mcExYh12vMG5PRyIw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1731939357; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post; bh=sxWnm0yUmaWUJAq5JznvEa3w6+tWrK4qMIvgi+MFyQI=; b=thwtmMdpv+FChY0BUnc+Y+51eb7uNDIbEH+On+NtfsQaHTOoY+mpPjNz2kGf8YF1dMYR5y xnef/3BUFNNZ9NwyJEb2S8f5GB8RXJBhqTGiY7IwVIApYSAcRQL0qdm6NMrpsHrett3FN3 L6KpoJfTu3mPJMsSGhl/gBG7ug7jbLl6YyAbrT2xYm3k+VKXIMBUioiUydH0hyMgJjSoFB pP9djd3aS3NhGZlx/DQuWVCi6ygj3gCqLf2quNqQjA5b1hdCprvwK4x/DSUTfPlzKI5dfr ME8xhHkzcf+0f3szDuFXuzTqzLPDctorV+U2YiXJ7zkbYfrdJysCrPWaxoEDOQ== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 5439E81ECC for ; Mon, 18 Nov 2024 15:15:57 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tD2XK-0000UO-1r; Mon, 18 Nov 2024 09:15:30 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tD2XB-0000U3-HL for help-guix@gnu.org; Mon, 18 Nov 2024 09:15:22 -0500 Received: from tritonas.serveriai.lt ([194.135.87.87]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tD2X8-0002i4-SI for help-guix@gnu.org; Mon, 18 Nov 2024 09:15:21 -0500 Received: from [88.119.78.42] (helo=thorfin) by tritonas.serveriai.lt with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1tD2X5-000000002N5-21iE; Mon, 18 Nov 2024 16:15:15 +0200 From: =?utf-8?Q?Ignas_Lap=C4=97nas?= To: Daniel Hatton Cc: GUIX help list Subject: Re: How to diagnose Bluetooth trouble? In-Reply-To: <20222fe3-5612-4ffb-9dc9-543545b1084b@btinternet.com> (Daniel Hatton's message of "Mon, 18 Nov 2024 13:48:23 +0000") References: <87y11hnfdw.fsf@lapenas.dev> <87jzd0ojub.fsf@lapenas.dev> <20222fe3-5612-4ffb-9dc9-543545b1084b@btinternet.com> User-Agent: mu4e 1.12.7; emacs 29.4 Date: Mon, 18 Nov 2024 16:15:15 +0200 Message-ID: <87ed38ocgc.fsf@lapenas.dev> MIME-Version: 1.0 Content-Type: text/plain X-Sender: ignas@lapenas.dev Received-SPF: pass client-ip=194.135.87.87; envelope-from=ignas@lapenas.dev; helo=tritonas.serveriai.lt X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: help-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: 1.38 X-Spam-Score: 1.38 X-Migadu-Queue-Id: 5439E81ECC X-Migadu-Scanner: mx12.migadu.com X-TUID: 16Yb6il/GYU6 > 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