You are not logged in.
Hello everyone.
I am unable to get the Bluetooth working in my HP laptop.
I have installed package rtlwifi_new-extended-dkms from AUR to get the Wifi running in my laptop. I am posting the lspci and ip link output for reference.
[guttuganguly@archLT ~]$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter
[guttuganguly@archLT ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether c4:65:16:85:9a:9a brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether dc:f5:05:2f:2b:3d brd ff:ff:ff:ff:ff:ff
I have installed the packages bluez and bluez-utils and started and enabled bluetooth.service, but to no avail.
I am posting the output of the command lsmod
[guttuganguly@archLT ~]$ lsmod
Module Size Used by
ccm 20480 6
fuse 139264 3
bnep 28672 2
snd_hda_codec_hdmi 65536 1
snd_hda_codec_realtek 126976 1
snd_hda_codec_generic 94208 1 snd_hda_codec_realtek
ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_realtek
rtl8723de 110592 0
x86_pkg_temp_thermal 20480 0
intel_powerclamp 20480 0
btcoexist 479232 1 rtl8723de
coretemp 20480 0
i915 2326528 12
phydm_mod 917504 1 rtl8723de
kvm 778240 0
irqbypass 16384 1 kvm
uvcvideo 114688 0
videobuf2_vmalloc 20480 1 uvcvideo
videobuf2_memops 20480 1 videobuf2_vmalloc
videobuf2_v4l2 28672 1 uvcvideo
videobuf2_common 57344 2 videobuf2_v4l2,uvcvideo
videodev 237568 3 videobuf2_v4l2,uvcvideo,videobuf2_common
rtl8723_common 28672 1 rtl8723de
btusb 65536 0
btrtl 24576 1 btusb
mc 61440 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
snd_soc_skl 118784 0
btbcm 16384 1 btusb
btintel 28672 1 btusb
snd_soc_skl_ipc 69632 1 snd_soc_skl
snd_soc_sst_ipc 20480 1 snd_soc_skl_ipc
snd_soc_sst_dsp 40960 1 snd_soc_skl_ipc
snd_hda_ext_core 36864 1 snd_soc_skl
snd_soc_acpi_intel_match 28672 1 snd_soc_skl
bluetooth 675840 12 btrtl,btintel,btbcm,bnep,btusb
snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_soc_skl
snd_soc_core 286720 1 snd_soc_skl
crct10dif_pclmul 16384 1
crc32_pclmul 16384 0
rtl_pci 36864 1 rtl8723de
ghash_clmulni_intel 16384 0
aesni_intel 372736 4
rtlwifi 180224 5 rtl_pci,rtl8723de,btcoexist,phydm_mod,rtl8723_common
ecdh_generic 16384 1 bluetooth
snd_compress 28672 1 snd_soc_core
ac97_bus 16384 1 snd_soc_core
snd_pcm_dmaengine 16384 1 snd_soc_core
aes_x86_64 20480 1 aesni_intel
crypto_simd 16384 1 aesni_intel
i2c_algo_bit 16384 1 i915
mac80211 999424 2 rtl_pci,rtlwifi
drm_kms_helper 212992 1 i915
joydev 28672 0
cryptd 24576 2 crypto_simd,ghash_clmulni_intel
ecc 32768 1 ecdh_generic
glue_helper 16384 1 aesni_intel
mousedev 24576 0
drm 516096 5 drm_kms_helper,i915
intel_cstate 16384 0
intel_uncore 147456 0
cfg80211 856064 2 rtlwifi,mac80211
snd_hda_intel 53248 3
hp_wmi 16384 0
intel_gtt 24576 1 i915
snd_hda_codec 159744 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
sparse_keymap 16384 1 hp_wmi
intel_rapl_perf 16384 0
psmouse 180224 0
agpgart 53248 2 intel_gtt,drm
iTCO_wdt 16384 0
snd_hda_core 102400 7 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_skl
libarc4 16384 1 mac80211
iTCO_vendor_support 16384 1 iTCO_wdt
syscopyarea 16384 1 drm_kms_helper
rfkill 28672 8 hp_wmi,bluetooth,cfg80211
snd_hwdep 20480 1 snd_hda_codec
sysfillrect 16384 1 drm_kms_helper
mei_hdcp 24576 0
intel_rapl_msr 20480 0
wmi_bmof 16384 0
snd_pcm 135168 8 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_core,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine
sysimgblt 16384 1 drm_kms_helper
intel_wmi_thunderbolt 20480 0
pcspkr 16384 0
input_leds 16384 0
fb_sys_fops 16384 1 drm_kms_helper
r8169 94208 0
i2c_hid 32768 0
evdev 24576 13
snd_timer 40960 1 snd_pcm
int3403_thermal 16384 0
hid 143360 1 i2c_hid
snd 110592 16 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm
realtek 20480 1
mac_hid 16384 0
libphy 98304 2 r8169,realtek
intel_pch_thermal 16384 0
soundcore 16384 1 snd
intel_xhci_usb_role_switch 16384 0
processor_thermal_device 20480 0
mei_me 45056 1
roles 16384 1 intel_xhci_usb_role_switch
intel_rapl_common 28672 2 intel_rapl_msr,processor_thermal_device
int340x_thermal_zone 16384 2 int3403_thermal,processor_thermal_device
int3400_thermal 20480 0
intel_soc_dts_iosf 20480 1 processor_thermal_device
acpi_thermal_rel 16384 1 int3400_thermal
mei 122880 3 mei_hdcp,mei_me
wmi 36864 3 hp_wmi,intel_wmi_thunderbolt,wmi_bmof
hp_wireless 16384 0
i2c_i801 36864 0
battery 24576 0
ac 16384 0
nf_log_ipv6 16384 5
ip6t_REJECT 16384 1
nf_reject_ipv6 20480 1 ip6t_REJECT
xt_hl 16384 22
ip6t_rt 20480 3
nf_log_ipv4 16384 5
nf_log_common 16384 2 nf_log_ipv4,nf_log_ipv6
ipt_REJECT 16384 1
nf_reject_ipv4 16384 1 ipt_REJECT
xt_LOG 20480 10
xt_limit 16384 13
xt_addrtype 16384 4
xt_tcpudp 20480 18
xt_conntrack 16384 16
ip6table_filter 16384 1
ip6_tables 36864 53 ip6table_filter
nf_conntrack_netbios_ns 16384 0
nf_conntrack_broadcast 16384 1 nf_conntrack_netbios_ns
nf_nat_ftp 20480 0
nf_nat 53248 1 nf_nat_ftp
nf_conntrack_ftp 24576 1 nf_nat_ftp
nf_conntrack 167936 6 xt_conntrack,nf_nat,nf_nat_ftp,nf_conntrack_netbios_ns,nf_conntrack_broadcast,nf_conntrack_ftp
nf_defrag_ipv6 24576 1 nf_conntrack
nf_defrag_ipv4 16384 1 nf_conntrack
libcrc32c 16384 2 nf_conntrack,nf_nat
iptable_filter 16384 1
crypto_user 16384 0
ip_tables 36864 9 iptable_filter
x_tables 49152 13 ip6table_filter,xt_conntrack,iptable_filter,xt_LOG,xt_tcpudp,xt_addrtype,ip6t_rt,ip6_tables,ipt_REJECT,ip_tables,xt_limit,xt_hl,ip6t_REJECT
ext4 770048 2
crc32c_generic 16384 0
crc16 16384 2 bluetooth,ext4
mbcache 16384 1 ext4
jbd2 135168 1 ext4
sd_mod 57344 4
serio_raw 20480 0
ahci 40960 3
atkbd 36864 0
libps2 20480 2 atkbd,psmouse
libahci 40960 1 ahci
xhci_pci 20480 0
libata 282624 2 libahci,ahci
crc32c_intel 24576 5
xhci_hcd 278528 1 xhci_pci
scsi_mod 249856 2 sd_mod,libata
i8042 32768 0
serio 28672 6 serio_raw,atkbd,psmouse,i8042
The status output of bluetooth is given below
guttuganguly@archLT ~]$ sudo systemctl status bluetooth.service
[sudo] password for guttuganguly:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor p>
Active: active (running) since Thu 2019-11-14 08:28:35 IST; 29min ago
Docs: man:bluetoothd(8)
Main PID: 477 (bluetoothd)
Tasks: 1 (limit: 4565)
Memory: 2.8M
CGroup: /system.slice/bluetooth.service
└─477 /usr/lib/bluetooth/bluetoothd
Nov 14 08:28:34 archLT systemd[1]: Starting Bluetooth service...
Nov 14 08:28:35 archLT bluetoothd[477]: Bluetooth daemon 5.52
Nov 14 08:28:35 archLT bluetoothd[477]: Starting SDP server
Nov 14 08:28:35 archLT systemd[1]: Started Bluetooth service.
Nov 14 08:28:35 archLT bluetoothd[477]: Bluetooth management interface 1.14 ini>
Nov 14 08:28:42 archLT bluetoothd[477]: No Bluetooth address for index 0
lines 1-16/16 (END)...skipping...
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2019-11-14 08:28:35 IST; 29min ago
Docs: man:bluetoothd(8)
Main PID: 477 (bluetoothd)
Tasks: 1 (limit: 4565)
Memory: 2.8M
CGroup: /system.slice/bluetooth.service
└─477 /usr/lib/bluetooth/bluetoothd
Nov 14 08:28:34 archLT systemd[1]: Starting Bluetooth service...
Nov 14 08:28:35 archLT bluetoothd[477]: Bluetooth daemon 5.52
Nov 14 08:28:35 archLT bluetoothd[477]: Starting SDP server
Nov 14 08:28:35 archLT systemd[1]: Started Bluetooth service.
Nov 14 08:28:35 archLT bluetoothd[477]: Bluetooth management interface 1.14 initialized
Nov 14 08:28:42 archLT bluetoothd[477]: No Bluetooth address for index 0
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-16/16 (END)
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2019-11-14 08:28:35 IST; 29min ago
Docs: man:bluetoothd(8)
Main PID: 477 (bluetoothd)
Tasks: 1 (limit: 4565)
Memory: 2.8M
CGroup: /system.slice/bluetooth.service
└─477 /usr/lib/bluetooth/bluetoothd
Nov 14 08:28:34 archLT systemd[1]: Starting Bluetooth service...
Nov 14 08:28:35 archLT bluetoothd[477]: Bluetooth daemon 5.52
Nov 14 08:28:35 archLT bluetoothd[477]: Starting SDP server
Nov 14 08:28:35 archLT systemd[1]: Started Bluetooth service.
Nov 14 08:28:35 archLT bluetoothd[477]: Bluetooth management interface 1.14 initialized
Nov 14 08:28:42 archLT bluetoothd[477]: No Bluetooth address for index 0
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-16/16 (END)
Other relevant outputs are given below
[guttuganguly@archLT ~]$ bluetoothctl
Agent registered
[bluetooth]# power on
No default controller available
I use gnome desktop. In the bluetooth panel in gnome-control-settings, I try to toggle the bluetooth button to 'on' position but nothing happens.
But I have found that using a live usb (Manjaro Linux Gnome) on my laptop I have been able to use bluetooth.
Where I am I going wrong. What am I missing?
Please pardon the long post.
Thanks in advance.
Last edited by guttuganguly (2019-12-09 03:48:25)
Offline
where you able to solve the issue with your bluetooth?
Offline
No my problem is still unsolved as on this day. My WiFi works but my Bluetooth is not working. I use the rtlwifi_new-extended-dkms package from AUR. It should be getting both my WiFi and Bluetooth working. But my Bluetooth woe is still persisting.
I request members of this forum to kindly help me with my problem.
Regards to all.
Offline
I dont know much about your package rtlwifi_new-extended-dkms. but looks like realtek drivers.
What is it your trying to connect with bluetooth? mouse? headset?
are you using a bluetooth dongle?
The relevant issue i see is
No default controller available
Your daemon is working without error.
there is something in your config files probably.
maybe check the wiki again to see if you missed something
https://wiki.archlinux.org/index.php/Bluetooth
Last edited by SurlyCycler (2019-11-23 18:05:52)
Offline
I am not using bluetooth dongle. RTL8723DE is the wifi-bluetooth combined chip in my Laptop. I am trying to connect with android devices using bluetooth but I am unable to get it to work.
Checked out the arch-wiki page on bluetooth to see if I am missing something. Unable to detect anything that I missed. Bluez and Bluez-utils installed, bluetooth service started and enabled. But to no avail. Did configuration changes for auto power on after boot as per arch-wiki but still nothing happens.
Offline
Found a bug report upstream similar to my problem, link given below.
https://github.com/lwfinger/rtlwifi_new/issues/501
Could my problem be due to a present bug in the AUR package?
Offline
It could be. But somehow it always boils down to configs along with new changes software changes in Arch and linux.
It seems to me i did do something to have that happen with my bluetooth but it was a config error or just something in the wrong spot in the config.
by anychance does your hp have a physical bluetooth switch on it?
try this code
$ rfkill list
Last edited by SurlyCycler (2019-11-25 02:16:00)
Offline
No my HP laptop does not have any physical bluetooth switch on it.
rfkill list output is given below
[guttuganguly@archLT ~]$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
My /etc/bluetooth/main.conf output is given below for reference
General]
# Default adapter 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
# Always allow pairing even if there are no agent registered
# Possible values: true, false
# Default: false
#AlwaysPairable = false
[ Read 119 lines ]
^G Get Help ^O Write Out ^W Where Is ^K Cut Text ^J Justify ^C Cur Pos
^X Exit ^R Read File ^\ Replace ^U Paste Text^T To Spell ^_ Go To Line
Offline
make a backup of your main.conf
in your main.conf add the following lines
[General]
# Default adapter name
# Defaults to 'BlueZ X.YZ'
#Name = BlueZ
DiscoverableTimeout = 0
Discoverable=true
and near the bottom you will see you can uncomment by removing the #
[policy]
AutoEnable=true
save and exit out
All this will do is turn bluetooth on automatically upon boot
and get it to look for devices on start
then run
sudo systemctl restart bluetooth
bluetoothctl
power on
if not try a reboot and the bluetoothctl
aslo do
$ groups
im just looking to see that you are part of the "lp" group required by bluetooth
lets see what happens
Last edited by SurlyCycler (2019-11-25 13:46:16)
Offline
I have gone through all the suggestions but to no avail. Bluetooth still does not work.
Some outputs which I hope may prove to be relevant.
[guttuganguly@archLT ~]$ sudo groups
[sudo] password for guttuganguly:
root
[guttuganguly@archLT ~]$ sudo useradd -g guttuganguly lp
useradd: user 'lp' already exists
[guttuganguly@archLT ~]$
Offline
I think wheel and lp are the only groups you need here....
you only need to do goups in $ user. but as long as its there.
Unfortunately im not sure what i can do to help.
I have the same packages other then blueberry and blueman. But i think they only give a few more tools to use.
i also went over to my manjaro boot but there seems to be a minimal install there just like what you have.
The only other thing that comes to mind is to ensure you have the right drivers, and if you had any issues with mkinitcpio installing the kernal (warnings)
keep researching. I am sure you will find a fix
sorry i could help.
Last edited by SurlyCycler (2019-11-27 21:54:25)
Offline
My Bluetooth problem has been solved.
The Bluetooth has started working after updates received on 07-12-2019 which included Linux kernel (version - 5.4.2) as well as Linux-firmware. Many additional packages were also updated during the 07-12-2019 update, so what actually corrected the non functioning Bluetooth, I am not sure. I can only speculate that it must have been the kernel update or/ and Linux-firmware update.
Initially after the update, I found that the WiFi network had also stopped functioning. But the command 'ip link' was showing the wireless interface. So I issued the command 'sudo ip link set <wireless interface> up' and viola not only the WiFi started functioning but the Bluetooth also started working.
So my Bluetooth problem has been solved, by arch updates it seems.
Offline