Hi,

With the last few kernels I have updated on my sid laptop, wifi is
disabled. The first time this happened I updated a net category package
)I don't remember which one) and wifi was restored.

I have tried booting with the last several kernels that I have installed doesn't seem to work. I also can't find iwconfig.

 TIA for any help,

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 11 May 2025 10:02:38 -0700
Paul Scott <waterhorsemusic@aol.com> wrote:

I have tried booting with the last several kernels that I have
installed doesn't seem to work. I also can't find iwconfig.

iwconfig comes in the package wireless-tools. You may need to
(re)install that.

--
Does anybody read signatures any more?

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, May 13, 2025 at 08:45:41AM -0700, Paul Scott wrote:

On 5/12/25 10:25 PM, Paul Scott wrote:

[...]

I see where it says that the wlp2s0 is DOWN

I'm not having great luck finding a command to bring it up after looking at

man ip

sudo ip link set wlp2s0 up

...but of course this won't connect you to the net.

*IF* you have wireless-tools installed, then you could try

sudo iwlist wlp2s0 scanning

and you would get a list of the APs your wifi "sees".

Now to get network, it depends on whether your machinery is
ifupdown, network manager, systemd-networkd or whatever.

(With ifupdown I can help a bit, with the others there are
far more knowledgeable folks than me around here).

Cheers
--
t

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCaCNrWgAKCRAFyCz1etHa RvTfAJ4j4gaCKlSpuJu9CFpF0dMJoSrZFwCeKh+mnXPzW6tBDLcLBdJanLIIc7c=
=YSxx
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, May 13, 2025 at 11:50:34AM -0700, Paul Scott wrote:

On 5/13/25 10:57 AM, David Wright wrote:

[...]

$ /sbin/rfkill

should show what's blocked, and sudo rfkill unblock all
should unblock it.

Cheers,
David.

Thank you!

Just installing rfkill solved the problem.

Have a great day,

That's what I call collaborative problem solving.

Congrats :-)

Cheers
--
t

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCaCOudQAKCRAFyCz1etHa Rv85AJ9pwnlFylQnhUJPwHycua1ZAJI4mgCdFDfPDibaOIWNTIhNpGRqz0whayM=
=++kS
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, May 14, 2025 at 09:57:17AM +0700, Max Nikulin wrote:

On 13/05/2025 22:55, tomas wrote:

sudo iwlist wlp2s0 scanning

To avoid a tool that is claimed to be a deprecated one:

sudo iw dev wlp2s0 scan

(With ifupdown I can help a bit, with the others there are
far more knowledgeable folks than me around here).

Tomas, since Paul has written that the issue was solved, I hope, the following question related to ifupdown would not be considered as hijacking the thread.

Fine with me :-)

I have noticed that deprecated wireless-tools have some kind of integration with ifupdown while README.Debian from iw explicitly states that no helpers are provided. Do you use in /etc/network/interfaces any configuration option handled by namely wireless-tools or you have solely wpasupplicant
preferences to connect to access points?

I only have needed wpa things in there (mainly wpa-ssid and wpa-psk; only
once I needed wpa-bssid to make sure my laptop connects to the 2.4 GHz band, since the AP and the laptop would prefer the 5 GHz -- more is better, right? -- but that one is unreliable as hell).

P.S. Since Paul mentioned XFCE and menu, I suspect that WiFi configuration
is handled by NetworkManager and the command to scan for available networks is

nmcli device wifi list

and just "nmcli" for configuration overview.

See? That's back on topic. So no hijack, after al ;-)

Cheers
--
t

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCaCQcOwAKCRAFyCz1etHa RiCJAJ4k2Fwnibr5hdk5gDIGatIgIpsNYwCggIVab36Ljp3gQJ6uct7oDP9KvmE=
=wtCC
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, May 15, 2025 at 10:04:11AM +0700, Max Nikulin wrote:

On 14/05/2025 11:29, tomas wrote:

On Wed, May 14, 2025 at 09:57:17AM +0700, Max Nikulin wrote:

I have noticed that deprecated wireless-tools have some kind of integration
with ifupdown while README.Debian from iw explicitly states that no helpers
are provided. Do you use in /etc/network/interfaces any configuration option
handled by namely wireless-tools or you have solely wpasupplicant preferences to connect to access points?

I only have needed wpa things in there (mainly wpa-ssid and wpa-psk; only

Thanks. So ifupdwn hooks from wireless-tools should not be used. I am in doubts concerning wpasupplicant driver. /usr/share/doc/wpasupplicant/README.Debian.gz states that old wext is used
by default while accordingly to the upstream changelog netlink driver is
used by default since 2014.

I'm not sure either. Just that the wpa things have sufficed for me,
so far.

once I needed wpa-bssid to make sure my laptop connects to the 2.4 GHz band,
since the AP and the laptop would prefer the 5 GHz -- more is better, right? --
but that one is unreliable as hell).

It is reasonable default for higher bandwidth from my point of view. Of course, there are specific cases when 2.4 GHz band is less busy or more friendly to hardware of particular devices.

Of course, as a default it makes sense. In my case, I guess it's mainly
the amount of walls between the AP and my desk what breaks 5GHz. Perhaps
it's some neighbour doing funny things. But without measuring you never
know ;-)

Cheers
--
t

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCaCVtUgAKCRAFyCz1etHa RkohAJ99X2o1mAFJAFOSrrQizgqNLNGfsgCeJNlJJYPyw4c9+lUh/1PFUSfX5RE=
=Jkoy
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)