Wifi doesn't work

Support
1

Hello,

Requirements:

I have [Searched] the forum for my issue and found nothing related or helpful
I have checked the [Resources category ]
I have reviewed the [Wiki] for relevant information
I have read the the [Release Notes and Errata]

OpenMandriva Lx version:

ROME latest snapshot

Desktop environment (KDE, LXQT…):

KDE

Description of the issue (screenshots if relevant):

I can’t get WIFI to work. It works fine on OpenSUSE, Ubuntu, MX (but not Fedora latest).

Relevant informations (hardware involved, software version, logs or output…):

Here’s my PCI info:
00:00.0 Host bridge: Intel Corporation Alder Lake-N Processor Host Bridge/DRAM Registers
DeviceName: Onboard - Other
Subsystem: Device 1f4c:b010
Flags: bus master, fast devsel, latency 0
Capabilities:
Kernel driver in use: igen6_edac
Kernel modules: igen6_edac

00:02.0 VGA compatible controller: Intel Corporation Alder Lake-N [UHD Graphics] (prog-if 00 [VGA controller])
DeviceName: Onboard - Video
Subsystem: Device 1f4c:b010
Flags: bus master, fast devsel, latency 0, IRQ 133
Memory at 6000000000 (64-bit, non-prefetchable) [size=16M]
Memory at 4000000000 (64-bit, prefetchable) [size=256M]
I/O ports at 4000 [size=64]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities:
Kernel driver in use: i915
Kernel modules: i915, xe

00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01)
DeviceName: Onboard - Other
Flags: fast devsel
Memory at 6001120000 (64-bit, non-prefetchable) [size=32K]
Capabilities:
Kernel driver in use: intel_vsec
Kernel modules: intel_vsec

00:12.0 Serial controller: Intel Corporation Device 54fc (prog-if 00 [8250])
DeviceName: Onboard - Other
Subsystem: Device 1f4c:b010
Flags: bus master, fast devsel, latency 0, IRQ 26
Memory at 6001110000 (64-bit, non-prefetchable) [size=64K]
Capabilities:
Kernel driver in use: intel_ish_ipc
Kernel modules: intel_ish_ipc

00:14.0 USB controller: Intel Corporation Alder Lake-N PCH USB 3.2 xHCI Host Controller (prog-if 30 [XHCI])
DeviceName: Onboard - Other
Subsystem: Device 1f4c:b010
Flags: bus master, medium devsel, latency 0, IRQ 123
Memory at 6001100000 (64-bit, non-prefetchable) [size=64K]
Capabilities:
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 RAM memory: Intel Corporation Alder Lake-N PCH Shared SRAM
DeviceName: Onboard - Other
Flags: fast devsel
Memory at 6001138000 (64-bit, non-prefetchable) [disabled] [size=16K]
Memory at 600113e000 (64-bit, non-prefetchable) [disabled] [size=4K]
Capabilities:

00:14.3 Network controller: Intel Corporation CNVi: Wi-Fi
DeviceName: Onboard - Ethernet
Subsystem: Intel Corporation Device 0034
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at 6001134000 (64-bit, non-prefetchable) [size=16K]
Capabilities:
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

00:16.0 Communication controller: Intel Corporation Alder Lake-N PCH HECI Controller
DeviceName: Onboard - Other
Subsystem: Device 1f4c:b010
Flags: bus master, fast devsel, latency 0, IRQ 122
Memory at 600113d000 (64-bit, non-prefetchable) [size=4K]
Capabilities:
Kernel driver in use: mei_me
Kernel modules: mei_me

00:17.0 SATA controller: Intel Corporation Alder Lake-N SATA AHCI Controller (prog-if 01 [AHCI 1.0])
DeviceName: Onboard - SATA
Subsystem: Device 1f4c:b010
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 132
Memory at 80a00000 (32-bit, non-prefetchable) [size=8K]
Memory at 80a03000 (32-bit, non-prefetchable) [size=256]
I/O ports at 4090 [size=8]
I/O ports at 4080 [size=4]
I/O ports at 4060 [size=32]
Memory at 80a02000 (32-bit, non-prefetchable) [size=2K]
Capabilities:
Kernel driver in use: ahci
Kernel modules: ahci

00:1c.0 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port #7 (prog-if 00 [Normal decode])
Subsystem: Device 1f4c:b010
Flags: bus master, fast devsel, latency 0, IRQ 120
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 3000-3fff [size=4K] [16-bit]
Memory behind bridge: 80900000-809fffff [size=1M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Capabilities:
Kernel driver in use: pcieport

00:1d.0 PCI bridge: Intel Corporation Alder Lake-N PCI Express Root Port #11 (prog-if 00 [Normal decode])
Subsystem: Device 1f4c:b010
Flags: bus master, fast devsel, latency 0, IRQ 121
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: [disabled] [16-bit]
Memory behind bridge: 80800000-808fffff [size=1M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Capabilities:
Kernel driver in use: pcieport

00:1f.0 ISA bridge: Intel Corporation Alder Lake-N PCH eSPI Controller
DeviceName: Onboard - Other
Subsystem: Device 1f4c:b010
Flags: bus master, fast devsel, latency 0

00:1f.3 Audio device: Intel Corporation Alder Lake-N PCH High Definition Audio Controller
DeviceName: Onboard - Sound
Subsystem: Device 1f4c:b010
Flags: bus master, fast devsel, latency 32, IRQ 166
Memory at 6001130000 (64-bit, non-prefetchable) [size=16K]
Memory at 6001000000 (64-bit, non-prefetchable) [size=1M]
Capabilities:
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_avs, snd_sof_pci_intel_tgl

00:1f.4 SMBus: Intel Corporation Alder Lake-N SMBus
DeviceName: Onboard - Other
Subsystem: Device 1f4c:b010
Flags: medium devsel, IRQ 16
Memory at 600113c000 (64-bit, non-prefetchable) [size=256]
I/O ports at efa0 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

00:1f.5 Serial bus controller: Intel Corporation Alder Lake-N SPI (flash) Controller
DeviceName: Onboard - Other
Subsystem: Device 1f4c:b010
Flags: fast devsel
Memory at 80a04000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: intel-spi
Kernel modules: spi_intel_pci

01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller
Flags: bus master, fast devsel, latency 0, IRQ 18
I/O ports at 3000 [size=256]
Memory at 80904000 (64-bit, non-prefetchable) [size=4K]
Memory at 80900000 (64-bit, non-prefetchable) [size=16K]
Capabilities:
Kernel driver in use: r8169
Kernel modules: r8169

02:00.0 Non-Volatile memory controller: Micron Technology Inc 2550 NVMe SSD (DRAM-less) (rev 01) (prog-if 02 [NVM Express])
Subsystem: Micron Technology Inc Device 1100
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at 80800000 (64-bit, non-prefetchable) [size=16K]
Capabilities:
Kernel driver in use: nvme
Kernel modules: nvme

2

Welcome! We are glad to see you here and hope you will make this your home.

3

When you say “doesn’t work”, what do you mean?

  • Does it detects wireless AP?
  • Is there anything useful at dmesg when iwlwifi module is loaded?
  • Which wireless card is this? Do you have the name? lspci doesn’t say much.
  • If you can’t get the wireless card name, can you provide the output from “lspci -nn” ?
4

You can use nmcli to get info about networkmanager. Please post output of:

nmcli

nmcli g

inxi -n

@WalterCool posts some good suggestions. We need to know more that “I can’t get wifi to work”.

Did wifi work on the ‘Live’ iso before installation?
What have you done to get wifi to work?
Have you made any changes to your system after installation?

I do a lot of iso and install testing. My experience is that I boot a ‘Live’ OMLx iso (Cooker, ROME, or Rock) and connect to wifi first thing with the network icon in Plasma system tray. After installation wifi just works, so the config must be copied during the install. Normally a user should be able to connect with that system tray icon after install if for some reason that did not do so on the ‘Live’ iso.

5

Thank you both for your help. Sorry I didn’t post enough details at first.

WiFi doesn’t show up in Network Manager. I’ve tried searching for solutions, but found nothing, which is why I thought I’d post here.

Dmesg shows a whole load of stuff. There are multiple lines saying “Direct firmware load for iwlwifi-so-a0-jf-…” failed.

WiFi did not work on the Live iso before installation. I haven’t made any changes whatsoever; this is a clean install, just updated.

Acording to the PC manufacturer, the wireless card is Intel® Wireless-AC 9560.

I’m connected to the internet currently via USB phone tethering.

Here’s the output of nmcli:

enp0s20f0u1: connected to Wired connection 1
        "Motorola Moto G 2014"
        ethernet (rndis_host), 02:69:1C:04:16:74, hw, mtu 1500
        ip4 default
        inet4 192.168.42.61/24
        route4 192.168.42.0/24 metric 100
        route4 default via 192.168.42.129 metric 100
        inet6 fe80::aeb5:8544:2c83:d2bf/64
        route6 fe80::/64 metric 1024

lo: connected (externally) to lo
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet4 127.0.0.1/8
        inet6 ::1/128

enp0s20f0u3u4u3: unavailable
        "Realtek RTL8153"
        ethernet (r8152), C8:4B:D6:D2:43:6D, hw, mtu 1500

enp1s0: unavailable
        "Realtek RTL8111/8168/8211/8411"
        ethernet (r8169), 58:47:CA:74:4C:50, hw, mtu 1500

DNS configuration:
        servers: 192.168.42.129
        interface: enp0s20f0u1

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.

Here’s nmcli g:

STATE      CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN     METERED       
connected  full          missing  enabled  missing  enabled  yes (guessed)

Here’s nmcli -n:

enp0s20f0u1: connected to Wired connection 1
        "Motorola Moto G 2014"
        ethernet (rndis_host), 02:69:1C:04:16:74, hw, mtu 1500
        ip4 default
        inet4 192.168.42.61/24
        route4 192.168.42.0/24 metric 100
        route4 default via 192.168.42.129 metric 100
        inet6 fe80::aeb5:8544:2c83:d2bf/64
        route6 fe80::/64 metric 1024

lo: connected (externally) to lo
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet4 127.0.0.1/8
        inet6 ::1/128

enp0s20f0u3u4u3: unavailable
        "Realtek RTL8153"
        ethernet (r8152), C8:4B:D6:D2:43:6D, hw, mtu 1500

enp1s0: unavailable
        "Realtek RTL8111/8168/8211/8411"
        ethernet (r8169), 58:47:CA:74:4C:50, hw, mtu 1500

DNS configuration:
        servers: 192.168.42.129
        interface: enp0s20f0u1

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.

Thanks again!

6

what’s about

rfkill list

7

Intel Wireless-AC 9560 Linux

The Intel® Wireless-AC 9560 is certified for use with Ubuntu 18.04 LTS and requires a Linux kernel version 4.14 or higher.23 It is supported by the iwlwifi driver, which is included in the Linux kernel.4 However, the wireless device also requires firmware to operate, which typically ships with your distribution or can be downloaded from the repository firmware git tree.4

Issues with the Intel® Wireless-AC 9560 on Linux have been reported, such as problems connecting to Wi-Fi after installation on Ubuntu 18.04.5 These issues can sometimes be resolved by ensuring the correct firmware is installed and available in the /lib/firmware directory.36 Additionally, some users have encountered problems with Wi-Fi and Bluetooth running simultaneously, which can be mitigated by disabling BT Coex by loading iwlwifi with bt_coex_active=0 as a module parameter.4

For troubleshooting, it is recommended to check if the necessary firmware is present and correctly installed. If issues persist, visiting Bugzilla for Intel Wi-Fi on Linux can provide further assistance and solutions to previously reported issues.4

  • Intel® Wireless-AC 9560 : Certified for Ubuntu 18.04 LTS and requires Linux kernel 4.14 or higher.23
  • iwlwifi Driver : Included in the Linux kernel and supports Intel® Wireless-AC 9560.4
  • Firmware : Required for the wireless device to operate and should be installed in the /lib/firmware directory.4
  • Troubleshooting : Check firmware installation and consider disabling BT Coex if Wi-Fi and Bluetooth issues arise.

So, maybe try disabling bluetooth.

1 Like
8

What you have shows that network manager does not recognize your wifi hardware. Also the last command was meant to be:

inxi -n

Also as @bruno suggested:

rfkill

That is a good basic command for this type of problem, and I forgot. :flushed:

As far as I know if the network icon in system tray does not show your wifi router or connection that could be a connectivity problem or an incompatible hardware problem.

Time to throw in that I am not a developer, don’t know code, like what of the interaction on this forum is users helping users. We can take a issue to developers. So we need to take the info provided above by @WilsonPhillips investigate if that wifi device or it’s driver is the issue, or if there is some kernel module needed and so forth.

And last a helpful hint for forum etiquette:

[Forum] How to post code as code

Posting code as code simply makes it easier to read the code.

[Forum] How to mark your topic as ‘resolved’

9

I’ve disabled bluetooth, but that hasn’t helped unfortunately.

Here’s the output of inxi -n:

Network:
  Device-1: Intel CNVi: Wi-Fi driver: iwlwifi
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp1s0 state: down mac: 58:47:ca:74:4c:50
  Device-3: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
  IF: enp0s20f0u3u4u3 state: down mac: c8:4b:d6:d2:43:6d
  IF-ID-1: enp0s20f0u7u4u4 state: unknown speed: -1 duplex: half
    mac: 02:69:1c:04:16:74

Here’s rfkill list


0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

I’ve looked on Intel’s site to find firmware, but it looks like the firmware is already in /lib/firmware. Perhaps it’s just not loading.

10

The module has been on the market for years and is supported fully by the iwlwifi driver. The system knows it it there and is giving it a MAC Address, yet it is down.

I also see that the Ethernet is running at an Unknown link speed and Half Duplex, so it is barely working.

Something is not right.

11

The Ethernet is tethering to my ancient mobile phone, so I don’t expect that to run very well really; it’s just temporary till I get wifi. One thing I’ve noticed, which I also noticed on Fedora (where wifi also doesn’t work), is that my mouse sometimes stutters. I never get this on systems where wifi is working properly. It doesn’t sound like it’s related, but I just wondered if that has any relevance.

12

If WiFi doesn’t work on OpenMandriva and it also doesn’t work on Fedora, where does it work?

Never mind, I went back to the first post and see that it works on openSUSE, Ubuntu, MX. We are two days in now. Is this just distro hopping or are you really trying to move here? If you are just distro-hopping, how much effort are you willing to put into this? We see those who spend a week trying to fix their problem and then we never hear from them again.

13

I’m not trying to be cynical, but this is the only thread we have seen you in, so we know nothing more than this one problem. Now, two with the stuttering mouse.

14

I don’t understand what you’re saying regarding the stuttering mouse. That’s not a problem I’m trying to fix; I just wondered whether or not it could be related. Why do you need to have seen me in other threads? I’m new to Mandriva; what am I supposed to do? I have no need to have posted anything else. I’m not new to Linux however, I’ve been using it since Breezy Badger.

I wouldn’t say I’m distro hopping, I would like to try OpenMandriva that’s all. Is that OK? I think lots of people try different distros, don’t they. If it worked, and I liked it, I’d stay with it.

But I don’t really want to spend weeks trying to fix this. Perhaps I’ll leave it, then.

Sorry I’ve wasted your time.

15

If you are seriously considering OpenMandriva, then maybe it will be worth all of the effort. I am just saying, sometimes it is best to stick with what you already know works.

Yes, I would lean toward the stuttering mouse being related to the WiFi issue.

16

Could you post the output from:

cat /etc/release
and
uname -a

This is in order so that we know which release you are on and which kernel you are running, there were networking issues with one of the 6.14.2 kernel releases that was subsequently fixed in a following release, this information would help us determine that you are not on the kernel release that had that issue.

Unfortunately this does not tell us much about the version of OMLx you are running, nor which ISO snapshot you use to install from

A little more information in this respect would come in handy in order that we can rule out that previous kernel being a potential culprit.

17

I don’t need to be told what might be best for me, thanks.

18

other test (show interfaces which are currently available, even if down)

ifconfig -a

if the wifi interface appears you can try:

ifconfig up «name-of-interface»

19

The output of cat /etc/release is:

OpenMandriva Lx release 25.04 (ROME) Rolling for x86_64

and uname -a is:

6.14.2-desktop-3omv2590 #1 SMP PREEMPT_DYNAMIC Fri Apr 18 21:01:44 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

@bruno here’s ifconfig -a:

enp0s20f0u3u4u3: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c8:4b:d6:d2:43:6d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp0s20f0u7u4u4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.42.61  netmask 255.255.255.0  broadcast 192.168.42.255
        inet6 fe80::4501:9fd:c3c:ce8a  prefixlen 64  scopeid 0x20<link>
        ether 02:69:1c:04:16:74  txqueuelen 1000  (Ethernet)
        RX packets 1274  bytes 996259 (972.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1027  bytes 273368 (266.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp1s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 58:47:ca:74:4c:50  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 82  bytes 6904 (6.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 82  bytes 6904 (6.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
20

Your kernel version looks okay as that is the release with the network issues resolved in it, thank you for providing the extra info on that even if only to rule it out.