From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Bluetooth disappeared because of MSWindows?
Date: Sun, 6 Dec 2015 12:06:23 +0000 [thread overview]
Message-ID: <201512061206.31885.michaelkintzios@gmail.com> (raw)
In-Reply-To: <5663E23D.50205@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 2677 bytes --]
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.
> >
> > 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.
> >
> > How come that switching off the device in one OS, affects the other? :-/
> >
> > What should I do next time to enable bluetooth from within Linux?
> >
> >
> > 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.
>
> 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:
>
> 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
booted on battery, so I thought at the time that they were related to Linux's
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
my device:
Bus 002 Device 008: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth
Mini-card
Bus 002 Device 005: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of
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 symptoms:
https://bugzilla.kernel.org/show_bug.cgi?id=47231
There are loads of Ubuntu users reporting that their bluetooth is nowhere to
be seen, but I didn't find any solutions there.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-06 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 23:31 [gentoo-user] Bluetooth disappeared because of MSWindows? Mick
2015-12-06 7:22 ` Alan McKinnon
2015-12-06 12:06 ` Mick [this message]
2015-12-06 18:07 ` Stroller
2015-12-06 19:34 ` Mick
2015-12-06 20:28 ` Terry Z.
2015-12-06 22:49 ` Mick
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201512061206.31885.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.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