Нет Ethernet на Intel NUC6CAY @ Ubuntu 20.04

У меня есть Intel NUC6CAY с LAN Realtek 8111HN на борту. Но этого не произошло. Я использую только что установленный Ubuntu 20.04. Поскольку предыдущая установка Mint имела ту же проблему после обновления до 20.04. До 20.04 пользовался 19.х или 18.х, не помню. Но LAN работал.

Edit: BIOS-Update у меня работает. См. Обновленные результаты ниже

ifconfig -a Показывает lo и wlp2s0 (WLAN).

lspci -nnk | grep -a3 Ethernet ничего не показывает.

dmesg |grep e1000e
[  198.740755] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[  198.740758] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
 sudo lshw -C network
  *-network                 
       Beschreibung: Kabellose Verbindung
       Produkt: Dual Band Wireless-AC 3168NGW [Stone Peak]
       Hersteller: Intel Corporation
       Physische ID: 0
       Bus-Informationen: pci@0000:02:00.0
       Logischer Name: wlp2s0
       Version: 10
       Seriennummer: de:ad:co:de:ba:se
       Breite: 64 bits
       Takt: 33MHz
       Fähigkeiten: pm msi pciexpress bus_master cap_list ethernet physical wireless
       Konfiguration: broadcast=yes driver=iwlwifi driverversion=5.4.0-42-generic firmware=29.1654887522.0 ip=192.168.2.42 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       Ressourcen: irq:129 memory:91100000-91101fff

Все эти C&P были выполнены после того, как я даже загрузил и скомпилировал r8168-8.048.03.tar. bz2 из https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software .

Я не являюсь обычным пользователем unix. Все это было сделано путем бессистемных исследований и попыток и ошибок.

Есть ли предположения, что делать, чтобы использовать соединение Ethernet?

Обновление / редактирование: sudo journalctl -b 0 возвращает более 11000 строк журнала. ищет eth дает мне systemd-udevd [378]: ethtool: автосогласование не установлено или включено, скорость и дуплекс недоступны для записи. ядро: Bluetooth: BNEP (эмуляция Ethernet) версии 1.3 Может быть, вы можете указать, что ищете. Ничего не нашел для realtek (кроме звуковой карты) гигабит, Ethernet

Я удалил все строки, которые math (. *) \ (Wlp2s0 \): (. *) \ N в следующем журнале:

sudo journalctl /usr/sbin/NetworkManager
-- Reboot --
Aug 12 22:14:24 homerunner NetworkManager[717]:   [1597263264.9381] NetworkManager (version 1.22.10) is starting... (for the first time)
Aug 12 22:14:24 homerunner NetworkManager[717]:   [1597263264.9383] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-powersave-on.conf)
Aug 12 22:14:24 homerunner NetworkManager[717]:   [1597263264.9854] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.0048] manager[0x5562be1cf030]: monitoring kernel firmware directory '/lib/firmware'.
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.0049] monitoring ifupdown state file '/run/network/ifstate'.
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.3240] hostname: hostname: using hostnamed
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.3241] hostname: hostname changed from (none) to "homerunner"
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.3246] dns-mgr[0x5562be1b7290]: init: dns=systemd-resolved rc-manager=symlink, plugin=systemd-resolved
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.3322] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:13.1/0000:02:00.0/ieee80211/phy0/rfkill0) (driver iwlwifi)
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.3333] manager[0x5562be1cf030]: rfkill: Wi-Fi hardware radio set enabled
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.3333] manager[0x5562be1cf030]: rfkill: WWAN hardware radio set enabled
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.3576] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-wifi.so)
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.3665] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-team.so)
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.3877] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-adsl.so)
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4009] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so)
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4026] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-wwan.so)
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4032] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4036] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4037] manager: Networking is enabled by state file
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4039] dhcp-init: Using DHCP client 'internal'
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4095] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-settings-plugin-ifupdown.so")
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4096] settings: Loaded settings plugin: keyfile (internal)
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4097] ifupdown: management mode: unmanaged
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4104] ifupdown: interfaces file /etc/network/interfaces doesn't exist
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4192] device (lo): carrier: link connected
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4198] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.4977] Error: failed to open /run/network/ifstate
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.5160] modem-manager: ModemManager available
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.5218] supplicant: wpa_supplicant running
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.6484] sup-iface[0x5562be1dc120,wlp2s0]: supports 5 scan SSIDs
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.6530] Wi-Fi P2P device controlled by interface wlp2s0 created
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.6540] manager: (p2p-dev-wlp2s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/3)
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.6554] device (p2p-dev-wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.6577] device (p2p-dev-wlp2s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 12 22:14:25 homerunner NetworkManager[717]:   [1597263265.6694] sup-iface: failed to cancel p2p connect: P2P cancel failed
Aug 12 22:14:28 homerunner NetworkManager[717]:   [1597263268.9714] policy: auto-activating connection 'NetofNet' (275c1c77-ac5b-4117-8803-a0ae7870c34e)
Aug 12 22:14:28 homerunner NetworkManager[717]:   [1597263268.9767] manager: NetworkManager state is now CONNECTING
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.0003] Config: added 'ssid' value 'NetofNet'
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.0003] Config: added 'scan_ssid' value '1'
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.0004] Config: added 'bgscan' value 'simple:30:-70:86400'
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.0004] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.0004] Config: added 'auth_alg' value 'OPEN'
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.0004] Config: added 'psk' value ''
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.0194] device (p2p-dev-wlp2s0): supplicant management interface state: ready -> authenticating
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.0220] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.0340] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> associated
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.0437] device (p2p-dev-wlp2s0): supplicant management interface state: associated -> 4-way handshake
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.0921] device (p2p-dev-wlp2s0): supplicant management interface state: 4-way handshake -> completed
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.1406] manager: NetworkManager state is now CONNECTED_LOCAL
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.1500] manager: NetworkManager state is now CONNECTED_SITE
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.1512] policy: set 'NetofNet' (wlp2s0) as default for IPv4 routing and DNS
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.1555] manager: startup complete
Aug 12 22:14:29 homerunner NetworkManager[717]:   [1597263269.4590] manager: NetworkManager state is now CONNECTED_GLOBAL
Aug 12 22:14:30 homerunner NetworkManager[717]:   [1597263270.5744] policy: set 'NetofNet' (wlp2s0) as default for IPv6 routing and DNS
Aug 12 22:14:33 homerunner NetworkManager[717]:   [1597263273.1526] agent-manager: agent[a5afc4246fa6048e,:1.44/org.gnome.Shell.NetworkAgent/1000]: agent registered

Выходы после обновления BIOS

ifconfig -a
enp3s0: flags=4099  mtu 1500
        ether 94:c6:91:a2:3f:b2  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
        device interrupt 128  base 0x5000 
...
sudo lshw -C network
  *-network                 
       Beschreibung: Kabellose Verbindung
       Produkt: Dual Band Wireless-AC 3168NGW [Stone Peak]
       Hersteller: Intel Corporation
       Physische ID: 0
       Bus-Informationen: pci@0000:02:00.0
       Logischer Name: wlp2s0
       Version: 10
       Seriennummer: 34:e1:2d:ca:77:86
       Breite: 64 bits
       Takt: 33MHz
       Fähigkeiten: pm msi pciexpress bus_master cap_list ethernet physical wireless
       Konfiguration: broadcast=yes driver=iwlwifi driverversion=5.4.0-42-generic firmware=29.1654887522.0 ip=192.168.0.25 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       Ressourcen: irq:130 memory:91200000-91201fff
  *-network
       Beschreibung: Ethernet interface
       Produkt: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       Hersteller: Realtek Semiconductor Co., Ltd.
       Physische ID: 0
       Bus-Informationen: pci@0000:03:00.0
       Logischer Name: enp3s0
       Version: 15
       Seriennummer: 94:c6:91:a2:3f:b2
       Kapazität: 1Gbit/s
       Breite: 64 bits
       Takt: 33MHz
       Fähigkeiten: pm msi pciexpress msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       Konfiguration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.048.00-NAPI latency=0 link=no multicast=yes port=twisted pair
       Ressourcen: irq:128 ioport:e000(Größe=256) memory:91104000-91104fff memory:91100000-91103fff

0
задан 15 August 2020 в 13:43

1 ответ

BIOS

Intel NUC6CAY

У вас установлена ​​версия BIOS AYAPLCEL.86A.0052.2018.0627.1943.

Похоже, доступна более новая версия BIOS, AYAPLCEL.86A.0066, датированная 17.12.2019, и его можно загрузить здесь или здесь .

Инструкции по обновлению BIOS находятся здесь .

Примечание: Убедитесь, что у меня есть правильную веб-страницу для вашей модели. Он охватывает две разные системы.

Примечание: Перед обновлением BIOS сделайте хорошие резервные копии.

0
ответ дан 21 August 2020 в 08:00

Другие вопросы по тегам:

Похожие вопросы: