[gentoo-user] Bluetooth disappeared because of MSWindows?

[gentoo-user] Bluetooth disappeared because of MSWindows?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1134 bytes --]

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.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] Bluetooth disappeared because of MSWindows?

[Alan McKinnon]

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.

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.

Then do a Google search for your hardware and laptop types, see what the
interwebz have to say.

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Bluetooth disappeared because of MSWindows?

[Mick]

[-- 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 --]

Re: [gentoo-user] Bluetooth disappeared because of MSWindows?

[Stroller]

> On Sun, 6 December 2015, at 12:06 p.m., Mick <michaelkintzios@gmail.com> wrote:
> 
> 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.

If you search by PCI ID you get a lot more hits (and better ones) than just searching by (something like) "Dell laptop bluetooth linux".

Please forgive me if you've tried that already.

https://www.google.co/search?q=413c:8156

Stroller.

Re: [gentoo-user] Bluetooth disappeared because of MSWindows?

[Mick]

[-- Attachment #1: Type: text/plain, Size: 433 bytes --]

On Sunday 06 Dec 2015 18:07:37 Stroller wrote:

> If you search by PCI ID you get a lot more hits (and better ones) than just
> searching by (something like) "Dell laptop bluetooth linux".
> 
> Please forgive me if you've tried that already.
> 
> https://www.google.co/search?q=413c:8156
> 
> Stroller.

Thank you Stroller, I had already searched by ID, but I haven't yet found 
anything pertinent.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] Bluetooth disappeared because of MSWindows?

[Terry Z.]

[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]

Dell machines have lately started shipping with dual mode hardware. Most
notably the i2s and hda modes. The trick is to boot with the right acpi
revs and often it requires a cold boot to change mode.
On Dec 5, 2015 6:31 PM, "Mick" <michaelkintzios@gmail.com> 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.
> --
> Regards,
> Mick
>

[-- Attachment #2: Type: text/html, Size: 1757 bytes --]

Re: [gentoo-user] Bluetooth disappeared because of MSWindows?

[Mick]

[-- Attachment #1: Type: text/plain, Size: 419 bytes --]

On Sunday 06 Dec 2015 15:28:27 Terry Z. wrote:
> Dell machines have lately started shipping with dual mode hardware. Most
> notably the i2s and hda modes. The trick is to boot with the right acpi
> revs and often it requires a cold boot to change mode.

Do you mean I2C?

I have emerged sys-power/acpid-2.0.23.  How am I supposed to change modes?  
Would you have a link that explains this?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]