How to enable bluetooth in opensuse 13.1 - Bluetooth Does't Enable even if i switch on bluetooth

Hi forum,

Greetings !

I wish not come here but after long search no help from any page, so i have to land here.

I recently installed opensuse 13.1 on my Samsung laoptop.

My wifi network on opensuse 13.1 laptop is working flawlessly when it comes to blue-tooth i have to figure out…

How to enable bluetooth in opensuse 13.1 - Bluetooth Does’t Enable even if i switch on bluetooth button.

suresh@linux-fqgm:~> dmesg | grep Bluetooth
21.553271] Bluetooth: Core ver 2.16
21.553382] Bluetooth: HCI device and connection manager initialized
21.553391] Bluetooth: HCI socket layer initialized
21.553394] Bluetooth: L2CAP socket layer initialized
21.553399] Bluetooth: SCO socket layer initialized
21.556261] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
21.556265] Bluetooth: BNEP filters: protocol multicas

suresh@linux-fqgm:~>/usr/sbin/rfkill list
0: samsung-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: samsung-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

**suresh@linux-fqgm:~> systemctl status bluetooth.service
**bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
Active: active (running) since Mon 2014-05-12 22:07:17 IST; 1h 17min ago
Docs: man:bluetoothd(8)
Main PID: 1071 (bluetoothd)
Status: “Running”
CGroup: /system.slice/bluetooth.service
└─1071 /usr/lib/bluetooth/bluetoothd

Where to start the debugging … How to enable bluetooth in opensuse? How to find the status wethere bluetooth it is enabled or not from command line.

Do i need to add any special user privileges to access bluetooth service

Regards

Suresh Saragadam

On 2014-05-12 19:16, sureshsaragadam wrote:

> How to enable bluetooth in opensuse 13.1 - Bluetooth Does’t Enable even
> if i switch on bluetooth button.

What desktop are you using?

>
> SURESH@LINUX-FQGM:~> DMESG | GREP BLUETOOTH
> 21.553271] BLUETOOTH: CORE VER 2.16

A comment: When pasting here computer commands and such, please use a
CODE BLOCK, so that the forum software doesn’t do silly things like
converting URLS to tiny urls or otherwise hide or alter the commands you
entered. You get them by clicking on the ‘#’ button in the forum editor.
See photo

And please do not use things like bold inside. It gets converted to
uppercase for some of us.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

I have installed opensuse 13.1 in a Samsung Laptop NP350U2B

I just worked around with bluetoothctl command
I learned there is no default controller available for my bluetooth, Is this a driver issue!!!


suresh@linux-fqgm:~> bluetoothctl 
[bluetooth]# list
[bluetooth]# show 
No default controller available

Thanks and Regards

On 05/12/2014 01:26 PM, sureshsaragadam wrote:
>
> I have installed opensuse 13.1 in a Samsung Laptop NP350U2B
>
> I just worked around with bluetoothctl command
> I learned there is no default controller available for my bluetooth, Is
> this a driver issue!!!
>
>
> Code:
> --------------------
>
> suresh@linux-fqgm:~> bluetoothctl
> [bluetooth]# list
> [bluetooth]# show
> No default controller available
>
> --------------------

Do you actually have a BlueTooth device? Please post the output of ‘lsusb’.

Do you actually have a BlueTooth device? Please post the output of ‘lsusb’.

Earlier the same laptop is loaded with Ubuntu, and at that time bluetooth is working fine, I think the issue is with Opensuse 13.1.


suresh@linux-fqgm:~> lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 2232:1015 

I am not working with a usb bluetooth device,
Here the problem is the Laptop integrated blue-tooth is not getting enabled.

Can any one please let me figure out the issue with bluetooth getting enabled.

http://s28.postimg.org/4zhu3opv1/Screenshot_from_2014_05_12_23_20_16.png

This is the screen shot image of my laptop, where it displays bluetooth is disabled.

On 05/12/2014 11:56 PM, sureshsaragadam wrote:
>
>>
>> Do you actually have a BlueTooth device? Please post the output of
>> ‘lsusb’.
>>
>
> Earlier the same laptop is loaded with Ubuntu, and at that time
> bluetooth is working fine, I think the issue is with Opensuse 13.1.
>
>
> Code:
> --------------------
>
> suresh@linux-fqgm:~> lsusb
> Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 003: ID 2232:1015
>
> --------------------
>
>
> I am not working with a usb bluetooth device,
> Here the problem is the Laptop integrated blue-tooth is not getting
> enabled.
>
> Can any one please let me figure out the issue with bluetooth getting
> enabled.

Every Bluetooth device that I know about is interfaced to its host through the
USB bus even though you do not have a device plugged into an external USB
connector. The device with the list above with ID 2232:1015 is such a device,
but I think that is a web cam, not BT. In fact, I was unable to find a driver
built into the kernel that supports that device, and it could be the BT device.

It is quite possible that the laptop vendor modified Ubuntu and installed a
special driver that is not part of regular Linux. Until you actually produce
either the output of ‘lspci -nn’ or ‘lsusb’ that shows a BT device, there is
little we can do to help you.

On 2014-05-13 07:36, sureshsaragadam wrote:
>
> [image:
> http://s28.postimg.org/4zhu3opv1/Screenshot_from_2014_05_12_23_20_16.png]
>
> This is the screen shot image of my laptop, where it displays bluetooth
> is disabled.

So? That doesn’t add any further info, sorry.

You could try “hwinfo --bluetooth”, but it will come out empty, I’m afraid.

Or you could try booting that ubuntu, and post info from there, like
what drivers it loads.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))



suresh@linux-fqgm:~> /sbin/lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09)
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09)
00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4)
00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b4)
00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation HM65 Express Chipset Family LPC Controller [8086:1c49] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 04)
01:00.0 Network controller [0280]: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) [168c:002e] (rev 01)
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)

suresh@linux-fqgm:~> lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 2232:1015  

suresh@linux-fqgm:~>  dmesg | grep Bluetooth
   24.255101] Bluetooth: Core ver 2.16
   24.255123] Bluetooth: HCI device and connection manager initialized
   24.255132] Bluetooth: HCI socket layer initialized
   24.255135] Bluetooth: L2CAP socket layer initialized
   24.255141] Bluetooth: SCO socket layer initialized
   24.259309] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
   24.259312] Bluetooth: BNEP filters: protocol multicast
   24.259320] Bluetooth: BNEP socket layer initialized

suresh@linux-fqgm:~> /usr/sbin/rfkill list
0: samsung-wlan: Wireless LAN
    Soft blocked: no
    Hard blocked: no
1: samsung-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
2: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

suresh@linux-fqgm:~>  systemctl status bluetooth.service 
bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Tue 2014-05-13 18:09:47 IST; 7min ago
     Docs: man:bluetoothd(8)
 Main PID: 1139 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─1139 /usr/lib/bluetooth/bluetoothd

suresh@linux-fqgm:~> bluetoothctl 
[bluetooth]# list
[bluetooth]# show
No default controller available
[bluetooth]# 


I have installed** rfkill** utility and it displays the bluetooth device is of Samsung make
with bluetoothctl command i came to know that there is no default controller available

So? That doesn’t add any further info, sorry.

You could try “hwinfo --bluetooth”, but it will come out empty, I’m afraid.

Or you could try booting that ubuntu, and post info from there, like
what drivers it loads.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

Unfortunately i am unable to boot with Ubuntu, it happened twice from past 2 years and so the reason i loaded opensuse,

“hwinfo --bluetooth”,

hwinfo output is empty

So how do i judge, No driver loaded? No Bluetooth Drive support?

On 2014-05-13 15:16, sureshsaragadam wrote:

> hwinfo output is empty
>
> So how do i judge, No driver loaded? No Bluetooth Drive support?

I don’t know. We have to identify the hardware first, where it connects to.

No, hwinfo does not need drivers.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

On 05/13/2014 08:16 AM, sureshsaragadam wrote:
>
> Unfortunately i am unable to boot with Ubuntu, it happened twice from
> past 2 years and so the reason i loaded opensuse,
>
> “hwinfo --bluetooth”,
>
> hwinfo output is empty
>
> So how do i judge, No driver loaded? No Bluetooth Drive support?

I still do not see any BT device in the PCI or USB lists. The other possibility
is that it is attached to the SMBus. To test that, try the command ‘sudo ls
/dev/i2c*’. If files are found, then there is some device attached. To explore
that bus, you will need to do the following:


sudo zypper install i2c-tools
sudo i2cdetect -y X

In the above, X should be the number in /dev/i2cX. It will likely be zero. Post
those results, and we will see if we can get further.


sudo zypper install i2c-tools
sudo i2cdetect -y X

In the above, X should be the number in /dev/i2cX. It will likely be zero. Post
those results, and we will see if we can get further.

suresh@linux-fqgm:~> sudo /usr/sbin/i2cdetect -y 0
Error: Could not open file /dev/i2c-0' or /dev/i2c/0’: No such file or directory

There is no i2c directory available in /dev/

**SAMSUNG Series 3 NP350U2B-A04IN - **laptop model
Does any log file querry should help in finding the bluetooth hardware bus

Hi sureshsaragadam

I note note that your ‘rfkill list’ output shows reports the status of the bluetooth device as

1: samsung-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no

Now, normally this would imply that the device was enabled, and it should be enumerated by ‘lsusb’. FWIW, I was also searching around for any hardware-related info concerning this model (NP350U2B) and I happened to stumble upon the following bug thread. (Please ignore the topic, just focussing on the reported bluetooth hardware)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1030608
They have attached files which amongst other things lists a bluetooth device
https://launchpadlibrarian.net/111428940/Lsusb.txt

Bus 002 Device 003: ID 8086:0189 Intel Corp.

It’s likely that your particular model laptop is using ssame/similar Intel chipset.

I also note that hci0 also exists (as expected) in that user’s laptop, yet it was missing in your output.
https://launchpadlibrarian.net/111428947/RfKill.txt

0: hci0: Bluetooth
        Soft blocked: yes
        Hard blocked: no
1: samsung-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Try disabling and re-enabling your bluetooth device with

rfkill block bluetooth
rfkill unblock bluetooth

then observe if the device shows up with

lsusb

If not, a bug report may be required.


suresh@linux-fqgm:~> lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 2232:1015


I tried blocking and unbloking through rfkill, yet my bluetooth is not working.

I downloaded lshw Utility and i am posting the output of the full hard ware list
bit lenthy i searched for bluetooth traces, no info



linux-fqgm.site
    description: Computer
    width: 64 bits
    capabilities: vsyscall32
  *-core
       description: Motherboard
       physical id: 0
     *-memory
          description: System memory
          physical id: 0
          size: 3870MiB
     *-cpu
          product: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz
          vendor: Intel Corp.
          physical id: 1
          bus info: cpu@0
          capacity: 2900MHz
          width: 64 bits
          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid cpufreq
     *-pci
          description: Host bridge
          product: 2nd Generation Core Processor Family DRAM Controller
          vendor: Intel Corporation
          physical id: 100
          bus info: pci@0000:00:00.0
          version: 09
          width: 32 bits
          clock: 33MHz
        *-display
             description: VGA compatible controller
             product: 2nd Generation Core Processor Family Integrated Graphics Controller
             vendor: Intel Corporation
             physical id: 2
             bus info: pci@0000:00:02.0
             version: 09
             width: 64 bits
             clock: 33MHz
             capabilities: vga_controller bus_master cap_list rom
             configuration: driver=i915 latency=0
             resources: irq:41 memory:f6400000-f67fffff memory:e0000000-efffffff ioport:e000(size=64)
        *-communication
             description: Communication controller
             product: 6 Series/C200 Series Chipset Family MEI Controller #1
             vendor: Intel Corporation
             physical id: 16
             bus info: pci@0000:00:16.0
             version: 04
             width: 64 bits
             clock: 33MHz
             capabilities: bus_master cap_list
             configuration: driver=mei_me latency=0
             resources: irq:42 memory:f7c0a000-f7c0a00f
        *-usb:0
             description: USB controller
             product: 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2
             vendor: Intel Corporation
             physical id: 1a
             bus info: pci@0000:00:1a.0
             version: 04
             width: 32 bits
             clock: 33MHz
             capabilities: ehci bus_master cap_list
             configuration: driver=ehci-pci latency=0
             resources: irq:16 memory:f7c08000-f7c083ff
        *-multimedia
             description: Audio device
             product: 6 Series/C200 Series Chipset Family High Definition Audio Controller
             vendor: Intel Corporation
             physical id: 1b
             bus info: pci@0000:00:1b.0
             version: 04
             width: 64 bits
             clock: 33MHz
             capabilities: bus_master cap_list
             configuration: driver=snd_hda_intel latency=0
             resources: irq:44 memory:f7c00000-f7c03fff
        *-pci:0
             description: PCI bridge
             product: 6 Series/C200 Series Chipset Family PCI Express Root Port 1
             vendor: Intel Corporation
             physical id: 1c
             bus info: pci@0000:00:1c.0
             version: b4
             width: 32 bits
             clock: 33MHz
             capabilities: pci normal_decode bus_master cap_list
             configuration: driver=pcieport
             resources: irq:16 ioport:d000(size=4096) memory:f7200000-f7bfffff ioport:f0b00000(size=10485760)
           *-network
                description: Wireless interface
                product: AR9287 Wireless Network Adapter (PCI-Express)
                vendor: Qualcomm Atheros
                physical id: 0
                bus info: pci@0000:01:00.0
                logical name: wlp1s0
                version: 01
                serial: 5c:ac:4c:a8:66:20
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list ethernet physical wireless
                configuration: broadcast=yes driver=ath9k driverversion=3.11.10-7-desktop firmware=N/A ip=192.168.0.102 latency=0 link=yes multicast=yes wireless=IEEE 802.11bgn
                resources: irq:16 memory:f7200000-f720ffff
        *-pci:1
             description: PCI bridge
             product: 6 Series/C200 Series Chipset Family PCI Express Root Port 4
             vendor: Intel Corporation
             physical id: 1c.3
             bus info: pci@0000:00:1c.3
             version: b4
             width: 32 bits
             clock: 33MHz
             capabilities: pci normal_decode bus_master cap_list
             configuration: driver=pcieport
             resources: irq:19 ioport:c000(size=4096) memory:f6800000-f71fffff ioport:f0000000(size=10485760)
           *-network
                description: Ethernet interface
                product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:02:00.0
                logical name: enp2s0
                version: 06
                serial: e8:11:32:74:6e:44
                size: 10Mbit/s
                capacity: 1Gbit/s
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
                configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8168e-3_0.0.4 03/27/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s
                resources: irq:43 ioport:c000(size=256) memory:f0004000-f0004fff memory:f0000000-f0003fff
        *-usb:1
             description: USB controller
             product: 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1
             vendor: Intel Corporation
             physical id: 1d
             bus info: pci@0000:00:1d.0
             version: 04
             width: 32 bits
             clock: 33MHz
             capabilities: ehci bus_master cap_list
             configuration: driver=ehci-pci latency=0
             resources: irq:23 memory:f7c07000-f7c073ff
        *-isa
             description: ISA bridge
             product: HM65 Express Chipset Family LPC Controller
             vendor: Intel Corporation
             physical id: 1f
             bus info: pci@0000:00:1f.0
             version: 04
             width: 32 bits
             clock: 33MHz
             capabilities: isa bus_master cap_list
             configuration: driver=lpc_ich latency=0
             resources: irq:0
        *-storage
             description: SATA controller
             product: 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller
             vendor: Intel Corporation
             physical id: 1f.2
             bus info: pci@0000:00:1f.2
             version: 04
             width: 32 bits
             clock: 66MHz
             capabilities: storage ahci_1.0 bus_master cap_list
             configuration: driver=ahci latency=0
             resources: irq:40 ioport:e0b0(size=8) ioport:e0a0(size=4) ioport:e090(size=8) ioport:e080(size=4) ioport:e060(size=32) memory:f7c06000-f7c067ff
        *-serial UNCLAIMED
             description: SMBus
             product: 6 Series/C200 Series Chipset Family SMBus Controller
             vendor: Intel Corporation
             physical id: 1f.3
             bus info: pci@0000:00:1f.3
             version: 04
             width: 64 bits
             clock: 33MHz
             configuration: latency=0
             resources: memory:f7c05000-f7c050ff ioport:e040(size=32)

Please letme know through this lshw output for bluettoth info

No evidence of its existence at all in your output. It appears to be disabled, except for the fact that is reported via ‘rfkill list’.

Hi
Do you see any output from the following command;


lsmod |grep bt

btusb                  32266  0 
bluetooth             396742  33 rfcomm,bnep,ath3k,btusb

Have you checked the output from the command (as root user)


journalctl -xb --no-pager|grep blue
and
journalctl -xb --no-pager|grep firm

If there is no output from the lsmod command, what happens if you try to load the btusb module;


modprobe btusb

Hi

Output of lsmod


suresh@linux-fqgm:~> lsmod | grep bt
btusb                  32266  0 
bluetooth             396742  6 btusb,bnep
btrfs                 913865  0 
raid6_pq              106004  1 btrfs
zlib_deflate           26914  1 btrfs
xor                    21411  1 btrfs
libcrc32c              12644  1 btrfs


suresh@linux-fqgm:~> lsmod | grep bluetooth
bluetooth             396742  6 btusb,bnep
rfkill                 26487  8 bluetooth,samsung_laptop,cfg80211


suresh@linux-fqgm:~> sudo journalctl -xb --no-pager|grep blue
May 15 23:15:54 linux-fqgm.site dbus[642]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
-- Subject: Unit bluetooth.service has begun with start-up
-- Unit bluetooth.service has begun starting up.
May 15 23:15:54 linux-fqgm.site bluetoothd[906]: Bluetooth daemon 5.8
May 15 23:15:54 linux-fqgm.site dbus[642]: [system] Successfully activated service 'org.bluez'
-- Subject: Unit bluetooth.service has finished start-up
-- Unit bluetooth.service has finished starting up.
May 15 23:15:54 linux-fqgm.site bluetoothd[906]: Starting SDP server
May 15 23:15:54 linux-fqgm.site bluetoothd[906]: Bluetooth management interface 1.3 initialized


suresh@linux-fqgm:~> sudo journalctl -xb --no-pager|grep firm
May 15 23:15:45 linux-fqgm kernel: psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x450f00)
May 15 23:15:54 linux-fqgm NetworkManager[758]: <info> monitoring kernel firmware directory '/lib/firmware'.



what i have noticed is the bluetooth is just using btusb and bnep
Is this ok with bluetooth module

Similar problem solved in other case,
https://bbs.archlinux.org/viewtopic.php?pid=1322604
Almost similar but no solution found for my case

Regards

Suresh S

On Thu 15 May 2014 06:06:01 PM CDT, sureshsaragadam wrote:

<snip>

what i have noticed is the bluetooth is just using btusb and bnep
Is this ok with bluetooth module

Regards

Suresh S

Hi
Well it probably would have the rfcomm one as well as the most
important one, your driver (in my case that is the ath3k one). It’s
almost as though it’s like a software one (kind of like a winmodem)…

If you press a Fn key + the one for the wireless, it doesn’t kick into
life either?


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.1 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

The OP’s ‘rfkill list’ output reports the bluetooth device status as

1: samsung-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no

The strange thing is that the device is not enumerated by the kernel (I’d at least expect to see the chipset reported), so maybe it is not enabled and rfkill is misreporting somehow? It might be worthwhile trying another Live distro (USB or DVD) to see whether there is any difference…