You are not logged in.

Pages: 1

#1 2022-11-27 18:15:07

PeerK
Member
Registered: 2020-06-24
Posts: 40

How to start wifi login-debugging? EndeavourOS: ok, Arch: nok

Yesterday I installed the first time Arch and all in all it works pretty well, except the wifi: Under EndeavourOS (live image) wifi worked out of the box. Under Arch something is going wrong:

# time nmcli dev -a wifi connect <userid> password <password> 
Fehler: Aktivierung der Verbindung ist gescheitert: (53) Das WLAN konnte nicht gefunden werden.
(Error: Activation of the connection failed: (53) The wlan could not be found.)

real    0m25.911s
user    0m0.012s
sys     0m0.017s

25 seconds: Seems to be a timeout ..

NetworkManager itself is up and running and I can see the local wifi routers: 

# nmcli d wifi list
IN-USE  BSSID              SSID                  MODE   CHAN  RATE        SIGNAL  BARS  SECURITY  
        xx:xx:xx:xx:xx:xx  Loading...         Infra  1     270 Mbit/s  77      ▂▄▆_  WPA2      
        xx:xx:xx:xx:xx:xx  <SSID 1>           Infra  1     260 Mbit/s  75      ▂▄▆_  WPA2      
        ...

Since my old Manjaro Ideapad , as well with kde/plasma, is working fine with the exact same NetworkManager-config. Can anybody help me, how to dig into this error?

Thanks :-)
Peer

Technicals ..

$ inxi -NSCG
Network:
  Device-1: Intel Ethernet I225-V driver: igc
  Device-2: MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e
System:
  Host: <HostName> Kernel: 6.0.10-arch2-1 arch: x86_64 bits: 64
    Desktop: KDE Plasma v: 5.26.3 Distro: Arch Linux
CPU:
  Info: 8-core model: AMD Ryzen 9 5900HX with Radeon Graphics bits: 64
    type: MT MCP cache: L2: 4 MiB
  Speed (MHz): avg: 1725 min/max: 1200/4679 cores: 1: 3300 2: 1200 3: 1200
    4: 1200 5: 1200 6: 1200 7: 1200 8: 1200 9: 1200 10: 3300 11: 1200 12: 1200
    13: 1200 14: 3300 15: 1200 16: 3300
Graphics:
  Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] driver: amdgpu
    v: kernel
  Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    driver: amdgpu v: kernel
  Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5 driver: X:
    loaded: amdgpu unloaded: modesetting,vesa dri: radeonsi gpu: amdgpu
    resolution: 2560x1440~60Hz
  API: OpenGL v: 4.6 Mesa 22.2.3 renderer: AMD Radeon RX 6600M (navi23 LLVM
    14.0.6 DRM 3.48 6.0.10-arch2-1)

Last edited by PeerK (2022-11-27 18:21:16)

Offline

#2 2022-11-27 18:28:34

PeerK
Member
Registered: 2020-06-24
Posts: 40

Re: How to start wifi login-debugging? EndeavourOS: ok, Arch: nok

Maybe relevant: Status NetworkManager

systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
     Active: active (running) since Sun 2022-11-27 18:23:44 CET; 59min ago
       Docs: man:NetworkManager(8)
   Main PID: 7323 (NetworkManager)
      Tasks: 3 (limit: 76415)
     Memory: 10.3M
        CPU: 3.078s
     CGroup: /system.slice/NetworkManager.service
             └─7323 /usr/bin/NetworkManager --no-daemon

Nov 27 19:0 [..] device (wlan0): set-hw-addr: set MAC address to 0E:xx:yy:aa:bb:9B (scanning)
Nov 27 19:0 [..] device (wlan0): supplicant interface state: inactive -> interface_disabled
Nov 27 19:0 [..] device (wlan0): supplicant interface state: interface_disabled -> inactive
Nov 27 19:1 [..] device (wlan0): set-hw-addr: set MAC address to 9A:xx:yy:aa:bb:97 (scanning)
Nov 27 19:1 [..] device (wlan0): supplicant interface state: inactive -> interface_disabled
Nov 27 19:1 [..] device (wlan0): supplicant interface state: interface_disabled -> inactive
Nov 27 19:1 [..] device (wlan0): set-hw-addr: set MAC address to 46:xx:yy:aa:bb:B1 (scanning)
Nov 27 19:1 [..] device (wlan0): supplicant interface state: inactive -> interface_disabled
Nov 27 19:1 [..] device (wlan0): supplicant interface state: interface_disabled -> inactive
Nov 27 19:2 [..] dhcp4 (enp7s0f4u2u2): state changed new lease, address=192.168.209.41

Last edited by PeerK (2022-11-27 18:33:16)

Offline

#3 2022-11-27 18:50:40

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,323

Re: How to start wifi login-debugging? EndeavourOS: ok, Arch: nok

As a sanity check, please post the output of find /etc/systemd
?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#4 2022-11-27 20:16:50

seth
Member
Registered: 2012-09-03
Posts: 60,804

Re: How to start wifi login-debugging? EndeavourOS: ok, Arch: nok

25s is the default dbus timeout.

loginctl session-status

In doubt (and you using startx/xinit), see the last link below.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#5 2022-11-27 22:23:38

PeerK
Member
Registered: 2020-06-24
Posts: 40

Re: How to start wifi login-debugging? EndeavourOS: ok, Arch: nok

ewaller wrote:

As a sanity check, please post the output of find /etc/systemd
?

Thanks smile

I already read, that there might be possible conflicts between NM and systemd networking services. But actually, I don't know, how to identify them. Here you are:

# find /etc/systemd/
/etc/systemd/
/etc/systemd/sleep.conf
/etc/systemd/networkd.conf
/etc/systemd/pstore.conf
/etc/systemd/system.conf
/etc/systemd/logind.conf
/etc/systemd/user.conf
/etc/systemd/user
/etc/systemd/user/sockets.target.wants
/etc/systemd/user/sockets.target.wants/pulseaudio.socket
/etc/systemd/user/sockets.target.wants/pipewire.socket
/etc/systemd/user/sockets.target.wants/p11-kit-server.socket
/etc/systemd/user/pipewire-session-manager.service
/etc/systemd/user/pipewire.service.wants
/etc/systemd/user/pipewire.service.wants/pipewire-media-session.service
/etc/systemd/user/default.target.wants
/etc/systemd/user/default.target.wants/xdg-user-dirs-update.service
/etc/systemd/oomd.conf
/etc/systemd/coredump.conf
/etc/systemd/timesyncd.conf
/etc/systemd/journal-upload.conf
/etc/systemd/system
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/network-online.target.wants
/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service
/etc/systemd/system/sysinit.target.wants
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/systemd/system/display-manager.service
/etc/systemd/system/dbus-org.freedesktop.timesync1.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/sshd.service
/etc/systemd/network
/etc/systemd/homed.conf
/etc/systemd/journald.conf
/etc/systemd/journal-remote.conf
/etc/systemd/resolved.conf

Offline

#6 2022-11-27 22:30:47

PeerK
Member
Registered: 2020-06-24
Posts: 40

Re: How to start wifi login-debugging? EndeavourOS: ok, Arch: nok

seth wrote:

25s is the default dbus timeout.

loginctl session-status

In doubt (and you using startx/xinit), see the last link below.

Great, thanks for the hint!

For me, session-status seems pretty ok:

loginctl session-status
5 - <myname> (1000)
           Since: Sun 2022-11-27 16:26:59 CET; 6h ago
          Leader: 2656 (sddm-helper)
            Seat: seat0; vc1
         Display: :0
         Service: sddm; type x11; class user
         Desktop: KDE
           State: active
            Unit: session-5.scope
                  ├─2656 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-authf658bd8f-376b-47ce-a8f2-37a99fb7108f --id 3 --start /usr/bin/startplasma-x11 --user <myname>
                  ├─2669 /usr/bin/kwalletd5 --pam-login 6 8
                  └─2670 /usr/bin/startplasma-x11

Nov 27 16:26:59 <mybox> systemd[1]: Started Session 5 of User <myname>.
Nov 27 16:26:59 <mybox> sddm-helper[2668]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Nov 27 16:26:59 <mybox> sddm-helper[2670]: Adding cookie to "/home/<myname>/.Xauthority"

Offline

#7 2022-11-28 09:05:49

seth
Member
Registered: 2012-09-03
Posts: 60,804

Re: How to start wifi login-debugging? EndeavourOS: ok, Arch: nok

Let's look at you pseudo-comman again, then:

nmcli dev -a wifi connect <userid> password <password>

What do you think "userid" is? Also I'm not sure that the "-a" is legal in that specific position (but idk and I don't use NM)
Try

nmcli dev wifi connect 'My SSID' password 'mysecretpassword' # the single quotes will prevent the shell from interpreting any special tokens in there

Any kind of "userid" has absolutely no business there.

Also please post the actual "wifi list"
The BSSID is no secret - if I'm in radio distance I can say that the forum user w/ the nick "PeerK" lives around here. That's all.
And if your SSID is embarrassing, just don't choose embarrassing SSIDs tongue

Since you're using plasma, can you connect w/ the plasma widget thingy?

Finally, look at your system journal after failign to connect.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

Pages: 1

Board footer

Powered by FluxBB