1 |
On Sunday 06 Dec 2015 07:22:37 Alan McKinnon wrote: |
2 |
> On 06/12/2015 01:31, Mick wrote: |
3 |
> > I came across a rather peculiar phenomenon today with my laptop. I |
4 |
> > realised that my bluetooth controller was nowhere to be found. I |
5 |
> > thought running hciconfig would bring it up, but all it did was to |
6 |
> > complain that there was no device found. rfkill would not list it |
7 |
> > either. |
8 |
> > |
9 |
> > Modprobing various modules did not produce a device, so searching for |
10 |
> > answers I thought of booting into MSWindows. After I enabled the device |
11 |
> > in MSWindows I rebooted into Linux and was surprised to see the |
12 |
> > bluetooth controller was visible again in lspci. |
13 |
> > |
14 |
> > How come that switching off the device in one OS, affects the other? :-/ |
15 |
> > |
16 |
> > What should I do next time to enable bluetooth from within Linux? |
17 |
> > |
18 |
> > |
19 |
> > PS. There's a parallel to this with the same laptop. Some years ago |
20 |
> > audio would randomly never come up at boot and no amount of alsactl |
21 |
> > could wake it up. A swift reboot into MSWindows would reset audio and |
22 |
> > all would work fine in Linux thereafter. Some cursory troubleshooting |
23 |
> > at the time didn't help me much. I don't expect that the two issues are |
24 |
> > related, but thought of mentioning it just in case. |
25 |
> |
26 |
> We've had a few cases of things like this on the list over the years. It |
27 |
> always end up probably a Linux driver bug. Here's what seems to happen: |
28 |
> |
29 |
> The hardware needs to be enabled/shutdown/fiddled or whatever in some |
30 |
> magic way that windows knows about but linux doesn't. Booting into |
31 |
> Windows applies the magic so when you reboot into Linux it's now in a |
32 |
> state Linux can use. |
33 |
|
34 |
Yes, this makes sense. The hickups with the audio would always happen when I |
35 |
booted on battery, so I thought at the time that they were related to Linux's |
36 |
power management. |
37 |
|
38 |
|
39 |
> Read the kernel docs for your driver, the odds are good you have to |
40 |
> apply a driver tweak for your hardware to make it work right. |
41 |
|
42 |
I have had a look at the Doc but haven't been able to find anything. This is |
43 |
my device: |
44 |
|
45 |
Bus 002 Device 008: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth |
46 |
Mini-card |
47 |
Bus 002 Device 005: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of |
48 |
BCM2046 Bluetooth) |
49 |
|
50 |
|
51 |
> Then do a Google search for your hardware and laptop types, see what the |
52 |
> interwebz have to say. |
53 |
|
54 |
I came across this bug report, although not directly relevant to my symptoms: |
55 |
|
56 |
https://bugzilla.kernel.org/show_bug.cgi?id=47231 |
57 |
|
58 |
There are loads of Ubuntu users reporting that their bluetooth is nowhere to |
59 |
be seen, but I didn't find any solutions there. |
60 |
-- |
61 |
Regards, |
62 |
Mick |