using opensuse 13.1 gnome.
searching for bluetooth in activities.
going to bluetooth.
unable to turn on the bluetooth.
showing “NO BLUETOOTH ADAPTERS FOUND”.
There could be many reasons why, but we need to know more information about your hardware, otherwise we can only guess. Assuming it’s a laptop or similar, even a make/model might be helpful. (If it’s new hardware, it might not yet be supported.)
See what is reported by the following terminal command
lsusb
or even better
usb-devices
It may be that the device is disabled (check hardware switches or buttons), and use ‘rfkill’ to check if disabled (soft-blocked). You may need to install ‘rfkill’ package first.
/usr/sbin/rfkill list
If it is soft-blocked, try unblocking with
sudo /usr/sbin/rfkill unblock bluetooth
then check if functional.
On Sun, 07 Sep 2014 19:06:01 +0000, Silu wrote:
> using opensuse 13.1 gnome.
>
> searching for bluetooth in activities.
> going to bluetooth.
> unable to turn on the bluetooth. showing “NO BLUETOOTH ADAPTERS FOUND”.
Something that I learned with new kit here is that some bluetooth
adapters need to be enabled in Windows first before you can see them in
Linux. I don’t know why, but once I installed the Windows 8.1 driver on
my new system and ensured it was working there, it showed up in openSUSE,
but until I did that, nothing would make it show up in openSUSE.
I’ve seen a few other posts around the 'net about it (that’s what put me
onto that track of trying to figure out how to get it working), and it
seems to be a fairly common issue.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On 2014-09-07 23:31, Jim Henderson wrote:
> On Sun, 07 Sep 2014 19:06:01 +0000, Silu wrote:
>
>> using opensuse 13.1 gnome.
>>
>> searching for bluetooth in activities.
>> going to bluetooth.
>> unable to turn on the bluetooth. showing “NO BLUETOOTH ADAPTERS FOUND”.
I have a silly doubt. These adapters you are talking about are
“usb-to-bluetooth” adapters, that provide bluetooth capability to a
machine that doesn’t have it natively, right? Just trying to understand.
> Something that I learned with new kit here is that some bluetooth
> adapters need to be enabled in Windows first before you can see them in
> Linux. I don’t know why, but once I installed the Windows 8.1 driver on
> my new system and ensured it was working there, it showed up in openSUSE,
> but until I did that, nothing would make it show up in openSUSE.
And this state is stable? I mean, you do not have to repeat the process
after powering off? If they are stable, it is at least something to be
thankful of…
> I’ve seen a few other posts around the 'net about it (that’s what put me
> onto that track of trying to figure out how to get it working), and it
> seems to be a fairly common issue.
Disgusting… yikes.
Do we have a list of these broken “adapters”? We could add them to a
list on the HCL here: http://en.opensuse.org/HCL:Bluetooth
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
One of my laptop you need to press the** Fn + F9** key to enable the bluetooth adapter. I am using kde by the way and kbluetooth does not appear until i have pressed those buttons. Just saying 
Ah, yes I recall mentioning that to you in a previous thread regarding livening up your BT device. That advice might be applicable to the OP too.
On Sun, 07 Sep 2014 22:03:06 +0000, Carlos E. R. wrote:
> On 2014-09-07 23:31, Jim Henderson wrote:
>> On Sun, 07 Sep 2014 19:06:01 +0000, Silu wrote:
>>
>>> using opensuse 13.1 gnome.
>>>
>>> searching for bluetooth in activities.
>>> going to bluetooth.
>>> unable to turn on the bluetooth. showing “NO BLUETOOTH ADAPTERS
>>> FOUND”.
>
> I have a silly doubt. These adapters you are talking about are
> “usb-to-bluetooth” adapters, that provide bluetooth capability to a
> machine that doesn’t have it natively, right? Just trying to understand.
In my case, it’s an Intel 7260-based wireless card that includes bluetooth
functionality. The frustrating thing for me was that Dell didn’t install
the Windows bluetooth driver, and their driver kit for the system doesn’t
include it - I had to do a fair amount of research to find the right
download from Intel - and Intel’s support techs in the relevant forums
(help that they are) were less than helpful to the people who were asking
the questions - they sent them back to the OEM several times before
pointing to the proper driver.
This one doesn’t appear to be USB-based.
>> Something that I learned with new kit here is that some bluetooth
>> adapters need to be enabled in Windows first before you can see them
>> in Linux. I don’t know why, but once I installed the Windows 8.1
>> driver on my new system and ensured it was working there, it showed up
>> in openSUSE,
>> but until I did that, nothing would make it show up in openSUSE.
>
> And this state is stable? I mean, you do not have to repeat the process
> after powering off? If they are stable, it is at least something to be
> thankful of…
It’s stable. It just needed to be enabled through the Windows driver
software first.
The only thing unstable about it is GNOME-related - when I power up, the
Apple bluetooth keyboard that I have (for my Macbook for work) won’t
connect to it unless I use bluetoothctl to trust and connect it. But the
adapter itself is working fine (mice and such connect without any
trouble).
>> I’ve seen a few other posts around the 'net about it (that’s what put
>> me onto that track of trying to figure out how to get it working), and
>> it seems to be a fairly common issue.
>
> Disgusting… yikes.
>
> Do we have a list of these broken “adapters”? We could add them to a
> list on the HCL here: http://en.opensuse.org/HCL:Bluetooth
The only one I know for sure is the one I’m using - the Intel 7260.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Sun, 07 Sep 2014 22:46:02 +0000, jetchisel wrote:
> One of my laptop you need to press the* Fn + F9* key to enable the
> bluetooth adapter. I am using kde by the way and kbluetooth does not
> appear until i have pressed those buttons. Just saying
No such thing works with the setup I have here.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Hello,
I have a problem with my bluetooth device as well:
My bluetooth USB dongle is not recognized in KDE. In settings->blutooth it says “No adapter found.”. The dongle works fine on other machines (running openSUSE 12.3, Windows XP, Windows Vista, …).
Here some more information on my configuration:
Hardware:
Motherboard: MSI Z97 Gaming 3
Bluetooth-Dongle: Hama USB 2.0 device (plugged into an USB-2.0-port of the above mentioned motherboard)
Software (Linux only - no dual-boot-system!):
openSUSE 13.1 (Bottle) (x86_64)
Linux 3.11.10-21-default
KDE 4.14.0
With “lsusb” the dongle is shown as
Bus 001 Device 004: ID 0400:080a National Semiconductor Corp. Bluetooth Device
“usb-devices” returns
T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=04 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS= 8 #Cfgs= 1
P: Vendor=0400 ProdID=080a Rev=01.00
C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none)
“hcitools dev” returns just
Devices:
“dmesg -H” reveals the following information on bluetooth and/or the device:
- +0,015902] usb 1-4: new full-speed USB device number 4 using xhci_hcd
+0,020214] usb 1-4: New USB device found, idVendor=0400, idProduct=080a
+0,000762] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
+0,000203] Bluetooth: Core ver 2.16
+0,000008] NET: Registered protocol family 31
+0,000000] Bluetooth: HCI device and connection manager initialized
+0,000006] Bluetooth: HCI socket layer initialized
+0,000001] Bluetooth: L2CAP socket layer initialized
+0,000003] Bluetooth: SCO socket layer initialized
+0,000512] usbcore: registered new interface driver btusb
+0,002357] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
+0,000001] Bluetooth: BNEP filters: protocol multicast
+0,000006] Bluetooth: BNEP socket layer initialized
“rfkill list” returns
*0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
*
Unplugging the device and plugging it back in will give the following messages in /var/log/messages:
[12092.000548] usb 1-4: USB disconnect, device number 4
[12098.791597] usb 1-4: new full-speed USB device number 6 using xhci_hcd
[12098.791724] usb 1-4: Device not responding to set address.
[12098.995743] usb 1-4: Device not responding to set address.
[12099.199587] usb 1-4: device not accepting address 6, error -71
[12099.495599] usb 1-4: new full-speed USB device number 8 using xhci_hcd
[12099.516282] usb 1-4: New USB device found, idVendor=0400, idProduct=080a
[12099.516290] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
The 13.1 release notes state problems with bluetooth in KDE, but my understanding was that at least the device would be recognized and only some functionality would be missing.
I have no idea how to get the device working, so some help would be appreciated.
Thank you very much!
Best regards
On Thu, 11 Sep 2014 12:46:02 +0000, tochiazuma wrote:
> I have a problem with my bluetooth device as well:
It might be a good idea to start a separate thread for your issue -
buried down in another thread is a way that questions like this get
missed.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Hello Jim,
thank you very much for your quick response.
I will follow your advise and move my post / open a new thread.
May be you can delete my post in this thread ?
Best regards
tochiazuma
On Fri, 12 Sep 2014 06:16:01 +0000, tochiazuma wrote:
> May be you can delete my post in this thread ?
There’s no need to do so.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C