LM18 - bluetooth always becomes enabled on thaw

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
michaeldjcox
Level 2
Level 2
Posts: 65
Joined: Mon Feb 10, 2014 10:31 am

LM18 - bluetooth always becomes enabled on thaw

Post by michaeldjcox »

Recently did the inplace upgrade from 17.3 to 18.

All worked well except one or two minor irritants.

I only occasionally use bluetooth so its generally off.

I notice that if I suspend and then resume everything is fine bluetooth remains disabled.

But if I hibernate and then thaw bluetooth always comes back turned on.

I had similar problems with 17.3 and changed pm-utils to always disable all radio on hibernate or suspend and this worked fine.

But of course linux mint 18 uses systemd and not pm-utils so my scripts are no longer run. I've tried hooking my script into various places in systemd to perform rfkill but it always ends up with thaw/resume failing because whatever I'm doing seems in interfere with what systemd is up to.

Anybody also seeing this issue please? Can anyone have a solution?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
bbaker6212
Level 5
Level 5
Posts: 538
Joined: Wed Aug 12, 2015 6:35 pm

Re: LM18 - bluetooth always becomes enabled on thaw

Post by bbaker6212 »

paste output from:

Code: Select all

lspci -nnk | grep -iA2 net; lsusb; rfkill list all; uname -a; dmesg | egrep -i 'blue|firm'
Linux Mint XFCE 21.1 , Windows 11, Pop!_OS 22.04 Acer Aspire 5 A515-57 (linux-probe), Core i5-1235U, 16GB RAM
Lenovo Ideapad 330S-15IKB (linux-probe), Core i5-8250U, 20GB RAM
michaeldjcox
Level 2
Level 2
Posts: 65
Joined: Mon Feb 10, 2014 10:31 am

Re: LM18 - bluetooth always becomes enabled on thaw

Post by michaeldjcox »

This is post-thaw where bluetooth has auto-enabled

Code: Select all

michael@mintpad ~ $ lspci -nnk | grep -iA2 net; lsusb; rfkill list all; uname -a; dmesg | egrep -i 'blue|firm'
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I218-LM [8086:155a] (rev 04)
	Subsystem: Lenovo ThinkPad X240 [17aa:2214]
	Kernel driver in use: e1000e
--
03:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b2] (rev 83)
	Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c270]
	Kernel driver in use: iwlwifi
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 5986:026a Acer, Inc 
Bus 002 Device 007: ID 8087:07dc Intel Corp. 
Bus 002 Device 003: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
Bus 002 Device 002: ID 0bdb:193e Ericsson Business Mobile Networks BV 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
	Soft blocked: no
	Hard blocked: no
3: phy0: Wireless LAN
	Soft blocked: yes
	Hard blocked: no
5: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
Linux mintpad 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[    0.344538] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[    5.246142] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[    5.333637] Bluetooth: Core ver 2.21
[    5.333651] Bluetooth: HCI device and connection manager initialized
[    5.333655] Bluetooth: HCI socket layer initialized
[    5.333658] Bluetooth: L2CAP socket layer initialized
[    5.333663] Bluetooth: SCO socket layer initialized
[    5.350520] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-7260-17.ucode failed with error -2
[    5.353776] iwlwifi 0000:03:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm
[    5.382558] Bluetooth: hci0: read Intel version: 370710018002030d00
[    5.385191] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[    5.515526] Bluetooth: hci0 exiting Intel manufacturer mode failed (-19)
[    5.759989] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.759992] Bluetooth: BNEP filters: protocol multicast
[    5.759997] Bluetooth: BNEP socket layer initialized
[    7.551317] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 4028.137250] Bluetooth: hci0: read Intel version: 370710018002030d00
[ 4028.460986] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[ 4028.585255] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 4028.676181] Bluetooth: RFCOMM TTY layer initialized
[ 4028.676188] Bluetooth: RFCOMM socket layer initialized
[ 4028.676193] Bluetooth: RFCOMM ver 1.11
[ 6238.814776] Bluetooth: hci0: read Intel version: 370710018002030d00
[ 6239.142580] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[ 6239.267781] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 6271.891955] Modules linked in: cmac uhid hid rfcomm drbg ansi_cprng ctr ccm bnep binfmt_misc nls_iso8859_1 arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel uvcvideo videobuf2_vmalloc aes_x86_64 videobuf2_memops lrw gf128mul videobuf2_v4l2 glue_helper ablk_helper cryptd iwlmvm videobuf2_core v4l2_common mac80211 videodev joydev input_leds media cdc_mbim snd_hda_codec_hdmi btusb cdc_ncm btrtl usbnet btbcm btintel mii bluetooth cdc_wdm cdc_acm snd_hda_codec_realtek snd_hda_codec_generic serio_raw iwlwifi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep cfg80211 rtsx_pci_ms lpc_ich snd_pcm memstick shpchp thinkpad_acpi nvram snd_seq_midi mei_me snd_seq_midi_event mei snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore mac_hid
michaeldjcox
Level 2
Level 2
Posts: 65
Joined: Mon Feb 10, 2014 10:31 am

Re: LM18 - bluetooth always becomes enabled on thaw

Post by michaeldjcox »

I found this link which describes the problem

https://github.com/systemd/systemd/issues/3026
Locked

Return to “Networking”