[Risolto] Driver bluetooth Atheros AR3011

elauksap · 10 Maggio 2020, 11:48am

Salve a tutti,

ho da qualche giorno installato Fedora 19 KDE sul mio portatile Asus K53SC, funziona tutto alla perfezione tranne due piccoli problemini (per il secondo aprirò un altro topic).
Non riesco ad attivare il bluetooth, fino a ieri avevo anche l’icona nella system tray (pur leggendo il messaggio “No Bluetooth adapters have been found.”) ma oggi è addirittura scomparsa anche quella.

Oggi lsusb mi restituisce:

Bus 001 Device 003: ID 13d3:3304 IMC Networks Asus Integrated Bluetooth module [AR3011]

(ieri invece leggevo anche la marca del produttore, cioè Atheros)

Chiedo aiuto a voi su cosa potrei fare per risolvere questo problema

Grazie in anticipo!

tempus · 10 Maggio 2020, 11:48am

Benvenuto. Proviamo a vedere

[code]$ lsmod

rfkill list[/code]

elauksap · 10 Maggio 2020, 11:48am

lsmod:

Module                  Size  Used by
bnep                   19704  2 
nf_conntrack_netbios_ns    12665  0 
nf_conntrack_broadcast    12527  1 nf_conntrack_netbios_ns
ipt_MASQUERADE         12880  1 
ip6table_nat           13015  1 
nf_nat_ipv6            13213  1 ip6table_nat
ip6table_mangle        12700  1 
ip6table_security      12710  1 
ip6table_raw           12683  1 
ip6t_REJECT            12939  2 
nf_conntrack_ipv6      18782  24 
nf_defrag_ipv6         34589  1 nf_conntrack_ipv6
iptable_nat            13011  1 
nf_nat_ipv4            13199  1 iptable_nat
nf_nat                 25743  5 ipt_MASQUERADE,nf_nat_ipv4,nf_nat_ipv6,ip6table_nat,iptable_nat
iptable_mangle         12695  1 
iptable_security       12705  1 
iptable_raw            12678  1 
nf_conntrack_ipv4      14808  20 
nf_defrag_ipv4         12673  1 nf_conntrack_ipv4
xt_conntrack           12760  42 
nf_conntrack           86430  11 nf_conntrack_netbios_ns,ipt_MASQUERADE,nf_nat,nf_nat_ipv4,nf_nat_ipv6,xt_conntrack,ip6table_nat,nf_conntrack_broadcast,iptable_nat,nf_conntrack_ipv4,nf_conntrack_ipv6
ebtable_filter         12827  0 
ebtables               30758  1 ebtable_filter
ip6table_filter        12815  1 
ip6_tables             26808  5 ip6table_filter,ip6table_mangle,ip6table_security,ip6table_nat,ip6table_raw
bbswitch               13943  0 
fuse                   82599  3 
uvcvideo               80968  0 
videobuf2_vmalloc      13163  1 uvcvideo
videobuf2_memops       13161  1 videobuf2_vmalloc
videobuf2_core         38773  1 uvcvideo
videodev              132348  2 uvcvideo,videobuf2_core
arc4                   12608  2 
ath9k                 141923  0 
ath9k_common           13503  1 ath9k
ath9k_hw              443174  2 ath9k_common,ath9k
ath                    23142  3 ath9k_common,ath9k,ath9k_hw
mac80211              564808  1 ath9k
cfg80211              460310  3 ath,ath9k,mac80211
r8169                  71677  0 
snd_hda_codec_hdmi     41276  1 
mii                    13527  1 r8169
iTCO_wdt               13480  0 
ath3k                  13318  0 
btusb                  28170  0 
nouveau               943445  0 
i2c_i801               18136  0 
snd_hda_codec_realtek    51465  1 
asus_nb_wmi            16990  0 
asus_wmi               24071  1 asus_nb_wmi
sparse_keymap          13584  1 asus_wmi
media                  20840  2 uvcvideo,videodev
iTCO_vendor_support    13419  1 iTCO_wdt
ttm                    79865  1 nouveau
x86_pkg_temp_thermal    14162  0 
coretemp               13435  0 
joydev                 17332  0 
bluetooth             361771  9 bnep,ath3k,btusb
snd_hda_intel          44075  4 
snd_hda_codec         179171  3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep              13554  1 snd_hda_codec
snd_seq                60752  0 
snd_seq_device         14136  1 snd_seq
snd_pcm                98071  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
lpc_ich                21080  0 
mfd_core               13182  1 lpc_ich
rfkill                 21694  5 cfg80211,bluetooth,asus_wmi
snd_page_alloc         18268  2 snd_pcm,snd_hda_intel
snd_timer              28698  2 snd_pcm,snd_seq
snd                    75313  17 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device
mei_me                 18421  0 
mei                    76745  1 mei_me
uinput                 17625  0 
soundcore              14491  1 snd
shpchp                 37032  0 
kvm_intel             138528  0 
kvm                   421021  1 kvm_intel
crc32_pclmul           13113  0 
serio_raw              13413  0 
crc32c_intel           22079  0 
ghash_clmulni_intel    13259  0 
microcode              23527  0 
mperf                  12607  0 
i915                  651861  3 
i2c_algo_bit           13257  2 i915,nouveau
drm_kms_helper         50239  2 i915,nouveau
mxm_wmi                12865  1 nouveau
drm                   278576  6 ttm,i915,drm_kms_helper,nouveau
i2c_core               34242  7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau,videodev
wmi                    18697  3 mxm_wmi,nouveau,asus_wmi
video                  19104  3 i915,nouveau,asus_wmi

rfkill list:

0: asus-wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: asus-bluetooth: Bluetooth
        Soft blocked: yes
        Hard blocked: no
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Anche dando rfkill unblock all, al successivo riavvio è di nuovo soft blocked!

Grazie per la risposta

tempus · 10 Maggio 2020, 11:48am

Sì, vorrei capire se fino al successivo riavvio il bluetooth funziona oppure non funziona neppure dopo aver dato rfkill unblock all

$ find /sys/devices -iname "rfkill*"

elauksap · 10 Maggio 2020, 11:48am

Ottengo questo:

$ find /sys/devices/ -iname "rfkill*" /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill2 /sys/devices/virtual/misc/rfkill /sys/devices/platform/asus-nb-wmi/rfkill /sys/devices/platform/asus-nb-wmi/rfkill/rfkill0 /sys/devices/platform/asus-nb-wmi/rfkill/rfkill1

tempus · 10 Maggio 2020, 11:48am

Bene, ora l’output di# IFS=$'\n'; mapfile -t lista< <(find /sys/devices -iname "rfkill?"); for i in ${lista@]}; do echo "$i"; udevadm info --path "$i" --query=property; done

Al post #4 forse non sono stato chiaro; il bluetooth funziona o no dopo aver dato rfkill unblock all (fino al successivo riavvio)?

elauksap · 10 Maggio 2020, 11:48am

/sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill2 DEVPATH=/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill2 RFKILL_NAME=phy0 RFKILL_STATE=1 RFKILL_TYPE=wlan SUBSYSTEM=rfkill /sys/devices/platform/asus-nb-wmi/rfkill/rfkill0 DEVPATH=/devices/platform/asus-nb-wmi/rfkill/rfkill0 RFKILL_NAME=asus-wlan RFKILL_STATE=1 RFKILL_TYPE=wlan SUBSYSTEM=rfkill /sys/devices/platform/asus-nb-wmi/rfkill/rfkill1 DEVPATH=/devices/platform/asus-nb-wmi/rfkill/rfkill1 RFKILL_NAME=asus-bluetooth RFKILL_STATE=1 RFKILL_TYPE=bluetooth SUBSYSTEM=rfkill

No, anche dopo rfkill unblock all continuo a leggere “No adapters found”.
Ancora grazie per la disponibilità

tempus · 10 Maggio 2020, 11:48am

Per quanto riguarda rfkill:

# echo 'SUBSYSTEM=="rfkill", ATTR{type}=="bluetooth", ATTR{state}="1"' > /etc/udev/rules.d/99-rfkill.rules

(dovrebbe “sbloccare” il bluetooth all’avvio).
Venendo all’effettivo funzionamento del bluetooth, mostra

$ tree /sys/bus/usb/drivers/

elauksap · 10 Maggio 2020, 11:48am

Ecco l’albero:

├── ath3k
│   ├── bind
│   ├── module -> ../../../../module/ath3k
│   ├── new_id
│   ├── remove_id
│   ├── uevent
│   └── unbind
├── btusb
│   ├── bind
│   ├── module -> ../../../../module/btusb
│   ├── new_id
│   ├── remove_id
│   ├── uevent
│   └── unbind
├── hub
│   ├── 1-0:1.0 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-0:1.0
│   ├── 1-1:1.0 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1:1.0
│   ├── 2-0:1.0 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-0:1.0
│   ├── 2-1:1.0 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0
│   ├── 3-0:1.0 -> ../../../../devices/pci0000:00/0000:00:1c.3/0000:04:00.0/usb3/3-0:1.0
│   ├── 4-0:1.0 -> ../../../../devices/pci0000:00/0000:00:1c.3/0000:04:00.0/usb4/4-0:1.0
│   ├── bind
│   ├── module -> ../../../../module/usbcore
│   ├── new_id
│   ├── remove_id
│   ├── uevent
│   └── unbind
├── usb
│   ├── 1-1 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1
│   ├── 1-1.1 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1
│   ├── 1-1.2 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2
│   ├── 1-1.4 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4
│   ├── 2-1 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1
│   ├── 2-1.1 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1
│   ├── bind
│   ├── uevent
│   ├── unbind                                                                    
│   ├── usb1 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1                  
│   ├── usb2 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2                  
│   ├── usb3 -> ../../../../devices/pci0000:00/0000:00:1c.3/0000:04:00.0/usb3
│   └── usb4 -> ../../../../devices/pci0000:00/0000:00:1c.3/0000:04:00.0/usb4
├── usbfs
│   ├── bind
│   ├── module -> ../../../../module/usbcore
│   ├── new_id
│   ├── remove_id
│   ├── uevent
│   └── unbind
├── usbhid
│   ├── 2-1.1:1.0 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0
│   ├── 2-1.1:1.1 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.1
│   ├── bind
│   ├── module -> ../../../../module/usbhid
│   ├── new_id
│   ├── remove_id
│   ├── uevent
│   └── unbind
├── usbserial
│   ├── bind
│   ├── uevent
│   └── unbind
├── usbserial_generic
│   ├── bind
│   ├── uevent
│   └── unbind
└── uvcvideo
    ├── 1-1.2:1.0 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0
    ├── 1-1.2:1.1 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1
    ├── bind
    ├── module -> ../../../../module/uvcvideo
    ├── new_id
    ├── remove_id
    ├── uevent
    └── unbind

35 directories, 39 files

Grazie a quel comando adesso all’avvio non è più soft blocked, pur rimanendo la situazione invariata

tempus · 10 Maggio 2020, 11:48am

Proviamo con

# echo "install ath3k modprobe --ignore-install ath3k ; /usr/bin/printf '%s\n' '13d3 3304' >> /sys/bus/usb/drivers/ath3k/new_id" > /etc/modprobe.d/ath3k-bluetooth.conf

; riavvia, vedi come si comporta

elauksap · 10 Maggio 2020, 11:48am

Mmm non è cambiato ancora nulla! Sempre “No adapters found”

tempus · 10 Maggio 2020, 11:48am

Torniamo al post #1.

[quote]Oggi lsusb mi restituisce:
…]

(ieri invece …][/quote]

[code]# yum history packages-info linux-firmware

rpm -qa kernel*[/code]

; se fai boot con un kernel precedente l’output di lsusb muta?
EDIT: anche

# systemctl status bluetooth.service

elauksap · 10 Maggio 2020, 11:48am

Anche con il kernel precedente l’output rimane uguale.

Ecco i tre output:

[code]Transaction ID : 4
Begin time : Tue Oct 1 15:37:12 2013
Package : linux-firmware-20130418-0.1.gitb584174.fc19.noarch
State : Updated
Size : 38,911,189
Build host : buildvm-26.phx2.fedoraproject.org
Build time : Thu Apr 18 16:57:27 2013
Packager : Fedora Project
Vendor : Fedora Project
License : GPL+ and GPLv2+ and MIT and Redistributable, no modification permitted
URL : http://www.kernel.org/
Source RPM : linux-firmware-20130418-0.1.gitb584174.fc19.src.rpm
Commit Time : Thu Apr 18 14:00:00 2013
Committer : Josh Boyer [email protected]
Reason : dep
From repo : koji-override-0
Installed by : root

Transaction ID : 4
Begin time : Tue Oct 1 15:37:12 2013
Package : linux-firmware-20130724-29.git31f6b30.fc19.noarch
State : Update
Size : 42,286,142
Build host : buildvm-11.phx2.fedoraproject.org
Build time : Wed Sep 4 18:03:38 2013
Packager : Fedora Project
Vendor : Fedora Project
License : GPL+ and GPLv2+ and MIT and Redistributable, no modification permitted
URL : http://www.kernel.org/
Source RPM : linux-firmware-20130724-29.git31f6b30.fc19.src.rpm
Commit Time : Fri Jul 26 14:00:00 2013
Committer : Dave Airlie [email protected]
Reason : dep
From repo : updates
Installed by : root
Changed by : System

Transaction ID : 1
Begin time : Thu Jun 27 19:09:59 2013
Package : linux-firmware-20130418-0.1.gitb584174.fc19.noarch
State : Dep-Install
Size : 38,911,189
Build host : buildvm-26.phx2.fedoraproject.org
Build time : Thu Apr 18 16:57:27 2013
Packager : Fedora Project
Vendor : Fedora Project
License : GPL+ and GPLv2+ and MIT and Redistributable, no modification permitted
URL : http://www.kernel.org/
Source RPM : linux-firmware-20130418-0.1.gitb584174.fc19.src.rpm
Commit Time : Thu Apr 18 14:00:00 2013
Committer : Josh Boyer [email protected]
Reason : dep
From repo : koji-override-0
Installed by : root
history packages-info
[/code]

kernel-devel-3.11.2-201.fc19.x86_64 kernel-3.9.5-301.fc19.x86_64 kernel-modules-extra-3.9.5-301.fc19.x86_64 kernel-headers-3.11.2-201.fc19.x86_64 kernel-3.11.2-201.fc19.x86_64 kernel-modules-extra-3.11.2-201.fc19.x86_64

[code]bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
Active: active (running) since Sat 2013-10-05 14:39:39 CEST; 48min ago
Main PID: 943 (bluetoothd)
CGroup: name=systemd:/system/bluetooth.service
└─943 /usr/sbin/bluetoothd -n

Oct 05 14:39:39 elauksap-PC bluetoothd[943]: Bluetooth daemon 4.101
Oct 05 14:39:39 elauksap-PC bluetoothd[943]: Starting SDP server
Oct 05 14:39:39 elauksap-PC systemd[1]: Starting Bluetooth service…
Oct 05 14:39:39 elauksap-PC systemd[1]: Started Bluetooth service.
Oct 05 14:39:39 elauksap-PC bluetoothd[943]: bluetoothd[943]: Bluetooth daemon…1
Oct 05 14:39:39 elauksap-PC bluetoothd[943]: bluetoothd[943]: Starting SDP server
Oct 05 14:39:40 elauksap-PC bluetoothd[943]: bluetoothd[943]: Parsing /etc/blu…y
Oct 05 14:39:40 elauksap-PC bluetoothd[943]: bluetoothd[943]: Bluetooth Manage…d
Oct 05 14:39:40 elauksap-PC bluetoothd[943]: Parsing /etc/bluetooth/input.conf…y
Oct 05 14:39:40 elauksap-PC bluetoothd[943]: Bluetooth Management interface in…d
[/code]

tempus · 10 Maggio 2020, 11:48am

Proviamo con

# echo "options ath9k btcoex_enable=1" > /etc/modprobe.d/ath9k.conf

, riavvia, vedi come si comporta. Se persiste il problema, vediamo

# journalctl -axb -u bluetooth.service

elauksap · 10 Maggio 2020, 11:48am

[code]Oct 05 16:42:13 elauksap-PC bluetoothd[722]: Bluetooth daemon 4.101
Oct 05 16:42:13 elauksap-PC bluetoothd[722]: Starting SDP server
Oct 05 16:42:12 elauksap-PC systemd[1]: Starting Bluetooth service…
– Subject: Unit bluetooth.service has begun with start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit bluetooth.service has begun starting up.
Oct 05 16:42:13 elauksap-PC bluetoothd[722]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Oct 05 16:42:13 elauksap-PC bluetoothd[722]: Bluetooth Management interface initialized
Oct 05 16:42:13 elauksap-PC bluetoothd[722]: bluetoothd[722]: Bluetooth daemon 4.101
Oct 05 16:42:13 elauksap-PC bluetoothd[722]: bluetoothd[722]: Starting SDP server
Oct 05 16:42:13 elauksap-PC bluetoothd[722]: bluetoothd[722]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Oct 05 16:42:13 elauksap-PC bluetoothd[722]: bluetoothd[722]: Bluetooth Management interface initialized
[/code]

tempus · 10 Maggio 2020, 11:48am

Vediamo

$ rpm -qa bluez\*|sort $ lspci -nnk|grep -iA6 net

elauksap · 10 Maggio 2020, 11:48am

Ecco:

bluez-4.101-9.fc19.x86_64 bluez-alsa-4.101-9.fc19.x86_64 bluez-compat-4.101-9.fc19.x86_64 bluez-cups-4.101-9.fc19.x86_64 bluez-gstreamer-4.101-9.fc19.x86_64 bluez-hcidump-2.5-2.fc19.x86_64 bluez-hid2hci-4.101-9.fc19.x86_64 bluez-libs-4.101-9.fc19.x86_64 bluez-libs-devel-4.101-9.fc19.x86_64

03:00.0 Network controller [0280]: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01) Subsystem: AzureWave AW-NB037H 802.11bgn Wireless Half-size Mini PCIe Card [AR9002WB-1NGCD] [1a3b:2c37] Kernel driver in use: ath9k 04:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller [1b21:1042] Subsystem: ASUSTeK Computer Inc. Device [1043:1059] Kernel driver in use: xhci_hcd 05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) Subsystem: ASUSTeK Computer Inc. Device [1043:1277] Kernel driver in use: r8169

e ancora grazie per la pazienza

tempus · 10 Maggio 2020, 11:48am

[code]# rm /etc/modprobe.d/ath3k-bluetooth.conf

echo “options ath9k btcoex_enable=1 bt_ant_diversity=1” > /etc/modprobe.d/ath9k.conf[/code]

; riavvia. Controlla nel BIOS se è impostata qualche opzione relativa al bluetooth.
Vediamo

[code]# journalctl -axb -u NetworkManager.service -p 4

journalctl -axb -u bluetooth.service

hcitool dev

hciconfig[/code]

elauksap · 10 Maggio 2020, 11:48am

Oct 06 19:10:19 elauksap-PC NetworkManager[650]: <warn> failed to allocate link cache: (-10) Operation not supported Oct 06 19:10:20 elauksap-PC NetworkManager[650]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... Oct 06 19:10:20 elauksap-PC NetworkManager[650]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... Oct 06 19:10:20 elauksap-PC NetworkManager[650]: <warn> Trying to remove a non-existant call id. Oct 06 19:10:32 elauksap-PC NetworkManager[650]: <warn> No agents were available for this request. Oct 06 19:10:32 elauksap-PC NetworkManager[650]: <warn> Activation (wlp3s0) failed for connection 'elauksap' Oct 06 19:10:33 elauksap-PC NetworkManager[650]: <warn> (wlp3s0) firewall zone remove failed: (32) UNKNOWN_INTERFACE: wlp3s0 Oct 06 19:11:07 elauksap-PC NetworkManager[650]: <warn> Dispatcher script timed out: Script '/etc/NetworkManager/dispatcher.d/10-sendmail' timed out. Oct 06 19:11:07 elauksap-PC NetworkManager[650]: <warn> Dispatcher script timed out: Script '/etc/NetworkManager/dispatcher.d/20-chrony' timed out.

[code]-- Logs begin at Tue 2013-10-01 14:43:42 CEST, end at Sun 2013-10-06 19:13:36 CEST
Oct 06 19:10:19 elauksap-PC systemd[1]: Starting Bluetooth service…
– Subject: Unit bluetooth.service has begun with start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit bluetooth.service has begun starting up.
Oct 06 19:10:19 elauksap-PC bluetoothd[977]: Bluetooth daemon 4.101
Oct 06 19:10:19 elauksap-PC bluetoothd[977]: Starting SDP server
Oct 06 19:10:19 elauksap-PC bluetoothd[977]: Parsing /etc/bluetooth/input.conf fai
Oct 06 19:10:19 elauksap-PC bluetoothd[977]: Bluetooth Management interface initia
Oct 06 19:10:19 elauksap-PC systemd[1]: Started Bluetooth service.
– Subject: Unit bluetooth.service has finished start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit bluetooth.service has finished starting up.

– The start-up result is done.
Oct 06 19:10:20 elauksap-PC bluetoothd[977]: bluetoothd[977]: Bluetooth daemon 4.1
Oct 06 19:10:20 elauksap-PC bluetoothd[977]: bluetoothd[977]: Starting SDP server
Oct 06 19:10:20 elauksap-PC bluetoothd[977]: bluetoothd[977]: Parsing /etc/bluetoo
Oct 06 19:10:20 elauksap-PC bluetoothd[977]: bluetoothd[977]: Bluetooth Management[/code]

hcitool invece non rileva nessun dispositivo.

PS: nel frattempo ho aggiornato al kernel 3.11.3, ma ovviamente ancora nulla! E nel BIOS non trovo alcuna opzione per il bluetooth

tempus · 10 Maggio 2020, 11:48am

In sequenza:

[code]# systemctl stop bluetooth.service

rmmod btusb

rmmod ath3k

modprobe -a ath3k

echo “13d3 3304” > /sys/bus/usb/drivers/ath3k/new_id

modprobe btusb

systemctl start bluetooth.service[/code]

; se non rileva ancora nulla, nemmeno con hcitool/hciconfig e nessun altro messaggio di errore compare su

# systemctl status bluetooth.service temo di non poter tentare di aiutarti oltre, se non reindirizzandoti su https://bugzilla.redhat.com/createaccount.cgi.