I’m currently on 20240801 snapshot and if I update, connection becomes unstable. E.g. you lose connection for like one second once in ~5 minutes.
How are you upgrading Tumbleweed you are not supposed to ‘update’ Tumbleweed as with Leap? I recently read this thread https://www.linuxquestions.org/questions/suse-opensuse-60/tumbleweed-upgrade-4175734592/ and it helped me understand some things about Tumbleweed and using zupper dup.
Thanks
My problem is not exactly like yours but it is similar. Sometimes (not all the time), my Wi-Fi would potentially drop and Tumbleweed would ask me for the password again but then I would go to Wi-Fi settings and connect it again which would end up working fine again. I don’t know what causes this issue.
Always zypper dup. Today I even tried updating thought discover.
Oh, and I rollback to working snapshot.
Post Info’s?
inxi -F
or
/sbin/lspci -nnk | grep -iA3 net
or
lsusb
to see what Wlan you use.
Link to gist
You could copy/paste it here to the Forum using Code-Tags:
Code-Tags
Post:
zypper lr -d
zypper se -si rtw89
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+--------------------------------------+----------------------------------------+---------+-----------+---------+----------+--------+---------------------------------------------------------------------------------+--------
1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
2 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
3 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
4 | https-download.opensuse.org-27a56efa | openSUSE:Tumbleweed | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ |
5 | https-download.opensuse.org-d7dea8a6 | openSUSE:Tumbleweed | Yes | (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/tumbleweed/repo/oss/ |
6 | openSUSE-20240725-0 | openSUSE-20240725-0 | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
7 | packman | Packman | No | ---- | ---- | 70 | rpm-md | https://mirror.karneval.cz/pub/linux/packman//suse/openSUSE_Tumbleweed/ |
8 | packman-essentials | packman-essentials | Yes | (r ) Yes | No | 90 | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/Essentials/ |
9 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/debug/tumbleweed/repo/oss/ |
10 | repo-openh264 | Open H.264 Codec (openSUSE Tumbleweed) | Yes | (r ) Yes | Yes | 95 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed |
11 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | 99 | N/A | http://download.opensuse.org/source/tumbleweed/repo/oss/ |
12 | vscode | vscode | Yes | (r ) Yes | No | 90 | rpm-md | https://packages.microsoft.com/yumrepos/vscode |
Loading repository data...
Reading installed packages...
No matching items found.
You could try the options from here:
or use the options in the 70-rtw89.conf file.
Otherwise open an bugreport.
Remind me I should put 70-rtw89.conf file in /etc/modprobe.d/*?
Yes in /etc/modprobe.d/
No luck either.
70-rtw89.conf gave to result.
Build of rtw89 fails with
/home/local/git/rtw89/phy.c:399:23: error: ‘struct ieee80211_sta’ has no member named ‘vht_cap’
399 | } else if (sta->vht_cap.vht_supported) {
And I don’t see any stable branch to check.
Tried to install rtw89-kmp-default from hardware repo with breaking of deps(I have no idea what ksym means).
You could try the both rtw89 packages from this Repo:
https://download.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Tumbleweed/
I patched them today and now you could test them.
If secure boot is enabled:
restart and:
Mok Example
Does not build and does not work for Tumbleweed, see my last post.
So test my build and I will send it to the hardware Repo.
Give me some time to make sure that everything is fine.
Secure boot disabled.
I only read this repo list and saw the following.
#2 is your Tumbleweed OSS repo, but #5 and #6 point to the same URL, thus they are superfluous (not only confusing for me, but also for the system).
I have no idea what #4 is, but I assume that it is also superfluous. I assume that both those with the strange codes in the Alias are the result of some 1-click installation.
And when you have Packman, you do not need Packman-Essentials, because the latter is a subset of the first.
Packman repo disabled.
Well. No difference. I used ping to catch cases when I lose connection.
With rtw89
╰─○ ping -D -i 5 google.com
PING google.com (142.250.75.14) 56(84) bytes of data.
[1723718469.308134] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=1 ttl=115 time=99.9 ms
[1723718474.225339] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=2 ttl=115 time=25.0 ms
[1723718479.317405] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=3 ttl=115 time=112 ms
[1723718490.611339] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=5 ttl=115 time=1268 ms
[1723718494.374584] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=6 ttl=115 time=26.5 ms
[1723718499.405438] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=7 ttl=115 time=55.1 ms
[1723718504.373783] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=8 ttl=115 time=20.2 ms
[1723718509.380144] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=9 ttl=115 time=21.3 ms
[1723718521.027392] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=11 ttl=115 time=1604 ms
[1723718524.493460] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=12 ttl=115 time=66.6 ms
[1723718529.454142] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=13 ttl=115 time=21.7 ms
[1723718543.629313] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=14 ttl=115 time=9192 ms # Here it
[1723718544.499507] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=16 ttl=115 time=21.3 ms
[1723718549.581777] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=17 ttl=115 time=98.2 ms
[1723718554.511171] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=18 ttl=115 time=22.4 ms
[1723718559.617299] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=19 ttl=115 time=123 ms
[1723718569.577779] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=21 ttl=115 time=24.2 ms
[1723718580.320346] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=23 ttl=115 time=737 ms
[1723718584.611363] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=24 ttl=115 time=23.7 ms
[1723718599.870996] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=27 ttl=115 time=20.7 ms
[1723718611.636371] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=29 ttl=115 time=1762 ms
[1723718615.015573] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=30 ttl=115 time=139 ms
[1723718620.500278] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=31 ttl=115 time=620 ms
[1723718635.189736] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=34 ttl=115 time=142 ms
[1723718640.104870] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=35 ttl=115 time=52.2 ms
[1723718645.122589] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=36 ttl=115 time=65.6 ms
[1723718658.189121] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=37 ttl=115 time=8127 ms # Again
[1723718660.127967] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=39 ttl=115 time=21.9 ms
I rollback and used ping too
ping -D -i 5 google.com
PING google.com (142.250.75.14) 56(84) bytes of data.
[1723718838.857724] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=1 ttl=115 time=184 ms
[1723718843.694019] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=2 ttl=115 time=24.4 ms
[1723718848.797855] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=3 ttl=115 time=125 ms
[1723718853.700112] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=4 ttl=115 time=26.3 ms
[1723718858.731165] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=5 ttl=115 time=55.1 ms
[1723718863.762432] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=6 ttl=115 time=83.1 ms
[1723718868.706757] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=7 ttl=115 time=23.4 ms
[1723718873.785620] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=8 ttl=115 time=99.4 ms
[1723718878.804528] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=9 ttl=115 time=114 ms
[1723718883.820421] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=10 ttl=115 time=125 ms
[1723718888.838360] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=11 ttl=115 time=137 ms
[1723718893.733234] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=12 ttl=115 time=26.9 ms
[1723718898.874177] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=13 ttl=115 time=164 ms
[1723718903.789482] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=14 ttl=115 time=74.4 ms
[1723718908.808432] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=15 ttl=115 time=87.9 ms
[1723718913.825343] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=16 ttl=115 time=98.9 ms
[1723718918.851921] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=17 ttl=115 time=120 ms
[1723718923.848661] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=18 ttl=115 time=111 ms
[1723718928.850432] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=19 ttl=115 time=107 ms
[1723718933.776445] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=20 ttl=115 time=26.8 ms
[1723718938.808825] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=21 ttl=115 time=53.5 ms
[1723718943.826902] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=22 ttl=115 time=66.2 ms
[1723718948.876121] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=23 ttl=115 time=110 ms
[1723718953.829364] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=24 ttl=115 time=58.2 ms
[1723718958.878238] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=25 ttl=115 time=102 ms
[1723718963.896065] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=26 ttl=115 time=115 ms
[1723718968.914641] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=27 ttl=115 time=127 ms
[1723718973.932238] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=28 ttl=115 time=139 ms
[1723718978.949164] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=29 ttl=115 time=151 ms
[1723718983.966735] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=30 ttl=115 time=163 ms
[1723718988.852533] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=31 ttl=115 time=43.6 ms
[1723718993.899747] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=32 ttl=115 time=85.3 ms
[1723718998.917355] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=33 ttl=115 time=97.6 ms
[1723719003.848120] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=34 ttl=115 time=22.8 ms
[1723719008.855695] 64 bytes from waw07s03-in-f14.1e100.net (142.250.75.14): icmp_seq=35 ttl=115 time=24.5 ms
After the latest zypper dup my Wi-Fi connection dropped dramatically in speed, I’m talking 1.7Gbps down/1Gbps up before, 150Mbps up/down now.
Intel AX210.
Is there was a new snapshot release? I tried installing rtw89 + blacklisting and only after that I updated again. See on issue with ping or etc.
Thanks @Sauerland for help.