Latest kernel v. 6.14.2-1 update messes up wifi functions

Support
, , ,
1

Hello,

  • OpenMandriva Lx 25.04 (ROME) Rolling

  • Desktop environment KDE

After updating my OM laptop to kernel 6.14.2 the wifi stopped working well.
I tried a number of things but none worked except reverting to kernel 6.14.0.

The hardware involved (out of inxi -n):

Network:
Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
driver: ath10k_pci

So if anyone has this issue similar to me, try reverting to kernel 6.14.0 first and see if that solves it.

Hopefully the kernel update later will fix this also.

1 Like
2

I confirm this. After installing the latest Rome update, my wifi connection stopped working. Network Manager kept displaying “Setting Network Address” and never connected to my wifi network. It did connect to my mobile hotspot though.

After trying different things I rebooted into an earlier kernel version (6.13.9) and found that the connection was restored.

I have also installed 6.15.0-desktop-0.rc1.1omv2590 and that works fine too.

So the problem is with Kernel 6.14.2 (both desktop and server).

3

Output of inxi -n:

Network:
  Device-1: Realtek RTL8852AE 802.11ax PCIe Wireless Network Adapter
    driver: rtw89_8852ae
4

I am also experiencing this on 6.14.2 with my ROME/rolling desktop machine which has a 10Gbit NIC, same symptoms as @pthesh described.

I booted into the prior 6.13.9 I was running and network connectivity is restored.

I have 2 other NICs and a WiFi6 adaptor in this machine I could test (yes I know, ludicrous number of NICs in one machine :sweat_smile:), but I do not think the result will be any different with those.

It was also affecting my qemu Cooker VM when I updated it late last night.

1 Like
5

Thanks for the heads up : ) i’ll just wait then : )

1 Like
6

@Hum_Had
welcome1

We are working on the issue.

7

Can anyone confirm?

sudo dnf install kernel-rc-desktop --refresh

8

I tried the kernel-rc-desktop / 6.15.0 and it does not boot after grub selection for me.

1 Like
9

Welcome! We are happy to see you and hope you will decide to make this your home.

10

well, i thought it’ll take sometime to get my hands on a laptop… but a friend had one which he did not use, so he gave it to me and i just got sucked into configuring and installing what i needed : )
i’ve been lurking here since a while but afair posted nothing : ).

2 Likes
11

Hello,

  • OpenMandriva Lx version:
    Rome

  • Desktop environment (KDE, LXQT…):
    KDE

  • Description of the issue (screenshots if relevant):
    Internet connection fails after updating to the new kernel desktop 6.14.2 rel. 1 via Discover.

  • Relevant informations (hardware involved, software version, logs or output…):
    Motherboard ROG STRIX Z490-F GAMING

1 Like
12

Known issue. W.I.P.
Workaround: boot to previous working kernel.

4 Likes
13

Just an update to my own issue with the 6.15.0 RC kernel on my machine and @rugyada helping to triage that issue with 6.15.0 on matrix chat with some rewiring on my end to rule out kvm hardware interferences (I had some interesting display resolution configurations today on my multimonitor setup :rofl: ), after installing the desktop rc kernel and then manually running:

sudo dracut -f
sudo update-grub2

My desktop machine boots the 6.15.0 RC kernel, with that said there are other users also helping triage this on matrix who tried 6.15.0-rc without any success, it is not what I would call a fix/workaround or recommend as a fix, it is labelled RC for a reason.

The 6.14.2 kernel still has network connecting issues for my machine, no change on that front but it is being investigated and hopefully will be fixed with a revision.

I would say meantime to anyone to boot their previous working kernel version they had installed prior to 6.14.2 until this issue is figured out.

2 Likes
14

I am still on Kernel: Linux 6.13.9-desktop-3omv2590 and would recommend everyone stay there for the time being, or at least make sure you can choose to boot to it in GRUB.

2 Likes
15

Our default limit of kernels installed at one time is limited to 3. If you would like to raise that limit, you can easily do so by editing

/etc/dnf/dnf.conf

and changing the number on the line

installonly_limit=3

I changed mine to 9, but I am not worried about space.

16

I confim. We are waiting.

17

Where did you find kernel 6.14.0? I do not find it here. Are you referring to some version of kernel-rc-desktop? Like one from here?

18

We had 6.14.0 and @bero rolled us back to 6.13.9

Which leads me to this question. If Grub is set to boot to the last good kernel, when I select a previous kernel, why do I have to select it every time?

19

Kernel 6.14.2 also does not properly provide wired Ethernet functionality either. I had to roll back to Kernel 6.14.0 (I don’t have 6.13.9 for whatever reason – perhaps because I have not updated my system for a bit. :sweat_smile:).

20

I only see this behavior in VBox VM’s on hardware I am using Rock/5.0 boot-loader and it boots the last booted kernel unless I tell it otherwise. This is the /etc/default/grub for that boot-loader:

GRUB_GFXPAYLOAD_LINUX=keep
GRUB_DISABLE_RECOVERY=false
GRUB_DISTRIBUTOR="OpenMandriva Lx"
GRUB_GFXMODE=1024x768,1024x600,800x600,640x480
# GRUB_GFXMODE=auto,1680x1050,1360x768,1280x800,1024x768,1024x600,800x600,640x480
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
GRUB_TIMEOUT="10"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash logo.nologo audit=0 rd.timeout=120 dm_mod.use_blk_mq=1 rd.systemd.show_status=0 systemd.show_status=0"
GRUB_CMDLINE_LINUX_RECOVERY=" failsafe drm.edid_firmware=edid/1024x768.bin vga=788 systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M audit=0 rd.timeout=120 "
GRUB_NOECHO="true"

I believe, based on imperfect memory, that is these 2 lines:

GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true

I do not know why this does not work in VBox VM’s. So I just checked one of those VM’s and lo and behold, the config is different:

GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=false

Now let me see… Sure enought changing GRUB_SAVEDEFAULT=false to true and running sudo update-grub2 does not change the behavior in VBox. So something to add to the list of things VBox screws up. To be honest I recall that this has been the case for years, like 4 or more years and I gave up on this a long time ago.

But what this exercise tells me is that if user wants this behavior on hardware they need to edit that line in /etc/default/grub to true and run sudo update-grub2.

1 Like