You are not logged in.
Pages: 1
So I forgot to add additional networking packages during installation, but I should still able to use internet with static ip?
I tried following
ip address add 192.168.1.2/24 broadcast + dev enp3s0
ip link set enp3s0 up
ip route add default via 192.168.1.1 dev enp3s0
but I'm unable to even ping the router which answers at 192.168.1.1... what do I need to put to the routing tables?
Also keep getting following message in my console... no clue what it means
r8169 0000:03:00.0 enp3s0: rtl_rxtx_empty_cond == 0 (loop: 42 delay: 100).
Last edited by jammer (2020-10-10 22:00:41)
Offline
Read the Wiki, especially Step 4
Offline
Or you could just configure systemd-networkd, as you already have it installed.
Offline
Read the Wiki, especially Step 4
I did read it and you can see I applied the steps mentioned but the network ain't still working
Offline
Did you remember to install the linux-firmware package? Did the ethernet connection work in the live environment? You should probably tell us which ethernet card you have.
keep getting following message in my console
Have you seen https://bugzilla.kernel.org/show_bug.cgi?id=107421?
Jin, Jîyan, Azadî
Offline
Did you remember to install the linux-firmware package? Did the ethernet connection work in the live environment? You should probably tell us which ethernet card you have.
Yes, I believe I installed firmwares. Ethernet wasn't working in live either. The card is on my motherboard Asus Z87-A, which I believe makes it Realtek 8111GR.
Have you seen https://bugzilla.kernel.org/show_bug.cgi?id=107421?
That doesn't look good... but I can say the Ethernet was working fine about year ago in previous Arch installation.
Offline
Or you could just configure systemd-networkd, as you already have it installed.
Ah thanks... still getting used to systemd
I added /etc/network/20-wired.network with
[Match]
Name=enp3s0
[Network]
DHCP=yes
and started networkd with systemctl start systemd-networkd and it just worked!
Kernel/driver also isn't printing stuff to console at the moment... I guess it might happen randomly during bootup sequence.
Last edited by jammer (2020-10-10 21:59:49)
Offline
Pages: 1