[SOLVED] Ethernet not connecting, kernel states ethernet is down.

Monarchalia · Yesterday 20:48:55

now i know this is my kernel being a royal pain...
Dec 27 18:19:21 HIVEMIND systemd[1]: Started Wireless service.
Dec 27 18:19:21 HIVEMIND nvidia-powerd[793]: ERROR! Failed to get SysPwrLimitGetInfo!!
Dec 27 18:19:21 HIVEMIND nvidia-powerd[793]: ERROR! Client (presumably SBIOS) has requested to disable Dynamic Boost DC controller
Dec 27 18:19:21 HIVEMIND systemd-networkd[470]: enp3s0: Link UP
Dec 27 18:19:21 HIVEMIND kernel: r8169 0000:03:00.0 enp3s0: Link is Down
Dec 27 18:19:21 HIVEMIND dhcpcd[712]: enp3s0: waiting for carrier
Dec 27 18:19:21 HIVEMIND NetworkManager[700]: <info> [1766877561.8295] manager[0x55b7cb9baa50]: monitoring kernel firmware directory '/lib/firmware'.

I've tried some solutions around, namely the realtek bugs of the same board/driver (https://wiki.archlinux.org/title/Networ … 8111/8168B)
and took a gander at this one(https://bbs.archlinux.org/viewtopic.php?id=260219), I'm working on a full systemctl log now...
will upload shortly.
https://0x0.st/PiEL.txt

Last edited by Monarchalia (Today 00:36:29)

Scimmia · Yesterday 20:58:16

Why do you have systemd-networkd, NetworkManager, and dhcpcd all running? What does `tree /etc/systemd/` show? You should only have one network management daemon enabled.

Monarchalia · Yesterday 21:06:44

I killed dhcpcd, the other 2 arent the same?

I will get you a response in about 30 minutes to the other thing...

Last edited by Monarchalia (Yesterday 21:08:01)

seth · Yesterday 21:14:13

the other 2 arent the same?

No, and you've also iwd and wpa_supplicant dogging on the wifi NIC.

Killing processes isn't a solution, you'll have to disable the services.
If you want to use iwd as NM backend see https://wiki.archlinux.org/title/Networ … Fi_backend and for dhcpcd as dhcp client https://wiki.archlinux.org/title/Networ … HCP_client
But don't enable or manually start any of those!

Monarchalia · Yesterday 21:29:51

output of tree /etc/systemd/

/etc/systemd/
├── coredump.conf
├── homed.conf
├── journald.conf
├── journal-remote.conf
├── journal-upload.conf
├── logind.conf
├── network
├── networkd.conf
├── oomd.conf
├── pstore.conf
├── resolved.conf
├── resolved.conf.pacnew
├── sleep.conf
├── system
│   ├── bluetooth.target.wants
│   │   └── bluetooth.service -> /usr/lib/systemd/system/bluetooth.service
│   ├── dbus-org.bluez.service -> /usr/lib/systemd/system/bluetooth.service
│   ├── dbus-org.freedesktop.nm-dispatcher.service -> /usr/lib/systemd/system/NetworkManager-dispatcher.service
│   ├── dbus-org.freedesktop.resolve1.service -> /usr/lib/systemd/system/systemd-resolved.service
│   ├── display-manager.service -> /usr/lib/systemd/system/sddm.service
│   ├── getty.target.wants
│   │   ├── getty@tty1.service -> /usr/lib/systemd/system/getty@.service
│   │   └── supergfxd.service -> /usr/lib/systemd/system/supergfxd.service
│   ├── graphical.target.wants
│   │   └── power-profiles-daemon.service -> /usr/lib/systemd/system/power-profiles-daemon.service
│   ├── httpd.service.d
│   │   └── hardening.conf
│   ├── multi-user.target.wants
│   │   ├── dhcpcd@enp3s0.service -> /usr/lib/systemd/system/dhcpcd@.service
│   │   ├── httpd.service -> /usr/lib/systemd/system/httpd.service
│   │   ├── iwd.service -> /usr/lib/systemd/system/iwd.service
│   │   ├── mariadb.service -> /usr/lib/systemd/system/mariadb.service
│   │   ├── NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
│   │   ├── remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
│   │   ├── snapd.service -> /usr/lib/systemd/system/snapd.service
│   │   ├── var-lib-snapd-snap-arduino-85.mount -> /etc/systemd/system/var-lib-snapd-snap-arduino-85.mount
│   │   ├── var-lib-snapd-snap-bare-5.mount -> /etc/systemd/system/var-lib-snapd-snap-bare-5.mount
│   │   ├── var-lib-snapd-snap-core18-2976.mount -> /etc/systemd/system/var-lib-snapd-snap-core18-2976.mount
│   │   ├── var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-198.mount -> /etc/systemd/system/var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-198.mount
│   │   ├── var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1535.mount -> /etc/systemd/system/var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1535.mount
│   │   └── var-lib-snapd-snap-snapd-25577.mount -> /etc/systemd/system/var-lib-snapd-snap-snapd-25577.mount
│   ├── network-online.target.wants
│   │   └── NetworkManager-wait-online.service -> /usr/lib/systemd/system/NetworkManager-wait-online.service
│   ├── snapd.mounts.target.wants
│   │   ├── var-lib-snapd-snap-arduino-85.mount -> /etc/systemd/system/var-lib-snapd-snap-arduino-85.mount
│   │   ├── var-lib-snapd-snap-bare-5.mount -> /etc/systemd/system/var-lib-snapd-snap-bare-5.mount
│   │   ├── var-lib-snapd-snap-core18-2976.mount -> /etc/systemd/system/var-lib-snapd-snap-core18-2976.mount
│   │   ├── var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-198.mount -> /etc/systemd/system/var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-198.mount
│   │   ├── var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1535.mount -> /etc/systemd/system/var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1535.mount
│   │   └── var-lib-snapd-snap-snapd-25577.mount -> /etc/systemd/system/var-lib-snapd-snap-snapd-25577.mount
│   ├── sockets.target.wants
│   │   ├── polkit-agent-helper.socket -> /usr/lib/systemd/system/polkit-agent-helper.socket
│   │   └── systemd-userdbd.socket -> /usr/lib/systemd/system/systemd-userdbd.socket
│   ├── sysinit.target.wants
│   │   └── systemd-resolved.service -> /usr/lib/systemd/system/systemd-resolved.service
│   ├── systemd-hibernate.service.wants
│   │   ├── nvidia-hibernate.service -> /usr/lib/systemd/system/nvidia-hibernate.service
│   │   └── nvidia-resume.service -> /usr/lib/systemd/system/nvidia-resume.service
│   ├── systemd-suspend.service.wants
│   │   ├── nvidia-resume.service -> /usr/lib/systemd/system/nvidia-resume.service
│   │   └── nvidia-suspend.service -> /usr/lib/systemd/system/nvidia-suspend.service
│   ├── systemd-suspend-then-hibernate.service.wants
│   │   └── nvidia-resume.service -> /usr/lib/systemd/system/nvidia-resume.service
│   ├── var-lib-snapd-snap-arduino-85.mount
│   ├── var-lib-snapd-snap-bare-5.mount
│   ├── var-lib-snapd-snap-core18-2976.mount
│   ├── var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-198.mount
│   ├── var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1535.mount
│   └── var-lib-snapd-snap-snapd-25577.mount
├── system.conf
├── timesyncd.conf
├── user
│   ├── graphical-session-pre.target.wants
│   │   └── xdg-user-dirs.service -> /usr/lib/systemd/user/xdg-user-dirs.service
│   ├── pipewire.service.wants
│   │   └── wireplumber.service -> /usr/lib/systemd/user/wireplumber.service
│   ├── pipewire-session-manager.service -> /usr/lib/systemd/user/wireplumber.service
│   └── sockets.target.wants
│       ├── p11-kit-server.socket -> /usr/lib/systemd/user/p11-kit-server.socket
│       ├── pipewire-pulse.socket -> /usr/lib/systemd/user/pipewire-pulse.socket
│       └── pipewire.socket -> /usr/lib/systemd/user/pipewire.socket
└── user.conf

in terms of backend stuff, neither iwd nor dhcpcd are being used as backend.
at this point I am absolutely chuffed to bits about how my network is functioning while being this contested... .

Note: turns out iwd is in fact the backend... I've stopped wpa_supplicant dhcpcd and networkd

Last edited by Monarchalia (Yesterday 21:33:38)

seth · Yesterday 21:39:08

Note: turns out iwd is in fact the backend... I've stopped wpa_supplicant dhcpcd and networkd

No.

│   │   ├── iwd.service -> /usr/lib/systemd/system/iwd.service

The service was enabled.
Deactivate that and configure NM to use iwd isntead of wpa_supplicant.
Then

I've stopped wpa_supplicant dhcpcd and networkd

Let's see:

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Monarchalia · Yesterday 21:49:56

oh wait bad log, I didn't reload arch.

http://0x0.st/PiIL.txt

Last edited by Monarchalia (Yesterday 21:52:33)

seth · Yesterday 21:54:53

dhcpcd@enp3s0.service                    | multi-user.target.wants
iwd.service                              | multi-user.target.wants

are still enabled, rebooting will not change that.

Monarchalia · Yesterday 21:58:06

Alright, I was today years old when i learned you have to put .service on the end... my bad.
http://0x0.st/PiIW.txt
Fresh out of the oven, all of them are gone.
alright so my internet dies whenever i disable iwd.service, so I'll have it enabled in interim periods till we get this figured out, I apologize for my lack of skill, usually it just works for me... was until i left for college at least.

Last edited by Monarchalia (Yesterday 22:02:03)

seth · Yesterday 22:01:05

you have to put .service on the end...

Typically not.
Did you also stop them?

systemctl status iwd

If yes, only NM and either iwd (iff cofigured) XOR wpa_supplicant should be running.

Monarchalia · Yesterday 22:03:32

iwd is not stopped, wpa_supplicant is (now)
due to me losing internet if i stop iwd, I'm leaving it on till I can get ethernet again

Scimmia · Yesterday 22:36:55

So you're using IWD, what are you using NM for? How do you actually want all of this to work?

Monarchalia · Yesterday 22:39:37

I use NM for interface, I know how to setup my school networks via NM gui... but anyways I need ethernet to work and the problem is originally my ethernet would connect then immediately disconnect, I need ethernet to work asap because it's my only real good network option due to my distance from my router.

seth · Yesterday 22:43:45

Disable the iw.service and either configure https://wiki.archlinux.org/title/Networ … Fi_backend or use wpa_supplicant, add a profile w/ NM

I need ethernet to work asap because it's my only real good network option due to my distance from my router.

Errrrr… wut?

Either way, your network issues most likely stem from the various services playing

So sort that out and then report back w/ an updated status quo and in doubt system journal.

Monarchalia · Yesterday 23:28:59

http://0x0.st/Pill.txt

Finished and cleaned shop

here's service list: http://0x0.st/PilU.txt

At this time, I previously had ethernet, but now the interface for it has disappeared.

seth · Yesterday 23:42:54

wpa_supplicant.service                   | multi-user.target.wants

Why is that now enabled?
NM will trigger these programs itself, stop making things more complicated then they are.
Then there's a complete mess of starting and stopping iwd in the journal
Disable wpa_supplicant.service and keep iwd and dhcpcd* disabled!
Reboot to the point where you'd expect to have network w/o messing around w/ the system.
Dump the journal:

sudo journalctl -b > /tmp/journal.txt

Then do what you feel you must to get a network connection and post the journal

cat /tmp/journal.txt | curl -F 'file=@-' 0x0.st

Monarchalia · Yesterday 23:50:38

http://0x0.st/Pilh.txt

wpa_supplicant is now fully disabled too.

seth · Yesterday 23:56:00

Dec 28 18:46:35 HIVEMIND iwd[792]: event: connect-info, ssid: HOT612, bss: dc:eb:69:71:43:b8, signal: -57, load: 0/255
Dec 28 18:46:35 HIVEMIND iwd[792]: event: state, old: autoconnect_quick, new: connecting (auto)
Dec 28 18:46:35 HIVEMIND NetworkManager[686]: <info>  [1766965595.5244] device (wlan0): new IWD device state is connecting
Dec 28 18:46:35 HIVEMIND NetworkManager[686]: <info>  [1766965595.5247] device (wlan0): Activation: starting connection 'HOT612' (a745066c-cdcb-4815-99a0-568c0fc268e5)
Dec 28 18:46:35 HIVEMIND NetworkManager[686]: <info>  [1766965595.5250] device (wlan0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Dec 28 18:46:35 HIVEMIND NetworkManager[686]: <info>  [1766965595.5251] manager: NetworkManager state is now CONNECTING
Dec 28 18:46:35 HIVEMIND NetworkManager[686]: <info>  [1766965595.5252] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Dec 28 18:46:35 HIVEMIND iwd[792]: event: state, old: connecting (auto), new: connecting (netconfig)
Dec 28 18:46:35 HIVEMIND NetworkManager[686]: <info>  [1766965595.5845] device (wlan0): new IWD device state is connecting
Dec 28 18:46:37 HIVEMIND NetworkManager[686]: ((../NetworkManager/src/libnm-systemd-core/src/libsystemd/sd-event/sd-event.c:4488)): assertion '<dropped>' failed
Dec 28 18:46:39 HIVEMIND iwd[792]: event: state, old: connecting (netconfig), new: connected
Dec 28 18:46:39 HIVEMIND NetworkManager[686]: <info>  [1766965599.5294] device (wlan0): new IWD device state is connected
Dec 28 18:46:39 HIVEMIND NetworkManager[686]: <info>  [1766965599.5296] device (wlan0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Dec 28 18:46:39 HIVEMIND NetworkManager[686]: <info>  [1766965599.5302] policy: set 'HOT612' (wlan0) as default for IPv4 routing and DNS
Dec 28 18:46:39 HIVEMIND NetworkManager[686]: <info>  [1766965599.5302] policy: set 'HOT612' (wlan0) as default for IPv6 routing and DNS
Dec 28 18:46:39 HIVEMIND NetworkManager[686]: <info>  [1766965599.5366] device (wlan0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Dec 28 18:46:39 HIVEMIND NetworkManager[686]: <info>  [1766965599.5376] device (wlan0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Dec 28 18:46:39 HIVEMIND NetworkManager[686]: <info>  [1766965599.5377] device (wlan0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Dec 28 18:46:39 HIVEMIND NetworkManager[686]: <info>  [1766965599.5378] manager: NetworkManager state is now CONNECTED_SITE
Dec 28 18:46:39 HIVEMIND NetworkManager[686]: <info>  [1766965599.5379] device (wlan0): Activation: successful, device activated.
Dec 28 18:46:41 HIVEMIND NetworkManager[686]: <info>  [1766965601.9116] manager: NetworkManager state is now CONNECTED_GLOBAL

So what makes you believe to not have internet access at this point?
Can you "ping _gateway"?

Monarchalia · Today 00:01:12

yeah i pinged gateway, easy pass...
I have internet, the issue is my ethernet isn't connecting at all. before i opened this at least it would connect for a second, but now not at all... the interface for ethernet (eth3s0 whatever the heck) is also now missing..

seth · Today 00:05:05

WAHHHHH … ok: there is no ethernet device at all.

lspci -k

And because of your partitions most likely see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Monarchalia · Today 00:23:11

I haven't used windows in 2 years mate xD. (does not exist on device)

http://0x0.st/PiUP.txt

like i said, I had it before with the mishmosh of connection managers i had installed, im pretty sure dhcpcd actually did that xD

Last edited by Monarchalia (Today 00:29:04)

Scimmia · Today 00:29:21

Does `modprobe r8169` change anything?

Monarchalia · Today 00:35:08

no way, that was it!

seth · Today 00:45:39

That's transient behavior, you've likely blacklisted the module.

modprobe -c | grep -v alias | grep r816

Monarchalia · Today 00:46:20

it appears so, let me resolve that!

edit: resolved!

Last edited by Monarchalia (Today 00:48:29)

Arch Linux

#1 Yesterday 20:48:55

[SOLVED] Ethernet not connecting, kernel states ethernet is down.

#2 Yesterday 20:58:16

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#3 Yesterday 21:06:44

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#4 Yesterday 21:14:13

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#5 Yesterday 21:29:51

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#6 Yesterday 21:39:08

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#7 Yesterday 21:49:56

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#8 Yesterday 21:54:53

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#9 Yesterday 21:58:06

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#10 Yesterday 22:01:05

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#11 Yesterday 22:03:32

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#12 Yesterday 22:36:55

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#13 Yesterday 22:39:37

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#14 Yesterday 22:43:45

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#15 Yesterday 23:28:59

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#16 Yesterday 23:42:54

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#17 Yesterday 23:50:38

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#18 Yesterday 23:56:00

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#19 Today 00:01:12

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#20 Today 00:05:05

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#21 Today 00:23:11

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#22 Today 00:29:21

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#23 Today 00:35:08

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#24 Today 00:45:39

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

#25 Today 00:46:20

Re: [SOLVED] Ethernet not connecting, kernel states ethernet is down.

Board footer