[SOLVED] Long boot times- time out on network.target- interface name

BlueGrisGris · 2022-08-16 22:21:13

Hi!

New to Arch, still working out the kinks. My boot times have been really long since I installed arch.

Here is the output of systemd-analyze critical-chain:

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @1min 30.410s
└─multi-user.target @1min 30.410s
  └─ntpd.service @1min 30.364s +44ms
    └─network.target @1min 30.362s
      └─dhcpcd.service @1.110s +216ms
        └─basic.target @1.110s
          └─sockets.target @1.110s
            └─dbus.socket @1.110s
              └─sysinit.target @1.109s
                └─systemd-sysctl.service @1.107s +2ms
                  └─systemd-modules-load.service @151ms +955ms
                    └─systemd-journald.socket @147ms
                      └─system.slice @137ms
                        └─-.slice @137ms

Here is journalctl:
http://0x0.st/o_VR.txt

From what I see in journalctl, this is the offensive line, right after the /tmp directory is cleaned up:

Aug 16 22:04:49 edm8950 kernel: ACPI Warning: \_SB.PC00.PEG1.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20220331/nsarguments-61)
Aug 16 22:04:49 edm8950 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)
Aug 16 22:04:49 edm8950 kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477)
Aug 16 22:04:49 edm8950 kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529)
........

But I am not sure how to proceed.

Thanks in advance!

Last edited by BlueGrisGris (2022-08-18 18:22:13)

seth · 2022-08-17 07:04:16

From what I see in journalctl, this is the offensive line

No. ACPI error are common because board vendors implement ACPI by poking aruond until windows boots. Reading specs is a lot of work - especially when you barely can read to begin with…

You've got

Aug 16 21:27:09 edm8950 systemd[1]: sys-subsystem-net-devices-enp0s3.device: Job sys-subsystem-net-devices-enp0s3.device/start timed out.
Aug 16 21:27:09 edm8950 systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/enp0s3.
Aug 16 21:27:09 edm8950 systemd[1]: Dependency failed for A basic dhcp ethernet connection.
Aug 16 21:27:09 edm8950 systemd[1]: netctl@custom\x2ddhcp\x2dprofile.service: Job netctl@custom\x2ddhcp\x2dprofile.service/start failed with result 'dependency'.
Aug 16 21:27:09 edm8950 systemd[1]: sys-subsystem-net-devices-enp0s3.device: Job sys-subsystem-net-devices-enp0s3.device/start failed with result 'timeout'.
Aug 16 21:27:09 edm8950 systemd[1]: Reached target Network.

because you're trying to use enp0s3 but the network device is (now) enp4s0 because while some people have a hard time reading, others have a hard time with thinking and brainfart some really dumb ideas such as https://systemd.io/PREDICTABLE_INTERFACE_NAMES/

=> Disable that and use eth0 and wlan0 - unless you put more NICs into the system, those will actually be predictable names.
https://wiki.archlinux.org/title/Networ … face_names

Then fix/align your netctl profiles

BlueGrisGris · 2022-08-18 18:18:16

That did the trick! For anyone coming here with the same issue, remember to disable/delete the old netctl profile. At first, I only enabled the new one, but the old one was still kicking around causing the time out on boot.

graphical.target @9.245s
└─multi-user.target @9.244s
  └─ntpd.service @9.220s +23ms
    └─network.target @9.219s
      └─netctl@eth0_static_ethernet.service @5.519s +3.700s
        └─sys-subsystem-net-devices-eth0.device @5.518s

seth wrote:

No. ACPI error are common because board vendors implement ACPI by poking aruond until windows boots. Reading specs is a lot of work - especially when you barely can read to begin with…

So nothing for me to fix here?
Thanks for your help! Marking as SOLVED

seth · 2022-08-18 19:41:46

So nothing for me to fix here?

You could run a BIOS update if available, but unless you're experiencing any real problems from this (hardware not showing up etc) I'd just leave it alone.
It is not inherently a harmful error message.

Arch Linux

#1 2022-08-16 22:21:13

[SOLVED] Long boot times- time out on network.target- interface name

#2 2022-08-17 07:04:16

Re: [SOLVED] Long boot times- time out on network.target- interface name

#3 2022-08-18 18:18:16

Re: [SOLVED] Long boot times- time out on network.target- interface name

#4 2022-08-18 19:41:46

Re: [SOLVED] Long boot times- time out on network.target- interface name

Board footer