When I turn on the computer, some days adapter and some days it says “no adapters found”.
Why does this happens?
On Thu, 27 Nov 2014 07:26:01 +0000, Filipe wrote:
> When I turn on the computer, some days adapter and some days it says “no
> adapters found”.
> Why does this happens?
It would be useful if you gave us some basic information about your
system, such as:
- What version of openSUSE are you using?
- What type of bluetooth adapter it is
The latter can be found probably using the lsusb -v command - just look
for something identifying the bluetooth adapter. For example, on my
system:
Bus 003 Device 006: ID 8087:07dc Intel Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x8087 Intel Corp.
idProduct 0x07dc
The idVendor and idProduct values can be used to identify the exact model
for anyone helping you out.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Thanks. I’m using opensuse 13.1. The output from lsusb -v is huge (thousands of lines), with 200 lines about bluetooth, but the inicial part is:
Bus 003 Device 007: ID 0cf3:e004 Atheros Communications, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x0cf3 Atheros Communications, Inc.
idProduct 0xe004
bcdDevice 0.01
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
On Thu, 27 Nov 2014 22:16:01 +0000, Filipe wrote:
> Thanks. I’m using opensuse 13.1. The output from lsusb -v is huge
> (thousands of lines), with 200 lines about bluetooth, but the inicial
> part is:
> idVendor 0x0cf3 Atheros Communications, Inc.
> idProduct 0xe004
Ath3k is the module that is used for that, and it’s the ar3012 bluetooth
chipset, it looks like.
A couple of things to look at:
-
When it’s not running, do you see ath3k in the output for lsmod?
-
If you run ‘rfkill list’ when it’s disabled, do you see anything
indicating that Bluetooth is software or hardware blocked?
If it’s hardware blocked, that’s a physical switch on the system that’s
blocking it. If it’s software blocked, you can try:
sudo rfkill unblock all
And see if that lets you use the adapter.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Thanks. Now bluetooth is not runing and the output of lsmod contains the following lines (among many others):
ath3k 13317 0
bluetooth 396742 7 bnep,ath3k,btusb
rfkill 26487 4 cfg80211,bluetooth
When I first typed “rfkill”, I’ve note that I did not have this program. Now I’ve installed rfkill and the output of “rfkill list” is:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
So it seems that it’s not blocked at all.
On Fri, 28 Nov 2014 04:26:01 +0000, Filipe wrote:
> Thanks. Now bluetooth is not runing and the output of lsmod contains
> the following lines (among many others):
>
> Code:
> --------------------
> ath3k 13317 0
> bluetooth 396742 7 bnep,ath3k,btusb rfkill 26487 4
> cfg80211,bluetooth
>
> --------------------
>
>
> When I first typed “rfkill”, I’ve note that I did not have this program.
> Now I’ve installed rfkill and the output of “rfkill list” is:
>
> Code:
> --------------------
> 0: phy0: Wireless LAN
> Soft blocked: no Hard blocked: no
>
> --------------------
> So it seems that it’s not blocked at all.
Did you happen to resume from a suspended state, or do a full reboot?
What happens if you do:
sudo systemctl restart bluetooth
?
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
I’m not sure I understand your question: “Did you happen to resume from a suspended state, or do a full reboot?”
What’s a suspended state?
I just used the command lsmod, afterwards I installed “rfkill” with yast and then it used “rfkill list”.
Anyway, today I turned on the computer and bluetooth is working. May be just by chance or may be because I’ve installed “rfkill”.
Here are the outputs form
lsmod:
ath3k 13317 0
bluetooth 396742 33 rfcomm,bnep,ath3k,btusb
rfkill 26487 4 cfg80211,bluetooth
rfkill list:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
So the output is different. Since it’s working today, I shall not try “sudo systemctl restart bluetooth” now. And I will wait and try that when bluetooth is not working and see what happens.
Thanks
I left home and turned off the computer. When I returned I turned on and bluetooth is not working. Then I’ve tried
sudo systemctl restart bluetooth
there was no output and nothing happened from this command. It even did not asked for my root password.
On Fri, 28 Nov 2014 10:06:01 +0000, Filipe wrote:
> I’m not sure I understand your question: “Did you happen to resume from
> a suspended state, or do a full reboot?”
> What’s a suspended state?
“Sleep” or “hibernate” as opposed to “power off”.
Sometimes when suspending to RAM (sleep) or hibernating, hardware doesn’t
get fully shut down or reinitialized when the system resumes from that
state.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
On Fri, 28 Nov 2014 14:26:01 +0000, Filipe wrote:
> I left home and turned off the computer. When I returned I turned on and
> bluetooth is not working. Then I’ve tried sudo systemctl restart
> bluetooth there was no output and nothing happened from this command. It
> even did not asked for my root password.
It sounds like your sudo setup is set up to not prompt.
What if you do:
sudo systemctl stop bluetooth
sudo systemctl start bluetooth
?
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Bluetooth is not working now and the commands
sudo systemctl stop bluetooth
sudo systemctl start bluetooth
sudo systemctl restart bluetooth
sudo rfkill unblock all
give no output and changes nothing about bluetooth.
And “rfkill list” gives
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
and lsmod still gives
ath3k 13317 0
bluetooth 396742 7 bnep,ath3k,btusb
rfkill 26487 4 bluetooth,cfg80211
On Sat, 29 Nov 2014 23:26:01 +0000, Filipe wrote:
> give no output and changes nothing about bluetooth.
Stop or start should actually say something.
What about:
sudo systemctl status bluetooth
?
Do you get any status messages at all, or does that also come up with no
output?
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
I’ve just turned on the computer and bluetooth is working now. The out put of “sudo systemctl status bluetooth” is
bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
Active: active (running) since Sun 2014-11-30 07:56:09 BRST; 3min 19s ago
Docs: man:bluetoothd(8)
Main PID: 2102 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─2102 /usr/lib/bluetooth/bluetoothd
Nov 30 07:56:09 linux-sb46 systemd[1]: Starting Bluetooth service...
Nov 30 07:56:09 linux-sb46 bluetoothd[2102]: Bluetooth daemon 5.8
Nov 30 07:56:09 linux-sb46 bluetoothd[2102]: Starting SDP server
Nov 30 07:56:09 linux-sb46 bluetoothd[2102]: Bluetooth management interface 1.3 initialized
Nov 30 07:56:09 linux-sb46 systemd[1]: Started Bluetooth service.
Nov 30 07:56:39 linux-sb46 bluetoothd[2102]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource
Nov 30 07:56:39 linux-sb46 bluetoothd[2102]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink
and the output of “sudo /usr/sbin/rfkill list” is
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
I shall try both commands again latter when bluetooth is not working.
On Sun, 30 Nov 2014 10:16:01 +0000, Filipe wrote:
> I shall try both commands again latter when bluetooth is not working.
Sounds good.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Bluetooth is NOT working now and the output of “sudo systemctl status bluetooth” is a little different
bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
Active: active (running) since Sun 2014-11-30 20:04:27 BRST; 4min 13s ago
Docs: man:bluetoothd(8)
Main PID: 2318 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─2318 /usr/lib/bluetooth/bluetoothd
Nov 30 20:04:27 linux-sb46 bluetoothd[2318]: Bluetooth daemon 5.8
Nov 30 20:04:27 linux-sb46 bluetoothd[2318]: Starting SDP server
Nov 30 20:04:27 linux-sb46 systemd[1]: Started Bluetooth service.
Nov 30 20:04:27 linux-sb46 bluetoothd[2318]: Bluetooth management interface 1.3 initialized
And the output of “sudo /usr/sbin/rfkill list” is
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
On Sun, 30 Nov 2014 22:16:01 +0000, Filipe wrote:
> Bluetooth is NOT working now and the output of “sudo systemctl status
> bluetooth” is a little different
>
>
>
> Code:
> --------------------
> bluetooth.service - Bluetooth service
> Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
> Active: active (running) since Sun 2014-11-30 20:04:27 BRST; 4min 13s
> ago Docs: man:bluetoothd(8)
> Main PID: 2318 (bluetoothd)
> Status: “Running”
> CGroup: /system.slice/bluetooth.service └─2318
> /usr/lib/bluetooth/bluetoothd
>
>
> Nov 30 20:04:27 linux-sb46 bluetoothd[2318]: Bluetooth daemon 5.8 Nov
> 30 20:04:27 linux-sb46 bluetoothd[2318]: Starting SDP server Nov 30
> 20:04:27 linux-sb46 systemd[1]: Started Bluetooth service.
> Nov 30 20:04:27 linux-sb46 bluetoothd[2318]: Bluetooth management
> interface 1.3 initialized
>
> --------------------
>
>
> And the output of “sudo /usr/sbin/rfkill list” is
>
> Code:
> --------------------
> 0: phy0: Wireless LAN
> Soft blocked: no Hard blocked: no
>
> --------------------
This output looks OK - restarting the service in this instance didn’t
change anything?
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
I’ve tried
sudo systemctl start bluetooth
sudo systemctl restart bluetooth
sudo rfkill unblock all
and nothing change.
On Sun, 30 Nov 2014 23:26:02 +0000, Filipe wrote:
> I’ve tried sudo systemctl start bluetooth sudo systemctl restart
> bluetooth sudo rfkill unblock all
>
> and nothing change.
I wonder if unloading/reloading ath3k would help.
When it’s not working, do you see anything in the output of dmesg or /var/
log/messages related to Bluetooth?
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
It’s not working now and the output of The outout of “dmesg | grep Bluetooth” is
1.678138] usb 3-13: Product: Bluetooth USB Host Controller
36.764405] Bluetooth: Core ver 2.16
36.764416] Bluetooth: HCI device and connection manager initialized
36.764421] Bluetooth: HCI socket layer initialized
36.764423] Bluetooth: L2CAP socket layer initialized
36.764429] Bluetooth: SCO socket layer initialized
40.543244] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096
40.543271] Bluetooth: Loading patch file failed
43.841083] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
43.841085] Bluetooth: BNEP filters: protocol multicast
43.841091] Bluetooth: BNEP socket layer initialized
and of “dmesg | grep ath3k” is
40.543286] ath3k: probe of 3-13:1.0 failed with error -110
40.543310] usbcore: registered new interface driver ath3k
How do I unload and reload ath3k?
On Mon, 01 Dec 2014 01:06:01 +0000, Filipe wrote:
> How do I unload and reload ath3k?
sudo rmmod ath3k
sudo modprobe ath3k
That should do it.
That it’s not loading the firmware seems to be the issue - a quick google
search on that particular driver and the error code seems to show that
there might be a known issue.
I found this on bugzilla.opensuse.org:
http://bugzilla.opensuse.org/show_bug.cgi?id=907378
That was for 13.2, so you might want to drop a note in there (use the
same login/pw that you use for these forums) indicating that you’ve seen
this on 13.1. The info that you’re using 13.1 might well help get the
issue resolved.
Jim
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C