From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 6C73E1384B4 for ; Sun, 6 Dec 2015 12:06:50 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D994021C0A7; Sun, 6 Dec 2015 12:06:36 +0000 (UTC) Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 80B0A21C09A for ; Sun, 6 Dec 2015 12:06:35 +0000 (UTC) Received: by wmvv187 with SMTP id v187so130989288wmv.1 for ; Sun, 06 Dec 2015 04:06:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=Kclys0kTCm8bVQsQbpYvxWadN49XjLr40ZtsDc+DzHg=; b=VMRAhYmeuVUAVajeaDHoxQ9HZYmcnAOufNRuabc8jxNPSB1LRRoRfRvQg+blxCo+1K LbkesLZBpV4O+GWWernan1CYVPfStj6wps6VIWlHpaF8WiCv782lus8uCNGL31Z78nD6 NXFnJEs8hoHebn+2rDaRBFjGLrcDiRYEymqjoT27zQhG+APWFliL/tE0rykNJtZ+D+p1 WmkIaH+/Qgv3sWJDuftXsX0J4HDIIgxeaiVdPOEDGsfmpWgE6MMIAOW+l0z8Kih5K8AW CdPnV+mmW+W1/36oAqomuLgc7TIpvoYX3iR7IZvbfcrY+l1+DAzdI+ZzSnqfuyAanAiV DtSQ== X-Received: by 10.28.26.147 with SMTP id a141mr16175399wma.36.1449403594448; Sun, 06 Dec 2015 04:06:34 -0800 (PST) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by smtp.gmail.com with ESMTPSA id jm4sm20235461wjb.7.2015.12.06.04.06.32 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 06 Dec 2015 04:06:33 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Bluetooth disappeared because of MSWindows? Date: Sun, 6 Dec 2015 12:06:23 +0000 User-Agent: KMail/1.13.7 (Linux/4.1.12-gentoo; KDE/4.14.8; x86_64; ; ) References: <201512052331.59084.michaelkintzios@gmail.com> <5663E23D.50205@gmail.com> In-Reply-To: <5663E23D.50205@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7592335.gRfP8oYlg7"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201512061206.31885.michaelkintzios@gmail.com> X-Archives-Salt: 734a33dc-6c0e-47de-9fc6-d4e6f19cd78d X-Archives-Hash: 0f7a99b8f760cc68ff55ee4426663683 --nextPart7592335.gRfP8oYlg7 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sunday 06 Dec 2015 07:22:37 Alan McKinnon wrote: > On 06/12/2015 01:31, Mick wrote: > > I came across a rather peculiar phenomenon today with my laptop. I > > realised that my bluetooth controller was nowhere to be found. I > > thought running hciconfig would bring it up, but all it did was to > > complain that there was no device found. rfkill would not list it > > either. > >=20 > > Modprobing various modules did not produce a device, so searching for > > answers I thought of booting into MSWindows. After I enabled the device > > in MSWindows I rebooted into Linux and was surprised to see the > > bluetooth controller was visible again in lspci. > >=20 > > How come that switching off the device in one OS, affects the other? := =2D/ > >=20 > > What should I do next time to enable bluetooth from within Linux? > >=20 > >=20 > > PS. There's a parallel to this with the same laptop. Some years ago > > audio would randomly never come up at boot and no amount of alsactl > > could wake it up. A swift reboot into MSWindows would reset audio and > > all would work fine in Linux thereafter. Some cursory troubleshooting > > at the time didn't help me much. I don't expect that the two issues are > > related, but thought of mentioning it just in case. >=20 > We've had a few cases of things like this on the list over the years. It > always end up probably a Linux driver bug. Here's what seems to happen: >=20 > The hardware needs to be enabled/shutdown/fiddled or whatever in some > magic way that windows knows about but linux doesn't. Booting into > Windows applies the magic so when you reboot into Linux it's now in a > state Linux can use. Yes, this makes sense. The hickups with the audio would always happen when= I=20 booted on battery, so I thought at the time that they were related to Linux= 's=20 power management. > Read the kernel docs for your driver, the odds are good you have to > apply a driver tweak for your hardware to make it work right. I have had a look at the Doc but haven't been able to find anything. This = is=20 my device: Bus 002 Device 008: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth= =20 Mini-card Bus 002 Device 005: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part= of=20 BCM2046 Bluetooth) > Then do a Google search for your hardware and laptop types, see what the > interwebz have to say. I came across this bug report, although not directly relevant to my symptom= s: https://bugzilla.kernel.org/show_bug.cgi?id=3D47231 There are loads of Ubuntu users reporting that their bluetooth is nowhere t= o=20 be seen, but I didn't find any solutions there. =2D-=20 Regards, Mick --nextPart7592335.gRfP8oYlg7 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJWZCTHAAoJELAdA+zwE4YeycYIALnBIja9YdHt06FcpO65CNyY hppsUPI5w+BSVWbizmFKB58bNzWlbOVvwtOAvD6g86yWw4Gto9RSFdiHNbZoIfjq 4zOxPBzTIn4uo5v2FvZV3pV7L0/MHrBLQ7Vh0teHBR3P/JD0YsqwNW24+LBlColT a99B0TDLDDCpDqMGM+hyoO4sU5XybcuWbRqaJAbqNDInLq/qrCg11aB8iDgCZnuc C4saAQ3co5NaNgOt+7pO1qVBlNdPTR9bwfpydNtIA9fgeOiFELu0uceiKqFUtOwL 9xn5CC+YAjFH6FCDtwslxgeaeOQsd2RA9a/qGaTq6phbwB4u0NR+t4S7hpYOnM4= =m8vg -----END PGP SIGNATURE----- --nextPart7592335.gRfP8oYlg7--