You are not logged in.
Trying to install arch on my Dell Latitude E6230 I run into a problem.
After having booted from the live usb, one of the first things I try, as per the installation guide, is to ping the internet to see that I have a valid connection.
ping -c 3 archlinux.org
This outputs the following
ping: archlinux.org: Name or service not known
This is not the first time I install arch on this particular pc, nor is it the first time I come across this problem. Earlier today I had the same problem, but then it suddenly worked fine, and kept working fine for as long as i ran arch.
Now, I am new to arch and want to set it up again since I want to make some changes during setup. And this time I came across this problem.
My internet connection is fine, I run the computer I write this message on from the same switch and I have tried to cross cables between the two without luck.
When I run
ip a
I get
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether f0:1f:af:10:e3:ea brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 172.16.218.82/23 brd 172.16.219.255 scope global dynamic eno1
valid_lft 604469sec preferred_lft 604469sec
inet6 fe80::f21f:afff:fe10:e3ea/64 scope link
valid_lft forever preferred_lft forever
3: wwp0s29u1u6i6: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 1a:ea:b4:01:6e:89 brd ff:ff:ff:ff:ff:ff
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 3c:a9:f4:37:1e:e4 brd ff:ff:ff:ff:ff:ff
From what I understand after doinf some investigating online, I understand that my ethernet adapter is the one marked
2: eno1
and that the
UP
in
BROADCAST,MULTICAST,UP,LOWER_UP
indicates that my adapter is up and running.
But from there I'm quite lost and need help.
Thanks to Trilby for pointing out that I needed to make my post a lot clearer.
Regards
/Jon
Last edited by jole (2020-06-14 17:03:58)
Offline
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Of course, thank you. My apologies for being a bit hasty there.
Offline
Thanks for the edits, that's much better.
Now we can see that not only is the interface up, but there is also a connection. This suggests that the problem may just be name resolution. Can you ping IP addresses, e.g., `ping 8.8.8.8`?
If so, please post the content of /etc/resolve.conf.
Last edited by Trilby (2020-06-10 21:22:50)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Thanks for a quick reply Trilby.
Yes, I'm able to ping 8.8.8.8
The contents of /etc/resolve.conf (the comments aside) are as follows:
nameserver 127.0.0.53
options edns0
Last edited by jole (2020-06-10 21:36:22)
Offline
So that's the problem. I've never used nor understood systemd-resolved which is likely what is in use on the iso now, so I can't help with a direct solution. But simple workarounds could either be shut down the systemd services and just run dhcpcd, or - alternatively - just append another nameserver to /etc/resolve.conf, e.g.
echo "nameserver 8.8.8.8" >> /etc/resolve.conf
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Ok, thanks.
I'll try your suggestion. I'll continue tomorrow if it doesn't work.
Offline
Started fresh today, trying to figure this one out.
Tinkered for about a few hour or so, and even though I've tried this on several occasions during the last hours it finally woked. I am not quite sure what did the trick, but here's what i did:
systemctl stop systemd-resolved.service
dhcpcd
Thank you Trilby for taking the time, much appreciated.
[Edit]
To satisfy my own curiosity I repeated the task several times. and it worked as described here every time. From my point of view, this issue is solved.
/Jon
Last edited by jole (2020-06-11 19:31:02)
Offline