Does your old adapter work under Leap 16.0?
I tried that, too, but unfortunately not.
Old adapter: I tried that, too, but unfortunately not.
Terminal output: I didn’t know that the output would be the same on eighter system, regardless which OS I’m running (stupid), sorry.
So voilà the output in Mint:
philipp@Philipps-Linux-PC:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 054c:0cef Sony Corp. MRW-G1
Bus 001 Device 003: ID 2109:2813 VIA Labs, Inc. VL813 Hub
Bus 001 Device 005: ID 2109:2813 VIA Labs, Inc. VL813 Hub
Bus 001 Device 006: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless rechargeable vertical mouse [More&Better]
Bus 001 Device 007: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 001 Device 008: ID 2516:0051 Cooler Master Co., Ltd. AMD SR4 lamplight Control
Bus 001 Device 009: ID 1532:02a1 Razer USA, Ltd Razer Ornata V3
Bus 001 Device 010: ID 0b05:184c ASUSTek Computer, Inc. 802.11ac NIC
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 054c:0cf0 Sony Corp. MRW-G1
Bus 002 Device 003: ID 2109:0813 VIA Labs, Inc. VL813 Hub
Bus 002 Device 004: ID 2109:0813 VIA Labs, Inc. VL813 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
philipp@Philipps-Linux-PC:~$
Thank you!
Please:
take off the USB-Wlan Stick, open a terminal and as root:
journalctl -f
Now put in the Wlan-USB-Stick and poste here all new lines in the journal terminal window.
Also post:
ip a
The execution of the command
sudo journalctl -f
in Mint took like hours including output of some red marked errors.
It endet with the line
(…) systemd[1]: anacron.service: Deactivaated sucessfully.
After 10 Minutes I cut the process off by terminating the terminal.
At the moment I try the same running Leap 16. Its already working since 10 Minutes.
It also says in red colour that Shared.Object files could not be opened (pam_fprintd.so and pam_pkcs11.so).
journalctl -f means:
All important events are shown here in realtime.
so put in your USB-Wlan-Stick and you will get some entries there.
These entries are what I want to see.
From Leap, not from Mint.
After waiting another 15 minutes, the command already showed 71 lines (with Wi-Fi adapter disconnected). Again, it’ still working adding some lines every 2-5 minutes.
I spend hours with that distro and still didn’t get anywhere. Having no time at the moment, I’ll stick with Mint (or even switch to Zorin as my wife uses this one) for now.
Maybe I’ll get back to openSuse some time in the future.
Thank you for your replies!!!
And sorry, I tried…
Philipp
Me again,
having some time on Sunday, I tried another installation of openSuse Leap 16. The problem with the Wi-Fi is already present in the installation manager (error message).
But I didn’t get the hint right that journalctl -f means that all events are shown in realtime - I though the list will end some time, sorry.
I removed and put in the adapter several times while running
lournalctl -f
so that’s what I got:
Jan 19 07:58:17 localhost.localdomain plasmashell[2210]: org.kde.plasma.nm.libs: Wireless scan on “wlp3s0f0u4” failed: “Scanning not allowed while unavailable”
Jan 19 07:58:17 localhost.localdomain systemsettings[3252]: org.kde.plasma.nm.libs: Wireless scan on “wlp3s0f0u4” failed: “Scanning not allowed while unavailable”
Jan 19 07:58:17 localhost.localdomain systemsettings[3252]: org.kde.plasma.nm.libs: Wireless scan on “wlp3s0f0u4” failed: “Scanning not allowed while unavailable”
Jan 19 08:00:41 localhost.localdomain systemsettings[3252]: org.kde.plasma.nm.libs: Wireless scan on “wlp3s0f0u4” failed: “Scanning not allowed while unavailable”
Jan 19 08:00:41 localhost.localdomain plasmashell[2210]: org.kde.plasma.nm.libs: Wireless scan on “wlp3s0f0u4” failed: “Scanning not allowed while unavailable”
Jan 19 08:01:00 localhost.localdomain DiscoverNotifier[2522]: AppStreamIntegration: No distro component found for “org.opensuse.opensuse-leap”
Jan 19 08:07:54 localhost.localdomain plasmashell[2210]: org.kde.plasma.nm.libs: Wireless scan on “wlp3s0f0u4” failed: “Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.”
Does that help?
Sorry, I’m still a linux beginner an in the team EIFOK error in front of keyboard.
Mint 22.3 looks very nice but I’m still interested in openSuse.
Thank you for your patience.
And I forgot:
ip a
gives back:
Philipp@localhost:~> 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: enp34s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:d8:61:d7:bc:a5 brd ff:ff:ff:ff:ff:ff
altname enx00d861d7bca5
3: wlp3s0f0u4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether a6:a4:f0:2c:ed:0e brd ff:ff:ff:ff:ff:ff permaddr cc:28:aa:71:ad:f7
altname wlxcc28aa71adf7
Philipp@localhost:~>
Hi Philipp!
I had the exact same issue. It turns out that when the system is laggy (like in your case with nomodeset), the KWallet (password manager) times out and creates a “broken” connection profile that keeps looping.
Try these steps in this specific order:
-
Delete the connection: Go to your Wi-Fi settings, right-click your network, and select “Forget” (or delete it). This is important to clear any “stale” settings.
-
Disable KWallet: Go to System Settings → KDE Wallet and uncheck “Enable the KDE wallet subsystem” . Click Apply.
-
Try again: Now try to connect to your Wi-Fi (or even a mobile hotspot) as if it were the first time.
By disabling the wallet and starting with a “fresh” connection, you bypass the GUI bug that causes the loop.
If it still fails, the terminal command nmcli dev wifi connect “SSID” password “PASSWORD” is your best friend to get online or try with a XFCE interface.
Good luck!
Source: Tumbleweed Install Issues (Wi-Fi/Plasma/Snapper) - Qualcomm QCA9377 - #13 by rafaelj3d
Thank you!
I already found that elsewhere and tried several times (5 Minutes ago again) but - nope, not even with that command line.
I might have found another reason:
I didn’t mention so far, that I use a Wi-Fi repeater (dual band).
On my smartphone, when I connect that repeater, it says it’s on 5 GHz (don’t know how to check that in Mint).
In openSuse in the settings (SSID) it says 2.4 GHz???
You may check your wifi router to allow enter new devices the network.
That is probably not the problem since I bought the repeater alongside with the Wi-Fi adapter. Every single device I connected with it hat no problem at all.
I did just a check on my kitchen lap, running kalpa and so kde.
It is usually conected via ethernet-cable. I tried setting up wifi and observed the behaviour you described.
Answer #30 gave the solution here:
Too often one forgets to push the confirmation button in lower right hand corner.
1 Like
Thank you. I did double check that KWallet is disabled. That’s unfortunately not the reason for the mess.
Anything interesting in my post about the output of
lournalctl -f
Any other suggestions?
Thank you!
Philipp
You have not posted the journal after putting the Stick in, you have waited too long.
Here my from openSUSE kernel not supported Stick:
Jan 23 14:54:44 linux64 plasmashell[207902]: qml: saving cacheKey = cache_23157dee2a968675843035bbd5aec016
Jan 23 14:55:26 linux64 kernel: usb 3-1.3: new high-speed USB device number 11 using xhci_hcd
Jan 23 14:55:27 linux64 kernel: usb 3-1.3: New USB device found, idVendor=2357, idProduct=011e, bcdDevice= 2.00
Jan 23 14:55:27 linux64 kernel: usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 23 14:55:27 linux64 kernel: usb 3-1.3: Product: 802.11ac WLAN Adapter
Jan 23 14:55:27 linux64 kernel: usb 3-1.3: Manufacturer: Realtek
Jan 23 14:55:27 linux64 kernel: usb 3-1.3: SerialNumber: 00e04c000001
I tried again. In fact the only new line is:
Jan 23 15:44:04 localhost.localdomain plasmashell[2222]: org.kde.plasma.nm.libs: Wireless scan on "wlp3s0f0u4" failed: "Scanning not allowed while unavailable"
It shows up after a minute or so after putting in the adapter.
I waited some more minutes but nothing more appeared (unless of course I did interact with the computer in some way).
Here is also the ip a result:
Philipp@localhost:~> 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: enp34s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:d8:61:d7:bc:a5 brd ff:ff:ff:ff:ff:ff
altname enx00d861d7bca5
5: wlp3s0f0u4: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether cc:28:aa:71:ad:f7 brd ff:ff:ff:ff:ff:ff
altname wlxcc28aa71adf7
Philipp@localhost:~>
Generally when changing anything in the Wi-Fi settings the computer stops accepting any input for a few secounds, while sometimes (not all the time) the CPU cooler prepares for takeoff.
Something which never happens while using Mint or Ubuntu.
Ok, sorry, it found that hint:
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
in the text, so I added “sudo” to the command (was that correct?) and then i got tons of output:
Jan 23 16:22:48 localhost.localdomain kernel: usb 1-4: new high-speed USB device number 9 using xhci_hcd
Jan 23 16:22:48 localhost.localdomain kernel: usb 1-4: New USB device found, idVendor=0b05, idProduct=184c, bcdDevice= 2.10
Jan 23 16:22:48 localhost.localdomain kernel: usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 23 16:22:48 localhost.localdomain kernel: usb 1-4: Product: 802.11ac NIC
Jan 23 16:22:48 localhost.localdomain kernel: usb 1-4: Manufacturer: Realtek
Jan 23 16:22:48 localhost.localdomain kernel: usb 1-4: SerialNumber: 123456
Jan 23 16:22:48 localhost.localdomain kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Jan 23 16:22:48 localhost.localdomain kernel: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Jan 23 16:22:48 localhost.localdomain kernel: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
Jan 23 16:22:48 localhost.localdomain kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Jan 23 16:22:48 localhost.localdomain kernel: cfg80211: failed to load regulatory.db
Jan 23 16:22:48 localhost.localdomain kernel: rtw_8822bu 1-4:1.0: Firmware version 27.2.0, H2C version 13
Jan 23 16:23:03 localhost.localdomain kernel: usb 1-4: USB disconnect, device number 9
Jan 23 16:23:03 localhost.localdomain kernel: rtw_8822bu 1-4:1.0: write register 0xc4 failed with -71
Jan 23 16:23:03 localhost.localdomain kernel: usbcore: registered new interface driver rtw_8822bu
following some 50 more lines. I don’t know which ones are important, but this sounds interesting:
Jan 23 16:24:41 localhost.localdomain systemd[1]: packagekit.service: Deactivated successfully.
Jan 23 16:24:45 localhost.localdomain NetworkManager[1437]: <warn> [1769181885.9936] device (wlp3s0f0u4): Activation: (wifi) association took too long, failing activation
Jan 23 16:24:45 localhost.localdomain NetworkManager[1437]: <info> [1769181885.9937] device (wlp3s0f0u4): state change: config -> failed (reason 'ssid-not-found', managed-type: 'full')
Does that help?
I asked my offline AI, that’s what it says:
"openai/gpt-oss-20b
Thought for 6.91 seconds
Short answer
The adapter is detected and the driver loads, but it never gets a signal – NetworkManager keeps timing‑out with “ssid‑not‑found”.
On openSUSE Leap 16.x this is almost always caused by a missing firmware package for the Realtek 8822BU.
Installing the firmware-realtek (or rtl88xxau) package and rebooting fixes the problem."
Little addendum, I stand what I said at #34 but found the security setting prefilled with wpa3, no connection was established, changing it to wpa2 did it.
The bottom bar widget shows security-type wpa 3.
So, you may just check automagically prefilled settings.