Форум русскоязычного сообщества Ubuntu


Получить помощь и пообщаться с другими пользователями Ubuntu можно
на irc канале #ubuntu-ru в сети Freenode
и в Jabber конференции ubuntu@conference.jabber.ru

Автор Тема: Проблема с Bluetooth AR3011  (Прочитано 1257 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн rishatik92

  • Автор темы
  • Новичок
  • *
  • Сообщений: 4
    • Просмотр профиля
Проблема с Bluetooth AR3011
« : 23 Октябрь 2016, 16:37:07 »
Тоже являюсь владельцем AR3011 и ubuntu 16.04

смотрите что сообщает sudo bluetoothd -n -d
# sudo bluetoothd -n -d
bluetoothd[6307]: Bluetooth daemon 5.37
bluetoothd[6307]: src/main.c:parse_config() parsing main.conf
bluetoothd[6307]: src/main.c:parse_config() Key file does not have key 'DiscoverableTimeout' in group 'General'
bluetoothd[6307]: src/main.c:parse_config() Key file does not have key 'PairableTimeout' in group 'General'
bluetoothd[6307]: src/main.c:parse_config() Key file does not have key 'AutoConnectTimeout' in group 'General'
bluetoothd[6307]: src/main.c:parse_config() Key file does not have key 'Name' in group 'General'
bluetoothd[6307]: src/main.c:parse_config() Key file does not have key 'Class' in group 'General'
bluetoothd[6307]: src/main.c:parse_config() Key file does not have key 'DeviceID' in group 'General'
bluetoothd[6307]: src/main.c:parse_config() Key file does not have key 'ReverseServiceDiscovery' in group 'General'
D-Bus setup failed: Name already in use
bluetoothd[6307]: Unable to get on D-Bus

# cat /etc/bluetooth/main.conf
[General]

# Default adaper name
# Defaults to 'BlueZ X.YZ'
#Name = BlueZ

# Default device class. Only the major and minor device class bits are
# considered. Defaults to '0x000000'.
#Class = 0x000100

# How long to stay in discoverable mode before going back to non-discoverable
# The value is in seconds. Default is 180, i.e. 3 minutes.
# 0 = disable timer, i.e. stay discoverable forever
#DiscoverableTimeout = 0

# How long to stay in pairable mode before going back to non-discoverable
# The value is in seconds. Default is 0.
# 0 = disable timer, i.e. stay pairable forever
#PairableTimeout = 0

# Automatic connection for bonded devices driven by platform/user events.
# If a platform plugin uses this mechanism, automatic connections will be
# enabled during the interval defined below. Initially, this feature
# intends to be used to establish connections to ATT channels. Default is 60.
#AutoConnectTimeout = 60

# Use vendor id source (assigner), vendor, product and version information for
# DID profile support. The values are separated by ":" and assigner, VID, PID
# and version.
# Possible vendor id source values: bluetooth, usb (defaults to usb)
#DeviceID = bluetooth:1234:5678:abcd

# Do reverse service discovery for previously unknown devices that connect to
# us. This option is really only needed for qualification since the BITE tester
# doesn't like us doing reverse SDP for some test cases (though there could in
# theory be other useful purposes for this too). Defaults to 'true'.
#ReverseServiceDiscovery = true

# Enable name resolving after inquiry. Set it to 'false' if you don't need
# remote devices name and want shorter discovery cycle. Defaults to 'true'.
#NameResolving = true

# Enable runtime persistency of debug link keys. Default is false which
# makes debug link keys valid only for the duration of the connection
# that they were created for.
#DebugKeys = false

# Restricts all controllers to the specified transport. Default value
# is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW).
# Possible values: "dual", "bredr", "le"
#ControllerMode = dual

# Enables Multi Profile Specification support. This allows to specify if
# system supports only Multiple Profiles Single Device (MPSD) configuration
# or both Multiple Profiles Single Device (MPSD) and Multiple Profiles Multiple
# Devices (MPMD) configurations.
# Possible values: "off", "single", "multiple"
#MultiProfile = off

# Permanently enables the Fast Connectable setting for adapters that
# support it. When enabled other devices can connect faster to us,
# however the tradeoff is increased power consumptions. This feature
# will fully work only on kernel version 4.1 and newer. Defaults to
# 'false'.
#FastConnectable = false

#[Policy]
#
# The ReconnectUUIDs defines the set of remote services that should try
# to be reconnected to in case of a link loss (link supervision
# timeout). The policy plugin should contain a sane set of values by
# default, but this list can be overridden here. By setting the list to
# empty the reconnection feature gets disabled.
#ReconnectUUIDs=00001112-0000-1000-8000-00805f9b34fb, 0000111f-0000-1000-8000-00805f9b34fb, 0000110a-0000-1000-8000-00805f9b34fb

# ReconnectAttempts define the number of attempts to reconnect after a link
# lost. Setting the value to 0 disables reconnecting feature.
#ReconnectAttempts=7

# ReconnectIntervals define the set of intervals in seconds to use in between
# attempts.
# If the number of attempts defined in ReconnectAttempts is bigger than the
# set of intervals the last interval is repeated until the last attempt.
#ReconnectIntervals=1, 2, 4, 8, 16, 32, 64

# AutoEnable defines option to enable all controllers when they are found.
# This includes adapters present on start as well as adapters that are plugged
# in later on. Defaults to 'false'.
#AutoEnable=false

# dmesg | grep -i Blue
[   20.468258] Bluetooth: Core ver 2.21
[   20.468272] Bluetooth: HCI device and connection manager initialized
[   20.468275] Bluetooth: HCI socket layer initialized
[   20.468277] Bluetooth: L2CAP socket layer initialized
[   20.468281] Bluetooth: SCO socket layer initialized
[   32.500502] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   32.500505] Bluetooth: BNEP filters: protocol multicast
[   32.500510] Bluetooth: BNEP socket layer initialized
[   32.760632] Bluetooth: hci0 setting interface failed (110)
[  154.795468] Bluetooth: hci0 urb ffff88033cf52180 failed to resubmit (113)
[  332.780570] Bluetooth: hci0 urb ffff88033b131c80 failed to resubmit (113)
[  332.780958] Bluetooth: hci0 urb ffff88033b131800 failed to resubmit (113)
[  406.826747] Bluetooth: hci0 setting interface failed (110)
[  506.774297] Bluetooth: hci0 urb ffff88033e27c480 failed to resubmit (113)
[  506.774665] Bluetooth: hci0 urb ffff88033e27c240 failed to resubmit (113)
[  519.925359] Bluetooth: hci0 urb ffff88033e27d200 failed to resubmit (113)
[  519.925733] Bluetooth: hci0 urb ffff88033e27cd80 failed to resubmit (113)


# hciconfig hci0
hci0: Type: BR/EDR  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:5 errors:2

# hciconfig hci up
Can't init device hci0: Connection timed out (110)


# sudo  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
4: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
# lsusb -d 0cf3:3005
Bus 001 Device 003: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth


я так понимаю, необходимо сконфигурировать файл /etc/bluetooth/main.conf
подскажите как можно это сделать?
« Последнее редактирование: 23 Октябрь 2016, 19:13:15 от rishatik92 »

Оффлайн Pilot6

  • Старожил
  • *
  • Сообщений: 11169
    • Просмотр профиля
Re: Проблема с Bluetooth AR3011
« Ответ #1 : 23 Октябрь 2016, 17:22:42 »
Начать надо с того, что у вас за система, что за ядро.
Я в личке не консультирую. Вопросы задавайте на форуме.

Оффлайн rishatik92

  • Автор темы
  • Новичок
  • *
  • Сообщений: 4
    • Просмотр профиля
Re: Проблема с Bluetooth AR3011
« Ответ #2 : 23 Октябрь 2016, 18:48:39 »
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.1 LTS
Release:        16.04
Codename:       xenial

Linux titan-pc 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux



Пользователь добавил сообщение 23 Октябрь 2016, 20:33:51:
Здесь пусто

# hcitool dev
Devices:

При старте системы вижу:
Bluetooth: hci0 setting interface failed (110)
« Последнее редактирование: 23 Октябрь 2016, 20:33:51 от rishatik92 »

Оффлайн Pilot6

  • Старожил
  • *
  • Сообщений: 11169
    • Просмотр профиля
Re: Проблема с Bluetooth AR3011
« Ответ #3 : 23 Октябрь 2016, 20:57:18 »
Тут либо Qualcomm опять новый девайс со старым ID выпустил, либо баг ядра. Конфиги тут ни при чем.
Я в личке не консультирую. Вопросы задавайте на форуме.

Оффлайн rishatik92

  • Автор темы
  • Новичок
  • *
  • Сообщений: 4
    • Просмотр профиля
Re: Проблема с Bluetooth AR3011
« Ответ #4 : 23 Октябрь 2016, 20:59:45 »
Только что починил!

rmmod ath3k
rmmod btusb
modprobe btusb
modprobe ath3k

Видимо проблема с инициализацией.
надо жестко в rc.local прописать.


Оффлайн Pilot6

  • Старожил
  • *
  • Сообщений: 11169
    • Просмотр профиля
Re: Проблема с Bluetooth AR3011
« Ответ #5 : 23 Октябрь 2016, 21:06:02 »
rishatik92,
Если в таком порядке работает, то наверное последняя команда не нужна.
ath3k только грузит фермваре.
Я в личке не консультирую. Вопросы задавайте на форуме.

Оффлайн rishatik92

  • Автор темы
  • Новичок
  • *
  • Сообщений: 4
    • Просмотр профиля
Re: Проблема с Bluetooth AR3011
« Ответ #6 : 23 Октябрь 2016, 21:57:15 »
да, для пущей надёжности оставлю так

 

Страница сгенерирована за 0.054 секунд. Запросов: 24.