I noticed that Garuda does not seem to enable the network devices on boot, but only does so after the Gnome-session has been started and I am on the desktop. This results in me having to wait for 10-15 seconds until the network is connected.
I googled this for Arch where the suggestion was to enable dhcpcd on boot - however I found that Garuda does not have this module in systemctl at all. Guess the network manager works differently or something?
How do I enable the start of the Ethernet connection during the boot sequence in Garuda?
Why do you need to wait 10-15 Seconds until an ethernet connection is established? That should be near instant.
And what means "wait"? Can't you do anything?
For me, usually, it takes longer to start a browser than it takes to have a connection established, especially for ethernet but also mostly for wifi nowadays.
So I suspect there is some issue with your network.
On the other hand, you can get rid of network manager and install something else. But I'd discuss that as next step, if there really is nothing wrong with your network.
Isn’t dhcpd an actual DHCP server? In regular consumer networks usually the router has this role already, therefore adding another DHCP server would likely cause issues.
The network devices are enabled before this, during the boot process. This sounds like maybe an authentication issue. Does your network have a captive portal?
These should not both be in use, rather one or the other. Either is fine, although NetworkManager is more commonly implemented in my experience. Solutions you see involving dhcpcd can likely be implemented with NetworkManager instead (obviously with different commands or services).
Please post the output of garuda-inxi as requested in the forum template.
@Garfonso No, the session is working fine and the system is usable. There's just no internet the first 10-15 seconds after the GNOME session started.
@Rest: No I have not installed another competing network manager. As I said: I tried to google the issue and learned the proposed solution from Arch community does not apply here. That's when I started bothering you with this
Yes, it's a regular ethernet interface. Wifi is disabled. No, the network does not require authentication or authorization - it's a normal router running a DHCP server for the whole home network.
I have a drive for Windows, but I have only used it to confirm that my hardware is fully functional (as I experienced other issues with the ALSA sound driver as published here). I am not actually using dual boot / grub for that at all (but if necessary directly via Bios).
Thanks all for the feedback so far. Enclosed the log outputs.
journalctl -r -b -u NetworkManager
Jan 31 08:20:14 myhostname NetworkManager[662]: <info> [1675149614.3641] dhcp6 (eno1): state changed new lease, address=fd59:73bc:fba1::923
Jan 31 08:20:14 myhostname NetworkManager[662]: <info> [1675149614.3614] dhcp6 (eno1): activation: beginning transaction (timeout in 45 seconds)
Jan 31 08:20:12 myhostname NetworkManager[662]: <info> [1675149612.9041] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 31 08:20:12 myhostname NetworkManager[662]: <info> [1675149612.7918] device (eno1): Activation: successful, device activated.
Jan 31 08:20:12 myhostname NetworkManager[662]: <info> [1675149612.7916] manager: NetworkManager state is now CONNECTED_SITE
Jan 31 08:20:12 myhostname NetworkManager[662]: <info> [1675149612.7914] device (eno1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 31 08:20:12 myhostname NetworkManager[662]: <info> [1675149612.7913] device (eno1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 31 08:20:12 myhostname NetworkManager[662]: <info> [1675149612.7482] device (eno1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 31 08:20:12 myhostname NetworkManager[662]: <info> [1675149612.7446] policy: set 'Kabelgebundene Verbindung 1' (eno1) as default for IPv4 routing and DNS
Jan 31 08:20:12 myhostname NetworkManager[662]: <info> [1675149612.7443] dhcp4 (eno1): state changed new lease, address=192.168.1.148
Jan 31 08:20:07 myhostname NetworkManager[662]: <info> [1675149607.4344] device (eno1): carrier: link connected
Jan 31 08:20:01 myhostname NetworkManager[662]: <info> [1675149601.4097] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Jan 31 08:20:01 myhostname NetworkManager[662]: <info> [1675149601.4093] device (eno1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jan 31 08:20:01 myhostname NetworkManager[662]: <info> [1675149601.4089] device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 31 08:20:01 myhostname NetworkManager[662]: <info> [1675149601.4088] manager: NetworkManager state is now CONNECTING
Jan 31 08:20:01 myhostname NetworkManager[662]: <info> [1675149601.4087] device (eno1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 31 08:20:01 myhostname NetworkManager[662]: <info> [1675149601.4087] device (eno1): Activation: starting connection 'Kabelgebundene Verbindung 1' (46cbf47f-c14c-31a1-9382-03b962bdd79a)
Jan 31 08:20:01 myhostname NetworkManager[662]: <info> [1675149601.4084] policy: auto-activating connection 'Kabelgebundene Verbindung 1' (46cbf47f-c14c-31a1-9382-03b962bdd79a)
Jan 31 08:20:01 myhostname NetworkManager[662]: <info> [1675149601.4079] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Jan 31 08:20:01 myhostname NetworkManager[662]: <info> [1675149601.4077] device (eno1): carrier: link connected
Jan 31 08:19:58 myhostname NetworkManager[662]: <info> [1675149598.5984] manager: startup complete
Jan 31 08:19:54 myhostname NetworkManager[662]: <info> [1675149594.7304] agent-manager: agent[67b075c4f395eda8,:1.23/org.gnome.Shell.NetworkAgent/1000]: agent registered
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5966] modem-manager: ModemManager available
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5959] ovsdb: disconnected from ovsdb
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5211] device (eno1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5211] settings: (eno1): created default wired connection 'Kabelgebundene Verbindung 1'
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5204] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5197] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5196] device (lo): carrier: link connected
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5196] dhcp: init: Using DHCP client 'internal'
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5192] settings: Loaded settings plugin: keyfile (internal)
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5184] manager: Networking is enabled by state file
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5183] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5180] manager: rfkill: Wi-Fi enabled by radio killswitch; disabled by state file
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5175] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.40.10-1/libnm-device-plugin-wwan.so)
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5167] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.40.10-1/libnm-device-plugin-wifi.so)
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5156] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.40.10-1/libnm-device-plugin-team.so)
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5068] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.40.10-1/libnm-device-plugin-ovs.so)
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5063] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.40.10-1/libnm-device-plugin-bluetooth.so)
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5047] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.40.10-1/libnm-device-plugin-adsl.so)
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5031] manager[0x55990ceb1090]: rfkill: WWAN hardware radio set enabled
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5031] manager[0x55990ceb1090]: rfkill: Wi-Fi hardware radio set disabled
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5029] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5027] hostname: static hostname changed from (none) to "myhostname"
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.5026] hostname: hostname: using hostnamed
Jan 31 08:19:52 myhostname systemd[1]: Started Network Manager.
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.4603] manager[0x55990ceb1090]: monitoring kernel firmware directory '/lib/firmware'.
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.4591] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.4582] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Jan 31 08:19:52 myhostname NetworkManager[662]: <info> [1675149592.4582] NetworkManager (version 1.40.10-1) is starting... (boot:5dd0ae9a-f1f2-4a64-9223-c535d1b5c092)
Jan 31 08:19:52 myhostname systemd[1]: Starting Network Manager...
systemd-analyze
Startup finished in 27.149s (firmware) + 35.207s (loader) + 13.912s (kernel) + 23.020s (userspace) = 1min 39.289s
graphical.target reached after 23.020s in userspace.
This is not exactly a speedy boot process you have there. That doesn’t necessarily indicate an issue, but if you have a slow boot process then having to wait a few seconds for services to be up is perfectly normal.
I don’t see any issues here. The network devices look like they are coming right up.
Let’s back up for a moment:
What specifically are you doing that has led you to this conclusion? Are you just opening a browser and it takes a while to load, or something else?
If you are opening a browser and you have to wait ten or fifteen seconds until it loads, that could be related to the slow boot time and a bottleneck when you launch the desktop environment (as opposed to an issue with establishing a network connection).
Test by booting, then instead of logging in on the GDM screen, switch to a TTY (Ctrl+Alt+F3) and test if you are WAN connected by sending a ping to archlinux.org (or whatever connectivity test you like).
I noticed this both through the browser (it is not loading the page but directly hits the “Unable to connect” screen) as well as Nextcloud Sync App which is not capable of synchronizing during that time frame. When that time frame is over, everything works as it should.
The boot-up time is not really a concern for me. However, since you deem it slow, do you have any resources I can read up on or suggestions on how to improve that? The hardware is brand new and should be up and atom
Since I am using full disk encryption, I activated auto-login. So not sure how to boot directly into a TTY. But I will try that next.
