Internal Intel Wi-Fi does not connect

[clive]

Hi

inxi -nxxa
Network:
Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 00:14.3
chip-ID: 8086:a0f0 class-ID: 0280
IF: wlan0 state: down
Device-2: ZyXEL ZyAIR G-202 802.11bg driver: zd1211rw type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-4.2:10 chip-ID: 0586:3410
class-ID: ff00
IF: wlan1 state: up
Device-3: Ralink RT5370 Wireless Adapter driver: rt2800usb type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-4.4:11
chip-ID: 148f:5370 class-ID: 0000 serial: 1.0
IF: wlan2 state: up

it would be nice if I could enable the onboard, and installed, Wi-Fi Intel AX201.

I have achieved a connection via “ethernet” with a lenovo adapter, also I have 2 external USB Wi-Fi adapters that are both UP and do connect.

NOTHING seems to be able to cause a connection for the Internal Intel, all the settings seem to match, ranging from the firewall to IP address.

Wicked network manager has been removed and the ‘network manager’ is functioning.

pointers please.

Yet again why MUST I make a choice of a TAG when I don’t understand the concept.

I am running Leap 15.6 and zyppered up to date.

[clive]

Things have changed slightly, and I may just accept that openSUSE network management is the pits.

~> sudo nmcli dev wifi connect WhiffyONE password 0diferous

nxi -nn
Network:
Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi
IF: wlan0 state: UP
Device-2: ZyXEL ZyAIR G-202 802.11bg driver: zd1211rw type: USB
IF: wlan1 state: down
Device-3: Ralink RT5370 Wireless Adapter driver: rt2800usb type: USB
IF: wlan2 state: up

It really shouldn’t be this difficult, any amount of Live Distros detect and connect automagically, just asking for the WhiffyONE and 0diferous details.

[deano_ferrari]

@clive

Things have changed slightly, and I may just accept that openSUSE network management is the pits.

NetworkManager is not distro-specific. Which desktop environment are you using? The GUI connection editor differs slightIy between desktops, but all essentially do the same. It’s not clear if you’ve even managed to configure a new wireless network connection and restrict it to using wlan0 during configuration…

From a terminal can you connect to your AP using something like
nmcli dev wifi connect <SSID> password <password> ifname wlan0
Does that get you connected ok?
nmcli con show <SSID>

[clive]

Hi
Thanks for trying to help.

nmanager is linux mint and similar.

I don’t use the term AP, but probably.

nmcli con show

NAME UUID TYPE DEVICE
WhiffyONE 80f-41ec wifi wlan0

I now get a connection automatically.

It really is the problem that a Lenovo Adapter, USB c type to Ethernet worked, 2 external USB Wi-Fi plug-ins worked, but not the INTERNALdevice.

I configured dozens of times, I toggled and RFKILLed to soft unblock etc etc, and really hated it when openSuSE stopped YAST2 being able to manage network connections some 4 years or so . Then I switched to Mint.

I am back now and the same problem persists.

Tried so many things, and cannot pinpoint why a connection suddenly happened after many hours of failed attempts.

Thanks again.

[deano_ferrari]

@clive

I don’t use the term AP, but probably.

It means access point, and in this case a Wi-Fi router that you are trying to connect to.

@clive

I now get a connection automatically.

So, it is working. Good. Is that after executing the CLI command I gave, or you managed to configure via the NM connection editor?

BTW, wen posting commands and output, please use the pre-formatted text ‘</>’ button.

Posting code or preformatted text

[clive]

Hi

Apologies for my poor formatting.

I have been using SuSE since the late 1990’s (SuSE 6.0 magazine cover disk), more on than off.

I do try lots of stuff to correct errors, and over the years have managed (mostly) to solve my own problems, which is why I feel annoyed at the current batch of problems, marring an otherwise excellent distro. NB: I do cause most of my own problems.

My way of connecting is usually “auto- auto” rather than the
IPv4 Address. . . . . . . . . . . : 192.168.1.118
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

manual entry.

DNS would be 192.168.1.1 as well, and DHCP 192.168.1.1 is acceptable.

Although while typing this quad9 seem to be my best option, so I may opt for that.

Thank you for the help, yet again.