einrichtung eines wlan usb-stick: tp-link archer t3u plus

kope96 · 30. Juli 2025

Hallo,

ich benutze openSUSE Tumbleweed und möchte gerne den WLAN-USB-Adapter TP-Link AC1300/Archer T3U Plus mit meinem Laptop (Dell Latitude 5490) nutzen.

Allerdings verstehe ich nicht, wie ich den Adapter in Betrieb nehmen kann. Wenn ich lsusb eingebe, dann wird der Adapter korrekt erkannt (Bus 002 Device 015: ID 2357:0138 TP-Link 802.11ac NIC). Ich weiß auch nicht, wie ich herausfinde, ob der Adapter "in Betrieb" ist oder ob ich noch etwas tun muss, um diesen einzurichten (also Treiber nachinstallieren; in den Netzwerkeinstellungen, etc.). Kann mir jemand Hinweise geben?

Viele Grüße

Peter

luigi · 30. Juli 2025

Was ergibt als root

Code

hwinfo --wlan

kope96 · 30. Juli 2025

o.k. ich poste mal den Teil der Ausgabe, der sich auf den tp-link Adapter beziehen sollte. Ich hoffe das reicht aus:

Code

23: USB 00.0: 0282 WLAN controller
  [Created at usb.124]
  Unique ID: R_O4.ohEyXIDRkg0
  Parent ID: pBe4.xYNhIwdOaa6
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb2/2-6/2-6:1.0
  SysFS BusID: 2-6:1.0
  Hardware Class: network
  Model: "TP-Link 802.11ac NIC"
  Hotplug: USB
  Vendor: usb 0x2357 "TP-Link"
  Device: usb 0x0138 "802.11ac NIC"
  Revision: "3.00"
  Serial ID: "123456"
  Driver: "rtw_8822bu"
  Driver Modules: "rtw88_8822bu"
  Device File: wlp0s20f0u6
  Features: WLAN
  HW Address: 36:c8:68:5e:ba:3f
  Permanent HW Address: 98:03:8e:4f:c7:94
  Link detected: no
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "usb:v2357p0138d0300dc00dsc00dp00icFFiscFFipFFin00"
  Driver Info #0:
    Driver Status: rtw88_8822bu is active
    Driver Activation Cmd: "modprobe rtw88_8822bu"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #27 (Hub)

Alles anzeigen

luigi · 30. Juli 2025

das sieht doch ganz gut aus.Und was sagt

Code

ip a

JSC · 30. Juli 2025

Zitat von kope96

Ich weiß auch nicht, wie ich herausfinde, ob der Adapter "in Betrieb" ist oder ob ich noch etwas tun muss,

Anwendungsstarter ->Systemsteinstellungen -> Wlan & Internet

Sauerland · 30. Juli 2025

Zitat von kope96

Link detected: no

Was sagt:

Code

/usr/sbin/rfkill list all

bei eingestecktem Stick?

Ansonsten:

Stick abziehen, Konsole/Terminal öffnen und als root ausführen:

Code

journalctl -f

kurz abwarten, Stick anstecken und alle neu hinzukommenden Ausgaben der Konsole/Terminals hier posten.

kope96 · 30. Juli 2025

Zitat von luigi
das sieht doch ganz gut aus.Und was sagt
Code
ip a

Die Ausgabe ist:

Code

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
3: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether e4:b9:7a:2e:4e:37 brd ff:ff:ff:ff:ff:ff
    altname enxe4b97a2e4e37
4: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 64:5d:86:b7:1c:3b brd ff:ff:ff:ff:ff:ff
    altname wlx645d86b71c3b
    inet 192.168.178.20/24 brd 192.168.178.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 863955sec preferred_lft 863955sec
    inet6 2003:ea:1748:9c00:72e2:ffd3:a734:54bd/128 scope global dynamic noprefixroute 
       valid_lft 7157sec preferred_lft 3557sec
    inet6 2003:ea:1748:9c00:f29b:c6c5:7cac:f024/64 scope global temporary dynamic 
       valid_lft 7164sec preferred_lft 1559sec
    inet6 2003:ea:1748:9c00:6d02:fa5:1f3:57d6/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 7164sec preferred_lft 1559sec
    inet6 fd6c:dc81:a84b:0:29dd:91bb:6bd4:7269/64 scope global temporary dynamic 
       valid_lft 7164sec preferred_lft 3564sec
    inet6 fd6c:dc81:a84b:0:d476:c70e:a35a:c2fc/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 7164sec preferred_lft 3564sec
    inet6 fe80::72e2:ffd3:a734:54bd/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
15: wlp0s20f0u6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 7a:e1:cc:6f:e5:67 brd ff:ff:ff:ff:ff:ff permaddr 98:03:8e:4f:c7:94
    altname wlx98038e4fc794
16: wwp0s20f0u2i12: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 62:66:da:e2:58:e0 brd ff:ff:ff:ff:ff:ff

Alles anzeigen

kope96 · 30. Juli 2025

Zitat von Sauerland
Was sagt:
Code
/usr/sbin/rfkill list all
bei eingestecktem Stick?

Ansonsten:
Stick abziehen, Konsole/Terminal öffnen und als root ausführen:
Code
journalctl -f
kurz abwarten, Stick anstecken und alle neu hinzukommenden Ausgaben der Konsole/Terminals hier posten.
Alles anzeigen

und zu /usr... lautet die Ausgabe:

Code

1: dell-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: dell-bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
3: dell-wwan: Wireless WAN
        Soft blocked: yes
        Hard blocked: no
4: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
13: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
14: phy10: Wireless LAN
        Soft blocked: no

Alles anzeigen

und zu journalctl -f

Code

Jul 30 18:11:12 pekolatitude5390 kernel: usb 1-9: new high-speed USB device number 21 using xhci_hcd
Jul 30 18:11:12 pekolatitude5390 kernel: usb 1-9: New USB device found, idVendor=2357, idProduct=0138, bcdDevice= 2.10
Jul 30 18:11:12 pekolatitude5390 kernel: usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 30 18:11:12 pekolatitude5390 kernel: usb 1-9: Product: 802.11ac NIC
Jul 30 18:11:12 pekolatitude5390 kernel: usb 1-9: Manufacturer: Realtek
Jul 30 18:11:12 pekolatitude5390 kernel: usb 1-9: SerialNumber: 123456
Jul 30 18:11:12 pekolatitude5390 kernel: rtw_8822bu 1-9:1.0: Firmware version 27.2.0, H2C version 13
Jul 30 18:11:12 pekolatitude5390 kernel: rtw_8822bu 1-9:1.0: rtw_usb_reg_sec: reg 0x4e0, usb write 1 fail, status: -71
Jul 30 18:11:12 pekolatitude5390 kernel: usb 1-9: USB disconnect, device number 21
Jul 30 18:11:12 pekolatitude5390 kernel: usb 2-6: new SuperSpeed USB device number 21 using xhci_hcd
Jul 30 18:11:12 pekolatitude5390 kernel: usb 2-6: New USB device found, idVendor=2357, idProduct=0138, bcdDevice= 3.00
Jul 30 18:11:12 pekolatitude5390 kernel: usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 30 18:11:12 pekolatitude5390 kernel: usb 2-6: Product: 802.11ac NIC
Jul 30 18:11:12 pekolatitude5390 kernel: usb 2-6: Manufacturer: Realtek
Jul 30 18:11:12 pekolatitude5390 kernel: usb 2-6: SerialNumber: 123456
Jul 30 18:11:12 pekolatitude5390 kernel: rtw_8822bu 2-6:1.0: Firmware version 27.2.0, H2C version 13
Jul 30 18:11:13 pekolatitude5390 NetworkManager[1274]: <info>  [1753891873.1939] device (wlan0): driver supports Access Point (AP) mode
Jul 30 18:11:13 pekolatitude5390 NetworkManager[1274]: <info>  [1753891873.1954] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/23)
Jul 30 18:11:13 pekolatitude5390 systemd[1]: Starting Load/Save RF Kill Switch Status...
Jul 30 18:11:13 pekolatitude5390 mtp-probe[85044]: checking bus 2, device 21: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-6"
Jul 30 18:11:13 pekolatitude5390 mtp-probe[85044]: bus: 2, device: 21 was not an MTP device
Jul 30 18:11:13 pekolatitude5390 NetworkManager[1274]: <info>  [1753891873.2429] rfkill16: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:14.0/usb2/2-6/2-6:1.0/ieee80211/phy14/rfkill16) (driver rtw_8822bu)
Jul 30 18:11:13 pekolatitude5390 kernel: rtw_8822bu 2-6:1.0 wlp0s20f0u6: renamed from wlan0
Jul 30 18:11:13 pekolatitude5390 NetworkManager[1274]: <info>  [1753891873.2471] device (wlan0): interface index 18 renamed iface from 'wlan0' to 'wlp0s20f0u6'
Jul 30 18:11:13 pekolatitude5390 systemd[1]: Started Load/Save RF Kill Switch Status.
Jul 30 18:11:13 pekolatitude5390 NetworkManager[1274]: <info>  [1753891873.3381] device (wlp0s20f0u6): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jul 30 18:11:13 pekolatitude5390 mtp-probe[85070]: checking bus 2, device 21: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-6"
Jul 30 18:11:13 pekolatitude5390 mtp-probe[85070]: bus: 2, device: 21 was not an MTP device
Jul 30 18:11:13 pekolatitude5390 NetworkManager[1274]: <info>  [1753891873.9499] device (wlp0s20f0u6): set-hw-addr: set MAC address to 12:FF:45:48:38:16 (scanning)
Jul 30 18:11:14 pekolatitude5390 ModemManager[1230]: <wrn> [plugin-manager] task 25: port context already scheduled
Jul 30 18:11:14 pekolatitude5390 NetworkManager[1274]: <info>  [1753891874.5624] device (wlp0s20f0u6): supplicant interface state: internal-starting -> disconnected
Jul 30 18:11:14 pekolatitude5390 NetworkManager[1274]: <info>  [1753891874.5626] device (wlp0s20f0u6): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Jul 30 18:11:17 pekolatitude5390 ModemManager[1230]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb2/2-6': not supported by any plugin
Jul 30 18:11:18 pekolatitude5390 systemd[1]: systemd-rfkill.service: Deactivated successfully.
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
Jul 30 18:11:20 pekolatitude5390 systemd[39780]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.

Alles anzeigen

kope96 · 30. Juli 2025

Zitat von JSC

Anwendungsstarter ->Systemsteinstellungen -> Wlan & Internet

Das hatte ich schon probiert, aber den Adapter nicht "sehen" können.

kope96 · 30. Juli 2025

Vielen Dank schon einmal für die Antworten/Nachfragen. Ich vermute, dass der Adapter schon funktioniert. Wenn ich in der Kontrollleiste auf das WLan-Symbol klicke sehe ich zwei Verbindungen zu meinem Netzwerk. Die eine "wlp2sO" und die andere "wlp0s20f0u6". Letztere habe ich aktiviert, die Verbindung zum Netz steht und der Adapter blinkt grün.

einrichtung eines wlan usb-stick: tp-link archer t3u plus

X11-Session verschwindet bald endgültig aus KDE

Keine Bildwiedergabe VLC etc.

Snapshot 07/2026: Videos aussortieren mit Go

Office-News: Launch der Version 1.0 durch Euro-Office :: begleitet durch heftige Kontroversen

Root-Attacke gegen Ivanti Endpoint Manager Mobile

rh5

T. Pietsch

mjacobs

psaueressig

TheMortal2024

Teilen