Error: Connection activation failed: No suitable device found for this connection

Ask Fedora
,
1

This is a continuation of post: Wired connection not working fedora 41 (dualboot linux/win10)

The networking port worked fine in Kernel 6.8… but in updating to 6.10 the network port broke. I am now in kernel 6.12 .

I redid all the steps in the solution of the above post:

However when nmcli connection up ethernet :
I get the error:

Error: Connection activation failed: No suitable device found for this connection (device lo not available because profile is not compatible with device (connection type is not “loopback”)).

I have done some searching, i have found similar issues but no clear solution.

2

One issue that may be relevant is windows. On some systems if windows shuts down the network devices they cannot be enabled in linux.

Try booting to windows and make certain that you are not using fast boot nor hibernation/sleep in windows when it is shut down.

3

late reply,

just disabled fast boot and hibernation, sleep was already disabled.

i redid the last command but i still have the same error.

4

this is a very late reply but after a long time of trial and error i finally have a working network connection on a dualboot PC, solution: cheating

the issue: i have a win10/linux fedora dualboot PC with a NAS in ad-hoc connected via a network cable → i can connect to my NAS in win10 but not in linux (which i use +90% of the time)

the first solution i tried was trying multiple things in linux and windows, i have changed multiple settings in both OSes but without luck, this is when i lost my patience

the second solution i tried was buying a network PCIe card, this didnt solve anything, in win10 i could use it, in linux i couldnt, i couldnt even create a new connection using the card, the PCIe card was completely locked out for linux
(the network card supports linux but win10 is annoying)

the third solution: a usb to network adapter cable, this works, this works directly in win10 and linux sees this device, i however had to create a new connection via nmcli , the default network didnt work

for the interested: it is a Sitecom AD-1014 adapter (not sponsored, not affiliated)
first: nmcli connection add type ethernet ipv.method link-local
then: nmcli connection up ethernet

i understand that this isnt the proper way of doing things but after 6 months of trial and error i dont care anymore, i just want my NAS

5

Another example where “Workaround” is more appropriate than “Solution”.

I’m confused – it seems you tried a USB ethernet cable, but “Sitecom AD-1014” appears to be a USB-A to USB-C adapter.

Vendor firmware could be at fault. Have you checked that you have current versions? It could help reach others with similar hardware if you post (as pre-formatted text) the output from running inxi -Fzxx in a terminal. Sometimes problems like this are addressed by user comments in the LHDB probes for your model or probes for other systems using the same (original and added) network hardware.

6

my apologies, this is a typo, it should be AD-1004!

result: inxi -Fzxx (network related results)

Network:
  Device-1: Realtek RTL8125 2.5GbE driver: N/A pcie: speed: 5 GT/s lanes: 1
    port: 5000 bus-ID: 02:00.0 chip-ID: 10ec:8125
  Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter
    vendor: Hewlett-Packard driver: rtw_8822be v: N/A pcie: speed: 2.5 GT/s
    lanes: 1 port: 4000 bus-ID: 03:00.0 chip-ID: 10ec:b822
  IF: wlp3s0 state: up mac: <filter>
  Device-3: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: N/A pcie: speed: 2.5 GT/s lanes: 1
    port: 3000 bus-ID: 04:00.0 chip-ID: 10ec:8168
  Device-4: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 1-1:2 chip-ID: 0bda:8153
  IF: enp0s20f0u1 state: up speed: 1000 Mbps duplex: full mac: <filter>
7

This device does not appear to be loading a driver.

It appears that the appropriate driver would be the r8169
I have the exact same ethernet adapter and it works for me.

$ inxi -Nzxx
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168
8

The subsystem vendors are different:
LHDB probes forASRock subsystem
LHDB probes for HP subsystem

The HP subsystem has fewer probes and a only a few indicate “working”. There is also:
LHDB probes for Realtek subsystem.

https://medium.com/@dawnbreather/fixing-realtek-rtl8111-8168-8411-pci-express-gigabit-ethernet-controller-issues-after-upgrading-to-d7a985ae49ef found that the 8168-dkms module worked, but I don’t see any Fedora packages.

9

oh, how did i miss that?!?

are there maybe other packages that might work? are the compatible drives the RTL numbers?

10

Over the years there have been a number of people posting patched Realtek drivers – mostly to support recent (at the time) kernels. There is an Altlinux driver that supports 6.14 kernels. Someone familiar with RPM packaging could probably repackage it for Fedora (Altlinux is based on a fork of Fedora years ago).

11

thank you!

the solution seems to be proper drivers :slight_smile: