Bluetooth killed by an update?

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
venik212
Posts: 151
Joined: Mon Jul 06, 2020 9:42 am

Bluetooth killed by an update?

#1 Post by venik212 »

Somehow (due to an update? change in the weather? planet misalignment?) blue manager and blue adapter no longer work, or even appear when chosen from the whisker menu. None of the cli revival commands I tried helped. This is on a Dell XPS 13 (9310). Bluetooth works fine on the Windows side of this dual boot system.

Code: Select all

Snapshot created on: 20221126_0604
System:    Kernel: 6.1.0-7mx-ahs-amd64 [6.1.20-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-7mx-ahs-amd64 
           root=UUID=<filter> ro quiet splash 
           init=/lib/systemd/systemd 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.3_x64 Wildflower November 26  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: XPS 13 9310 v: N/A serial: <filter> Chassis: 
           type: 10 serial: <filter> 
           Mobo: Dell model: 0MRT12 v: A00 serial: <filter> UEFI: Dell v: 3.13.1 date: 02/20/2023 
Battery:   ID-1: BAT0 charge: 47.4 Wh (100.0%) condition: 47.4/51.0 Wh (93.0%) volts: 8.4 min: 7.6 
           model: BYD DELL FP86V09 type: Li-poly serial: <filter> status: Full 
CPU:       Info: Quad Core model: 11th Gen Intel Core i7-1185G7 bits: 64 type: MT MCP 
           arch: Tiger Lake family: 6 model-id: 8C (140) stepping: 1 microcode: A6 cache: 
           L2: 12 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 47923 
           Speed: 998 MHz min/max: 400/4800 MHz Core speeds (MHz): 1: 1054 2: 979 3: 748 4: 3000 
           5: 1200 6: 946 7: 1094 8: 3000 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Dell driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:9a49 class-ID: 0300 
           Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 3-6:99 
           chip-ID: 0c45:672a class-ID: 0e02 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x318mm (20.0x12.5") 
           s-diag: 599mm (23.6") 
           Monitor-1: eDP-1 res: 1920x1200 hz: 60 dpi: 169 size: 288x180mm (11.3x7.1") 
           diag: 340mm (13.4") 
           OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: Dell 
           driver: sof-audio-pci-intel-tgl alternate: snd_hda_intel,snd_sof_pci_intel_tgl 
           bus-ID: 00:1f.3 chip-ID: 8086:a0c8 class-ID: 0401 
           Sound Server-1: ALSA v: k6.1.0-7mx-ahs-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Qualcomm QCA6390 Wireless Network Adapter vendor: Rivet Networks 
           driver: ath11k_pci v: kernel port: efa0 bus-ID: 72:00.0 chip-ID: 17cb:1101 
           class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
           IF-ID-1: surfshark_ipv6 state: unknown speed: N/A duplex: N/A mac: <filter> 
           IF-ID-2: surfshark_wg state: unknown speed: N/A duplex: N/A mac: N/A 
Drives:    Local Storage: total: 2.1 TiB used: 221.98 GiB (10.3%) 
           ID-1: /dev/mmcblk0 maj-min: 179:0 model: FE4S5 size: 238.75 GiB block-size: 
           physical: 512 B logical: 512 B type: SSD serial: <filter> scheme: MBR 
           SMART Message: Unknown smartctl error. Unable to generate data. 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-2: /dev/nvme0n1 maj-min: 259:0 vendor: KIOXIA model: KXG60PNV2T04 NVMe 2048GB 
           size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
           type: SSD serial: <filter> rev: 10704104 temp: 44.9 C scheme: GPT 
Partition: ID-1: / raw-size: 949.97 GiB size: 933.99 GiB (98.32%) used: 221.9 GiB (23.8%) fs: ext4 
           dev: /dev/nvme0n1p4 maj-min: 259:4 
           ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 86.2 MiB (89.8%) fs: vfat 
           dev: /dev/nvme0n1p1 maj-min: 259:1 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 49.0 C mobo: 44.0 C 
           Fan Speeds (RPM): cpu: 4681 fan-2: 4403 
Repos:     Packages: 2553 note: see --pkg apt: 2547 lib: 1125 flatpak: 6 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://la.mxrepo.com/mx/repo/ bullseye main non-free
           No active apt repos in: /etc/apt/sources.list.d/nordvpn.list 
           Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
           1: deb [arch=amd64] https://repo.skype.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/surfshark.list 
           1: deb https://ocean.surfshark.com/debian stretch main
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb http://linux.teamviewer.com/deb stable main
Info:      Processes: 291 Uptime: 4h 2m wakeups: 2677 Memory: 31.06 GiB used: 3.04 GiB (9.8%) 
           Init: systemd v: 247 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

User avatar
j2mcgreg
Global Moderator
Posts: 6545
Joined: Tue Oct 23, 2007 12:04 pm

Re: Bluetooth killed by an update?

#2 Post by j2mcgreg »

I had similar problems when using the 6.1 kernel with my HP 15 ( same age as your XPS). This issue was solved for me when I upgraded to the Liquorix 6.2.6 kernel that is available under the Enabled Repos tab of MXPI. Note that you will also have to install the corresponding headers.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
Stevo
Developer
Posts: 14420
Joined: Fri Dec 15, 2006 7:07 pm

Re: Bluetooth killed by an update?

#3 Post by Stevo »

MX updater has an option to list the update history, so if you post that, it might show whether it's causation or coincidence.
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing

venik212
Posts: 151
Joined: Mon Jul 06, 2020 9:42 am

Re: Bluetooth killed by an update?

#4 Post by venik212 »

Thanks. I could not find the (probably very useful) update history-- when I click on the updater tray icon I get the synaptic package manager, which does have something called history, but it stopped two years ago... ;-(

User avatar
richb
Administrator
Posts: 10842
Joined: Wed Jul 12, 2006 2:17 pm

Re: Bluetooth killed by an update?

#5 Post by richb »

Right click on the updater icon. A popup will show where you can click on history.
Forum Rules
Guide - How to Ask for Help

richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB

venik212
Posts: 151
Joined: Mon Jul 06, 2020 9:42 am

Re: Bluetooth killed by an update?

#6 Post by venik212 »

I was unable to find the Liquorix kernel, and my bluetooth manager is still AWOL. Never a dull moment while using MX...

Post Reply

Return to “MX Help”