Ubuntu 22.04 LTS - Bluetooth Atheros AR3012 não funciona. [RESOLVIDO]

SiroBatista
(usa Ubuntu)

Enviado em 23/04/2022 - 15:58h

Oi gente, tudo bem?
Seguinte, eu instalei o recém-lançado Ubuntu 22.04 LTS hoje, mas meu Bluetooth não funciona. Eu percebi que, quando o sistema dá boot, aparece uma linha que antes não aparecia que diz:

- Bluetooth: patch file not found ar3k/AthrBT_0x31010000.dfu
- Bluetooth: Loading patch file failed

Quando uso o "sudo systemctl status bluetooth.service" ele dá essa saída.

bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2022-04-23 15:36:50 -03; 7min ago
Docs: man:bluetoothd(8)
Main PID: 1057 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4533)
Memory: 1.8M
CPU: 73ms
CGroup: /system.slice/bluetooth.service
└─1057 /usr/lib/bluetooth/bluetoothd

abr 23 15:36:50 Siro-Linux systemd[1]: Starting Bluetooth service...
abr 23 15:36:50 Siro-Linux bluetoothd[1057]: Bluetooth daemon 5.64
abr 23 15:36:50 Siro-Linux systemd[1]: Started Bluetooth service.
abr 23 15:36:50 Siro-Linux bluetoothd[1057]: Starting SDP server
abr 23 15:36:50 Siro-Linux bluetoothd[1057]: Bluetooth management interface 1.21 initialized

Parece estar ativo, porém na interface Bluetooth das configurações do sistema mostra como se eu estivesse com o Bluetooth desligado e meu celular não acha o PC também. Tentei os comandos "sudo systemctl enable bluetooth.service", "sudo systemctl start bluetooth.service" e "sudo service bluetooth restart", mas nenhum funcionou. Tentei reinstalar o bluez, atualizar, usar o "sudo apt install -f" pra ver se não tinha algum pacote quebrado, mas também não funcionou, o terminal deu saída de que tudo estava normal com os pacotes.

Meu arquivo do /etc/bluetooth/main.conf está assim:

[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=true

ricardogroetaers
(usa Linux Mint)

Enviado em 23/04/2022 - 18:18h

O que mostra o comando?
inxi -nxxx

SiroBatista
(usa Ubuntu)

Enviado em 23/04/2022 - 20:54h

Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Acer Incorporated ALI driver: r8169 v: kernel pcie: speed: 2.5 GT/s
lanes: 1 port: 3000 bus-ID: 02:00.1 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0f1 state: down mac: f8:a9:63:65:c8:22
Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
vendor: Lite-On driver: ath9k v: kernel pcie: speed: 2.5 GT/s lanes: 1
bus-ID: 03:00.0 chip-ID: 168c:0036 class-ID: 0280
IF: wlp3s0 state: up mac: 5c:c9:d3:50:e8:23

ricardogroetaers
(usa Linux Mint)

Enviado em 24/04/2022 - 01:40h

O dispositivo de rede bluetooth não aparece no comando inxi.
Hipóteses:
- inxi não foi projetado para reconhecer o dispositivo?
- falta drivers para fazer o dispositivo funcionar?
- dispositivo desabilitado no setup?

SiroBatista
(usa Ubuntu)

Enviado em 24/04/2022 - 15:22h

Parece que realmente faltava alguma coisa.
Consegui achar a solução aqui: https://askubuntu.com/questions/1403934/patch-file-not-found-ar3k-athrbt-0x31010000-dfu

Basicamente a solução foi fazer o download da versão 1.201 do linux-firmware e extrair pra conseguir uma pasta lá de dentro chamada ar3k.
Depois disso iniciei meu gerenciador de arquivos, que no caso é o Nautilus, com privilégios de super usuário com "sudo nautilus", copiei a pasta ar3k e colei na /lib/firmware. Depois que reiniciei o Bluetooth voltou.

olivealan
(usa Outra)

Enviado em 28/04/2022 - 09:09h

Após a atualização para 22.04 também fiquei com o mesmo problema no notebook Dell de minha esposa, vou tentar seguir esse procedimento para ver se resolve.
Grato!

ricardogroetaers
(usa Linux Mint)

Enviado em 30/04/2022 - 00:05h

Obrigado pelo tópico.
Obs: O Linux Mint 19.3 (equivalente ao Ubuntu 18.04) já vem com esse firmware, embora esta máquina minha não tenha bluetooth.