You are not logged in.
I'm trying to install Arch Linux from scratch following the official installation guide. Although an Ethernet connection is recommended, my computer doesn't have an Ethernet port, so I must use wifi. I successfully connected to wifi using the wifi-menu command, but when I try to ping any site this happens:
ping google.com
ping: google.com: Name or service not known
Any help is appreciated.
Last edited by Dincio (2020-07-01 15:16:25)
Offline
Can you "ping 8.8.8.8"?
What's the output of
ip a
ip r
stat /etc/resolv.conf
cat /etc/resolv.conf
?
Offline
Can you "ping 8.8.8.8"?
I get the same result as any domain name (ping: connect: Name or service not known)
What's the output of [...]
https://i.ibb.co/7X3Jpcy/photo6039347781027607019.jpg
This image is the best I can do without resorting to manual copying... which I would really like to use as a last resort. Of course I would be glad to know if there's a more efficient way of extracting text from the terminal.
moderator edit -- replaced oversized image with link.
Pasting pictures and code
Last edited by 2ManyDogs (2020-06-29 16:01:31)
Offline
You don't seem to have run the wifi-menu command (successfully) as there are no IP addresses configured on the device nor appropriate routes.
Either that or your local network does not have a (working) DHCP server. Do you set IP addresses manually?
Last edited by schard (2020-06-29 15:41:51)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Why is resolve.conf the systemd-resolved'ohh symlink? Does the installation iso now use systemd-networkd or networkmanager instead of wifi-menu/netctl?
Something brought the interface up, that was probably not wifi-menu (because it should™ have brought it down with the failure) and in that case: wifi-menu will not try to control an active NIC.
Offline
@seth: The latest Arch ISO was migrated from dhcpcd to systemd-networkd.
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
You don't seem to have run the wifi-menu command (successfully) as there are no IP addresses configured on the device nor appropriate routes.
I don't know how to determine weather wifi-menu worked or not... (on the installation guide it said only to check it with the ping command). I tried to document my usage of wifi-menu below in hope it will give an insight into the problem:
Uhttps://i.ibb.co/1XD4wz5/photo6042033552926815501.jpg
https://i.ibb.co/TK58Xfm/photo6042033552926815502.jpg
https://i.ibb.co/xFcQdmq/photo6042033552926815503.jpg
https://i.ibb.co/XkkPDPX/photo6042033552926815504.jpg
https://i.ibb.co/b1CSscP/photo6042033552926815505.jpg
https://i.ibb.co/LztjRzB/photo6042033552926815506.jpg
Either that or your local network does not have a (working) DHCP server.
I read the beginning sections of https://wiki.archlinux.org/index.php/dh … stallation and tried to start dhcpcd with
systemctl start dhcpcd.service
before running wifi-menu, but nothing changed...
This is the output of
systemctl status dhcpcd.service
, in case it helps at all:
https://i.ibb.co/HFPPcrL/photo6042033552926815515.jpg
Do you set IP addresses manually?
I never had to manually configure any ip address (wifi works on my previous Ubuntu desktop).
Offline
You don't need to start dhcpcd on the live iso, since it's been replaced by systemd-networkd as mentioned.
That being said, now that it's up and running on your live system according to the status output you posted and it'd handling then wlan0 interface, which is waiting for a carrier.
If the wifi_menu connection failed, you most likely entered a wrong passphrase for the network.
What happens if you try to connect via wifi-menu now?
Maybe also try to connect via wpa_cli.
Last edited by schard (2020-06-30 14:01:42)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
You don't need to start dhcpcd on the live iso, since it's been replaced by systemd-networkd as mentioned.
Yeah, my bad for not noticing. Would you like it if I rebooted the system and tried to get status info on systemd-netword/resolved?
That being said, now that it's up and running on your live system according to the status output you posted and it'd handling then wlan0 interface, which is waiting for a carrier.
If the wifi_menu connection failed, you most likely entered a wrong passphrase for the network.
What happens if you try to connect via wifi-menu now?
So, to summerize my process until now:
- wifi-menu (I have now noticed that I get a frowny face on the far right of my screen, is it important?).
- ping doesn't work
- systemctl start dhcpcd.service
- wifi-menu
- select my network
output of wifi-menu:
https://i.ibb.co/3hf9H7M/photo6042033552926815519.jpg
Maybe also try to connect via wpa_cli.
Do I need to reboot or can I do this after performing the steps mentioned above?
Offline
The face is a zsh-grml feature telling you that the command failed w/ an error.
- systemctl start dhcpcd.service
- wifi-menu
Don't do that. dhcpcd takes control over the NIC and wifi-menu will refuse to operate it.
I assume what happens is systemd-networkd tries to configure the network, fails but at least brings up the NIC and blocks wifi-menu.
=> Output of
systemctl list-unit-files --state=enabled
Offline
I rebooted the system and just ran wifi-menu wiithout starting dhcpcd.
=> Output of
systemctl list-unit-files --state=enabled
output after running wifi-menu:
https://i.ibb.co/SxsWwP0/photo6042033552926815525.jpg
Last edited by Dincio (2020-06-30 17:07:42)
Offline
As predicted.
"systemctl stop ..." everything systemd-networkd* and systemd-resolved (they might implicitly stop each other and yell errors because you're stopping a non-running service. that's ok) - start wit the socket.
Then remove the /etc.resole.conf symlink an retry wifi-menu.
Offline
As predicted.
"systemctl stop ..." everything systemd-networkd* and systemd-resolved (they might implicitly stop each other and yell errors because you're stopping a non-running service. that's ok) - start wit the socket.
Then remove the /etc.resole.conf symlink an retry wifi-menu.
Unfortunately I still get the same error... here's what I did in details:
- systemctl stop systemd-networkd.socket
- systemctl stop systemd-networkd.service
- systemctl stop systemd-resolved.service
- rm -rf /etc.resole.conf
- wifi-menu
Are you sure you did not make a spelling mistake when mentioning the /etc.resole.conf file? In assuming that you did, I also tried the steps above, but deleting /etc/resolv.conf instead. Still the result was the same.
Offline
Yes, mega-typo, sorry.
After stopping all those services, was the interface still up?
In case you'd also have to bring it down first.
Honestly, just pick a slightly older iso (the may one is ok according to #6) w/o systemd-networkd getting in the way.
This is getting ridiculous.
Alternatively don't do any of this (you cannot use wifi-menu nor dhcpcd) and see whether systemd-networkd actually works if you establish a carrier w/ wpa_cli or wpa_passphrase, https://wiki.archlinux.org/index.php/Wpa_supplicant
Not as convenient as wifi-menu, though.
Offline
ikr i have this issue too, i've been looking for 4 days straight and none of the guide makes me ping into domain, but it can ping to dns like 8.8.8.8.
ping domain just leave empty and stuck there forever.
so i go back to my old iso image which is 2017 on feb, it can easily connected with wifi-menu no more shit, but i can't install archlinux due to invalid archlinux-keyring, upgrading doesn't help because old archlinux use xz while new use zstd.
it's so weird, it's like i''m looping into no where just to install archlinux again.
New ISO image problem with internet.
Old ISO image problem with keyring while internet works perfectly fine.
Last edited by adekmaulana (2020-06-30 20:49:35)
Offline
Try the 2020.07.01 release when it's out as there have been a lot of changes to archiso https://gitlab.archlinux.org/archlinux/ … ts/master/
Last edited by loqs (2020-06-30 20:59:43)
Offline
Or use the 2020.05.01 image (should have functional wifi-menu and not suffer from the keyring issues)
Offline
Or use the 2020.05.01 image (should have functional wifi-menu and not suffer from the keyring issues)
I tried this first and ping finally worked after running wifi-menu! Thanks to everyone for the help.
Offline
Please remember to mark your thread [SOLVED] (edit the title of your first post).
Offline
Please remember to mark your thread [SOLVED] (edit the title of your first post).
Done, sorry forr the newbie mistake.
Offline