Re: rfkill list wlan, Hard blocked: yes
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.
Reply to: