Confirmed on Atheros AR816x/AR817x wired driver. 6.14.1 does not have this issue. For clarification, I cannot automatically or statically assign an IP address.
On my system (RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller) it looks like it’s not getting an IP address from dhcp
So another workaround is manually setting a know working IP address:
sudo ifconfig $yourcard $selectedIP
At least this worked for me.
I am not running it and could not test it, but thank you for that input.
Another workaround that should work is (for me anyway):
sudo dhclient wlp1s0
Ofc you replace the wlp1s0
with your own wifi connection or card. You find that out with simply running ifconfig
. I am using kernel 6.14.2-1 right now with that,
Workaround confirmed on my system. Dhcp was restored on my ethernet connection.
What do you suggest? Should we wait for a bug fix or put this workaround at session start?
I believe @bero is working on a patched kernel right now. I don’t know how long it takes to build, so you can do the workaround or just boot a previous kernel.
This has to be fixed, as @WilsonPhillips says @bero is working on this.
For me sudo ifconfig $yourcard $selectedIP
works if I use my wifi router IP. Along with the previously mentioned sudo dhclient $yourcard
. So multiple workarounds plus other kernels available.
Same thing happened to me but im on a 2.5 Gigabit LAN(RTL8125BG), it wouldn’t even work even after I tried to USB tether my phone to the system.
I see some work arounds were posted so ill try one of those.
*EDIT: sudo dhclient $yourcard worked, thanks.
Small update, I tested the 6.14.2-2 kernel build today and from my initial testing it has restored network connectivity on my machine at least, I reported my results to devs in matrix cooker chat.
I expect that after more test confirmations from the tester team it will be pushed down to ROME/Rolling as soon as that happens provided no issues are reported.
For people NOT using nvidia driver, in ROME system you can do:
sudo dnf update kernel-desktop --enablerepo=cooker-x86_64 --refresh
(replace x86_64 with znver1 if it’s your case)
Reboot
Confirmed on my Intel I7 laptop.
Had the same issue after rebooting from this update. Rolled back to Rock install.
As a data point, fortunately all is well with all of the Rome kernels on my HP Z2 Mini G3 Workstation -
[root@chad ~]# inxi -n
Network:
Device-1: Intel Ethernet I219-LM driver: e1000e
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 70:5a:0f:4a:87:41
Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi
IF: wlp2s0 state: up mac: 00:28:f8:37:d7:6e
IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
[root@chad ~]# uname -a
Linux chad 6.15.0-desktop-0.rc1.1omv2590 #1 SMP PREEMPT_DYNAMIC Wed Apr 9 23:20:24 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
[root@chad ~]#
Let me understand well:
since I use no NVIDIA driver, after having updated all except but kernel 6.14.2-1 (and also kernel-firmware ?), if I type command you indicated * sudo dnf update kernel-desktop --enable repo=cooker-x86_64 --refresh
* kernel will be installed without no more issues (Network and so on…) ?
Unless you need the znver1 instead.
sudo dnf upgrade --enablerepo=cooker-znver1 kernel-desktop --refresh
But if you can boot to the previous kernel and keep working, why not just wait?
Yes, at least that is what all reports so far are saying. Also the kernel-firmware and kernel-firmware-extra packages should be OK to upgrade. This network issue was strictly related to a specific main kernel version (kernel 6.14.2-1). Kernel 6.14.2-2 corrects the networking problem.
Edit: Or just use an older kernel like 6.13.9 and wait.
Actually, I upgraded firmware and it seems all right.
Then, I’ll wait for kernel 6.14.2-2, still continuing with 6.13.9, as I do at moment.
I guess all the other packages non yet installed, like pysides and shiboken, have dependencies on kernel 6.14.2-1.
Well, we are doing a UM right now, so whenever that is complete, all the new packages will be moved over from Cooker to ROME, so the repos are down until that is over.
For everyone waiting for the new kernel. Dinner is served.
sudo dnf clean all ; dnf clean all ; sudo dnf distro-sync --refresh --allowerasing 2>&1| tee dsync2-log.txt
Everything works perfectly now @bero and the whole OMLx team - you are great!