Hello! I have been using KDE Manjaro for about 3 days now and I have had a bunch of issues with bluetooth connectivity. My bluetooth mouse will work flawlessly sometimes and then just cut out and stop working. It is not a hardware issue because manjaro says it’s connected, even if I turn it off. Also if I try and disconnect the device from the bluetooth panel it does not work. I also cannot turn off bluetooth and turn it back on, as the bluetooth panel comes back but is greyed out and just hangs that way. I am very frustrated 
, any help is appreciated. Thank you!
inxi -Gazy
might help us understand.
but yeah … bluetooth is gross in general.
for some reason it thinks i’m posting a link
pastebin(dot)com/raw/GwP3gpqN
Oh gosh.
I am so quick to give the graphics version 
inxi -Nazy
will be our network version. sorry.
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 01:00.0
chip ID: 8086:2723
Also I see that it says
Display: x11 server: X. Org 1.20.8 compositor: kwin_x11 driver: amdgpu
FAILED: ati unloaded: modesetting alternate: fbdev,vesa display ID: :0
Is this a bad thing?
Thats fine … its using amdgpu … so the other dont work … no worries.
To your wireless/bt card
there are some options for iwlwifi that might make it work better … but I cant find them at the moment.
Something about bt_coex I think.
when do you think you could find them? Thank you for your help.
Also when I put the PC in sleep it won’t turn back on, it display a corrupted type image and the cursor will appear and it’s nothing but black. Thank you cscs!
Ok lets just do the whole thing . take a look at this (and please provide the inxi in code format)
System:
Kernel: 5.8.3-2-MANJARO x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64
root=UUID=9c35f079-eaf6-4901-ab9c-20678485dc21 rw quiet apparmor=1
security=apparmor resume=UUID=b3fcebbd-c5c6-4c7a-be26-86375fb284d4
udev.log_priority=3
Desktop: KDE Plasma 5.19.4 tk: Qt 5.15.0 wm: kwin_x11 dm: SDDM
Distro: Manjaro Linux
Machine:
Type: Convertible System: HP product: HP ENVY x360 Convertible 15m-ee0xxx
v: Type1ProductConfigId serial: Chassis: type: 31 serial:
Mobo: HP model: 876F v: 13.35 serial: UEFI: Insyde v: F.11
date: 06/23/2020
Battery:
ID-1: BAT1 charge: 47.4 Wh condition: 50.5/51.0 Wh (99%) volts: 13.2/11.6
model: Hewlett-Packard PABAS0241231 type: Li-ion serial:
status: Charging
Device-1: hid-0018:04F3:2B05.0001-battery model: ELAN2514:00 04F3:2B05
serial: N/A charge: N/A status: N/A
CPU:
Topology: 6-Core model: AMD Ryzen 5 4500U with Radeon Graphics bits: 64
type: MCP arch: Zen family: 17 (23) model-id: 60 (96) stepping: 1
microcode: 8600102 L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 28455
Speed: 1398 MHz min/max: 1400/2375 MHz boost: enabled Core speeds (MHz):
1: 1397 2: 1397 3: 1397 4: 1397 5: 1397 6: 1397
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW,
STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Renoir vendor: Hewlett-Packard driver: amdgpu v: kernel
bus ID: 04:00.0 chip ID: 1002:1636
Display: x11 server: X(dot)Org 1.20.8 compositor: kwin_x11 driver: amdgpu
FAILED: ati unloaded: modesetting alternate: fbdev,vesa display ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: eDP res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.5x7.6")
diag: 395mm (15.5")
OpenGL: renderer: AMD RENOIR (DRM 3.38.0 5.8.3-2-MANJARO LLVM 10.0.1)
v: 4.6 Mesa 20.1.6 direct render: Yes
Audio:
Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
bus ID: 04:00.1 chip ID: 1002:1637
Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
vendor: Hewlett-Packard driver: snd_rn_pci_acp3x v: kernel
alternate: snd_pci_acp3x bus ID: 04:00.5 chip ID: 1022:15e2
Device-3: AMD Family 17h HD Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus ID: 04:00.6 chip ID: 1022:15e3
Sound Server: ALSA v: k5.8.3-2-MANJARO
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 01:00.0
chip ID: 8086:2723
IF: wlo1 state: up mac:
IF-ID-1: virbr0 state: down mac:
IF-ID-2: virbr0-nic state: down mac:
Drives:
Local Storage: total: 238.47 GiB used: 82.57 GiB (34.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLQ256HAJD-000H1
size: 238.47 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 serial: rev: HPS4NFXV scheme: GPT
Partition:
ID-1: / raw size: 229.37 GiB size: 224.77 GiB (97.99%)
used: 82.57 GiB (36.7%) fs: ext4 dev: /dev/nvme0n1p2
Swap:
Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.80 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p3
Sensors:
System Temperatures: cpu: 41.6 C mobo: 20.0 C gpu: amdgpu temp: 35 C
Fan Speeds (RPM): N/A
Info:
Processes: 237 Uptime: 44m Memory: 7.23 GiB used: 1.74 GiB (24.1%)
Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: pacman: 1285 lib: 357
flatpak: 0 Shell: Bash v: 5.0.18 running in: konsole inxi: 3.1.05
After doing some investigation, I found an article about iwlwifi on the debian wiki, and it said the following:
Some devices like the 6235 do include a Bluetooth device in the same card, which may lead into radio conflict. Newer devices (7200 and up) try to solve them intelligently, but it is not the case of older ones.
If your WiFi is slow when using Bluetooth, try adding the following to /etc/modprobe.d/iwlwifi.conf and reboot: options iwlwifi bt_coex_active=0 swcrypto=1 11n_disable=8
This appears to have solved the issue, but I cannot say as to whether or not it is just being agreeable at the moment or if it is actually a long-term solution. Sleep mode also appears to be working in order at the moment, but I have only tested it once and it could be a random but rare occurrence. If it happens again I will create a thread following the guidelines of the article you have posted about good information, along with pictures of the anomalies that appear on the screen. Thank you cscs!
2 Likes
After some usage, I have come to the conclusion that this has created a SIGNIFICANT improvement over the original performance. The issue has been resolved.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.