Done! https://bugzilla.opensuse.org/show_bug.cgi?id=1261536
(Remember, just because I submitted a bug report doesn’t mean I’m no longer a noob.
)
Done! https://bugzilla.opensuse.org/show_bug.cgi?id=1261536
(Remember, just because I submitted a bug report doesn’t mean I’m no longer a noob.
)
I have the Intel Wi-Fi 6 AX200(2*2 ax) card.
Sure, see below.
advait@localhost:~> inxi -N
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
advait@localhost:~>
Interesting, AX200 here works just fine with kernel <= 6.19.11.
Interesting, AX200 here works just fine with kernel <= 6.19.11.
OK. Any ideas why 6.19.10 would cause my wifi to break?
Kernel 6.19.10 contains several wifi-related commits, but I have no idea (one has to bisect the kernel). Does kernel 7.0 rc6 from https://download.opensuse.org/repositories/Kernel:/HEAD/standard/ solve the issue?
Interesting, AX200 here works just fine with kernel <= 6.19.11.
I can confirm no issues on 6.18-6.19 kernels with AX201
I don’t know if it might be related, but snapshot 20260404 includes:
==== kernel-firmware-iwlwifi ====
Version update (20260317 -> 20260331)
- Update to version 20260331 (git commit 441bcf2eaa2a):
* iwlwifi: add Bz/Sc FW for core103-40 release
* iwlwifi: Add Hr/Gf firmware for core103-40 release
* iwlwifi: update ty/So/Ma firmwares for core103-40 release
Yes, thanks, I just saw this in the release notes. My simple-minded noob response is “Try it and see what happens!” ![]()
I’ll report back.
I ran sudo zypper dup and installed the updates ( 2.83GB! ). That was about half hour ago and my wifi is working fine. Looks like this update fixed whatever wifi bug was there.
Nice.
Yeah, this sounds like a kernel regression, not something you did wrong. If WiFi works again after rolling back to 6.19.5, then your hardware and setup are fine, it’s just the newer kernel in openSUSE Tumbleweed that likely broke something in the WiFi driver. When you see “adapter present but no networks found”, that usually means the driver loaded but scanning isn’t working properly anymore.
Staying on the older snapshot is honestly the right call for now until a fix lands in a newer update.
Make sure that your Wi-Fi is locked so anytime you update the Wi-Fi still work
"[quote=“yahya3322, post:33, topic:192954, full:true”]
Make sure that your Wi-Fi is locked so anytime you update the Wi-Fi still work
[/quote]
"
You mean run this before update? (sudo zypper dup)
sudo rfkill block (number)
I mean it’s like
sudo zypper addlock <driver_name>
And to check write:
zypper locks
sudo zypper addlock <driver_name>
How do I find the “driver name” of my Wifi adapter? Or I guess it would be the name of the Wifi driver?
By this I do it and it successes
lspci -k | grep -A 3 -i network
Try it!
I mean it’s like
sudo zypper addlock <driver_name>
And to check write:
zypper locks
My intuition is to not block updates to iwlwifi because I don’t want to miss bug fixes and security updates. Also I think dependencies can change. If an update breaks my wifi, I’ve learned that I can easily rollback to a good snapshot and quickly be back working. Then I just wait a few days until a new update fixes the issue.
I’m a Linux noob, so let me know if that sounds ok or not. I like learning new things about Linux. Others are welcome to chime in.
@invalid_user_name You are correct in your assessment. Locking packages without need is often contraproductive and backfires spectacularly. Unfortunatley, package locks are often randomly recommended without basic knowledge.
Your “intuition” is the right approach. Properly update your system and ONLY if you encounter issues, rollback and lock the package which caused the issues. In this way you always have an up to date system and only applied specific locks when really needed.
and ONLY if you encounter issues, rollback and lock the package which caused the issues.
My feeling is to avoid locking packages after a rollback because I’ll forget that I locked it and lose track of packages I locked. It seems that rolling back and just waiting for a fix has been successful. I’ve learned how browse update details to see if the effected package has been updated.
But I’m a noob so feel free to share deeper knowledge.
Ok I dont know if it’s good to lock or know but I think you must know what is the Wi-Fi card name and model and after you know insure that the driver is the true one for your model and if not installed install it. Im not a pro especially in Wi-Fi problems band I was just facing a speed problem
5 KiB/s . See how to solve it and tell us to avoid this problem