[opensuse-factory] Bluetooth adapter not detected after snapshot 20160430
After installing the latest update, the bluetooth adaptor which was previously working on my Asus UX31L is no longer detected by the OS. Output of hcitool dev shows nothing. Output for $lsmod | grep blue bluetooth 528384 0 rfkill 28672 10 cfg80211,bluetooth,asus_wmi Output for $rfkill list 0: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have tried activating bluetooth via the Yast services manager to no effect. Is anyone else encountering this problem?
On 05/03/2016 03:48 AM, Chan Ju Ping wrote:
After installing the latest update, the bluetooth adaptor which was previously working on my Asus UX31L is no longer detected by the OS.
Output of hcitool dev shows nothing.
Output for $lsmod | grep blue bluetooth 528384 0 rfkill 28672 10 cfg80211,bluetooth,asus_wmi
Output for
$rfkill list 0: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no
I have tried activating bluetooth via the Yast services manager to no effect. Is anyone else encountering this problem?
If your BT device is connected via USB, then at least one of the drivers will be btusb. Does "lsmod | grep btusb" show anything? It would also be useful to post the output of "lsusb". Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 3 May 2016 10:06:01 CDT Larry Finger wrote:
On 05/03/2016 03:48 AM, Chan Ju Ping wrote:
After installing the latest update, the bluetooth adaptor which was previously working on my Asus UX31L is no longer detected by the OS.
Output of hcitool dev shows nothing.
Output for $lsmod | grep blue bluetooth 528384 0 rfkill 28672 10 cfg80211,bluetooth,asus_wmi
Output for
$rfkill list 0: asus-wlan: Wireless LAN
Soft blocked: no Hard blocked: no
1: asus-bluetooth: Bluetooth
Soft blocked: no Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no Hard blocked: no
I have tried activating bluetooth via the Yast services manager to no effect. Is anyone else encountering this problem?
If your BT device is connected via USB, then at least one of the drivers will be btusb. Does "lsmod | grep btusb" show anything? It would also be useful to post the output of "lsusb".
Larry
It's actually built-in Bluetooth.
On Tue, May 3, 2016 at 12:22 PM, Chan Ju Ping <email@chanjp.me> wrote:
If your BT device is connected via USB, then at least one of the drivers will be btusb. Does "lsmod | grep btusb" show anything? It would also be useful to post the output of "lsusb".
Larry
It's actually built-in Bluetooth.
He said "connected via USB" .that can be you plugging a device in an an USB port or the device is internally wired to the USB controller. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 3 May 2016 12:28:37 CDT Cristian Rodríguez wrote:
On Tue, May 3, 2016 at 12:22 PM, Chan Ju Ping <email@chanjp.me> wrote:
If your BT device is connected via USB, then at least one of the drivers will be btusb. Does "lsmod | grep btusb" show anything? It would also be useful to post the output of "lsusb".
Larry
It's actually built-in Bluetooth.
He said "connected via USB" .that can be you plugging a device in an an USB port or the device is internally wired to the USB controller.
My Bluetooth mouse is not connected via USB, and I do not have a USB Bluetooth dongle because it is built in. I am certain the Bluetooth chipset is part of the Intel wireless card. Here is my lsusb output for further clarification. $lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0eef:7926 D-WAV Scientific Co., Ltd Bus 001 Device 006: ID 04f2:b3fc Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
On Tuesday, 3 May 2016 10:42:51 CDT Chan Ju Ping wrote:
On Tuesday, 3 May 2016 12:28:37 CDT Cristian Rodríguez wrote:
On Tue, May 3, 2016 at 12:22 PM, Chan Ju Ping <email@chanjp.me> wrote:
If your BT device is connected via USB, then at least one of the drivers will be btusb. Does "lsmod | grep btusb" show anything? It would also be useful to post the output of "lsusb".
Larry
It's actually built-in Bluetooth.
He said "connected via USB" .that can be you plugging a device in an an USB port or the device is internally wired to the USB controller.
My Bluetooth mouse is not connected via USB, and I do not have a USB Bluetooth dongle because it is built in. I am certain the Bluetooth chipset is part of the Intel wireless card. Here is my lsusb output for further clarification.
$lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0eef:7926 D-WAV Scientific Co., Ltd Bus 001 Device 006: ID 04f2:b3fc Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The last snapshot fixed whatever issue was introduced in the previous one. Thanks TW devs!
On 05/03/2016 02:46 PM, Chan Ju Ping wrote:
On Tuesday, 3 May 2016 10:42:51 CDT Chan Ju Ping wrote:
On Tuesday, 3 May 2016 12:28:37 CDT Cristian Rodríguez wrote:
On Tue, May 3, 2016 at 12:22 PM, Chan Ju Ping <email@chanjp.me> wrote:
If your BT device is connected via USB, then at least one of the drivers will be btusb. Does "lsmod | grep btusb" show anything? It would also be useful to post the output of "lsusb".
My Bluetooth mouse is not connected via USB, and I do not have a USB Bluetooth dongle because it is built in. I am certain the Bluetooth chipset is part of the Intel wireless card. Here is my lsusb output for further clarification.
$lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0eef:7926 D-WAV Scientific Co., Ltd Bus 001 Device 006: ID 04f2:b3fc Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The last snapshot fixed whatever issue was introduced in the previous one.
I'm glad that your Bluetooth is working, but there are some misconceptions that should be addressed. Of course your BT mouse is not connected via USB - that would be a wired mouse. It is connected to your computer via radio waves in the 2.4 GHz band, which is shared with a lot of wifi. The receiver for that radio information is interfaced to the main bus structure of the computer. Using a PCIe interface would be too expensive, thus most BT host devices use USB. The few that do not are connected via serial port. As your system does not show any BT device on the USB bus, it may be that you have a serial BT adapter. My laptop, which has an Intel 7260 for wifi shows the following line in the lsusb output: Bus 003 Device 002: ID 8087:07dc Intel Corp. That is a BT adapter. There is no USB dongle as that device is built into the wifi card. That makes sense as the wifi and BT can share the 2.4 GHz radio. When someone asks you for information about your system, please assume that they know what they are asking to see. Once you become an expert, then you can dispute their need to know. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, May 3, 2016 8:20:44 PM CDT Larry Finger wrote:
On 05/03/2016 02:46 PM, Chan Ju Ping wrote:
On Tuesday, 3 May 2016 10:42:51 CDT Chan Ju Ping wrote:
On Tuesday, 3 May 2016 12:28:37 CDT Cristian Rodríguez wrote:
On Tue, May 3, 2016 at 12:22 PM, Chan Ju Ping <email@chanjp.me> wrote:
If your BT device is connected via USB, then at least one of the drivers will be btusb. Does "lsmod | grep btusb" show anything? It would also be useful to post the output of "lsusb".
My Bluetooth mouse is not connected via USB, and I do not have a USB Bluetooth dongle because it is built in. I am certain the Bluetooth chipset is part of the Intel wireless card. Here is my lsusb output for further clarification.
$lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0eef:7926 D-WAV Scientific Co., Ltd Bus 001 Device 006: ID 04f2:b3fc Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The last snapshot fixed whatever issue was introduced in the previous one.
I'm glad that your Bluetooth is working, but there are some misconceptions that should be addressed. Of course your BT mouse is not connected via USB - that would be a wired mouse. It is connected to your computer via radio waves in the 2.4 GHz band, which is shared with a lot of wifi. The receiver for that radio information is interfaced to the main bus structure of the computer. Using a PCIe interface would be too expensive, thus most BT host devices use USB. The few that do not are connected via serial port. As your system does not show any BT device on the USB bus, it may be that you have a serial BT adapter. My laptop, which has an Intel 7260 for wifi shows the following line in the lsusb output:
Bus 003 Device 002: ID 8087:07dc Intel Corp.
That is a BT adapter. There is no USB dongle as that device is built into the wifi card. That makes sense as the wifi and BT can share the 2.4 GHz radio.
When someone asks you for information about your system, please assume that they know what they are asking to see. Once you become an expert, then you can dispute their need to know.
Larry
That is my error. Consider me chastened.
participants (3)
-
Chan Ju Ping -
Cristian Rodríguez -
Larry Finger