| 1 |
Dell machines have lately started shipping with dual mode hardware. Most |
| 2 |
notably the i2s and hda modes. The trick is to boot with the right acpi |
| 3 |
revs and often it requires a cold boot to change mode. |
| 4 |
On Dec 5, 2015 6:31 PM, "Mick" <michaelkintzios@×××××.com> wrote: |
| 5 |
|
| 6 |
> I came across a rather peculiar phenomenon today with my laptop. I |
| 7 |
> realised |
| 8 |
> that my bluetooth controller was nowhere to be found. I thought running |
| 9 |
> hciconfig would bring it up, but all it did was to complain that there was |
| 10 |
> no |
| 11 |
> device found. rfkill would not list it either. |
| 12 |
> |
| 13 |
> Modprobing various modules did not produce a device, so searching for |
| 14 |
> answers |
| 15 |
> I thought of booting into MSWindows. After I enabled the device in |
| 16 |
> MSWindows |
| 17 |
> I rebooted into Linux and was surprised to see the bluetooth controller was |
| 18 |
> visible again in lspci. |
| 19 |
> |
| 20 |
> How come that switching off the device in one OS, affects the other? :-/ |
| 21 |
> |
| 22 |
> What should I do next time to enable bluetooth from within Linux? |
| 23 |
> |
| 24 |
> |
| 25 |
> PS. There's a parallel to this with the same laptop. Some years ago audio |
| 26 |
> would randomly never come up at boot and no amount of alsactl could wake it |
| 27 |
> up. A swift reboot into MSWindows would reset audio and all would work |
| 28 |
> fine |
| 29 |
> in Linux thereafter. Some cursory troubleshooting at the time didn't help |
| 30 |
> me |
| 31 |
> much. I don't expect that the two issues are related, but thought of |
| 32 |
> mentioning it just in case. |
| 33 |
> -- |
| 34 |
> Regards, |
| 35 |
> Mick |
| 36 |
> |
Archives