You are not logged in.

#1 2022-08-11 20:36:44

fortuna
Member
Registered: 2021-02-09
Posts: 76

mt76x0u dongle disconnects

So, to improve the poor built-in laptop wifi I ordered this wifi dongle as recommended here.
And it is fast.... when it finally connects. But it takes ages before it does and then it disconnects randomly to start all over again.
The mt76x0u driver is loaded but maybe tweaking its parameters may do the trick?

This is the relevant dmesg output after plugging in the dongle:

[Thu Aug 11 22:29:52 2022] usb 1-5: new high-speed USB device number 7 using ehci-pci
[Thu Aug 11 22:29:52 2022] usb 1-5: New USB device found, idVendor=0e8d, idProduct=7610, bcdDevice= 1.00
[Thu Aug 11 22:29:52 2022] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Thu Aug 11 22:29:52 2022] usb 1-5: Product: WiFi
[Thu Aug 11 22:29:52 2022] usb 1-5: Manufacturer: MediaTek
[Thu Aug 11 22:29:52 2022] usb 1-5: SerialNumber: 1.0
[Thu Aug 11 22:29:52 2022] usb 1-5: reset high-speed USB device number 7 using ehci-pci
[Thu Aug 11 22:29:52 2022] mt76x0u 1-5:1.0: ASIC revision: 76100002 MAC revision: 76502000
[Thu Aug 11 22:29:52 2022] audit: type=1131 audit(1660249793.795:151): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Thu Aug 11 22:29:53 2022] mt76x0u 1-5:1.0: EEPROM ver:02 fae:04
[Thu Aug 11 22:29:53 2022] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht'
[Thu Aug 11 22:29:53 2022] audit: type=1130 audit(1660249794.805:152): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Thu Aug 11 22:29:53 2022] mt76x0u 1-5:1.0 wlp0s29f7u5: renamed from wlan0
[Thu Aug 11 22:29:58 2022] audit: type=1131 audit(1660249799.805:153): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[Thu Aug 11 22:30:05 2022] systemd-journald[194]: Data hash table of /var/log/journal/d19ae6d0a93d4e7fac3ba63e79fe9c72/system.journal has a fill level at 75.1 (2733 of 3640 items, 2097152 file size, 767 bytes per hash table item), suggesting rotation.
[Thu Aug 11 22:30:05 2022] systemd-journald[194]: /var/log/journal/d19ae6d0a93d4e7fac3ba63e79fe9c72/system.journal: Journal header limits reached or header out-of-date, rotating.
[Thu Aug 11 22:30:05 2022] wlp0s29f7u5: authenticate with d8:07:b6:d6:b3:39
[Thu Aug 11 22:30:06 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 1/3)
[Thu Aug 11 22:30:07 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 2/3)
[Thu Aug 11 22:30:08 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 3/3)
[Thu Aug 11 22:30:08 2022] wlp0s29f7u5: authentication with d8:07:b6:d6:b3:39 timed out
[Thu Aug 11 22:30:09 2022] audit: type=1101 audit(1660249810.475:154): pid=3367 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="sil" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:09 2022] audit: type=1110 audit(1660249810.485:155): pid=3367 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:09 2022] audit: type=1105 audit(1660249810.485:156): pid=3367 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:09 2022] audit: type=1106 audit(1660249810.515:157): pid=3367 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:09 2022] audit: type=1104 audit(1660249810.515:158): pid=3367 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:14 2022] wlp0s29f7u5: authenticate with d8:07:b6:d6:b3:39
[Thu Aug 11 22:30:14 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 1/3)
[Thu Aug 11 22:30:16 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 2/3)
[Thu Aug 11 22:30:17 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 3/3)
[Thu Aug 11 22:30:17 2022] wlp0s29f7u5: authentication with d8:07:b6:d6:b3:39 timed out
[Thu Aug 11 22:30:21 2022] audit: type=1101 audit(1660249822.575:159): pid=3371 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="sil" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:21 2022] audit: type=1110 audit(1660249822.575:160): pid=3371 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:21 2022] audit: type=1105 audit(1660249822.575:161): pid=3371 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:21 2022] audit: type=1106 audit(1660249822.605:162): pid=3371 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:21 2022] audit: type=1104 audit(1660249822.605:163): pid=3371 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:23 2022] wlp0s29f7u5: authenticate with d8:07:b6:d6:b3:39
[Thu Aug 11 22:30:23 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 1/3)
[Thu Aug 11 22:30:25 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 2/3)
[Thu Aug 11 22:30:26 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 3/3)
[Thu Aug 11 22:30:26 2022] wlp0s29f7u5: authentication with d8:07:b6:d6:b3:39 timed out
[Thu Aug 11 22:30:37 2022] mt76x0u 1-5:1.0: Warning: MAC TX did not stop!
[Thu Aug 11 22:30:37 2022] audit: type=1101 audit(1660249838.355:164): pid=3375 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="sil" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:37 2022] audit: type=1110 audit(1660249838.355:165): pid=3375 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:37 2022] audit: type=1105 audit(1660249838.365:166): pid=3375 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:37 2022] audit: type=1106 audit(1660249838.405:167): pid=3375 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:37 2022] audit: type=1104 audit(1660249838.405:168): pid=3375 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:49 2022] mt76x0u 1-5:1.0: Warning: MAC TX did not stop!
[Thu Aug 11 22:30:49 2022] audit: type=1101 audit(1660249850.205:169): pid=3379 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="sil" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:49 2022] audit: type=1110 audit(1660249850.205:170): pid=3379 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:49 2022] audit: type=1105 audit(1660249850.215:171): pid=3379 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:49 2022] audit: type=1106 audit(1660249850.255:172): pid=3379 uid=1000 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:49 2022] audit: type=1104 audit(1660249850.255:173): pid=3379 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:30:54 2022] wlp0s29f7u5: authenticate with d8:07:b6:d6:b3:39
[Thu Aug 11 22:30:55 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 1/3)
[Thu Aug 11 22:30:56 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 2/3)
[Thu Aug 11 22:30:57 2022] wlp0s29f7u5: send auth to d8:07:b6:d6:b3:39 (try 3/3)
[Thu Aug 11 22:30:58 2022] wlp0s29f7u5: authentication with d8:07:b6:d6:b3:39 timed out
[Thu Aug 11 22:31:03 2022] audit: type=1101 audit(1660249864.106:174): pid=3382 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct="sil" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:31:03 2022] audit: type=1110 audit(1660249864.116:175): pid=3382 uid=1000 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_env,pam_faillock acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
[Thu Aug 11 22:31:03 2022] audit: type=1105 audit(1660249864.126:176): pid=3382 uid=1000 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_systemd_home,pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'

Offline

#2 2022-08-11 21:16:53

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

user@laptop:~/box$ lsmod | grep mt
mt76x0u                20480  0
mt76x0_common          53248  1 mt76x0u
mt76x02_usb            20480  1 mt76x0u
mt76_usb               36864  2 mt76x02_usb,mt76x0u
mt76x02_lib            90112  3 mt76x02_usb,mt76x0_common,mt76x0u
mt76                   90112  5 mt76_usb,mt76x02_lib,mt76x02_usb,mt76x0_common,mt76x0u
mac80211             1216512  7 mt76,iwl3945,iwlegacy,mt76x02_lib,mt76x02_usb,mt76x0_common,mt76x0u
cfg80211             1056768  6 mt76,iwl3945,iwlegacy,mt76x02_lib,mac80211,mt76x02_usb

Is this correct?

Last edited by fortuna (2022-08-11 22:36:11)

Offline

#3 2022-08-11 22:01:04

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: mt76x0u dongle disconnects

[Thu Aug 11 22:30:49 2022] mt76x0u 1-5:1.0: Warning: MAC TX did not stop!

On a hunch

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

and see https://wiki.archlinux.org/title/Networ … domization

Offline

#4 2022-08-11 22:38:21

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

user@laptop:~$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
atd.service                              | multi-user.target.wants
cronie.service                           | multi-user.target.wants
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
lm_sensors.service                       | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
smb.service                              | multi-user.target.wants
sshd.socket                              | sockets.target.wants
systemd-timesyncd.service                | sysinit.target.wants

Offline

#5 2022-08-11 22:52:17

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

Should this do the trick?

user@laptop:~$ sudo systemctl disable NetworkManager-wait-online.service

Offline

#6 2022-08-11 23:04:06

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: mt76x0u dongle disconnects

No, that service triggers a target that some other services wait for.
See the linked wiki paragraph and try to disable the MAC randomization (because some APs really don't like that behavior)

Offline

#7 2022-08-12 16:44:23

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

NetworkManager doesn't seem to do MAC randomization. DHCP always assigns the same IP address. A few android phones around here do and the AP has no problem with that. It is running OpenWrt firmware.
Anyway, MAC randomization is now disabled in NetworkManager config.
Fingers crossed.

Offline

#8 2022-08-12 18:31:10

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: mt76x0u dongle disconnects

Ftr, the feature is only relevant for the scanning that NM frequently performs, not the actual connection. So yes, NM (by default) *does* MAC randomization (on scanning) and that will not have any impact on the IP assignment, because it uses the default MAC when trying to associate to an AP.

Offline

#9 2022-08-13 19:02:53

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

It still takes up to a few minutes and several attempts for the dongle to connect after (re-)boot although it may have improved a little after disabling MAC randomization.
It may be important to point out that these problems only occur when connecting to a wifi5 network. Connecting to wifi4 succeeds in the first attempt.
BTW, is it normal that the dongle disconnects for about 20 secs after a left click in the systray nm-applet?

Offline

#10 2022-08-13 20:41:16

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: mt76x0u dongle disconnects

problems only occur when connecting to a wifi5 network. Connecting to wifi4 succeeds in the first attempt

Both on 5GHz?

You could try to pass

mac80211.minstrel_vht_only=true

to the kernel.

Offline

#11 2022-08-13 23:08:51

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

I think minstrel_vht_only is set true already:

user@laptop:~$ sudo cat /sys/module/mac80211/parameters/minstrel_vht_only
Y

Are the other parameters set correctly?

user@laptop:~$ cd /sys/module/mac80211/parameters/; ls | while read i; do echo -n "$i = "; sudo cat $i; done
beacon_loss_count = 7
ieee80211_default_rc_algo = minstrel_ht
max_nullfunc_tries = 2
max_probe_tries = 5
minstrel_vht_only = Y
probe_wait_ms = 500

Offline

#12 2022-08-14 06:15:16

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: mt76x0u dongle disconnects

seth wrote:

problems only occur when connecting to a wifi5 network. Connecting to wifi4 succeeds in the first attempt

Both on 5GHz?

fyi:

cd /sys/module/mac80211/parameters/; ls | while read i; do echo -n "$i = "; sudo cat $i; done

systool -vm mac80211

Offline

#13 2022-08-14 12:08:59

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

Both on 5GHz?

Sorry for the misunderstanding. My fault.
The AP is dual band and has two radios configured:

  • 802.11bgn Channel: 1 (2.412 GHz)

  • 802.11nac Channel: 40 (5.200 GHz)

The built-in laptop wifi connects to both channels flawlessly.
The dongle connects to channel 1 without any problem. Connecting to channel 40 takes minutes and several attempts.

systool -vm mac80211

Thanks. Learnt something today cool

user@laptop:~$ systool -vm mac80211
Module = "mac80211"

  Attributes:
    coresize            = "1216512"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "7"
    srcversion          = "60AB101F8E93492E2A12038"
    taint               = ""
    uevent              = <store method only>

  Parameters:
    beacon_loss_count   = "7"
    ieee80211_default_rc_algo= "minstrel_ht"
    max_nullfunc_tries  = "2"
    max_probe_tries     = "5"
    minstrel_vht_only   = "Y"
    probe_wait_ms       = "500"

  Sections:

Offline

#14 2022-08-14 12:28:09

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: mt76x0u dongle disconnects

The AP is dual band and has two radios configured:

Is the AP under your control?
Can you enable a 5GH 802.11n channel only? (I don't see how to disable ac in the mt76x0u module and it's quite likely not possible)

Also post a complete system journal (sudo jorunalctl -b) after supposingly connecting to the 5GHz AP w/ the dongle and one journal after connecting w/ the built-in chip.
Because

The built-in laptop wifi connects to both channels flawlessly.

So, to improve the poor built-in laptop wifi I ordered this wifi dongle as recommended here.

seems somehow contradictive.

To avoid a d'ohh moment: move closer to the AP, 5GHz has a much shorther range than 2.4GHz…

Offline

#15 2022-08-14 17:43:11

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

Is the AP under your control?

Yes.

Can you enable a 5GH 802.11n channel only?

No. The AP has a Qualcomm Atheros QCA9560 chipset and it doesn't do 5 GHz even though it says it's 802.11bgn.

Because
The built-in laptop wifi connects to both channels flawlessly.
So, to improve the poor built-in laptop wifi I ordered this wifi dongle as recommended here.
seems somehow contradictive.

Yes. I understand. Let me explain. The laptop built-in wifi connects immediately, which is good, but once connected it's very slow. The dongle is approx. 4x faster. That's why I bought it. I didn't foresee this trouble.

System journal after connecting to the 5GHz AP w/ the dongle:
http://ix.io/47Br
It connected in the 5th attempt.

System journal after connecting to the 5GHz AP w/ the laptop built-in chip:
http://ix.io/47BM
It connected in the 1st attempt.

Offline

#16 2022-08-14 20:52:45

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: mt76x0u dongle disconnects

The chip seems to be in scanning mode a lot, even during connection attempts you get a scan attempt which fails because scanning is already pending…

Aug 14 19:31:17 laptop wpa_supplicant[323]: wlp0s29f7u7: Reject scan trigger since one is already pending
Aug 14 19:31:17 laptop wpa_supplicant[323]: wlp0s29f7u7: Failed to initiate AP scan

Stop/disable NetworkManager and try to connect w/ wifi-menu from the netctl package.
If that works instantly, you could try to lock the BSSIDs of the profiles, https://wiki.archlinux.org/title/Networ … ets_(WiFi)

Offline

#17 2022-08-14 21:39:30

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

Stop/disable NetworkManager and try to connect w/ wifi-menu from the netctl package.
If that works instantly, you could try to lock the BSSIDs of the profiles, https://wiki.archlinux.org/title/Networ … ets_(WiFi)

That doesn't work. The first attempt took a while and failed. New attempts give straight away:

user@laptop:~$ systemctl status "netctl@wlp0s29f7u7\\x2dcasillas5.service"
× netctl@wlp0s29f7u7\x2dcasillas5.service - Networking for netctl profile wlp0s29f7u7-casillas5
     Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
     Active: failed (Result: exit-code) since Sun 2022-08-14 23:23:16 CEST; 27s ago
   Duration: 16.970s
       Docs: man:netctl.profile(5)
    Process: 2291 ExecStart=/usr/lib/netctl/network start wlp0s29f7u7-casillas5 (code=exited, status=1/FA>
   Main PID: 2291 (code=exited, status=1/FAILURE)
        CPU: 20ms

I don't recall the exact details but I remember that when I changed arch from desktop to laptop I installed NetworkManager to handle wifi networks. On the desktop the wired interface was handled without NetworkManager. Is it possible that systemd is still running a network manager? It would show up in the listing of post #4, right?

Offline

#18 2022-08-15 06:07:22

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: mt76x0u dongle disconnects

It would show up in the listing of post #4, right?

Yes.

Process: 2291 ExecStart=/usr/lib/netctl/network start wlp0s29f7u7-casillas5 (code=exited, status=1/FA>

Don't copy and paste out of the pager, it caps the output.
Also check the system journal on what actually failed here (could be wpa_supplicant failing to associate, could be a missing dhcpcd process)

Offline

#19 2022-08-15 15:28:59

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

I admire your patience!

sudo journalctl -b after stopping NetworkManager, removing wifi-menu profile, executing

sudo wifi-menu wlp0s29f7u7

manually choosing "casillas5" from scanned networks and entering password:

http://ix.io/47H6

Offline

#20 2022-08-15 15:42:15

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: mt76x0u dongle disconnects

Ask me about an upcoming show on amazon prime to see my patience disappearing very fast…

Back on topic:
We're timing out but networkmanager had been active during that boot, so really disable networkmanager, reboot and try netctl - if it still times out, NM/scanning is off the hook.

Offline

#21 2022-08-15 16:17:00

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

networkmanager had been active during that boot

I thought you wouldn't notice wink

Same procedure but now after booting without NetworkManager nor NetworkManager-wait-online.service:

http://ix.io/47Ho

After finishing NetworkManager is started to upload the journal and post this. After starting NetworkManager the same dongle connects to the WIFI 4 network "casillas".

Last edited by fortuna (2022-08-15 16:26:23)

Offline

#22 2022-08-15 16:36:29

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: mt76x0u dongle disconnects

Aug 15 18:06:33 laptop systemd[1]: Starting Networking for netctl profile wlp0s29f7u7-casillas5...
Aug 15 18:06:33 laptop network[775]: Starting network profile 'wlp0s29f7u7-casillas5'...
Aug 15 18:06:33 laptop systemd[1]: Started Networking for netctl profile wlp0s29f7u7-casillas5.
Aug 15 18:06:33 laptop systemd[1]: Reached target Network.
Aug 15 18:06:39 laptop kernel: wlp0s29f7u7: authenticate with d8:07:b6:d6:b3:39
Aug 15 18:06:39 laptop kernel: wlp0s29f7u7: send auth to d8:07:b6:d6:b3:39 (try 1/3)
Aug 15 18:06:40 laptop kernel: wlp0s29f7u7: send auth to d8:07:b6:d6:b3:39 (try 2/3)
Aug 15 18:06:42 laptop kernel: wlp0s29f7u7: send auth to d8:07:b6:d6:b3:39 (try 3/3)
Aug 15 18:06:42 laptop kernel: wlp0s29f7u7: authentication with d8:07:b6:d6:b3:39 timed out
Aug 15 18:06:50 laptop network[775]: WPA association/authentication failed for interface 'wlp0s29f7u7'
Aug 15 18:06:56 laptop kernel: mt76x0u 1-7:1.0: Warning: MAC TX did not stop!
Aug 15 18:06:56 laptop network[775]: Failed to bring the network up for profile 'wlp0s29f7u7-casillas5'
Aug 15 18:06:56 laptop systemd[1]: netctl@wlp0s29f7u7\x2dcasillas5.service: Main process exited, code=exited, status=1/FAILURE
Aug 15 18:06:56 laptop systemd[1]: netctl@wlp0s29f7u7\x2dcasillas5.service: Failed with result 'exit-code'.
Aug 15 18:06:56 laptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=netctl@wlp0s29f7u7\x2dcasillas5 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Aug 15 18:06:56 laptop systemd[1]: netctl@wlp0s29f7u7\x2dcasillas5.service: Consumed 1.220s CPU time.

No, exact same problem - so it's not the scanning.

The consistent driver message "mt76x0u 1-5:1.0: Warning: MAC TX did not stop!" shows up rarwly but in https://bugzilla.kernel.org/show_bug.cgi?id=202541 and https://github.com/openwrt/mt76/issues/230
You're not attaching it to an xhci port, nor are the any protocol errors, but maybe try a different usb slot anyway.
For the second link, wavemon is here: https://archlinux.org/packages/communit … 4/wavemon/

Offline

#23 2022-08-15 17:54:45

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

On the first link, as you know from the journal the laptop is a Dell Latitude D820. As you said, it has only USB 2.0 Ports. Number of USB 2.0 Ports: 4.
Tried them all. No significant difference. There is some spread in how long it takes to connect, so sometimes you think using a different USB  port is faster but then repeating the test it is not or it takes even longer than average.

As for the second link, as I said the AP runs OpenWrt firmware. It provides excellent information. E.g. when connected @ 5 GHz:

With MediaTek Inc. WIFI dongle:

RX Rate 180.0 Mbit/s, 40 MHz, VHT-MCS 8, VHT-NSS 1, Short GI
TX Rate 150.0 Mbit/s, 40 MHz, VHT-MCS 7, VHT-NSS 1, Short GI

With Dell Latitude D820 built-in WiFi:

RX Rate 36.0 Mbit/s, 20 MHz
TX Rate 54.0 Mbit/s, 20 MHz

If you still need it, in what format do you want me to post Wavemon output? It doesn't seem to produce plain text suitable to be copied here.

BTW, I changed the AP radio from channel 40 to 44 and tried forcing CCMP (AES) and TKIP ciphers. Made no difference.

Offline

#24 2022-08-15 18:49:26

fortuna
Member
Registered: 2021-02-09
Posts: 76

Re: mt76x0u dongle disconnects

Good old screenshot comes to the rescue:
https://up.nl.eu.org/mt76x0u-dongle/wav … illas5.jpg

8.9% is a high number of TX retries, isn't it?

Offline

#25 2022-08-15 19:08:06

seth
Member
Registered: 2012-09-03
Posts: 49,992

Re: mt76x0u dongle disconnects

I didn't have all that high hopes for the usb port and the NSS is correct ("1") so that's a dead end, too.
A <10% retry rate is actually fairly good, anything below 20% is acceptable.

It's not the signal (we know that because it's working fine after the connection)

My next (and for the momemt "last") best guess is to try whether iwd fares better, https://wiki.archlinux.org/title/Iwd & https://wiki.archlinux.org/title/Networ … Fi_backend (you can immediately try to use it as NM backend)
nb. that installing iwd will result in different NIC names, https://wiki.archlinux.org/title/Iwd#Wi … ed_by_udev

AP runs OpenWrt firmware. It provides excellent information

You could also check the APs logs on conneciton attempts on whether it complains about anything…

Offline

Board footer

Powered by FluxBB