Arch Linux

ravis

Member

Registered: 2014-05-17

Posts: 3

Unable to connect to internet post-installation reboot

Hello Everyone,

So I somehow managed to install Arch linux successfully. At the time of installation, I followed the official guide as well as this guide.

During the installation, I had successfully connected to wireless by the mentioned method in the guide and was able to install packages.

I issued following commands to stay connected to internet after reboot:
# systemctl enable dhcpcd.service
# systemctl start dhcpcd.service

Now when I do the first reboot, I am unable to connect to internet. I tried all the ways mentioned in both the guides. Here is the screenshot of my terminal :

(Link to the screenshot if you are unable to see above one: http://s13.postimg.org/p4e7mqcyt/photo_2.jpg)

As you can see, the command "ip link show wlp4s0" indicated that the interface is UP. But still I am not connected to the internet i.e. Ping to google fails. I am unable to install any new packages because of this. (No pacman)

What is going wrong in my steps? How should I proceed? Any help is appreciated.

Thank you.

Ravi

---

What if the cure for cancer is trapped inside the mind of someone who can't afford an education?

torors

Member

Registered: 2012-09-28

Posts: 107

Re: Unable to connect to internet post-installation reboot

wlp4s0 is not up. If you read the whole line, you will find "state DOWN". Try to put up your card manualy. Or you can boot from the DVD and chroot into your system like you did during installation. Then you can install netctl, wicd or network-manager.

Last edited by torors (2014-05-17 10:07:17)

Shark

Member

From: /dev/zero

Registered: 2011-02-28

Posts: 686

Re: Unable to connect to internet post-installation reboot

You shouldn't start dhcpd service if you use wifi-menu (that meas netctl). First of - do:

systemctl disable dhcpcd.service
systemctl stop dhcpcd.service

Then do wifi-menu.

Last edited by Shark (2014-05-17 11:14:36)

---

If you have built castles in the air, your work need not be lost; that is where they should be. Now put foundations under them.
Henry David Thoreau

Registered Linux User: #559057

ravis

Member

Registered: 2014-05-17

Posts: 3

Re: Unable to connect to internet post-installation reboot

@shark, @torros Thanks for your reply.

I misunderstood by reading the first UP. Sorry about that.

If I boot from the live disk to chroot, first I've to mount the root drive. Problem is, I had installed Arch on /dev/sdbX and fstab had the entries accordingly. But now they are shown as /dev/sdaX and there is no fstab file. Why this problem? How do I proceed from here? (I don't want to risk generating a new fstab)

Automatic wifi - I had installed "dialog" in the installation process. But now after the reboot, if I try wifi-menu command to connect, it is again asking me install dialog. Why it is failing to detect previously installed dialog?

Manual wifi - In the installation, I did the netctl profile settings which should have become permanent (post reboot) as per the tutorial.  But it's not the case.
I have even tried connecting manually using the netctl profile after the reboot. Still no luck.

Please guide.

Thanks again.
---------

UPDATE: Following is what I'm getting when I start a profile using netctl. It shows my wifi profile as well. See if it can help.

(Link to screenshot: http://s14.postimg.org/67wjfqddr/photo.jpg)

Last edited by ravis (2014-05-17 13:55:58)

---

What if the cure for cancer is trapped inside the mind of someone who can't afford an education?

torors

Member

Registered: 2012-09-28

Posts: 107

Re: Unable to connect to internet post-installation reboot

What do you mean "there is no fstab file"? Look in /etc.

May be this link is helpful, it solved a similar problem for me:
https://wiki.archlinux.org/index.php/ne … ice_failed

Last edited by torors (2014-05-17 15:41:27)

Shark

Member

From: /dev/zero

Registered: 2011-02-28

Posts: 686

Re: Unable to connect to internet post-installation reboot

Automatic wifi - I had installed "dialog" in the installation process. But now after the reboot, if I try wifi-menu command to connect, it is again asking me install dialog. Why it is failing to detect previously installed dialog?

Have you chroot? And install the package in chroot environment? If you had then the dialog should be installed.

Also, look in Archwik for manual connection. Create a file for your wireless from examples. See here:
https://wiki.archlinux.org/index.php/Ne … figuration

As @torors said, look in /etc. I hardly believe that you don't have the fstab because otherwise you couldn't boot. the OS.

Last edited by Shark (2014-05-18 09:31:05)

---

If you have built castles in the air, your work need not be lost; that is where they should be. Now put foundations under them.
Henry David Thoreau

Registered Linux User: #559057

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: Unable to connect to internet post-installation reboot

I hardly believe that you don't have the fstab because otherwise you couldn't boot. the OS.

You can boot without fstab as long as you pass correct partition to kernel in bootloader config with root=<partition>

I think it's possible that during installation your install media got recognized as sda and that's why the disk where you installed to was sdb.
If you're absolutely sure the disk is sda in your installation you should change fstab accordingly, or replace the /dev/sdXX entries with UUIDs

EDIT. sorry I misunderstood the situation. you could still use UUIDs if you're unsure of the device though

Last edited by ooo (2014-05-18 08:14:13)

mindstalk

Member

Registered: 2014-05-16

Posts: 23

Re: Unable to connect to internet post-installation reboot

I also had wifi problems with a recent install.  I don't know if my issues are yours, but for what it's worth:

In my /etc/wpa_supplicant.conf file I'd misspelled my network name, the ssid value.  Oops!  More subtly, the generated file had two psk lines: one commented out, with my actual passphrase, and one with some giant alphanumeric string.  Switching one was commented out was part of the solution.  Finally, I found I had two background wpa_supplicant processes, and two many processes generates conflicts.  Killing those was part of the solution; unfortunately I don't remember the rest in detail, but I probably started a new wpa_supplicant after that.

Right now my relevant processes up are
root       279     1  0 May16 ?        00:00:00 /usr/bin/dhcpcd -q -b

and
root       369     1  0 May16 ?        00:00:08 wpa_supplicant -B -P /run/wpa_supplicant_wlp2s0.pid -i wlp2s0 -D nl80211,wext -c/run/network/wpa_supplicant_wlp2s0.conf -W

...though I see from your second screenshot that you seem to be using WEP, not WPA, as your wifi security, so most of what I said won't be relevant.  But checking what processes are running and double-checking your config files might be.
root       374     1  0 May16 ?        00:00:04 wpa_actiond -p /run/wpa_supplicant -i wlp2s0 -P /run/network/wpa_actiond_wlp2s0.pid -a /usr/lib/network/auto.action

not that I started those by hand... wlp2s0 is my wifi device; yours seems different.