Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #266390 > unrolled thread

rfkill list wlan, Hard blocked: yes

Started byGeert Stappers <stappers@stappers.nl>
First post2024-01-21 19:00 +0100
Last post2024-01-22 06:20 +0100
Articles 11 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  rfkill list wlan, Hard blocked: yes Geert Stappers <stappers@stappers.nl> - 2024-01-21 19:00 +0100
    Re: rfkill list wlan, Hard blocked: yes Marco Moock <mm@dorfdsl.de> - 2024-01-21 19:50 +0100
    Re: rfkill list wlan, Hard blocked: yes David Wright <deblis@lionunicorn.co.uk> - 2024-01-21 20:00 +0100
      Re: rfkill list wlan, Hard blocked: yes Geert Stappers <stappers@stappers.nl> - 2024-01-21 22:00 +0100
        Re: rfkill list wlan, Hard blocked: yes David Wright <deblis@lionunicorn.co.uk> - 2024-01-21 23:10 +0100
        Re: rfkill list wlan, Hard blocked: yes David Wright <deblis@lionunicorn.co.uk> - 2024-01-23 18:20 +0100
      ThinkPad Extra Buttons as  /devices/platform/thinkpad_acpi/input/input16 Geert Stappers <stappers@stappers.nl> - 2024-01-21 22:50 +0100
        Re: ThinkPad Extra Buttons as  /devices/platform/thinkpad_acpi/input/input16 David Wright <deblis@lionunicorn.co.uk> - 2024-01-21 23:40 +0100
          Re: ThinkPad Extra Buttons as  /devices/platform/thinkpad_acpi/input/input16 Geert Stappers <stappers@stappers.nl> - 2024-01-22 07:50 +0100
            Re: ThinkPad Extra Buttons as  /devices/platform/thinkpad_acpi/input/input16 David Wright <deblis@lionunicorn.co.uk> - 2024-01-23 05:10 +0100
        Re: ThinkPad Extra Buttons as  /devices/platform/thinkpad_acpi/input/input16 Charles Curley <charlescurley@charlescurley.com> - 2024-01-22 06:20 +0100

#266390 — rfkill list wlan, Hard blocked: yes

FromGeert Stappers <stappers@stappers.nl>
Date2024-01-21 19:00 +0100
Subjectrfkill list wlan, Hard blocked: yes
Message-ID<HYKgW-4CHZ-5@gated-at.bofh.it>
In-Reply-To: <Za1J1D39OA7362Ce@axis.corp>
Subject: Re: ip link   versus   nmcli device,   WIFI   firmware related


On Sun, Jan 21, 2024 at 10:44:04AM -0600, David Wright wrote:
> On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> ( https://lists.debian.org/debian-user/2024/01/msg01038.html )
> > [    7.854942] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
> > [    7.860452] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
> > [    8.356275] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
> 
> Run rfkill and, if it's blocked, unblock it.

Installed package `rfkill`  (it wasn't installed before)
and tried it.

It does report "hard blocked", but rfkill can't change it.


root@nero:~# rfkill
ID TYPE      DEVICE                   SOFT    HARD
 0 bluetooth tpacpi_bluetooth_sw   blocked blocked
 1 wwan      tpacpi_wwan_sw      unblocked blocked
 2 wlan      phy0                unblocked blocked
root@nero:~# nmcli radio
WIFI-HW  WIFI      WWAN-HW  WWAN     
enabled  disabled  enabled  disabled 
root@nero:~# rfkill list wlan
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes
root@nero:~# rfkill unblock wlan
root@nero:~# rfkill list wlan
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes
root@nero:~# rfkill unblock all
root@nero:~# rfkill list wlan
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes
root@nero:~# nmcli radio
WIFI-HW  WIFI      WWAN-HW  WWAN     
enabled  disabled  enabled  disabled 
root@nero:~#


I always tried a "function key" on the keyboard of the laptop,
also without the desired effect.

So now in doubt how to proceed.




 
> Cheers,
> David.


Groeten
Geert Stappers
-- 
Silence is hard to parse

[toc] | [next] | [standalone]

#266403

FromMarco Moock <mm@dorfdsl.de>
Date2024-01-21 19:50 +0100
Message-ID<HYL3j-4Dd9-1@gated-at.bofh.it>
In reply to#266390
Am 21.01.2024 um 18:58:43 Uhr schrieb Geert Stappers:

> It does report "hard blocked", but rfkill can't change it.

Look for a hardware switch or a keystroke (mostly combined with FN) to
enable it.

[toc] | [prev] | [next] | [standalone]

#266407

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2024-01-21 20:00 +0100
Message-ID<HYLcZ-4DgC-7@gated-at.bofh.it>
In reply to#266390
On Sun 21 Jan 2024 at 18:58:43 (+0100), Geert Stappers wrote:
> On Sun, Jan 21, 2024 at 10:44:04AM -0600, David Wright wrote:
> > On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> > ( https://lists.debian.org/debian-user/2024/01/msg01038.html )
> > > [    7.854942] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
> > > [    7.860452] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
> > > [    8.356275] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
> > 
> > Run rfkill and, if it's blocked, unblock it.
> 
> Installed package `rfkill`  (it wasn't installed before)
> and tried it.
> 
> It does report "hard blocked", but rfkill can't change it.
> 
> I always tried a "function key" on the keyboard of the laptop,
> also without the desired effect.

Has that worked in the past … on previous Debians … on
the originally installed OS?

Do you see any reaction in the logs (daemon.log and syslog)
when you press that function key? Does xev show a XF86WLAN
keysym occurring (or anything)?

Presumably as there's a function key, there's no button
on the laptop, as commonly found on ones old enough.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#266424

FromGeert Stappers <stappers@stappers.nl>
Date2024-01-21 22:00 +0100
Message-ID<HYN57-4Epp-5@gated-at.bofh.it>
In reply to#266407
On Sun, Jan 21, 2024 at 12:59:01PM -0600, David Wright wrote:
> On Sun 21 Jan 2024 at 18:58:43 (+0100), Geert Stappers wrote:
> > On Sun, Jan 21, 2024 at 10:44:04AM -0600, David Wright wrote:
> > > On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> > > ( https://lists.debian.org/debian-user/2024/01/msg01038.html )
> > > > [    7.854942] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
> > > > [    7.860452] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
> > > > [    8.356275] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
> > > 
> > > Run rfkill and, if it's blocked, unblock it.
> > 
> > Installed package `rfkill`  (it wasn't installed before)
> > and tried it.
> > 
> > It does report "hard blocked", but rfkill can't change it.
> > 
> > I always tried a "function key" on the keyboard of the laptop,
> > also without the desired effect.
> 
> Has that worked in the past … on previous Debians … on
> the originally installed OS?

I think it has.  Years ago.

In recent years only the ethernet interface has been used.

 
> Do you see any reaction in the logs (daemon.log and syslog)
> when you press that function key? Does xev show a XF86WLAN
> keysym occurring (or anything)?

The laptop doesn't run  X any more. Tried `xev` anyway:

| # xev
| xev:  unable to open display ''
| #

With `dmesg -w` was neither the function key press seen.

 
> Presumably as there's a function key, there's no button
> on the laptop, as commonly found on ones old enough.

Indeed, no dedicated "airplane switch" present.


Tried with parameter for the rfkill kernel module.
Either I did that wrong or it had not the desired effect.


Further suggestions appriciated.


What follows is the parameter attempt.


root@nero:~# modinfo -p rfkill
master_switch_mode:SW_RFKILL_ALL ON should: 0=do nothing (only unlock); 1=restore; 2=unblock all (uint)
default_state:Default initial state for all radio types, 0 = radio off (uint)
root@nero:~# echo 'rfkill master_switch_mode=2' > /etc/modules-load.d/rfkil_unblock.conf
root@nero:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.10.0-27-amd64
root@nero:~# dmesg | grep -e rfkill -e iwlwifi
[    8.002917] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked
[    8.019804] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is blocked
[    8.685725] iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[    8.768395] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-1000-5.ucode
[    8.768624] iwlwifi 0000:02:00.0: loaded firmware version 39.31.5.1 build 35138 1000-5.ucode op_mode iwldvm
[    8.768677] iwlwifi 0000:02:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    9.074938] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
[    9.074943] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[    9.074946] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[    9.074950] iwlwifi 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C
[    9.088734] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
[    9.088763] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
[    9.194253] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
root@nero:~# reboot
Connection to nero closed by remote host.
Connection to nero closed.
stappers@paddy:~
$ bong
E: Missing hostname
I: This programm reduces output of 
I: Like  is a hostname as parameter required
stappers@paddy:~
$ bong nero
         ------------
21:24:18 just_started 0:00:00
PING nero.gpm.stappers.nl (172.24.0.54) 56(84) bytes of data.
21:24:19 still_up 0:00:01
21:26:09 up_again 0:01:50
stappers@paddy:~
$ ssh nero
Linux nero 5.10.0-27-amd64 #1 SMP Debian 5.10.205-2 (2023-12-31) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Jan 21 20:25:08 2024 from 172.24.0.36
stappers@nero:~$ sudo su -
root@nero:~# dmesg | grep -e rfkill -e iwlwifi
[    7.952756] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked
[    7.976749] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is blocked
[    8.397512] iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[    8.405654] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-1000-5.ucode
[    8.405864] iwlwifi 0000:02:00.0: loaded firmware version 39.31.5.1 build 35138 1000-5.ucode op_mode iwldvm
[    8.405909] iwlwifi 0000:02:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    8.658837] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
[    8.658843] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[    8.658846] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[    8.658850] iwlwifi 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C
[    8.676689] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
[    8.702522] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
[    8.778160] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
root@nero:~# cat /etc/modules-load.d/rfkil_unblock.conf 
rfkill master_switch_mode=2
root@nero:~# 



 
> Cheers,
> David.
 

Groeten
Geert Stappers
-- 
Silence is hard to parse

[toc] | [prev] | [next] | [standalone]

#266430

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2024-01-21 23:10 +0100
Message-ID<HYOaR-4Fh0-5@gated-at.bofh.it>
In reply to#266424
On Sun 21 Jan 2024 at 21:57:20 (+0100), Geert Stappers wrote:
> On Sun, Jan 21, 2024 at 12:59:01PM -0600, David Wright wrote:
> > On Sun 21 Jan 2024 at 18:58:43 (+0100), Geert Stappers wrote:
> > > On Sun, Jan 21, 2024 at 10:44:04AM -0600, David Wright wrote:
> > > > On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> > > > ( https://lists.debian.org/debian-user/2024/01/msg01038.html )
> > > > > [    7.854942] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
> > > > > [    7.860452] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
> > > > > [    8.356275] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
> > > > 
> > > > Run rfkill and, if it's blocked, unblock it.
> > > 
> > > Installed package `rfkill`  (it wasn't installed before)
> > > and tried it.
> > > 
> > > It does report "hard blocked", but rfkill can't change it.
> > > 
> > > I always tried a "function key" on the keyboard of the laptop,
> > > also without the desired effect.
> > 
> > Has that worked in the past … on previous Debians … on
> > the originally installed OS?
> 
> I think it has.  Years ago.
> 
> In recent years only the ethernet interface has been used.

Just checking, as some laptops are supplied without a wifi option.

You could try checking the BIOS—my Lenovo has an ?InsydeH2O BIOS
with a section:

Wireless                                Enabled
Bluetooth                               Enabled
Power Beep                              Disabled
Intel Virtual Technology                Disabled
BIOS Back Flash                         Disabled
HotKey Mode                             Enabled → Disabled
Always On USB                           Disabled
AOAC Configuration                      Enabled
Deep S3 Function                        Disabled

You could install the regulatory database if it's not there
(wireless-regdb). However, I think normal behaviour is to
allow wifi to run at the lowest legal power when the
regulatory domain is not known.

After that, I'm getting out of my depth:

> [    8.002917] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked
> [    8.019804] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is blocked
> [    8.685725] iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control

Possibilities here are suggested by:

https://www.reddit.com/r/debian/comments/8c6ytj/active_state_power_management_aspm/

https://www.reddit.com/r/debian/comments/y4ahsh/solution_cant_disable_aspm_os_doesnt_have_aspm/

and:

https://www.kernel.org/doc/html/v5.19/admin-guide/kernel-parameters.html

which warns:

  pcie_aspm=   [PCIE] Forcibly enable or disable PCIe Active State Power Management.
       off     Disable ASPM.
       force   Enable ASPM even on devices that claim not to support it.
               WARNING: Forcing ASPM on may cause system lockups.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#266524

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2024-01-23 18:20 +0100
Message-ID<HZsBj-555b-1@gated-at.bofh.it>
In reply to#266424
On Sun 21 Jan 2024 at 21:57:20 (+0100), Geert Stappers wrote:
> On Sun, Jan 21, 2024 at 12:59:01PM -0600, David Wright wrote:
> > On Sun 21 Jan 2024 at 18:58:43 (+0100), Geert Stappers wrote:
> > > On Sun, Jan 21, 2024 at 10:44:04AM -0600, David Wright wrote:
> > > > On Sun 21 Jan 2024 at 17:33:57 (+0100), Geert Stappers wrote:
> > > > ( https://lists.debian.org/debian-user/2024/01/msg01038.html )
> > > > > [    7.854942] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
> > > > > [    7.860452] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
> > > > > [    8.356275] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
> > > > 
> > > > Run rfkill and, if it's blocked, unblock it.
> > > 
> > > Installed package `rfkill`  (it wasn't installed before)
> > > and tried it.
> > > 
> > > It does report "hard blocked", but rfkill can't change it.
> > > 
> > > I always tried a "function key" on the keyboard of the laptop,
> > > also without the desired effect.
> > 
> > Has that worked in the past … on previous Debians … on
> > the originally installed OS?
> 
> I think it has.  Years ago.

You might need to firm up that answer. I now see thinkpad
added to your Subject line, and also occurring in the logs.
A naive search for such a device turns up:
https://www.amazon.com/Centrino-Wireless-N-112BNHMW-300Mbps-Wireless/dp/B009WJ44CA
which warns "About this item // Note: this wireless card
could not work on IBM/Lenovo/Thinkpad and HP version laptop".
Several reviews expressed disappointment with the product.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#266428 — ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16

FromGeert Stappers <stappers@stappers.nl>
Date2024-01-21 22:50 +0100
SubjectThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16
Message-ID<HYNRv-4EUS-15@gated-at.bofh.it>
In reply to#266407
Hi,


Hoping that is it possible:

How to inject key stroke  or "button pressed" in /devices/platform/thinkpad_acpi/input/input16 ?



Website  https://xyproblem.info says I should tell what the original
problem is. It is `rfkill list` reporting "hard blocked", not being
enable to use WIFI,  `nmcli radio wifi` reporting "disabled".

Pressing "Function key with symbol of computer sending signal" has no
effect. Which could be caused by the horrible state of keyboard.
When keyboard is needed, is an USB-attached keyboard needed. Usual use
case of the laptop is "headless server, server with SSH access".

So I'm ask if 
  export KEYCODE=42
  echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16
could cause "wlan radio enable"? Or should KEYCODE be another magic number?



What also would be helpfull, is knowning if 

  echo 4242 > /devics/platform/laptop_chipset/input/input17

could change brightness (or another visible effect)


Regards Geert Stappers


Below some information from the original problem.


root@nero:~# dmesg | grep -e thinkpad -e iwlwifi -e rfkill
[    7.867099] thinkpad_acpi: ThinkPad ACPI Extras v0.26
[    7.867103] thinkpad_acpi: http://ibm-acpi.sf.net/
[    7.867106] thinkpad_acpi: ThinkPad BIOS 8QET54WW (1.15 ), EC unknown
[    7.867108] thinkpad_acpi: Lenovo ThinkPad X121e, model 304579G
[    7.870746] thinkpad_acpi: radio switch found; radios are disabled
[    7.870778] thinkpad_acpi: Tablet mode switch found (type: MHKG), currently in laptop mode
[    7.870815] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
[    7.870817] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
[    7.952756] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked
[    7.976749] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is blocked
[    7.978727] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
[    7.979632] thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
[    8.002749] thinkpad_acpi: Error probing battery 2
[    8.003148] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16
[    8.397512] iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[    8.405654] iwlwifi 0000:02:00.0: firmware: direct-loading firmware iwlwifi-1000-5.ucode
[    8.405864] iwlwifi 0000:02:00.0: loaded firmware version 39.31.5.1 build 35138 1000-5.ucode op_mode iwldvm
[    8.405909] iwlwifi 0000:02:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    8.658837] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
[    8.658843] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[    8.658846] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[    8.658850] iwlwifi 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C
[    8.676689] iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
[    8.702522] iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
[    8.778160] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
root@nero:~# 


-- 
Silence is hard to parse

[toc] | [prev] | [next] | [standalone]

#266431 — Re: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2024-01-21 23:40 +0100
SubjectRe: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16
Message-ID<HYODT-4Fqa-3@gated-at.bofh.it>
In reply to#266428
On Sun 21 Jan 2024 at 22:41:01 (+0100), Geert Stappers wrote:
> Pressing "Function key with symbol of computer sending signal" has no
> effect. Which could be caused by the horrible state of keyboard.
> When keyboard is needed, is an USB-attached keyboard needed. Usual use
> case of the laptop is "headless server, server with SSH access".

I'm not sure what you mean by horrible state.

> So I'm ask if 
>   export KEYCODE=42
>   echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16
> could cause "wlan radio enable"? Or should KEYCODE be another magic number?

FWIW my wifi hardware button's keycode is 246.

But I would have thought the files to peruse might be:

  $ ls -GlgR /sys/class/rfkill/rfkill0/
  /sys/class/rfkill/rfkill0/:
  total 0
  lrwxrwxrwx 1    0 Jan 21 16:13 device -> ../../phy0
  -r--r--r-- 1 4096 Jan 21 16:13 hard
  -r--r--r-- 1 4096 Jan 21 16:13 index
  -r--r--r-- 1 4096 Jan 21 16:13 name
  -r--r--r-- 1 4096 Jan 21 16:13 persistent
  drwxr-xr-x 2    0 Jan 21 16:13 power
  -rw-r--r-- 1 4096 Jan 21 16:13 soft
  -rw-r--r-- 1 4096 Jan 21 16:13 state
  lrwxrwxrwx 1    0 Jan 21 16:13 subsystem -> ../../../../../../../class/rfkill
  -r--r--r-- 1 4096 Jan 21 16:13 type
  -rw-r--r-- 1 4096 Jan 21 16:13 uevent

  /sys/class/rfkill/rfkill0/power:
  total 0
  -rw-r--r-- 1 4096 Jan 21 16:14 async
  -rw-r--r-- 1 4096 Jan 21 16:14 autosuspend_delay_ms
  -rw-r--r-- 1 4096 Jan 21 16:14 control
  -r--r--r-- 1 4096 Jan 21 16:14 runtime_active_kids
  -r--r--r-- 1 4096 Jan 21 16:14 runtime_active_time
  -r--r--r-- 1 4096 Jan 21 16:14 runtime_enabled
  -r--r--r-- 1 4096 Jan 21 16:14 runtime_status
  -r--r--r-- 1 4096 Jan 21 16:14 runtime_suspended_time
  -r--r--r-- 1 4096 Jan 21 16:14 runtime_usage
  $ 

> What also would be helpfull, is knowning if 
> 
>   echo 4242 > /devics/platform/laptop_chipset/input/input17
> 
> could change brightness (or another visible effect)

Likewise:

  $ ls -GlgR /sys/class/backlight/intel_backlight/
  /sys/class/backlight/intel_backlight/:
  total 0
  -r--r--r-- 1 4096 Jan 21 16:19 actual_brightness
  -rw-r--r-- 1 4096 Jan 21 16:19 bl_power
  -rw-r--r-- 1 4096 Jan 18 21:57 brightness
  lrwxrwxrwx 1    0 Jan 21 16:19 device -> ../../card1-eDP-1
  -r--r--r-- 1 4096 Jan 18 21:57 max_brightness
  drwxr-xr-x 2    0 Jan 21 16:19 power
  -r--r--r-- 1 4096 Jan 21 16:19 scale
  lrwxrwxrwx 1    0 Jan 18 21:57 subsystem -> ../../../../../../../class/backlight
  -r--r--r-- 1 4096 Jan 18 21:57 type
  -rw-r--r-- 1 4096 Jan 18 21:57 uevent

  /sys/class/backlight/intel_backlight/power:
  total 0
  -rw-r--r-- 1 4096 Jan 21 16:19 async
  -rw-r--r-- 1 4096 Jan 21 16:19 autosuspend_delay_ms
  -rw-r--r-- 1 4096 Jan 21 16:19 control
  -r--r--r-- 1 4096 Jan 21 16:19 runtime_active_kids
  -r--r--r-- 1 4096 Jan 21 16:19 runtime_active_time
  -r--r--r-- 1 4096 Jan 21 16:19 runtime_enabled
  -r--r--r-- 1 4096 Jan 21 16:19 runtime_status
  -r--r--r-- 1 4096 Jan 21 16:19 runtime_suspended_time
  -r--r--r-- 1 4096 Jan 21 16:19 runtime_usage
  $ 

A recent thread on that starts at:

  https://lists.debian.org/debian-user/2023/10/msg00621.html

with a nice algorithm in:

  https://lists.debian.org/debian-user/2023/10/msg00648.html

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#266442 — Re: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16

FromGeert Stappers <stappers@stappers.nl>
Date2024-01-22 07:50 +0100
SubjectRe: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16
Message-ID<HYWi6-4K6p-1@gated-at.bofh.it>
In reply to#266431
On Sun, Jan 21, 2024 at 04:34:23PM -0600, David Wright wrote:
> On Sun 21 Jan 2024 at 22:41:01 (+0100), Geert Stappers wrote:
> > Pressing "Function key with symbol of computer sending signal" has no
> > effect. Which could be caused by the horrible state of keyboard.
> > When keyboard is needed, is an USB-attached keyboard needed. Usual use
> > case of the laptop is "headless server, server with SSH access".
> 
> I'm not sure what you mean by horrible state.

That the laptop has a worndown (usage damaged) keyboard. [1]

 
> > So I'm ask if 
> >   export KEYCODE=42
> >   echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16
> > could cause "wlan radio enable"? Or should KEYCODE be another magic number?
> 
> FWIW my wifi hardware button's keycode is 246.

How was that keycode found?

 
> But I would have thought the files to peruse might be:
> 
>   $ ls -GlgR /sys/class/rfkill/rfkill0/
>   /sys/class/rfkill/rfkill0/:
>   total 0
>   lrwxrwxrwx 1    0 Jan 21 16:13 device -> ../../phy0
>   -r--r--r-- 1 4096 Jan 21 16:13 hard
>   -r--r--r-- 1 4096 Jan 21 16:13 index
>   -r--r--r-- 1 4096 Jan 21 16:13 name
>   -r--r--r-- 1 4096 Jan 21 16:13 persistent
>   drwxr-xr-x 2    0 Jan 21 16:13 power
>   -rw-r--r-- 1 4096 Jan 21 16:13 soft
>   -rw-r--r-- 1 4096 Jan 21 16:13 state
>   lrwxrwxrwx 1    0 Jan 21 16:13 subsystem -> ../../../../../../../class/rfkill
>   -r--r--r-- 1 4096 Jan 21 16:13 type
>   -rw-r--r-- 1 4096 Jan 21 16:13 uevent
> 
>   /sys/class/rfkill/rfkill0/power:
>   total 0
>   -rw-r--r-- 1 4096 Jan 21 16:14 async
>   -rw-r--r-- 1 4096 Jan 21 16:14 autosuspend_delay_ms
>   -rw-r--r-- 1 4096 Jan 21 16:14 control
>   -r--r--r-- 1 4096 Jan 21 16:14 runtime_active_kids
>   -r--r--r-- 1 4096 Jan 21 16:14 runtime_active_time
>   -r--r--r-- 1 4096 Jan 21 16:14 runtime_enabled
>   -r--r--r-- 1 4096 Jan 21 16:14 runtime_status
>   -r--r--r-- 1 4096 Jan 21 16:14 runtime_suspended_time
>   -r--r--r-- 1 4096 Jan 21 16:14 runtime_usage
>   $ 

Ah, nice.


<screenshot>
root@nero:/sys/class/rfkill/rfkill2# ls
device	hard  index  name  persistent  power  soft  state  subsystem  type  uevent
root@nero:/sys/class/rfkill/rfkill2# head *
==> device <==
head: error reading 'device': Is a directory

==> hard <==
1

==> index <==
2

==> name <==
phy0

==> persistent <==

0

==> power <==
head: error reading 'power': Is a directory

==> soft <==

0

==> state <==
2

==> subsystem <==
head: error reading 'subsystem': Is a directory

==> type <==
wlan

==> uevent <==
RFKILL_NAME=phy0
RFKILL_TYPE=wlan
RFKILL_STATE=2
root@nero:/sys/class/rfkill/rfkill2# echo 0 > hard
-bash: hard: Permission denied
root@nero:/sys/class/rfkill/rfkill2# echo 1 > soft
root@nero:/sys/class/rfkill/rfkill2# rfkill list 2
2: phy0: Wireless LAN
	Soft blocked: yes
	Hard blocked: yes
root@nero:/sys/class/rfkill/rfkill2# echo 0 > soft
root@nero:/sys/class/rfkill/rfkill2# rfkill list 2
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes
root@nero:/sys/class/rfkill/rfkill2# 
</screenshot>


Almost there and then reached a dead end.


Back to "send key code".


 
> > What also would be helpfull, is knowning if 
> > 
> >   echo 4242 > /devics/platform/laptop_chipset/input/input17
> > 
> > could change brightness (or another visible effect)
> 
> Likewise:
> 
>   $ ls -GlgR /sys/class/backlight/intel_backlight/
  <lines_deleted>
>   $ 
> 
> A recent thread on that starts at:
> 
>   https://lists.debian.org/debian-user/2023/10/msg00621.html
> 
> with a nice algorithm in:
> 
>   https://lists.debian.org/debian-user/2023/10/msg00648.html
> 

Yes, nice. However the /sys/class/backlight/intel_backlight/
translates to the /sys/class/rfkill/rfkill2/ which has been explored.



> Cheers,
> David.
 

Groeten
Geert Stappers

[1] The "horrible state" was and is also "best days are over"
-- 
Silence is hard to parse

[toc] | [prev] | [next] | [standalone]

#266491 — Re: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2024-01-23 05:10 +0100
SubjectRe: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16
Message-ID<HZggN-4XDD-5@gated-at.bofh.it>
In reply to#266442
On Mon 22 Jan 2024 at 07:40:00 (+0100), Geert Stappers wrote:
> On Sun, Jan 21, 2024 at 04:34:23PM -0600, David Wright wrote:
> > On Sun 21 Jan 2024 at 22:41:01 (+0100), Geert Stappers wrote:
> > > Pressing "Function key with symbol of computer sending signal" has no
> > > effect. Which could be caused by the horrible state of keyboard.
> > > When keyboard is needed, is an USB-attached keyboard needed. Usual use
> > > case of the laptop is "headless server, server with SSH access".
> > 
> > I'm not sure what you mean by horrible state.
> 
> That the laptop has a worndown (usage damaged) keyboard. [1]
> 
> > > So I'm ask if 
> > >   export KEYCODE=42
> > >   echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16
> > > could cause "wlan radio enable"? Or should KEYCODE be another magic number?
> > 
> > FWIW my wifi hardware button's keycode is 246.
> 
> How was that keycode found?

By running xev and pressing the button, which is on the front edge
of the laptop. Having the button there is really inconvenient, as
it's easy for a belt buckle or such to accidentally press it.
In theory, that should be easily noticed, as the button is translucent
and illuminated when wifi is connected (and flashes when attempting
to connect). However, the light is not consistent in behaviour.

But another suggestion comes from a more modern laptop, which has
an aeroplane Fn-key (action/hot key), and that uses 255.

So that's 246 / XF86WLAN   on an old laptop with a physical button,
and       255 / XF86RFKill on a newer laptop with a Fn-key.

[ … ]

> Back to "send key code".

One can but try. Did you check the BIOS, BTW?

$ xmodmap -pk or -pke will print what keycodes are available,
but I don't claim to know how all this stuff works (if it does).

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#266439 — Re: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16

FromCharles Curley <charlescurley@charlescurley.com>
Date2024-01-22 06:20 +0100
SubjectRe: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16
Message-ID<HYUSZ-4Jkt-1@gated-at.bofh.it>
In reply to#266428
On Sun, 21 Jan 2024 22:41:01 +0100
Geert Stappers <stappers@stappers.nl> wrote:

> Hoping that is it possible:
> 
> How to inject key stroke  or "button pressed" in
> /devices/platform/thinkpad_acpi/input/input16 ?

Thinkwiki might be useful. https://www.thinkwiki.org/wiki/ThinkWiki

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web