Wifi disconnects when lid closes

Hello,
Everytime I close the lid on my laptop the wifi disconnects and upon opening it stays like that.
I have to right click on network manager on the taskbar and check “Enable wifi”.
I have red other post on the forum and searched online.
Changed settings in Power Manager on Laptop lid to do nothing or switch off display it still happens.
Changed the file logind.conf and the Upower and nothing.

I’m dual booting this laptop with MX Linux XFCE and this situation doesn’t happen.
Any clues on how to fix this?

[jesuslinux@A4910MJ ~]$ inxi -Fxza
System:
  Kernel: 6.12.63-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64 root=/dev/sda4
  Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.51 wm: xfwm4 v: 4.20.0
    with: xfce4-panel tools: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: HP product: HP Pavilion Notebook v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 81FB v: 80.21 serial: <superuser required>
    part-nu: X0K19EA#AB9 uuid: <superuser required> Firmware: UEFI
    vendor: American Megatrends v: F.32 date: 04/26/2019
Battery:
  ID-1: BAT0 charge: 26.4 Wh (100%) condition: 26.4/26.4 Wh (100%) volts: 8.37
    min: 7.7 model: Hewlett-Packard Primary type: Li-ion serial: N/A charging:
    status: full cycles: 237
CPU:
  Info: model: AMD A9-9410 RADEON R5 5 COMPUTE CORES 2C+3G bits: 64 type: MCP
    arch: Excavator level: v3 note: check built: 2015 process: GF 28nm
    family: 0x15 (21) model-id: 0x70 (112) stepping: 0 microcode: 0x6006705
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 2 smt: <unsupported> cache:
    L1: 192 KiB desc: d-2x32 KiB; i-2x64 KiB L2: 2 MiB desc: 2x1024 KiB
  Speed (MHz): avg: 1397 min/max: 1400/2900 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 1397 2: 1397
    bogomips: 11582
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  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: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT disabled
  Type: spec_rstack_overflow 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: Retpolines; IBPB: conditional; STIBP:
    disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape status: Not affected
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Stoney [Radeon R2/R3/R4/R5
    Graphics] vendor: Hewlett-Packard driver: amdgpu v: kernel arch: GCN-3
    code: Volcanic Islands process: TSMC 28nm built: 2014-19 ports:
    active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:98e4
    class-ID: 0300
  Device-2: Sunplus Innovation HP Wide Vision HD driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-1.3:4
    chip-ID: 1bcf:2c87 class-ID: 0e02
  Display: x11 server: X.org v: 1.21.1.21 compositor: xfwm4 v: 4.20.0
    driver: X: loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-size: <missing: xdpyinfo>
  Monitor-1: eDP-1 mapped: eDP model: ChiMei InnoLux 0x15c6 built: 2013 res:
    mode: 1366x768 hz: 60 scale: 100% (1) dpi: 101 gamma: 1.2
    size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes:
    max: 1366x768 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.5 vendor: amd mesa v: 25.3.2-arch1.1 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon R5 Graphics (radeonsi stoney ACO
    DRM 3.61 6.12.63-1-MANJARO) device-ID: 1002:98e4 memory: 500 MiB
    unified: no
  Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings
    x11: xprop,xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Stoney HDMI/DP Audio
    vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:01.1
    chip-ID: 1002:15b3 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Family 15h Audio
    vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:09.2
    chip-ID: 1022:157a class-ID: 0403
  API: ALSA v: k6.12.63-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000
    bus-ID: 02:00.0 chip-ID: 10ec:8136 class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Realtek RTL8723BE PCIe Wireless Network Adapter
    vendor: Hewlett-Packard driver: rtl8723be v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:b723
    class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 2.1
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-1.4:5 chip-ID: 0bda:b008
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 238.47 GiB used: 46.58 GiB (19.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SKC600256G
    size: 238.47 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 0107 scheme: GPT
Partition:
  ID-1: / raw-size: 40 GiB size: 39.08 GiB (97.69%) used: 17.87 GiB (45.7%)
    fs: ext4 dev: /dev/sda4 maj-min: 8:4
  ID-2: /home raw-size: 74.95 GiB size: 73.22 GiB (97.69%)
    used: 5.66 GiB (7.7%) fs: ext4 dev: /dev/sda5 maj-min: 8:5
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda6 maj-min: 8:6
Sensors:
  System Temperatures: cpu: 67.5 C mobo: N/A gpu: amdgpu temp: 67.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB note: est. available: 7.21 GiB used: 2.41 GiB (33.4%)
  Processes: 262 Power: uptime: 35m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 2.87 GiB services: upowerd,xfce4-power-manager
    Init: systemd v: 258 default: graphical tool: systemctl
  Packages: 1246 pm: dpkg pkgs: 0 pm: pacman pkgs: 1232 libs: 363
    tools: pamac,yay pm: flatpak pkgs: 14 Compilers: gcc: 15.2.1 Shell: Bash
    v: 5.3.9 running-in: xfce4-terminal inxi: 3.3.40

I don’t know the answer, so I did a search with keywords linux disable power save for Realtek RTL8723BE

This led me to a section on the Arch Wiki on USB autosuspend which suggests udev rules to control which devices should be included/excluded from autosuspend.

I recall Ubuntu has some extensive udev rules applied, to adjust the default, sometimes undesired, behavior of various devices, so I am thinking that MX Linux (IIRC being based on Ubuntu) has inherited those rules, but that is a guess.

You could look into their rules - compare with Manjaro - and apply the relevant rule(s).

I faced the same situation as you, albeit on a different model but still the same brand HP laptop that is a convertible. I can help you with rectifying this annoying behavior if you send me the following:

$ cat /sys/class/dmi/id/modalias
$ sudo pacman -S evtest
$ sudo evtest                  # select device event of `AT Translated Set 2 keyboard`

Then close and open the lid so that it does a random airplane mode activation. Press Ctrl+C to end the execution then copy the output of the last command here.

1 Like

Do you think I can copy the etc/udev rules form MX to Manjaro with no issues?

Both are XFCE and systemd.

MX is based on Debian.

In theory that should be possible. But you know what they say… :backhand_index_pointing_down:

“In theory, theory and practice are the same thing. In practice, they are not.”

:stuck_out_tongue:

1 Like
[jesuslinux@A4910MJ ~]$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	Power Button
/dev/input/event1:	Lid Switch
/dev/input/event10:	HP WMI hotkeys
/dev/input/event11:	SynPS/2 Synaptics TouchPad
/dev/input/event12:	HDA ATI HDMI HDMI/DP,pcm=3
/dev/input/event13:	HD-Audio Generic Mic
/dev/input/event14:	HD-Audio Generic Headphone
/dev/input/event2:	Power Button
/dev/input/event3:	Video Bus
/dev/input/event4:	AT Translated Set 2 keyboard
/dev/input/event5:	MOSART Semi. 2.4G Wireless Mouse
/dev/input/event6:	MOSART Semi. 2.4G Wireless Mouse
/dev/input/event7:	Wireless hotkeys
/dev/input/event8:	ST LIS3LV02DL Accelerometer
/dev/input/event9:	PC Speaker
Select the device event number [0-14]: ^C                          
[jesuslinux@A4910MJ ~]$ 

[jesuslinux@A4910MJ ~]$ cat /sys/class/dmi/id/modalias
dmi:bvnAmericanMegatrendsInc.:bvrF.32:bd04/26/2019:br15.32:efr80.21:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn81FB:rvr80.21:cvnHP:ct10:cvrChassisVersion:skuX0K19EA#AB9:


Now run it as sudo evtest /dev/input/event4. Don’t forget to include the output of cat /sys/class/dmi/id/modalias.

1 Like
[jesuslinux@A4910MJ ~]$ sudo evtest /dev/input/event4
Input driver version is 1.0.1
Input device ID: bus 0x11 vendor 0x1 product 0x1 version 0xab83
Input device name: "AT Translated Set 2 keyboard"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 1 (KEY_ESC)
    Event code 2 (KEY_1)
    Event code 3 (KEY_2)
    Event code 4 (KEY_3)
    Event code 5 (KEY_4)
    Event code 6 (KEY_5)
    Event code 7 (KEY_6)
    Event code 8 (KEY_7)
    Event code 9 (KEY_8)
    Event code 10 (KEY_9)
    Event code 11 (KEY_0)
    Event code 12 (KEY_MINUS)
    Event code 13 (KEY_EQUAL)
    Event code 14 (KEY_BACKSPACE)
    Event code 15 (KEY_TAB)
    Event code 16 (KEY_Q)
    Event code 17 (KEY_W)
    Event code 18 (KEY_E)
    Event code 19 (KEY_R)
    Event code 20 (KEY_T)
    Event code 21 (KEY_Y)
    Event code 22 (KEY_U)
    Event code 23 (KEY_I)
    Event code 24 (KEY_O)
    Event code 25 (KEY_P)
    Event code 26 (KEY_LEFTBRACE)
    Event code 27 (KEY_RIGHTBRACE)
    Event code 28 (KEY_ENTER)
    Event code 29 (KEY_LEFTCTRL)
    Event code 30 (KEY_A)
    Event code 31 (KEY_S)
    Event code 32 (KEY_D)
    Event code 33 (KEY_F)
    Event code 34 (KEY_G)
    Event code 35 (KEY_H)
    Event code 36 (KEY_J)
    Event code 37 (KEY_K)
    Event code 38 (KEY_L)
    Event code 39 (KEY_SEMICOLON)
    Event code 40 (KEY_APOSTROPHE)
    Event code 41 (KEY_GRAVE)
    Event code 42 (KEY_LEFTSHIFT)
    Event code 43 (KEY_BACKSLASH)
    Event code 44 (KEY_Z)
    Event code 45 (KEY_X)
    Event code 46 (KEY_C)
    Event code 47 (KEY_V)
    Event code 48 (KEY_B)
    Event code 49 (KEY_N)
    Event code 50 (KEY_M)
    Event code 51 (KEY_COMMA)
    Event code 52 (KEY_DOT)
    Event code 53 (KEY_SLASH)
    Event code 54 (KEY_RIGHTSHIFT)
    Event code 55 (KEY_KPASTERISK)
    Event code 56 (KEY_LEFTALT)
    Event code 57 (KEY_SPACE)
    Event code 58 (KEY_CAPSLOCK)
    Event code 59 (KEY_F1)
    Event code 60 (KEY_F2)
    Event code 61 (KEY_F3)
    Event code 62 (KEY_F4)
    Event code 63 (KEY_F5)
    Event code 64 (KEY_F6)
    Event code 65 (KEY_F7)
    Event code 66 (KEY_F8)
    Event code 67 (KEY_F9)
    Event code 68 (KEY_F10)
    Event code 69 (KEY_NUMLOCK)
    Event code 70 (KEY_SCROLLLOCK)
    Event code 71 (KEY_KP7)
    Event code 72 (KEY_KP8)
    Event code 73 (KEY_KP9)
    Event code 74 (KEY_KPMINUS)
    Event code 75 (KEY_KP4)
    Event code 76 (KEY_KP5)
    Event code 77 (KEY_KP6)
    Event code 78 (KEY_KPPLUS)
    Event code 79 (KEY_KP1)
    Event code 80 (KEY_KP2)
    Event code 81 (KEY_KP3)
    Event code 82 (KEY_KP0)
    Event code 83 (KEY_KPDOT)
    Event code 85 (KEY_ZENKAKUHANKAKU)
    Event code 86 (KEY_102ND)
    Event code 87 (KEY_F11)
    Event code 88 (KEY_F12)
    Event code 89 (KEY_RO)
    Event code 90 (KEY_KATAKANA)
    Event code 91 (KEY_HIRAGANA)
    Event code 92 (KEY_HENKAN)
    Event code 93 (KEY_KATAKANAHIRAGANA)
    Event code 94 (KEY_MUHENKAN)
    Event code 95 (KEY_KPJPCOMMA)
    Event code 96 (KEY_KPENTER)
    Event code 97 (KEY_RIGHTCTRL)
    Event code 98 (KEY_KPSLASH)
    Event code 99 (KEY_SYSRQ)
    Event code 100 (KEY_RIGHTALT)
    Event code 102 (KEY_HOME)
    Event code 103 (KEY_UP)
    Event code 104 (KEY_PAGEUP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 107 (KEY_END)
    Event code 108 (KEY_DOWN)
    Event code 109 (KEY_PAGEDOWN)
    Event code 110 (KEY_INSERT)
    Event code 111 (KEY_DELETE)
    Event code 112 (KEY_MACRO)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 117 (KEY_KPEQUAL)
    Event code 118 (KEY_KPPLUSMINUS)
    Event code 119 (KEY_PAUSE)
    Event code 121 (KEY_KPCOMMA)
    Event code 122 (KEY_HANGUEL)
    Event code 123 (KEY_HANJA)
    Event code 124 (KEY_YEN)
    Event code 125 (KEY_LEFTMETA)
    Event code 126 (KEY_RIGHTMETA)
    Event code 127 (KEY_COMPOSE)
    Event code 128 (KEY_STOP)
    Event code 138 (KEY_HELP)
    Event code 140 (KEY_CALC)
    Event code 142 (KEY_SLEEP)
    Event code 143 (KEY_WAKEUP)
    Event code 152 (KEY_SCREENLOCK)
    Event code 155 (KEY_MAIL)
    Event code 156 (KEY_BOOKMARKS)
    Event code 157 (KEY_COMPUTER)
    Event code 158 (KEY_BACK)
    Event code 159 (KEY_FORWARD)
    Event code 163 (KEY_NEXTSONG)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 165 (KEY_PREVIOUSSONG)
    Event code 166 (KEY_STOPCD)
    Event code 172 (KEY_HOMEPAGE)
    Event code 173 (KEY_REFRESH)
    Event code 183 (KEY_F13)
    Event code 184 (KEY_F14)
    Event code 185 (KEY_F15)
    Event code 193 (KEY_F23)
    Event code 210 (KEY_PRINT)
    Event code 212 (KEY_CAMERA)
    Event code 217 (KEY_SEARCH)
    Event code 224 (KEY_BRIGHTNESSDOWN)
    Event code 225 (KEY_BRIGHTNESSUP)
    Event code 226 (KEY_MEDIA)
    Event code 227 (KEY_SWITCHVIDEOMODE)
    Event code 236 (KEY_BATTERY)
    Event code 238 (KEY_WLAN)
    Event code 244 (KEY_BRIGHTNESS_ZERO)
    Event code 389 (KEY_DVD)
    Event code 446 (KEY_HANGUP_PHONE)
    Event code 465 (KEY_FN_ESC)
    Event code 531 (KEY_TOUCHPAD_ON)
    Event code 532 (KEY_TOUCHPAD_OFF)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
  Event type 17 (EV_LED)
    Event code 0 (LED_NUML) state 0
    Event code 1 (LED_CAPSL) state 0
    Event code 2 (LED_SCROLLL) state 0
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    250
    Repeat code 1 (REP_PERIOD)
      Value     33
Properties:
Testing ... (interrupt to exit)
Event: time 1767741590.695444, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9c
Event: time 1767741590.695444, type 1 (EV_KEY), code 96 (KEY_KPENTER), value 0
Event: time 1767741590.695444, -------------- SYN_REPORT ------------
Event: time 1767741594.730624, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8
Event: time 1767741594.730624, type 1 (EV_KEY), code 532 (KEY_TOUCHPAD_OFF), value 1
Event: time 1767741594.730624, -------------- SYN_REPORT ------------
Event: time 1767741594.730651, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8
Event: time 1767741594.730651, type 1 (EV_KEY), code 532 (KEY_TOUCHPAD_OFF), value 0
Event: time 1767741594.730651, -------------- SYN_REPORT ------------
Event: time 1767741594.990168, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8
Event: time 1767741594.990168, type 1 (EV_KEY), code 532 (KEY_TOUCHPAD_OFF), value 1
Event: time 1767741594.990168, -------------- SYN_REPORT ------------
Event: time 1767741594.990196, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8
Event: time 1767741594.990196, type 1 (EV_KEY), code 532 (KEY_TOUCHPAD_OFF), value 0
Event: time 1767741594.990196, -------------- SYN_REPORT ------------
Event: time 1767741604.588473, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7
Event: time 1767741604.588473, type 1 (EV_KEY), code 238 (KEY_WLAN), value 1
Event: time 1767741604.588473, -------------- SYN_REPORT ------------
Event: time 1767741604.628929, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7
Event: time 1767741604.628929, type 1 (EV_KEY), code 238 (KEY_WLAN), value 0
Event: time 1767741604.628929, -------------- SYN_REPORT ------------
Event: time 1767741608.785294, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d
Event: time 1767741608.785294, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1
Event: time 1767741608.785294, -------------- SYN_REPORT ------------
Event: time 1767741608.942864, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2e
Event: time 1767741608.942864, type 1 (EV_KEY), code 46 (KEY_C), value 1
Event: time 1767741608.942864, -------------- SYN_REPORT ------------
^C
[jesuslinux@A4910MJ ~]$ 

Great! Now run the following:

$ echo -e 'evdev:atkbd:dmi:bvn*:bvr*:bd*:br*:efr*:svnHP:pnHPPavilionNotebook:*\n KEYBOARD_KEY_d7=unknown\n' | sudo tee /etc/udev/hwdb.d/61-keyboard-local.hwdb
$ sudo systemd-hwdb update
$ sudo udevadm trigger /dev/input/event4

Let me know how it goes.

2 Likes

etc/dev/rules.d folder in manjaro is empty.

In Mx Linux the same folder has:

Why a screenshot when you can do the same with ls and get an output that can be indexed, searched and copy/pasted?

Anyway, they are all plain text files, so inspect them, and then you can try copying them over and see what it does.

2 Likes

Your instructions solved this annoyance!
Already tested it after reboot and everyhing!
Genius!

Thank you very much Sir

1 Like

Great solution @braveheartleo, coiuld you please provide the technical background and some explanation why it happens and why the solution can fix it.

I know the issue is solved - just om input on how to find a rule in MXLinux or Ubuntu or whatever, matching a device from your system.

Udev rules are for controlling and manipulating any device.

I don’t know if it would useful to copy all rules, I would search the ruleset that affect my device.

Taking info from your inxi we have chip-ID 10ec:b723 which splits into idVendor and idProduct.

We then apply a search in the udev rules

grep -rl -e 'ATTR{idVendor}=="10ec"' -e 'ATTR{idProduct}=="b723"' /etc/udev/rules.d

Or in the system folder

grep -rl -e 'ATTR{idVendor}=="10ec", ATTR{idProduct}=="b723"' /usr/lib/udev/rules.d
2 Likes

You’re welcome. :smiley:

Technical background regarding the solution is provided in this file systemd/hwdb.d/60-keyboard.hwdb at main · systemd/systemd · GitHub

From there you can see several HP laptop models defined, preventing the ‘random activation of airplane mode’ coming from the lid keys, particularly the KEY_WLAN. The list is not exhaustive, so one has to come up with the right entry for a model that is not covered in the file.

3 Likes

The thing is that on MXLinux XFCE on the same machine this issue does not happen…

DIfferent downstreams, different implementations. Either Debian, antiX, or MX Linux itself may have done some additional quality of life changes that improve on issues such as this. Where that change may be one will have to take a closer look.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.