In opensuse 16.0 Leap Fritz WLAN Adapter AC 860 nicht installiert

Deutsch (German) Netzwerk
1

Nach Update auf opensuse 16.0 Leap wird Fritz WLAN Adapter AC 860 nicht installiert.
lsusb liefert, das der Adaper am USB-Port erkannt wird:

stephweb@Weber-PC1:~> lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 004 Device 003: ID 057c:8503 AVM GmbH FRITZ!WLAN AC 860
Bus 004 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
stephweb@Weber-PC1:~>

Allerdings lsusb -v | grep -i Realtek (oder MediaTek) liefert leider keine Ausgabe:

stephweb@Weber-PC1:~> lsusb -v | grep -i Realtek
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing

kernel-firmware-realtek wurde von mir probeweise noch installier, allerdings kein Ergebnis!
Was tun?
Meinen Dank an Euch vielmals vorab!

2

kernel-firmware-mediatek ist installiert?

Und nebenbei bitte noch das Ergebnis von

modprobe -c | frep -Ei "057c.*8503"

hier vorführen. Ausgeführt als Root.

3

Damit ist warscheinlich grep gemeint.

1 Like
4

Ja sicher. Danke für den Hinweis.
Hier jetzt berichtigt:

 modprobe -c | grep -Ei "057c.*8503"
5

Hallo,
kernel-firmware-mediatek ist ebenfalls installiert.
Ansonsten hier noch das:

stephweb@Weber-PC1:~> sudo modprobe -c | grep -Ei "057c.*8503"
alias usb:v057Cp8503d*dc*dsc*dp*ic*isc*ip*in* mt76x2u
6

Wie kommst eigentlich darauf? Alles spricht dafür, dass der W-LAN-Adapter erkannt/„installiert“ wurde.
Liegt eventuell ein anderes Problem vor (zum Beispiel keine Verbindung zum Router oder Internet)? Dann solltest du deine Angaben besser formulieren.

7

Poste mal:
rfkill list all
und
ip a

8

Here it is:

stephweb@Weber-PC1:~> sudo rfkill list all
stephweb@Weber-PC1:~> ip a
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
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 74:d4:35:09:ac:b4 brd ff:ff:ff:ff:ff:ff
    altname enp3s0
    altname enx74d43509acb4
    inet 192.168.0.206/24 brd 192.168.0.255 scope global dynamic noprefixroute eth0
       valid_lft 604486sec preferred_lft 604486sec
    inet6 fe80::76d4:35ff:fe09:acb4/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
stephweb@Weber-PC1:~>

Für den ersten Befehl leider keine Ausgabe!
Meinen Dank vielmals vorab!

9

Als root ausfüheren und hier posten:

journalctl -b | grep -Ei 'mt76|network|firmware|error|wlan'
10

Hier ist es:

stephweb@Weber-PC1:~> sudo journalctl -b | grep -Ei 'mt76|network|firmware|error|wlan'
[sudo] Passwort für root: 
Feb 27 15:21:33 localhost kernel: Spectre V2 : Enabling Speculation Barrier for firmware calls
Feb 27 15:21:33 localhost kernel: Relocating firmware framebuffer to offset 0x0000000001000000[d] within [mem 0xd8000000-0xd9ffffff flags 0x14220c]
Feb 27 15:21:33 localhost kernel: drop_monitor: Initializing network drop monitor service
Feb 27 15:21:33 localhost kernel: RAS: Correctable Errors collector initialized.
Feb 27 15:21:33 localhost kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:33 localhost systemd-vconsole-setup[274]: /usr/bin/setfont failed with a "system error" (EX_OSERR), ignoring.
Feb 27 15:21:33 localhost systemd-vconsole-setup[281]: setfont: ERROR kdfontop.c:212 put_font_kdfontop: Unable to load such font with such kernel version
Feb 27 15:21:34 localhost systemd-vconsole-setup[486]: setfont: ERROR kdfontop.c:212 put_font_kdfontop: Unable to load such font with such kernel version
Feb 27 15:21:34 localhost systemd-vconsole-setup[468]: /usr/bin/setfont failed with a "system error" (EX_OSERR), ignoring.
Feb 27 15:21:35 localhost kernel: usb 5-1.1: Product: FRITZ!WLAN AC 860
Feb 27 15:21:35 localhost kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:37 localhost kernel: SELinux:  policy capability network_peer_controls=1
Feb 27 15:21:37 localhost kernel: SELinux:  policy capability always_check_network=0
Feb 27 15:21:37 localhost systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
Feb 27 15:21:37 localhost systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
Feb 27 15:21:37 localhost systemd[1]: Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
Feb 27 15:21:38 localhost kernel: mt76x2u 5-1.1:1.0: ASIC revision: 76120044
Feb 27 15:21:38 localhost kernel: mt76x2u 5-1.1:1.0: ROM patch build: 20141115060606a
Feb 27 15:21:39 localhost avahi-daemon[859]: Network interface enumeration completed.
Feb 27 15:21:39 localhost alsactl[963]: alsa-lib main.c:1554:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2
Feb 27 15:21:39 localhost kernel: mt76x2u 5-1.1:1.0: firmware upload failed: -110
Feb 27 15:21:39 localhost systemd[1]: Reached target Preparation for Network.
Feb 27 15:21:39 localhost systemd[1]: Starting Network Manager...
Feb 27 15:21:39 localhost NetworkManager[994]: <info>  [1772202099.6973] NetworkManager (version 1.52.0) is starting... (boot:b7226de8-fd69-4e14-a023-252e6ca9e488)
Feb 27 15:21:39 localhost NetworkManager[994]: <info>  [1772202099.6975] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/conncheck-openSUSE.conf
Feb 27 15:21:39 localhost NetworkManager[994]: <info>  [1772202099.7014] manager[0x561966f4a6d0]: monitoring kernel firmware directory '/lib/firmware'.
Feb 27 15:21:39 localhost NetworkManager[994]: <info>  [1772202099.8229] hostname: hostname: using hostnamed
Feb 27 15:21:39 localhost NetworkManager[994]: <info>  [1772202099.8234] dns-mgr: init: dns=default,systemd-resolved rc-manager=netconfig (auto)
Feb 27 15:21:39 localhost NetworkManager[994]: <info>  [1772202099.8234] policy: set-hostname: set hostname to 'localhost.localdomain' (no hostname found)
Feb 27 15:21:39 localhost NetworkManager[994]: <info>  [1772202099.8237] manager[0x561966f4a6d0]: rfkill: Wi-Fi hardware radio set enabled
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8238] manager[0x561966f4a6d0]: rfkill: WWAN hardware radio set enabled
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8285] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.52.0/libnm-device-plugin-wifi.so)
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8317] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.52.0/libnm-device-plugin-wwan.so)
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8343] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.52.0/libnm-device-plugin-bluetooth.so)
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8345] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8345] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8346] manager: Networking is enabled by state file
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8351] settings: Loaded settings plugin: keyfile (internal)
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8369] dhcp: init: Using DHCP client 'internal'
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8372] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8383] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8387] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8393] device (lo): Activation: starting connection 'lo' (595c845e-be47-469b-bed6-0a978f636ae2)
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8401] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Feb 27 15:21:39 localhost.localdomain NetworkManager[994]: <info>  [1772202099.8404] device (eth0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Feb 27 15:21:39 localhost.localdomain systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 27 15:21:39 localhost.localdomain systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 27 15:21:39 localhost.localdomain dns-dnsmasq.sh[1039]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Feb 27 15:21:40 localhost.localdomain systemd[1]: Started Network Manager.
Feb 27 15:21:40 localhost.localdomain NetworkManager[994]: <info>  [1772202100.0674] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Feb 27 15:21:40 localhost.localdomain NetworkManager[994]: <info>  [1772202100.0683] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Feb 27 15:21:40 localhost.localdomain NetworkManager[994]: <info>  [1772202100.0684] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')
Feb 27 15:21:40 localhost.localdomain NetworkManager[994]: <info>  [1772202100.0686] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')
Feb 27 15:21:40 localhost.localdomain systemd[1]: Reached target Network.
Feb 27 15:21:40 localhost.localdomain NetworkManager[994]: <info>  [1772202100.0690] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Feb 27 15:21:40 localhost.localdomain NetworkManager[994]: <info>  [1772202100.0713] modem-manager: ModemManager available
Feb 27 15:21:40 localhost.localdomain dns-dnsmasq.sh[1069]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Feb 27 15:21:40 localhost.localdomain dns-dnsmasq.sh[1087]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Feb 27 15:21:40 localhost.localdomain NetworkManager[994]: <info>  [1772202100.1342] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Feb 27 15:21:40 localhost.localdomain NetworkManager[994]: <info>  [1772202100.1345] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Feb 27 15:21:40 localhost.localdomain NetworkManager[994]: <info>  [1772202100.1351] policy: set-hostname: set hostname to 'localhost.localdomain' (no hostname found)
Feb 27 15:21:40 localhost.localdomain NetworkManager[994]: <info>  [1772202100.1351] device (lo): Activation: successful, device activated.
Feb 27 15:21:40 localhost.localdomain dns-dnsmasq.sh[1114]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Feb 27 15:21:40 localhost.localdomain dns-dnsmasq.sh[1130]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Feb 27 15:21:40 localhost.localdomain kernel: mt76x2u 5-1.1:1.0: probe with driver mt76x2u failed with error -5
Feb 27 15:21:40 localhost.localdomain kernel: usbcore: registered new interface driver mt76x2u
Feb 27 15:21:41 localhost.localdomain systemd[1]: Startup finished in 15.869s (firmware) + 4.595s (loader) + 830ms (kernel) + 2.468s (initrd) + 5.108s (userspace) = 28.871s.
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.6802] device (eth0): carrier: link connected
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.6806] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.6812] policy: auto-activating connection 'eth0' (7ba00b1d-8cdd-30da-91ad-bb83ed4f7474)
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.6816] device (eth0): Activation: starting connection 'eth0' (7ba00b1d-8cdd-30da-91ad-bb83ed4f7474)
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.6816] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.6818] manager: NetworkManager state is now CONNECTING
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.6819] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.7855] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.7862] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.8150] dhcp4 (eth0): state changed new lease, address=192.168.0.206, acd pending
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.9688] dhcp4 (eth0): state changed new lease, address=192.168.0.206
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.9703] policy: set 'eth0' (eth0) as default for IPv4 routing and DNS
Feb 27 15:21:42 localhost.localdomain NetworkManager[994]: <info>  [1772202102.9709] policy: set-hostname: set hostname to 'Weber-PC1' (from DHCPv4)
Feb 27 15:21:43 Weber-PC1 NetworkManager[994]: <info>  [1772202103.1231] device (eth0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Feb 27 15:21:43 Weber-PC1 dns-dnsmasq.sh[1530]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Feb 27 15:21:43 Weber-PC1 dns-dnsmasq.sh[1548]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Feb 27 15:21:43 Weber-PC1 NetworkManager[994]: <info>  [1772202103.2124] device (eth0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Feb 27 15:21:43 Weber-PC1 NetworkManager[994]: <info>  [1772202103.2130] device (eth0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Feb 27 15:21:43 Weber-PC1 NetworkManager[994]: <info>  [1772202103.2138] manager: NetworkManager state is now CONNECTED_SITE
Feb 27 15:21:43 Weber-PC1 NetworkManager[994]: <info>  [1772202103.2143] device (eth0): Activation: successful, device activated.
Feb 27 15:21:43 Weber-PC1 NetworkManager[994]: <info>  [1772202103.2160] manager: startup complete
Feb 27 15:21:43 Weber-PC1 dns-dnsmasq.sh[1576]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Feb 27 15:21:43 Weber-PC1 dns-dnsmasq.sh[1597]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Feb 27 15:21:43 Weber-PC1 NetworkManager[994]: <info>  [1772202103.3423] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 27 15:21:43 Weber-PC1 dns-dnsmasq.sh[1626]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Feb 27 15:21:43 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:43 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:43 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:43 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:43 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:43 Weber-PC1 NetworkManager[994]: <info>  [1772202103.7932] agent-manager: agent[a0087a35b06fa288,:1.25/org.kde.plasma.networkmanagement/1000]: agent registered
Feb 27 15:21:44 Weber-PC1 kded6[1437]: kf.bluezqt: PendingCall Error: "Could not activate remote peer 'org.bluez': unit failed"
Feb 27 15:21:44 Weber-PC1 kscreen_backend_launcher[1698]: kscreen.xcb.helper: Event Error:  147
Feb 27 15:21:44 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:44 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:44 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:44 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:44 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:44 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:44 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:44 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:44 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:44 Weber-PC1 kernel: PM: hibernation: The secret key is invalid. It can be regenerated through /sys/firmware/efi/secret-key/regen
Feb 27 15:21:45 Weber-PC1 org_kde_powerdevil[1727]: Error(s) opening ddc devices
Feb 27 15:21:45 Weber-PC1 org_kde_powerdevil[1727]: Error EACCES(-13): Keine Berechtigung opening /dev/i2c-12
Feb 27 15:21:45 Weber-PC1 org_kde_powerdevil[1727]: [  1727] Error(s) opening ddc devices
Feb 27 15:21:45 Weber-PC1 org_kde_powerdevil[1727]: [  1727] Error EACCES(-13): Keine Berechtigung opening /dev/i2c-12
Feb 27 15:21:45 Weber-PC1 systemd[1]: Starting Network Manager Wait Online...
Feb 27 15:21:46 Weber-PC1 systemd[1]: Finished Network Manager Wait Online.
Feb 27 15:21:46 Weber-PC1 systemd[1]: Reached target Network is Online.
Feb 27 15:21:53 Weber-PC1 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
stephweb@Weber-PC1:~>
11

Poste:
uname -a
zypper se -si firmware

12

Hier ist es:

stephweb@Weber-PC1:~> uname -a
Linux Weber-PC1 6.12.0-160000.25-default #1 SMP PREEMPT_DYNAMIC Fri Jan 16 09:29:05 UTC 2026 (9badd3c) x86_64 x86_64 x86_64 GNU/Linux
stephweb@Weber-PC1:~> zypper se -si firmware
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name                        | Type  | Version             | Arch   | Repository
---+-----------------------------+-------+---------------------+--------+----------------
i  | kernel-firmware-all         | Paket | 20250206-160000.3.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-amdgpu      | Paket | 20250718-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-ath10k      | Paket | 20250206-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-ath11k      | Paket | 20250424-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-ath12k      | Paket | 20250523-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-atheros     | Paket | 20250206-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-bluetooth   | Paket | 20250714-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-bnx2        | Paket | 20250627-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-brcm        | Paket | 20250623-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-chelsio     | Paket | 20250627-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-dpaa2       | Paket | 20250206-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-i915        | Paket | 20250708-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-intel       | Paket | 20250718-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-iwlwifi     | Paket | 20250609-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-liquidio    | Paket | 20250206-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-marvell     | Paket | 20250206-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-media       | Paket | 20250717-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-mediatek    | Paket | 20250708-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-mellanox    | Paket | 20250717-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-mwifiex     | Paket | 20250206-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-network     | Paket | 20250717-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-nfp         | Paket | 20250206-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-nvidia      | Paket | 20250516-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-platform    | Paket | 20250717-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-prestera    | Paket | 20250206-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-qcom        | Paket | 20250714-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-qlogic      | Paket | 20250717-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-radeon      | Paket | 20250627-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-realtek     | Paket | 20250717-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-serial      | Paket | 20250717-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-sound       | Paket | 20250721-160000.1.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-ti          | Paket | 20250206-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-ueagle      | Paket | 20250206-160000.2.2 | noarch | repo-oss (16.0)
i  | kernel-firmware-usb-network | Paket | 20250717-160000.1.2 | noarch | repo-oss (16.0)

    Hinweis: Für eine erweiterte Suche inkl. nicht momentan aktivierter Remote-Ressourcen bitte
    'zypper search-packages' verwenden.
stephweb@Weber-PC1:~>
13

Versuch es mal mit einer anderen Firmware:
als root:
zypper in -f https://download.opensuse.org/repositories/Kernel:/firmware/16.0/noarch/kernel-firmware-mediatek-20260221-lp160.1.1.noarch.rpm

Dann gibt es eine Meldung wegen fehlendem key, diese mit i ignorieren.

Stick raus, wieder rein und schauen.

Evtl. neu starten und Stick anstöpseln.

14

Hallo,
also erstmal die Device ist nun im Yast erkannt, wenngleich unter einem anderen Namen.
Dennoch erhalt ich dubioserweise keinen Zugriff aufs Internet, obgleich ein Fehler sonst nicht vorliigen sollte.
Den Network manager habe ich ausgeschaltet, weil er auch keine Lösung erzeugte und manuell im Yast konfiguriert.
Was jetzt tun?
Meinen Dank vielmals im voraus!

15

Es könnte, zumindest gemäß dem Network Manager, ein Fehler bei der Vergabe der DHCP-IP-Adresse vorliegen!

16

Poste:
ip -a

Auch das Netzwerkkabel abgezogen?

17

Hier it is:

stephweb@MrRight-PC2:~> ip -a
Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
       ip [ -force ] -batch filename
where  OBJECT := { address | addrlabel | fou | help | ila | ioam | l2tp | link |
                   macsec | maddress | monitor | mptcp | mroute | mrule |
                   neighbor | neighbour | netconf | netns | nexthop | ntable |
                   ntbl | route | rule | sr | stats | tap | tcpmetrics |
                   token | tunnel | tuntap | vrf | xfrm }
       OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |
                    -h[uman-readable] | -iec | -j[son] | -p[retty] |
                    -f[amily] { inet | inet6 | mpls | bridge | link } |
                    -4 | -6 | -M | -B | -0 |
                    -l[oops] { maximum-addr-flush-attempts } | -echo | -br[ief] |
                    -o[neline] | -t[imestamp] | -ts[hort] | -b[atch] [filename] |
                    -rc[vbuf] [size] | -n[etns] name | -N[umeric] | -a[ll] |
                    -c[olor]}
stephweb@MrRight-PC2:~>

Das Netzwerkkabel war abgezogen, ich surfe nun wieder über Kabel!

18

Mein Fehler:
ip a
ohne Kabel.

19

Hier ist es:

stephweb@MrRight-PC2:~> ip a 
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 
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 
   link/ether 74:d4:35:09:ac:b4 brd ff:ff:ff:ff:ff:ff 
   altname enp3s0 
   altname enx74d43509acb4 
3: wlp2s0u1u1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 
   link/ether 0c:72:74:72:61:ff brd ff:ff:ff:ff:ff:ff 
   altname wlx0c72747261ff 
stephweb@MrRight-PC2:~>
20

Ich würde jetzt mal mit dem Netzwerkmanager (einfacher bei Wlan) versuchen eine Verbindung herzustellen.

1 Like