You are not logged in.
hiya
first off i should probably say that im not using (and dont intend on using) any wireless connection, this issue is about my ethernet bc my pc is pretty massive and is not moving a lot
so recently i moved and plugged in my ethernet and at first it worked, but on every restart the internet breaks despite network manager showing that it is infact connected, i just dont get traffic and cannot connect to anywebsite, for some reason fiddling with systemctl settings occationally fixes it, like one time i restarted dhcpcd@enp4s0 and then it magically came back online, im so lost rn i really dont know what to do, but its not consistent, there have been occations where i have been doing basically nothing and the internet has came back up
im worried it could be something to do with the fact i use a Realtek ethernet driver and gigabyte motherboard which the wiki says can cause bugs and that IOMMU needs to be started on boot but firstly, it seems to do that i need to get grub setup but ive seen the setup for it with partitioning and id rather stay far away from that, especially considering the issue could be considerably more simple
i have searched through the wiki but all bug fixes lead to a dead end, the journalctl is so daunting i dont know which errors are the actual issue here. anyone plz helpp
Offline
one time i restarted dhcpcd@enp4s0 and then it magically came back online
If you're using NetworkManager you shouldn't have any other networking services enabled. Disable that service and any others that might conflict with NM.
It would also be helpful if your posts were more concise. It would have been easy to miss that detail ![]()
Jin, Jîyan, Azadî
Offline
apologies
i feel like such an idiot rn, especially considering i literally read that part on the wiki and tried it and clearly i didnt do it correctly bc i just now went through and disabled basically every systemctl service network manager apart from the actual NM and it works upon restart. I seriously thought i tried that before
thanks so much bc i was loosing hope, im still amazed at how i messed that up before, solved!! ?
Last edited by Toodths (2024-09-15 10:10:20)
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Online
~ full post quote
nothin to be sorry for - for me it's the packages not exclude themslefs via dependency conflicts and allowed to be installed along eachother in the first place
so - someone might ask: why waste all those years asking for conflicting services and tell people how to do it right instead of open issues so conflicts get added to the package? has someone? were these requests denied? if so: why? or upside-down: what's the point in allow conflicting packages to be installed along eachother?
Offline
what's the point in allow conflicting packages to be installed along eachother?
To give one example: in case the user wants to switch networking tools. It's a bit difficult to install new packages if the networking software is broken...
Arch shouldn't enable services by default[1] so the various networking packages only "conflict" with each other's services if the user enables them by mistake.
[1] Don't get me started on the keyring... ![]()
Jin, Jîyan, Azadî
Offline
iwd/wpa_supplicant, dhcpcd/dhclient, networkmanager/networkd/netctl can work together or be in conflict - if I want to install dhcpcd and dhclient to test them as dhcp backends for NM, do you want to deny that?
iwd can serve as backend for NM, provide the carrier for networkd, work by itself or along any dhcp client (which is more or less desireable depending on whether there's also a wired NIC).
Then a system might be used by multiple individuals with different preferences and ultimate, networkd is part of the systemd moloch. So NM, netctl and dhc* are always "conflicted".
networkd however requires an external wifi carrier, but if you install iwd, you can bring it into conflict w/ networkd.
So basically, we can just have systemd and wpa_supplicant in the repos.
Arch doesn't promote or preconfigure a setup, but the flipside of that is the necessity of a competent user.
Online