On gnome, i can't stop bluetoothrnel/firmware

Pommede1 · June 23, 2025, 4:35pm

~hello

on gnome, when i try to stop the bluetooth, i have the aeroplane mode which turns on, turns off and the bluetooth turns on again.
i have this error:

Bluetooth: hci0: HCI reset during shutdown failed
Error Bluetooth: hci0: Initiating acpi reset method
Error Bluetooth: hci0: command 0x0c1a tx timeout
Error Bluetooth: hci0: Error when powering off device on rfkill (-110)
Error Bluetooth: hci0: Opcode 0x0c1a failed: -110

a problem with the kernel/firmware; anyone with a A211 bluetooth with this problem?
thanks for your help

System:
  Kernel: 6.15.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=c40ef420-4ede-40ec-a143-6dabd770e681 rw rootflags=subvol=@
    loglevel=3 ibt=off
  Desktop: GNOME v: 48.2 tk: GTK v: 3.24.49 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 48.0 Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 21BN002VFR v: ThinkPad X13 Gen 3
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 21BN002VFR
    serial: <superuser required> part-nu: LENOVO_MT_21BN_BU_Think_FM_ThinkPad
    X13 Gen 3 uuid: <superuser required> UEFI: LENOVO v: N3CET65W (1.46 )
    date: 11/14/2024
Battery:
  ID-1: BAT0 charge: 28.4 Wh (58.4%) condition: 48.6/54.7 Wh (88.8%)
    power: 14.4 W volts: 15.5 min: 15.4 model: Sunwoda 5B10W51855 type: Li-poly
    serial: <filter> status: discharging cycles: 150
CPU:
  Info: model: 12th Gen Intel Core i5-1235U bits: 64 type: MST AMCP
    arch: Alder Lake level: v3 note: check built: 2021+
    process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 4
    microcode: 0x437
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 10 threads: 12 mt: 2 tpc: 2
    st: 8 smt: enabled cache: L1: 928 KiB desc: d-8x32 KiB, 2x48 KiB; i-2x32
    KiB, 8x64 KiB L2: 6.5 MiB desc: 2x1.2 MiB, 2x2 MiB L3: 12 MiB
    desc: 1x12 MiB
  Speed (MHz): avg: 936 min/max: 400/4400:3300 scaling: driver: intel_pstate
    governor: powersave cores: 1: 936 2: 936 3: 936 4: 936 5: 936 6: 936 7: 936
    8: 936 9: 936 10: 936 11: 936 12: 936 bogomips: 59904
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics] vendor: Lenovo
    driver: i915 v: kernel alternate: xe arch: Xe process: Intel 10nm
    built: 2021-22+ ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4,
    HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:46a8 class-ID: 0300
  Device-2: Syntek Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-4:3 chip-ID: 174f:1812
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: gnome-shell driver: gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0964 built: 2020 res: 1920x1200
    dpi: 171 gamma: 1.2 size: 286x179mm (11.26x7.05") diag: 337mm (13.3")
    ratio: 16:10 modes: 1920x1200
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.1.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Iris Xe Graphics (ADL
    GT2) device-ID: 8086:46a8 memory: 14.96 GiB unified: yes display-ID: :0.0
  API: Vulkan v: 1.4.313 layers: 5 device: 0 type: integrated-gpu name: Intel
    Iris Xe Graphics (ADL GT2) driver: mesa intel v: 25.1.4-arch1.1
    device-ID: 8086:46a8 surfaces: N/A device: 1 type: cpu name: llvmpipe
    (LLVM 20.1.6 256 bits) driver: mesa llvmpipe v: 25.1.4-arch1.1 (LLVM
    20.1.6) device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Lenovo
    driver: sof-audio-pci-intel-tgl alternate: snd_hda_intel, snd_soc_avs,
    snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:51c8 class-ID: 0403
  API: ALSA v: k6.15.3-zen1-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.4.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:51f0 class-ID: 0280
  IF: wlp0s20f3 state: down mac: <filter>
  IF-ID-1: enp0s20f0u1 state: up speed: 425 Mbps duplex: half mac: <filter>
  IF-ID-2: utun420 state: unknown speed: N/A duplex: N/A mac: N/A
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:18 chip-ID: 8087:0033
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 10 state: up address: N/A
Sensors:
  System Temperatures: cpu: N/A mobo: N/A
  Fan Speeds (rpm): cpu: 0
Info:
  Memory: total: 16 GiB note: est. available: 15.32 GiB used: 7.51 GiB (49.0%)
  Processes: 410 Power: uptime: 7h 57m states: freeze,mem,disk
    suspend: s2idle wakeups: 2 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.11 GiB services: gsd-power,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 1380 libs: 410 tools: pamac,paru pm: flatpak
    pkgs: 0 Compilers: gcc: 15.1.1 Shell: garuda-inxi default: fish v: 4.0.2
    running-in: gnome-terminal inxi: 3.3.38
Garuda (2.7.2-1):
  System install date:     2025-06-12
  Last full system update: 2025-06-22
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut

SGS · June 23, 2025, 5:57pm

Please.

Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>) , or put three tildes (~) above and below the text

Pommede1 · June 23, 2025, 6:02pm

hope it’s correct

tbg · June 23, 2025, 8:23pm

My guess would be that is a side effect of recent changes to the linux-firmware package. Search the forum for the most recent posts on that topic. You will likely need to uninstall/reinstall the linux-firmware package, (search recent forum posts).

You could also try rmmodding the btusb Bluetooth driver module if nothing else helps.

Pommede1 · June 24, 2025, 8:37am

no i’ve cachyos on another partition, no update for 2 months, and i’ve got the same problem
can you give me more details about btusb? i quite a beginner
thks !

Pommede1 · June 25, 2025, 4:39pm

i did with the new linux-firmware from today..same result…
what can you propose with btusb or btintel?

tbg · June 26, 2025, 7:29am

See:

To unload the bluetooth driver module is usually pretty straightforward:

sudo modprobe -r btusb

Pommede1 · June 26, 2025, 11:23am

[quote=“Pommede1, post:1, topic:44594”]

0%)
  Processes: 410 Power: uptime: 7h 57m states: freeze,mem,disk
    suspend: s2idle wakeups: 2 hibernate: platform avail: shutdown, reboot

same result
and modprobe -r btusb, i’ve no longer access to bluetooth..it was better before
if i can help i’ve have this

“MESSAGE”: “A security policy denied :1.6 to send method call /midi/profile:org.bluez.GattProfile1.Release to :1.105.”,
“PRIORITY”: “4”,
“_SYSTEMD_UNIT”: “dbus-broker.service”

tbg · June 26, 2025, 12:23pm

I would suggest testing some alternate kernels such as the linux-lts kernel as well as a few others.

Please post:

sudo dmesg | grep Blue
hwinfo --netcard --wlan --bluetooth | grep -Ei "model\:|driver\:|status\:|cmd\:|file\:|detected\:" | grep -v "Config Status"

Pommede1 · June 26, 2025, 5:18pm

yes i was thinking about trying another kernel..

[    5.521377] Bluetooth: Core ver 2.22
[    5.521401] Bluetooth: HCI device and connection manager initialized
[    5.521405] Bluetooth: HCI socket layer initialized
[    5.521407] Bluetooth: L2CAP socket layer initialized
[    5.521410] Bluetooth: SCO socket layer initialized
[    5.586132] Bluetooth: hci0: Device revision is 0
[    5.586135] Bluetooth: hci0: Secure boot is enabled
[    5.586137] Bluetooth: hci0: OTP lock is enabled
[    5.586137] Bluetooth: hci0: API lock is enabled
[    5.586138] Bluetooth: hci0: Debug lock is disabled
[    5.586139] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    5.586140] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[    5.588877] Bluetooth: hci0: DSM reset method type: 0x00
[    5.593775] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[    5.593786] Bluetooth: hci0: Boot Address: 0x100800
[    5.593787] Bluetooth: hci0: Firmware Version: 88-13.25
[    7.062539] Bluetooth: hci0: Waiting for firmware download to complete
[    7.062557] Bluetooth: hci0: Firmware loaded in 1434354 usecs
[    7.062914] Bluetooth: hci0: Waiting for device to boot
[    7.079463] Bluetooth: hci0: Device booted in 16444 usecs
[    7.081937] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc
[    7.084557] Bluetooth: hci0: Applying Intel DDC parameters completed
[    7.088577] Bluetooth: hci0: Firmware timestamp 2025.13 buildtype 1 build 82008
[    7.088593] Bluetooth: hci0: Firmware SHA1: 0x47cf9d0e
[    7.092398] Bluetooth: hci0: Fseq status: Success (0x00)
[    7.092415] Bluetooth: hci0: Fseq executed: 00.00.02.41
[    7.092420] Bluetooth: hci0: Fseq BT Top: 00.00.02.41
[    7.256063] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    7.256066] Bluetooth: BNEP filters: protocol multicast
[    7.256070] Bluetooth: BNEP socket layer initialized
[    7.257158] Bluetooth: MGMT ver 1.23
[    9.095293] Bluetooth: RFCOMM TTY layer initialized
[    9.095303] Bluetooth: RFCOMM socket layer initialized
[    9.095306] Bluetooth: RFCOMM ver 1.11
[ 3260.602265] Bluetooth: hci0: command 0x0c1a tx timeout
[ 3260.602266] Bluetooth: hci0: Opcode 0x0c1a failed: -110
[ 3260.602281] Bluetooth: hci0: Initiating acpi reset method
[ 3260.602283] Bluetooth: hci0: Error when powering off device on rfkill (-110)
[ 3270.778276] Bluetooth: hci0: HCI reset during shutdown failed
[ 3271.130130] Bluetooth: hci0: Device revision is 0
[ 3271.130140] Bluetooth: hci0: Secure boot is enabled
[ 3271.130143] Bluetooth: hci0: OTP lock is enabled
[ 3271.130144] Bluetooth: hci0: API lock is enabled
[ 3271.130146] Bluetooth: hci0: Debug lock is disabled
[ 3271.130148] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 3271.130151] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[ 3271.130275] Bluetooth: hci0: DSM reset method type: 0x00
[ 3271.136411] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[ 3271.136476] Bluetooth: hci0: Boot Address: 0x100800
[ 3271.136478] Bluetooth: hci0: Firmware Version: 88-13.25
[ 3272.833467] Bluetooth: hci0: Waiting for firmware download to complete
[ 3272.834232] Bluetooth: hci0: Firmware loaded in 1658025 usecs
[ 3272.834364] Bluetooth: hci0: Waiting for device to boot
[ 3272.851129] Bluetooth: hci0: Device booted in 16460 usecs
[ 3272.853350] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc
[ 3272.855149] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 3272.858304] Bluetooth: hci0: Firmware timestamp 2025.13 buildtype 1 build 82008
[ 3272.858318] Bluetooth: hci0: Firmware SHA1: 0x47cf9d0e
[ 3272.862448] Bluetooth: hci0: Fseq status: Success (0x00)
[ 3272.862465] Bluetooth: hci0: Fseq executed: 00.00.02.41
[ 3272.862470] Bluetooth: hci0: Fseq BT Top: 00.00.02.41
[ 3272.932834] Bluetooth: MGMT ver 1.23

  Model: "Intel Alder Lake-P PCH CNVi WiFi"
  Driver: "iwlwifi"
  Device File: wlp0s20f3
  Link detected: yes
    Driver Status: iwlwifi is active
    Driver Activation Cmd: "modprobe iwlwifi"
  Model: "Intel AX211 Bluetooth"
  Driver: "btusb"
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"
  Model: "Intel AX211 Bluetooth"
  Driver: "btusb"
    Driver Status: btusb is active
    Driver Activation Cmd: "modprobe btusb"

tbg · June 27, 2025, 12:59am

Your above statement is contradicted by your last wireless status output:

Have you tried toggling Bluetooth off and on via the command line?

Unload the Bluetooth driver module, then reload the Bluetooth driver:

sudo modprobe -r btusb && sudo modprobe btusb

Or, alternately:

Activate, then deactivate the Bluetooth driver module.

sudo modprobe btusb && sudo modprobe -r btusb

From your log output:

If “Secure Boot” is enabled in your bios, it should not be. Be sure Secure Boot" is disabled in your bios.

Pommede1 · June 27, 2025, 9:17am

secure boot is disabled..sure..strange that dmesg says the opposite

and with sudo modprobe -r btusb
i’ve no bluetooth (it’s normal) then i cancel it.
my problem is to stop the bluetooth when i click…and restart if i want to..but it’s not so serious to have it always enable..(better than not functional)

Pommede1 · June 28, 2025, 5:04pm

it was working with the new update but after a second reboot, it doesn’t anymore

tbg · June 29, 2025, 12:53am

This ^^^ is far too vague and lacking in details to be of much use to anybody. Please be more specific and far more detailed with your responses.

Please post:

pacman -Q |grep linux-firmware*
sudo dmesg | grep Blue
lsmod | grep Blue

Pommede1 · June 29, 2025, 9:16am

i don’t what it’s needed to help me

pacman -Q |grep linux-firmware
linux-firmware 20250627-1
linux-firmware-amdgpu 20250627-1
linux-firmware-atheros 20250627-1
linux-firmware-broadcom 20250627-1
linux-firmware-cirrus 20250627-1
linux-firmware-intel 20250627-1
linux-firmware-mediatek 20250627-1
linux-firmware-nvidia 20250627-1
linux-firmware-other 20250627-1
linux-firmware-radeon 20250627-1
linux-firmware-realtek 20250627-1
linux-firmware-whence 20250627-1

sudo dmesg | grep Blue
[    4.735998] Bluetooth: Core ver 2.22
[    4.736031] Bluetooth: HCI device and connection manager initialized
[    4.736036] Bluetooth: HCI socket layer initialized
[    4.736038] Bluetooth: L2CAP socket layer initialized
[    4.736042] Bluetooth: SCO socket layer initialized
[    4.841635] Bluetooth: hci0: Device revision is 0
[    4.841639] Bluetooth: hci0: Secure boot is enabled
[    4.841640] Bluetooth: hci0: OTP lock is enabled
[    4.841640] Bluetooth: hci0: API lock is enabled
[    4.841641] Bluetooth: hci0: Debug lock is disabled
[    4.841642] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    4.841645] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[    4.843290] Bluetooth: hci0: DSM reset method type: 0x00
[    4.848103] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[    4.848114] Bluetooth: hci0: Boot Address: 0x100800
[    4.848115] Bluetooth: hci0: Firmware Version: 88-13.25
[    4.893939] Bluetooth: hci0: Failed to send firmware data (-19)
[    4.893947] Bluetooth: hci0: sending frame failed (-19)
[    4.893953] Bluetooth: hci0: FW download error recovery failed (-19)
[    4.893971] Bluetooth: hci0: sending frame failed (-19)
[    4.893975] Bluetooth: hci0: Failed to read MSFT supported features (-19)
[    5.504697] Bluetooth: hci0: Device revision is 0
[    5.504701] Bluetooth: hci0: Secure boot is enabled
[    5.504702] Bluetooth: hci0: OTP lock is enabled
[    5.504703] Bluetooth: hci0: API lock is enabled
[    5.504704] Bluetooth: hci0: Debug lock is disabled
[    5.504705] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    5.504706] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[    5.505641] Bluetooth: hci0: DSM reset method type: 0x00
[    5.507818] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[    5.507834] Bluetooth: hci0: Boot Address: 0x100800
[    5.507835] Bluetooth: hci0: Firmware Version: 88-13.25
[    6.433910] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.433913] Bluetooth: BNEP filters: protocol multicast
[    6.433917] Bluetooth: BNEP socket layer initialized
[    6.984745] Bluetooth: hci0: Waiting for firmware download to complete
[    6.985636] Bluetooth: hci0: Firmware loaded in 1443178 usecs
[    6.985685] Bluetooth: hci0: Waiting for device to boot
[    7.001599] Bluetooth: hci0: Device booted in 15573 usecs
[    7.003763] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc
[    7.005635] Bluetooth: hci0: Applying Intel DDC parameters completed
[    7.008708] Bluetooth: hci0: Firmware timestamp 2025.13 buildtype 1 build 82008
[    7.008712] Bluetooth: hci0: Firmware SHA1: 0x47cf9d0e
[    7.012650] Bluetooth: hci0: Fseq status: Success (0x00)
[    7.012652] Bluetooth: hci0: Fseq executed: 00.00.02.41
[    7.012654] Bluetooth: hci0: Fseq BT Top: 00.00.02.41
[    7.081756] Bluetooth: MGMT ver 1.23
[    8.319502] Bluetooth: RFCOMM TTY layer initialized
[    8.319515] Bluetooth: RFCOMM socket layer initialized
[    8.319520] Bluetooth: RFCOMM ver 1.11
[ 4211.505576] Bluetooth: hci0: Opcode 0x0c1a failed: -110
[ 4211.505595] Bluetooth: hci0: Error when powering off device on rfkill (-110)
[ 4211.505593] Bluetooth: hci0: command 0x0c1a tx timeout
[ 4211.505633] Bluetooth: hci0: Initiating acpi reset method
[ 4211.505658] Bluetooth: hci0: HCI reset during shutdown failed
[ 4212.207720] Bluetooth: hci0: Device revision is 0
[ 4212.207727] Bluetooth: hci0: Secure boot is enabled
[ 4212.207729] Bluetooth: hci0: OTP lock is enabled
[ 4212.207731] Bluetooth: hci0: API lock is enabled
[ 4212.207732] Bluetooth: hci0: Debug lock is disabled
[ 4212.207733] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 4212.207736] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[ 4212.207839] Bluetooth: hci0: DSM reset method type: 0x00
[ 4212.211882] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[ 4212.211896] Bluetooth: hci0: Boot Address: 0x100800
[ 4212.211898] Bluetooth: hci0: Firmware Version: 88-13.25
[ 4213.802155] Bluetooth: hci0: Waiting for firmware download to complete
[ 4213.802847] Bluetooth: hci0: Firmware loaded in 1553685 usecs
[ 4213.803058] Bluetooth: hci0: Waiting for device to boot
[ 4213.819734] Bluetooth: hci0: Device booted in 16402 usecs
[ 4213.821861] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc
[ 4213.823732] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 4213.826727] Bluetooth: hci0: Firmware timestamp 2025.13 buildtype 1 build 82008
[ 4213.826733] Bluetooth: hci0: Firmware SHA1: 0x47cf9d0e
[ 4213.830700] Bluetooth: hci0: Fseq status: Success (0x00)
[ 4213.830704] Bluetooth: hci0: Fseq executed: 00.00.02.41
[ 4213.830706] Bluetooth: hci0: Fseq BT Top: 00.00.02.41
[ 4213.900221] Bluetooth: MGMT ver 1.23

lsmod | grep blue
bluetooth            1155072  34 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
rfkill                 45056  8 iwlmvm,bluetooth,thinkpad_acpi,cfg80211

Duke187 · June 29, 2025, 6:15pm

hi,

Do you run the System with Dual-Boot with windows? Because your inxi looks like you deleted stuff out of it like SSDs/Nvmes and the last dualboot with windows ???

My output shows this:

System install date:     2025-05-30
Last full system update: 2025-06-29
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

To avoid that windows is hijacking your Hardware disable fastboot on windows. I have to press SHIFT Button then Shutdown to get my BT working on Garuda. If not im not able to activate it even my WIFI same issue too. What is this command tell you rfkill list Hard blocked?

gampel · June 29, 2025, 6:57pm

pls post your current garuda-inxi

Pommede1 · June 30, 2025, 6:54am

yes i’ve got a dual boot with windows 11

rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

gampel · June 30, 2025, 7:45am

To be on the safe side…

pls deactivate fastboot inside M$
bios: fast + secure boot off
never a warm boot from M$ to linux (reverse yes)

Pommede1 · June 30, 2025, 10:36am

what is fastboot inside windows? i know fastboot from adb..
like i said, secure boot is off..fastboot off too; only dmesg says on?

i don’t understand well this phrase, i use grub at start..

but i’ve got exactly the same config in my thinkpad L14 and no problems…and the problem was before installing windows on a partition.