Hi, Since about 06-2023 the bluetooth adapter in my system is not seen anymore. Afaics with Yast, all software/drivers needed to activate bluetooth is installed, but hwinfo of today does not show anything bluetooth related. It did in earlier calls of hwinfo: hwinfo20200309.txt: P: /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-9/1-9:1.0/bluetooth/hci0 hwinfo20200309.txt: E: DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-9/1-9:1.0/bluetooth/hci0 hwinfo20200309.txt: E: SUBSYSTEM=bluetooth hwinfo20200309.txt: E: SYSTEMD_ALIAS=/sys/subsystem/bluetooth/devices/hci0 hwinfo20200309.txt: E: SYSTEMD_WANTS=bluetooth.target hwinfo20200309.txt: E: SYSTEMD_USER_WANTS=bluetooth.target hwinfo20200309.txt: P: /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-9/1-9:1.0/bluetooth/hci0/rfkill0 hwinfo20200309.txt: E: DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-9/1-9:1.0/bluetooth/hci0/rfkill0 hwinfo20200309.txt: E: RFKILL_TYPE=bluetooth hwinfo20200309.txt:/devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-9/1-9:1.0/bluetooth/hci0 hwinfo20200309.txt:/devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-9/1-9:1.0/bluetooth/hci0/rfkill0 hwinfo20200309.txt: bluetooth 626688 41 rfcomm,bnep,btusb,btrtl,btbcm,btintel, Live 0xffffffffc27d5000 hwinfo20200309.txt: ecdh_generic 16384 2 bluetooth, Live 0xffffffffc1e9b000 hwinfo20200309.txt: rfkill 28672 12 bluetooth,cfg80211, Live 0xffffffffc1f6a000 hwinfo20200309.txt: Hardware Class: bluetooth Is there still a chance that this is NOT hardware related? And if so, what can I do to activate it again? Any help (again) much appreciated! regards, Jogchum Reitsma
On 2023-07-02 11:06, Jogchum Reitsma wrote:
Hi,
Since about 06-2023 the bluetooth adapter in my system is not seen anymore. Afaics with Yast, all software/drivers needed to activate bluetooth is installed, but hwinfo of today does not show anything bluetooth related.
It did in earlier calls of hwinfo:
hwinfo is not reliable regarding bluetooth. Laicolasse:~ # hwinfo --bluetooth Laicolasse:~ # And this is a machine where BT works. Laicolasse:~ # inxi --bluetooth Bluetooth: Device-1: Foxconn / Hon Hai Wireless_Device type: USB driver: btusb Report: bt-adapter ID: hci0 state: up address: 60:E9:AA:A0:1A:4A Laicolasse:~ # -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-07-02 12:41, Jogchum Reitsma wrote:
Op 02-07-2023 om 12:02 schreef Carlos E. R.:
inxi --bluetooth
Hm, that would indicate something is indeed wrong over here:
inxi --bluetooth Bluetooth: Message:No bluetooth data found.
Both as user and as root same message.
Ok, yes. I don't know how the BT stack works, so I can not help you diagnose the issue further. I see these modules: Laicolasse:~ # lsmod | grep blue bluetooth 892928 36 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 16384 2 bluetooth rfkill 28672 5 bluetooth,thinkpad_acpi crc16 16384 2 bluetooth,ext4 Laicolasse:~ # Laicolasse:~ # lsmod | grep btusb btusb 65536 0 btrtl 28672 1 btusb btbcm 24576 1 btusb btintel 45056 1 btusb btmtk 16384 1 btusb bluetooth 892928 36 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm usbcore You could try to modprobe btusb or bluetooth (I don't know which is the master, but probably the later). If it is hooked to the USB bus, it should be visible there: Laicolasse:~ # lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 30c9:0050 Luxvisions Innotech Limited Integrated RGB Camera Bus 003 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 06cb:00f9 Synaptics, Inc. Bus 001 Device 002: ID 0489:e0d8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Laicolasse:~ # Well, it is there, but not obvious: it is the Foxconn. If it is not visible, there is a hardware issue. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Hi Carlos, Both lsmod | grep blue lsmod | grep btusb give an empty result here, so even more an indication of broken hardware, I would say Thanks, regards, Jogchum
On 2023-07-02 14:00, Jogchum Reitsma wrote:
Hi Carlos,
Both
lsmod | grep blue lsmod | grep btusb
give an empty result here, so even more an indication of broken hardware, I would say
No, for that you have to check "lsusb". The above is software. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Op 02-07-2023 om 14:13 schreef Carlos E. R.:
On 2023-07-02 14:00, Jogchum Reitsma wrote:
Hi Carlos,
Both
lsmod | grep blue lsmod | grep btusb
give an empty result here, so even more an indication of broken hardware, I would say
No, for that you have to check "lsusb". The above is software.
OK, no bluetooth there too: lsusb Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 11b0:6368 ATECH FLASH TECHNOLOGY Multi-Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04b8:0130 Seiko Epson Corp. GT-X770 [Perfection V500] Bus 001 Device 008: ID 1377:600e Sennheiser electronic GmbH & Co. KG PXC 550-II Bus 001 Device 007: ID 248a:8366 Maxxter Wireless Optical Mouse ACT-MUSW-002 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
On Sun, 02 Jul 2023, 15:08:24 +0200, Jogchum Reitsma wrote:
Op 02-07-2023 om 14:13 schreef Carlos E. R.:
On 2023-07-02 14:00, Jogchum Reitsma wrote:
Hi Carlos,
Both
lsmod | grep blue lsmod | grep btusb
give an empty result here, so even more an indication of broken hardware, I would say
No, for that you have to check "lsusb". The above is software.
OK, no bluetooth there too:
lsusb Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 11b0:6368 ATECH FLASH TECHNOLOGY Multi-Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04b8:0130 Seiko Epson Corp. GT-X770 [Perfection V500] Bus 001 Device 008: ID 1377:600e Sennheiser electronic GmbH & Co. KG PXC 550-II Bus 001 Device 007: ID 248a:8366 Maxxter Wireless Optical Mouse ACT-MUSW-002 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Any chance BT is disabled in your BIOS/UEFI? Perhaps you recently upgraded it, too, and it got somehow disabled. I've seen that before... Cheers. l8er manfred
On 2023-07-02 15:08, Jogchum Reitsma wrote:
Op 02-07-2023 om 14:13 schreef Carlos E. R.:
On 2023-07-02 14:00, Jogchum Reitsma wrote:
Hi Carlos,
Both
lsmod | grep blue lsmod | grep btusb
give an empty result here, so even more an indication of broken hardware, I would say
No, for that you have to check "lsusb". The above is software.
OK, no bluetooth there too:
lsusb Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 11b0:6368 ATECH FLASH TECHNOLOGY Multi-Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04b8:0130 Seiko Epson Corp. GT-X770 [Perfection V500] Bus 001 Device 008: ID 1377:600e Sennheiser electronic GmbH & Co. KG PXC 550-II Bus 001 Device 007: ID 248a:8366 Maxxter Wireless Optical Mouse ACT-MUSW-002 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Hummm... Make sure, because sometimes it is not easy to see. Mine, for instance, is: Bus 001 Device 002: ID 0489:e0d8 Foxconn / Hon Hai Wireless_Device Try with "lsusb --verbose | less". Mine is then obvious: ... Interface Association: bLength 8 bDescriptorType 11 bFirstInterface 0 bInterfaceCount 3 bFunctionClass 224 Wireless bFunctionSubClass 1 Radio Frequency bFunctionProtocol 1 Bluetooth iFunction 4 BT_FUNCTION -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
In data domenica 2 luglio 2023 15:08:24 CEST, Jogchum Reitsma ha scritto:
Op 02-07-2023 om 14:13 schreef Carlos E. R.:
On 2023-07-02 14:00, Jogchum Reitsma wrote:
Hi Carlos,
Both
lsmod | grep blue lsmod | grep btusb
give an empty result here, so even more an indication of broken hardware, I would say
No, for that you have to check "lsusb". The above is software.
OK, no bluetooth there too:
lsusb Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 11b0:6368 ATECH FLASH TECHNOLOGY Multi-Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04b8:0130 Seiko Epson Corp. GT-X770 [Perfection V500] Bus 001 Device 008: ID 1377:600e Sennheiser electronic GmbH & Co. KG PXC 550-II Bus 001 Device 007: ID 248a:8366 Maxxter Wireless Optical Mouse ACT-MUSW-002 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I do not know if this helps, but especially with Leap I had a BT adapter that had troubles to wake up after suspend. The only way (if it is one of these dongles) to find out is, to unplug and replug during the session. Then you scan again. Chances are good that it will appear, but from then on, the possible solutions are not known to me. A second advice would be: try it on another sub plug to see if it is not an issue of the usb controller it used/uses. For what I recall the usb dongle having the issue was an ASUS.
participants (4)
-
Carlos E. R. -
Jogchum Reitsma -
Manfred Hollstein -
Stakanov