Driver for Archer T3U no more in AUR repo

[megavolt]

Here is the problem:

déc. 25 16:00:36 NetworkManager[697]: <info>  [1608908436.2365] device (wlo1): Activation: (wifi) access point 'Livebox-93E0' has security, but secrets are required.
déc. 25 16:00:36 NetworkManager[697]: <info>  [1608908436.2365] device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')

config -> need-auth (reason 'none', sys-iface-state: 'managed')

It tries to connect with device wlo1 which is your internal card, but no password or the wrong password is there saved… and then it goes inactive.

déc. 25 16:01:01 NetworkManager[697]: <warn>  [1608908461.7290] device (wlo1): Activation: (wifi) association took too long, failing activation

[Philline00]

what have I to do ??

[megavolt]

I am not using KDE, but there should be way to delete the config of the connection to access point ‘Livebox-93E0’ and type again the correct password.

While doing so, it would be good start this FIRST to check the activity of the NetworkManager:

journalctl -u NetworkManager --no-hostname --follow

[Philline00]

Yes the way live in KDE …
waitting …

[megavolt]

Oh wait… sorry I overlooked something:

déc. 25 15:59:55 NetworkManager[697]: <info>  [1608908395.8563] device (wlo1): supplicant interface state: interface_disabled -> inactive
déc. 25 15:59:55 NetworkManager[697]: <info>  [1608908395.8786] device (wlo1): supplicant interface state: inactive -> scanning
déc. 25 15:59:57 NetworkManager[697]: <info>  [1608908397.0292] device (wlo1): supplicant interface state: scanning -> authenticating
déc. 25 15:59:57 NetworkManager[697]: <info>  [1608908397.1984] device (wlo1): supplicant interface state: authenticating -> disconnected
déc. 25 16:00:07 NetworkManager[697]: <info>  [1608908407.2012] device (wlo1): supplicant interface state: disconnected -> scanning
déc. 25 16:00:08 NetworkManager[697]: <info>  [1608908408.3198] device (wlo1): supplicant interface state: scanning -> authenticating
déc. 25 16:00:08 NetworkManager[697]: <info>  [1608908408.4779] device (wlo1): supplicant interface state: authenticating -> disconnected
déc. 25 16:00:18 NetworkManager[697]: <info>  [1608908418.4809] device (wlo1): supplicant interface state: disconnected -> scanning
déc. 25 16:00:20 NetworkManager[697]: <warn>  [1608908420.7290] device (wlo1): Activation: (wifi) association took too long, failing activation

Could you also post the output of:

rfkill

Maybe the card has been blocked?

Otherwise i can only expect that the antenna is broken somehow or has a lose contact on the card internally … so that it does not find any SSIDs or the driver, which is a unified one, is just bad on kernel 4.19 … try a newer kernel which have better drivers.

[Philline00]

@megavolt

rfkill

[philline0@philline0-hplx ~]$ rfkill
ID TYPE DEVICE SOFT HARD
0 wlan hp-wifi débloqué débloqué
1 wlan phy0 débloqué débloqué
2 bluetooth hci0 débloqué débloqué
3 wlan phy1 débloqué débloqué

[Wollie]

Just a tip: Add

LANG=C

in front of your command (as you did already) to get English output.

[Philline00]

Meantime been done : 1/ deleted the livebox connecting 2 / shutdown the PC. 3/reinstall the wlo (dongle unplugged) and newly introduce activating key and forcing the mac adress as “journalctl”
result : no change …

oh … sorry for the language …but adding lang=c is not active
[philline0@philline0-hplx ~]$ rfkill
ID TYPE DEVICE SOFT HARD
0 wlan hp-wifi débloqué débloqué
1 wlan phy0 débloqué débloqué
2 bluetooth hci0 débloqué débloqué
3 wlan phy1 débloqué débloqué
i translate the 8 answers for soft and hard are all “unblocked”.

WHAT ABOUT THE DRIVER ? for such card ? …

[Philline00]

@megavolt

Otherwise i can only expect that the antenna is broken somehow or has a lose contact on the card internally … so that it does not find any SSIDs or the driver, which is a unified one, is just bad on kernel 4.19 … try a newer kernel which have better drivers

Access a 5.4-80 kernel is not possible … I should reinstall my config ! …

The card has been physically reinstalled to be sure it well connected.
Otherwise, with a dongle it is right … that is not the case of the card … so something fails with the card …if not the driver, it’s the sender …you are right…
So the dongle will do the work…forever.

I very appreciated your guiding… with the respect of an old debutant.
Thanks you very much.
philline00 - Basic user.

ps - Re-opened a new topic some days ago because i was not sure we could pursue on this one …
Don,t be annoyed with this way. You gave me all the needed supports and that’s so enough.