Wired network doesn't appear after cold boot. Needs restart to show up

General system Newbie
1

Hello! I’ve been having this issue since I fresh installed EndeavourOS on a new SSD a couple weeks ago.

My wired network won’t show up! The local loop shows up, but my wired connection won’t show up. Every time I have to restart my computer (explicitly hit the restart button, as shutting down and booting up again doesn’t work) to get the wired connection to show up.

What could be doing this? I’ll link the logs below. Let me know if there’s logs I could provide in either state of the machine, as the log below is my machine when it’s working.

rainmaker0102@system: $ inxi -Fxxc0z
System:
  Kernel: 6.6.36-1-lts arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
  Desktop: KDE Plasma v: 6.1.1 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop System: Dell product: Precision T1650 v: 01
    serial: <superuser required> Chassis: type: 6 serial: <superuser required>
  Mobo: Dell model: 0C3YXR v: A01 serial: <superuser required>
    part-nu: Precision T1650 UEFI: Dell v: A28 date: 06/28/2018
CPU:
  Info: quad core model: Intel Core i7-3770 bits: 64 type: MT MCP
    arch: Ivy Bridge rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 3727 high: 3764 min/max: 1600/3900 cores: 1: 3764
    2: 3703 3: 3760 4: 3696 5: 3700 6: 3725 7: 3747 8: 3728 bogomips: 54295
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: PNY
    driver: nvidia v: 555.58 arch: Ampere pcie: speed: 8 GT/s lanes: 16 ports:
    active: none off: DP-2,DP-3 empty: DP-1,HDMI-A-1 bus-ID: 01:00.0
    chip-ID: 10de:2504
  Device-2: Microdia IC800 1080P HD driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-3:2 chip-ID: 0c45:636b
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
    compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia d-rect: 3840x1080
    display-ID: 0
  Monitor-1: DP-2 pos: right res: 1920x1080 size: N/A
  Monitor-2: DP-3 pos: primary,left res: 1920x1080 size: N/A
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
    gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11:
    drv: zink inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
    display-ID: :1.0
  API: Vulkan v: 1.3.279 surfaces: xcb,xlib,wayland device: 0
    type: discrete-gpu driver: nvidia device-ID: 10de:2504
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20
  Device-2: NVIDIA GA106 High Definition Audio vendor: PNY
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:228e
  Device-3: C-Media Audio Adapter (Unitek Y-247A)
    driver: cmedia_hs100b,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-1.4:4 chip-ID: 0d8c:0014
  Device-4: Microdia IC800 1080P HD driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-3:2 chip-ID: 0c45:636b
  API: ALSA v: k6.6.36-1-lts status: kernel-api
  Server-1: PipeWire v: 1.2.0 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e
    v: kernel port: f040 bus-ID: 00:19.0 chip-ID: 8086:1502
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-1.2:3
    chip-ID: 0a12:0001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
    lmp-v: 6
Drives:
  Local Storage: total: 6.39 TiB used: 3.56 TiB (55.7%)
  ID-1: /dev/sda vendor: PNY model: CS900 2TB SSD size: 1.82 TiB
    speed: 6.0 Gb/s serial: <filter>
  ID-2: /dev/sdb vendor: Seagate model: ST4000NM0035-1V4107 size: 3.64 TiB
    speed: 3.0 Gb/s serial: <filter>
  ID-3: /dev/sdc vendor: Lexar model: SSD NS100 1TB size: 953.87 GiB
    speed: 3.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 1.8 TiB used: 290.59 GiB (15.8%) fs: btrfs dev: /dev/sda2
  ID-2: /boot/efi size: 1022 MiB used: 584 KiB (0.1%) fs: vfat
    dev: /dev/sda1
  ID-3: /home size: 1.8 TiB used: 290.59 GiB (15.8%) fs: btrfs
    dev: /dev/sda2
  ID-4: /var/log size: 1.8 TiB used: 290.59 GiB (15.8%) fs: btrfs
    dev: /dev/sda2
Swap:
  ID-1: swap-1 type: partition size: 17.13 GiB used: 661.2 MiB (3.8%)
    priority: -2 dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 71.0 C mobo: 23.0 C
  Fan Speeds (rpm): cpu: 1387 mobo: 1146
Info:
  Memory: total: 16 GiB available: 15.57 GiB used: 6.59 GiB (42.3%)
  Processes: 330 Power: uptime: 20m wakeups: 0 Init: systemd v: 256
    default: graphical
  Packages: pm: pacman pkgs: 1571 Compilers: clang: 17.0.6 gcc: 14.1.1
    Shell: Bash v: 5.2.26 running-in: konsole inxi: 3.3.35
2

Just to confirm, were you running Linux of some sort prior to this, and if so, was it an issue then?

That’s not good :grimacing:
You risk bigger issues if that’s the current “fix”. I do wonder if this is somehow related. It’d be interesting to know what’s causing the system to fail to shut down. You might have a look in this topic for some pointers on what to look for.

Already running the latest BIOS update, that’s :+1:

I assume this was generated after achieving an “up” state?

These steps are a bit like prodding your network adaptor with a stick. When it’s down, what happens if you run this to restart the network service:

systemctl restart systemd-networkd

Then perhaps release/renew DHCP lease:

dhclient -r eno1
3

if anything else was on that SSD or other drives plugged in during install I would say ^^ for sure. Isn’t there a NetworkManager.service to check too? [Or plasma just networkd?]

4

This was not an issue before. I was running EndeavourOS on the same machine, but different ssd. I had issues with the SSD reading and writing, so I bought a new SSD and reinstalled EndeavourOS with the latest ISO at the time.

Nothing changed! Restarting the NetworkManager service just restarted the local loop.

This was interesting! It talked about using a live ISO to check the hardware. This issue is present on the live ISO! I think I remember seeing it on the ISO, but just rebooted it so I could install it.

5

I also checked the nvidia-dkms drivers vs the nvidia & nvidia-lts drivers and same thing still happens

6

Here’s the result of journalctl -b -1 | eos-sendlog
https://0x0.st/XMNU.txt

7

A user here had a similar issue to you, and what seemed to resolve it for them was using the e1000e-dkms driver in the AUR (after they had to fiddle with it a bit, but the package was updated since this topic).

However, that package has since been orphaned, and it may not even build anymore. You can always give it a go though. The driver version it references is the most recent version.

8

Considering the history of this machine and that I’ve run EndeavourOS on it without this issue, I assumed it had to be the new HDD/SSD configuration, as I’ve got three drives now instead of just two plus my blu ray drive.

Going back to just one SSD and one HDD has seemed to fix it for the time being. Probably a goof with the motherboard, but not surprising considering it’s a little old at this point. I’ll probably look into an upgrade in the future.

Thanks everyone!

1 Like
9

That’s a new one for me, but I’m glad you were able to pinpoint the issue.

One possible option in the meantime, is something simple like a USB ethernet adaptor. If this is an option you pursue, just make sure it is explicitly supported by Linux. I have a few of these, and not all are.

10

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.