Ошибка сбой активации соединения no suitable device found for this connection

Перейти к контенту

  • Печать

Страницы: [1] 2  Все   Вниз

Тема: Не работает Network Manager после установки через debootstrap  (Прочитано 7198 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
oermolaev

После установки системы 16.10 с помощью debootstrap и xubuntu-desktop не удается настроить соединение через Network Manager.

~$ nmcli general status
СОСТОЯНИЕ  СВЯЗЬ  WIFI-HW  WIFI     WWAN-HW  WWAN   
отключено  нет    включен  включен  включен  включен

~$ nmcli device status
УСТРОЙСТВО  ТИП       СОСТОЯНИЕ      СОЕДИНЕНИЕ
enp3s0      ethernet  не настроенно  --         
lo          loopback  не настроенно  --Создаю соединение вручную:

~$ nmcli connection add con-name "dhcp" type ethernet ifname enp3s0
Соединение «dhcp» (3daf6552-095e-4ca9-96ad-b18a79ac5ac2) добавлено.
Но не работает:

~$ nmcli con up dhcp
Ошибка: сбой активации соединения: No suitable device found for this connection.При настройке сети через /etc/network/interfaces всё работает:

~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether d0:50:99:3f:75:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.12.102/24 brd 192.168.12.255 scope global enp3s0
       valid_lft forever preferred_lft forever
    inet6 fe80::d250:99ff:fe3f:75fa/64 scope link
       valid_lft forever preferred_lft forever

Чего здесь не хватает?

Оффлайн
DimanBG

oermolaev, по ходу, ты просто обозвал соединение dhcp и всё. А настройки сети в NM? Хоть он и консольный.

Оффлайн
snowin

Чего здесь не хватает?

наоборот, слишком много всего

Оффлайн
Heider

Покаж

ls /etc/NetworkManager/system-connections/

Оффлайн
oermolaev

DimanBG, на картинке видно: «Устройство не управляется».
Вот как сделать чтоб управлялось?
Вот ещё фотка:

Heider,

~$ ls /etc/NetworkManager/system-connections/
dhcp

Оффлайн
Heider

DimanBG, похоже, правильно догадался. :)
Покажи теперь:

sudo cat /etc/NetworkManager/system-connections/dhcp

Оффлайн
oermolaev

« Последнее редактирование: 25 Декабря 2016, 19:36:56 от oermolaev »

Оффлайн
Heider

У меня для проводного соединения в этой директории вообще файл не создается, только для wifi. Для проводного соединение создается сразу после подключения кабеля без всякого файла настроек. Попробуй удалить или переместить файл dhcp, возможно проблема в том, что он захватывает устройство enp3s0, но не подключает его, как надо.

Оффлайн
AnrDaemon

А в /etc/network/interfaces нет мусора?
А в настройках самого NM он не отключен?

Хотите получить помощь? Потрудитесь представить запрошенную информацию в полном объёме.

Прежде чем [Отправить], нажми [Просмотр] и прочти собственное сообщение. Сам-то понял, что написал?…

Оффлайн
oermolaev

А в /etc/network/interfaces нет мусора?

Временно прописал настройки интерфейса чтобы иметь возможность выхода в интернет

~$ cat /etc/network/interfaces.d/enp3s0
auto lo
iface lo inet loopback

#auto enp3s0
iface enp3s0 inet dhcp

Оффлайн
AnrDaemon

Так из-за этого NM и отказывается сотрудничать.

Хотите получить помощь? Потрудитесь представить запрошенную информацию в полном объёме.

Прежде чем [Отправить], нажми [Просмотр] и прочти собственное сообщение. Сам-то понял, что написал?…

Оффлайн
oermolaev

AnrDaemon, что бы сюда написать я снимаю комментарий со строки «iface enp3s0 inet dhcp» и поднимаю интерфейс вручную:

ifup enp3s0

Оффлайн
symon.2014

oermolaev, У меня впечатление , что 6 посте в тексте не хватает мак адреса сетевой карты. 

Оффлайн
AnrDaemon

я снимаю комментарий

Достаточно dhclient $IFACE же ж :)
Ну как максимум, ip link set uo dev $IFACE добавить.

Хотите получить помощь? Потрудитесь представить запрошенную информацию в полном объёме.

Прежде чем [Отправить], нажми [Просмотр] и прочти собственное сообщение. Сам-то понял, что написал?…

Оффлайн
oermolaev

AnrDaemon, согласен. dhclient также решает вопрос с инртернетом, но не решает проблему с Network Manager.

  • Печать

Страницы: [1] 2  Все   Вверх

I added a new connection config (CentOS 7):

DEVICE="eth1"
BOOTPROTO="static"
ONBOOT="yes"
IPADDR=10.68.0.1
GATEWAY=10.68.0.1
NETMASK=255.255.255.248

Next, I ran systemctl restart network and got an error in journalctl:

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

How can I fix it?

Matthias Braun's user avatar

asked Nov 3, 2018 at 16:55

ruslanen's user avatar

CentOS 7 uses «predictable interface names», a new convention for naming network devices that replaces the old eth* convention. Thus, your device is named something else, probably something like enp0s25, not eth1. Check with ip a what your device is named, and substitute it for eth1 in your config file.

answered Nov 3, 2018 at 17:16

Joseph Sible-Reinstate Monica's user avatar

0

I’m new to nmcli and trying to figure out how to create an eth0 connection. sudo nmcli con prints the following:

NAME       UUID     TYPE      DEVICE
MyWlan0    ...      wifi      wlan0
MyEth0     ...      ethernet  --

No matter what command I give, my MyEth0 connection will not show eth0 under DEVICE above (just ‘—‘) and, as a result, I’ll get the following error when I try sudo nmcli con up MyEth0:

Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged).

This is how I created the connection:

sudo nmcli con add con-name MyEth0 type ethernet ifname eth0

I’ve also tried modifying it with the following sorts of commands:

sudo nmcli con mod MyEth0 connection.interface-name eth0

Running sudo nmcli con show MyEth0 connection | grep eth0 does indicate that the connection.interface-name is eth0, but it does not appear this way according to the behavior described above.

Any ideas?

Edit:

Here is the output of sudo lshw -C network:

  *-network:0
       description: Ethernet interface
       physical id: 2
       logical name: eth0
       serial: dc:a6:32:27:84:45
       size: 100Mbit/s
       capacity: 1Gbit/s
       capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=bcmgenet driverversion=v2.0 duplex=full link=yes multicast=yes port=MII speed=100Mbit/s
  *-network:1
       description: Wireless interface
       physical id: 3
       logical name: wlan0
       serial: dc:a6:32:27:84:46
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=brcmfmac driverversion=7.45.18 firmware=01-6a2c8ad4 ip=192.168.1.201 multicast=yes wireless=IEEE 802.11

Источник

После обновления случился сабж. Сетевой адаптер выключен, networkmanager работает. Помогает включение и назначение параметров IP через dhclient вручную, но KDE-шный апплет при этом показывает, что линка нет и в редакторе соединений нет возможности включить или выключить соединение. 

root@valkeru-desktop:~# ifconfig 
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 1  (Локальная петля (Loopback))
        RX packets 320  bytes 23680 (23.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 320  bytes 23680 (23.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@valkeru-desktop:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 10:bf:48:7e:0e:6f brd ff:ff:ff:ff:ff:ff
root@valkeru-desktop:~# /etc/init.d/network-manager status
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since Чт 2017-01-05 17:54:26 MSK; 1min 42s ago
     Docs: man:NetworkManager(8)
 Main PID: 1093 (NetworkManager)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/NetworkManager.service
           └─1093 /usr/sbin/NetworkManager --no-daemon

янв 05 17:54:26 valkeru-desktop NetworkManager[1093]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
янв 05 17:54:26 valkeru-desktop NetworkManager[1093]: <info>  [1483628066.8499] device (lo): link connected
янв 05 17:54:26 valkeru-desktop NetworkManager[1093]: <info>  [1483628066.8505] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
янв 05 17:54:26 valkeru-desktop NetworkManager[1093]: <info>  [1483628066.8516] manager: startup complete
янв 05 17:54:26 valkeru-desktop NetworkManager[1093]: <info>  [1483628066.8542] urfkill disappeared from the bus
янв 05 17:54:26 valkeru-desktop NetworkManager[1093]: <info>  [1483628066.8589] ofono is now available
янв 05 17:54:26 valkeru-desktop NetworkManager[1093]: <warn>  [1483628066.8593] failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
янв 05 17:54:26 valkeru-desktop NetworkManager[1093]: <info>  [1483628066.8598] ModemManager available in the bus
янв 05 17:54:36 valkeru-desktop NetworkManager[1093]: <info>  [1483628076.8730] manager: WiFi hardware radio set enabled
янв 05 17:54:36 valkeru-desktop NetworkManager[1093]: <info>  [1483628076.8731] manager: WWAN hardware radio set enabled
root@valkeru-desktop:~# ifconfig enp2s0 up
root@valkeru-desktop:~# ifconfig
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::12bf:48ff:fe7e:e6f  prefixlen 64  scopeid 0x20<link>
        ether 10:bf:48:7e:0e:6f  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 18  bytes 2348 (2.3 KB)
        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 1  (Локальная петля (Loopback))
        RX packets 323  bytes 24007 (24.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 323  bytes 24007 (24.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@valkeru-desktop:~# dhclient enp2s0
root@valkeru-desktop:~# ifconfig
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.200.1.2  netmask 255.0.0.0  broadcast 10.255.255.255
        inet6 fe80::12bf:48ff:fe7e:e6f  prefixlen 64  scopeid 0x20<link>
        ether 10:bf:48:7e:0e:6f  txqueuelen 1000  (Ethernet)
        RX packets 7  bytes 1165 (1.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 42  bytes 5557 (5.5 KB)
        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 1  (Локальная петля (Loopback))
        RX packets 327  bytes 24287 (24.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 327  bytes 24287 (24.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Upgrade: milou:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
evolution-data-server-common:amd64 (3.22.1-0ubuntu2, 3.22.3-0ubuntu0.1)
plasma-workspace:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu2~ubuntu16.10~ppa2)
libtaskmanager6:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu2~ubuntu16.10~ppa2)
libplasma-geolocation-interface5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu2~ubuntu16.10~ppa2)
liboxygenstyle5-5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libksignalplotter7:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
gtk3-engines-breeze:amd64 (5.8.4-0ubuntu1~ubuntu16.10~ppa1, 5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kdeconnect:amd64 (1.0.1-1ubuntu1~ubuntu16.10~ppa1, 1.0.3-0ubuntu1~ubuntu16.10~ppa1)
libpowerdevilui5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kde-cli-tools:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kde-config-gtk-style:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
bluedevil:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kde-config-gtk-style-preview:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
breeze-cursor-theme:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
plasma-nm:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
plasma-pa:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libpam-kwallet-common:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
plasma-dataengines-addons:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libprocesscore7:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kwin-style-breeze:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kwin-data:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
ksshaskpass:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
plasma-wallpapers-addons:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libkf5sysguard-bin:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
systemsettings:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
plasma-discover-common:amd64 (5.8.4-0ubuntu1~ubuntu16.10~ppa2, 5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kde-style-breeze:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kmenuedit:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
khotkeys:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
plasma-discover:amd64 (5.8.4-0ubuntu1~ubuntu16.10~ppa2, 5.8.5-0ubuntu1~ubuntu16.10~ppa1)
breeze:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kde-style-oxygen-qt5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
plasma-desktop:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kactivitymanagerd:amd64 (5.8.4-0ubuntu1~ubuntu16.10~ppa1, 5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libkdecorations2-5v5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kdeconnect-plasma:amd64 (1.0.1-1ubuntu1~ubuntu16.10~ppa1, 1.0.3-0ubuntu1~ubuntu16.10~ppa1)
user-manager:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kde-style-breeze-qt4:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
plasma-desktop-data:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
powerdevil-data:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libksgrd7:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libkworkspace5-5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu2~ubuntu16.10~ppa2)
kwin-addons:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kde-cli-tools-data:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
plasma-runners-addons:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
oxygen-sounds:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libebackend-1.2-10:amd64 (3.22.1-0ubuntu2, 3.22.3-0ubuntu0.1)
kde-config-sddm:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libkscreenlocker5:amd64 (5.8.4-0ubuntu1~ubuntu16.10~ppa1, 5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libpam-kwallet4:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libpam-kwallet5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kgamma5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libebook-1.2-16:amd64 (3.22.1-0ubuntu2, 3.22.3-0ubuntu0.1)
sddm-theme-breeze:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu2~ubuntu16.10~ppa2)
libkwinglutils9:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kwayland-integration:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kinfocenter:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libkf5screen-bin:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kwrited:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libkf5screen7:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kwin:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libwebkit2gtk-4.0-37:amd64 (2.14.1-0ubuntu1, 2.14.2-0ubuntu1)
plasma-integration:amd64 (5.8.4-0ubuntu1~ubuntu16.10~ppa1, 5.8.5-0ubuntu2~ubuntu16.10~ppa2)
kwin-x11:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
ksysguard-data:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libkwin4-effect-builtins1:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
ksysguardd:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libkwinxrenderutils9:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libebook-contacts-1.2-2:amd64 (3.22.1-0ubuntu2, 3.22.3-0ubuntu0.1)
unattended-upgrades:amd64 (0.92ubuntu1.1, 0.92ubuntu1.2)
libkfontinstui5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libedata-book-1.2-25:amd64 (3.22.1-0ubuntu2, 3.22.3-0ubuntu0.1)
kscreen:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
usb-modeswitch:amd64 (2.2.5+repack0-1ubuntu1, 2.2.5+repack0-1ubuntu1.1)
linux-firmware:amd64 (1.161, 1.161.1)
libkfontinst5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libcamel-1.2-59:amd64 (3.22.1-0ubuntu2, 3.22.3-0ubuntu0.1)
polkit-kde-agent-1:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libkf5sysguard-data:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kde-config-screenlocker:amd64 (5.8.4-0ubuntu1~ubuntu16.10~ppa1, 5.8.5-0ubuntu1~ubuntu16.10~ppa1)
khotkeys-data:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kdeplasma-addons-data:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
liboxygenstyleconfig5-5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libjavascriptcoregtk-4.0-18:amd64 (2.14.1-0ubuntu1, 2.14.2-0ubuntu1)
plasma-look-and-feel-org-kde-breezedark-desktop:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
powerdevil:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libedataserver-1.2-22:amd64 (3.22.1-0ubuntu2, 3.22.3-0ubuntu0.1)
libpowerdevilcore2:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libprocessui7:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libkdecorations2private5v5:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
ksysguard:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libkwineffects9:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
kwin-common:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
qml-module-qtquick-controls-styles-breeze:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libwebkit2gtk-4.0-37-gtk2:amd64 (2.14.1-0ubuntu1, 2.14.2-0ubuntu1)
plasma-widgets-addons:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu1~ubuntu16.10~ppa1)
libweather-ion7:amd64 (4:5.8.4-0ubuntu1~ubuntu16.10~ppa1, 4:5.8.5-0ubuntu2~ubuntu16.10~ppa2)
Источник

I added a new connection config (CentOS 7):

DEVICE="eth1"
BOOTPROTO="static"
ONBOOT="yes"
IPADDR=10.68.0.1
GATEWAY=10.68.0.1
NETMASK=255.255.255.248

Next, I ran systemctl restart network and got an error in journalctl:

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

How can I fix it?

Matthias Braun's user avatar

asked Nov 3, 2018 at 16:55

ruslanen's user avatar

CentOS 7 uses «predictable interface names», a new convention for naming network devices that replaces the old eth* convention. Thus, your device is named something else, probably something like enp0s25, not eth1. Check with ip a what your device is named, and substitute it for eth1 in your config file.

answered Nov 3, 2018 at 17:16

Joseph Sible-Reinstate Monica's user avatar

0

You must log in to answer this question.

Not the answer you’re looking for? Browse other questions tagged

.

Источник

glad to be on these forums!

I searched around a bit on the forums, but couldn’t find a good pre-existing case for this that might resolve anything.

The error just happened out of nowhere after a boot-up, but I do have an «enp» type wireless device name listed at «DEVICE=» in a file named «ifcfg-[my own device name]» which can be a problem if not the case, so what happened here?

When I run «systemctl restart network», I get: «job for network.service failed because the control process exited with error code».

1) Restarting anything does no good for anything.
2) I haven’t tried re-installing anything — yet.
3) «ip add flush [device name]» does nothing, says my device doesn’t exist.
4) Pinging 127.0.0.1 gives response.

At one point, I got this message too: «failed to start lsb bring up/down networking»

What suddenly happened here?

I’m on a fedora30.

Thx for taking the time to read this.

RX

Источник

Concord_nz

Posts: 2
Joined: 2019/10/01 00:34:32

No suitable device found for this connection after Kernel 3.10.0-1062 upgrade

I just performed a yum update, which included Kernel 3.10.0-1062.
Now my wired (on motherboard) network will not work.

journalctl

Code: Select all

NetworkManager[764]: <info>  [1569885360.3296] agent-manager: req[0x55da19f555c0, :1.19/nmcli-connect/0]: agent registered
NetworkManager[764]: <info>  [1569885360.3309] audit: op="connection-activate" uuid="03ce46c7-e008-4570-811c-6a48ff37e1ba" name="enp3s0" result="fail" reason="No suitable device found for this connection (device enp3s0 not available because device has no carrier)."
network[907]: Bringing up interface enp3s0:  Error: Connection activation failed: No suitable device found for this connection (device enp3s0 not available because device has no carrier).

network status

Code: Select all

● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2019-10-01 12:16:00 NZDT; 21s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 907 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

systemd[1]: Starting LSB: Bring up/down networking...
network[907]: Bringing up loopback interface:  [  OK  ]
network[907]: Bringing up interface enp3s0:  Error: Connection activation failed: No suitable device found for this connection (device enp3s0 not available because device has no carrier).
network[907]: [FAILED]
systemd[1]: network.service: control process exited, code=exited status=1
systemd[1]: Failed to start LSB: Bring up/down networking.
systemd[1]: Unit network.service entered failed state.
systemd[1]: network.service failed.

Luckily if I drop back to 3.10.0-957 during boot everything is fine.

ifconfig

Code: Select all

TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="dhcp"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="enp3s0"
UUID="03ce46c7-e008-4570-811c-6a48ff37e1ba"
DEVICE="enp3s0"
ONBOOT="yes"
ZONE=public

chemal

Posts: 776
Joined: 2013/12/08 19:44:49

Re: No suitable device found for this connection after Kernel 3.10.0-1062 upgrade

Post

by chemal » 2019/10/01 03:10:36

What brand of ethernet controller do you have? A Realtek RTL8168 perhaps? Check with:

Concord_nz

Posts: 2
Joined: 2019/10/01 00:34:32

Re: No suitable device found for this connection after Kernel 3.10.0-1062 upgrade

Post

by Concord_nz » 2019/10/01 20:05:30

Hi,

Thanks for the tips.

I read some other topics while I was waiting and came across the «power off & unplug for 20 seconds fix».

Despite having unplugged this box and shifting it to a different cable and switch when this first occurred, I tried it again: powered off, unplugged for 60 seconds and booted back up into the latest kernel and it the network came back online. So odd.

Источник

Возможно, вам также будет интересно:

  • Ошибка сбой активации соединения could not find source connection
  • Ошибка сбой при инициализации
  • Ошибка сбой активации продукта word
  • Ошибка сбой при выполнении arxload
  • Ошибка сбой активации продукта excel

    • Понравилась статья? Поделить с друзьями:
    0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии