Wired and wireless internet not working. Cannot install Arch

eipi · 2014-07-07 15:47:54

Hello everyone,

this is the first time I write something on the forums, so hi to all!

Usually there's already an answer somewhere to fix my problems, but not this time (or I can't seem to find it or know what to look for) So after this last week trying to fix the problem and search on the internet for a solution, I'm going a little crazy. I hope someone can help.

The situation is as follows: I'm trying to reinstall Arch Linux on my old little netbook (Samsung NC10) and I cannot get an internet connection working. Wireless or wired, doesn't matter, it won't work.

Previously (2012-2013) I've had Arch Linux working flawlessly on this same computer and no problems at all. Now that installation is gone, so I cannot boot into it (long story short, I wanted a fresh install so I wiped the hard drive, I couldn't imagine I wasn't going to be able to connect to the internet). The internet also worked if I used USB sticks with Live distros. But now, it doesn't.

So that's the background.

Now what I've tried to do.
- Following the Beginner's Guide: failed
- Set up wireless network manually: failed
- Tried other distros: failed
- Plug in the ethernet cable: failed
- Restart router: failed

I think the most interesting information is the one I got after trying to set up the wireless network manually. So that's what I'll discuss here, so that this post doesn't get to long.

I followed this guide: https://wiki.archlinux.org/index.php/Wi … nual_setup

And everything goes smooth and fine until I have to connect to the network, authenticate, etc. I can scan the wireless networks and get their SSIDs, everything. But when I try to connect, it fails.

I have tried with my home wlan (WPA) and with the wifi network created by my android phone (no protection) for internet sharing. None of the options have worked.

When trying to connect to the unprotected wifi network of the phone, I get this:

# iw dev wlp2s0 connect AndroidAP
# iw dev wlp2s0 link
Not connected.

And when trying to start wpa_supplicant for connecting to my home wireless network, I get something like this:

# wpa_supplicant -i wlp2s0 -c <(wpa_passphrase WLAN_5E19 mywifikey)
Succesfully initialized wpa_supplicant
wlp2s0: CTRL-EVENT-SCAN_STARTED
wlp2s0: SME: Trying to authenticate with ...(SSID='WLAN_5E19' freq=2437MHz)
wlp2s0: CTRL-EVENT-SCAN_STARTED
wlp2s0: CTRL-EVENT-SCAN_STARTED
wlp2s0: SME: Trying to authenticate with ...(SSID='WLAN_5E19' freq=2437MHz)
wlp2s0: CTRL-EVENT-SCAN_STARTED
wlp2s0: CTRL-EVENT-SCAN_STARTED
wlp2s0: SME: Trying to authenticate with ...(SSID='WLAN_5E19' freq=2437MHz)
wlp2s0: Trying to associate with .... (SSID=... freq...)
wlp2s0: CTRL-EVENT-SCAN_STARTED
wlp2s0: SME: Trying to authenticate with ...(SSID='WLAN_5E19' freq=2437MHz)
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WLAN_5E19" auth_failures=1 duration=10
wlp2s0: CTRL-EVENT-SCAN_STARTED
wlp2s0: CTRL-EVENT-SCAN_STARTED
etc...

And it continues like that endlessly. If I ignore all that and run it in the background and then rundhcpcd wlp2s0, I get (I'm not copying all of it):

# dhcpcd wlp2s0
... starting wpa_supplicant
... failed to start wpa_supplicant
... Succesfully initialized wpa_supplicant
Line 1062: unknown EAP method 'SIM'
You may need to add support for this EAP method during wpa_supplicant build time configuration
Line 1062: failed to parse eap 'SIM'
Line 1065: failed to parse network block
Line 1072: unknown EAP method 'PSK'
....
...
Line 1108: unknown method 'IKEV2'
Line 1111: failed to parse network block
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant.conf'
dhcpcd[493]: waiting for carrier
...
...

So the problem I have is authenticating with the router (although I don't understand then why I cannot connect to my phone's unprotected wifi...). And also, connecting the ethernet cable doesn't work, there's no way.

Things that have changed since the last time I used Arch Linux on this computer:
- The router (but the other computers can connect without any problem and I have been able not so long ago (a few months maybe) to get a connection working with a Linux Mint Live USB in this very same computer)
- The screen of the computer. I have just replaced the old one with a new one, it was broken.
- And I can't think of anything else

I have tried many things, so I wasn't sure what results should I share here first. If I chose incorrectly and it's better for me to post other outputs here, please let me know and I'll fix it. I hope the post has enough information already, though. Sorry if it's too long, I didn't want to leave anything out and make anyone loose their time.

Looking forward to any ideas or help anyone might have. Thanks in advance!

jocheem67 · 2014-07-07 16:16:21

Two questions: you can connect through other devices to your home network ? Wasn't clear to me.

The output of lspci please ?

start with the loading ( or not loading ) of drivers..it's in the wiki.

Did you think of checking the bios ?

Change your routers WPA to no passphrase...

eipi · 2014-07-07 16:32:05

My bad, I forgot the lspci. Sorry for that!

00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
02:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)

I'm adding also the last lines of lspci -k:

02:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: Foxconn International, Inc. Device e00c
Kernel driver in use: ath5k
Kernel modules: ath5k
03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)
Subsystem: Samsung Electronics Co Ltd Device ca00
Kernel driver in use: sky2
Kernel modules: sky2

Regarding the drivers/firmware I've been following the wiki and as far as I understood it seems I don't need to load anything else. From lspci -k I understand that the drivers are already loaded. And firmware doesn't seem to be needed either, as I get no output from dmesg | grep firmware. But I could be misunderstanding something, sorry if I'm wrong

What I've checked of the bios is making sure nothing was disabled, but I didn't see anything weird. I tried disabling power saving, just in case that was doing something, but no difference. Anything in particular about the bios that you're thinking of?

I'll get going with the settings of the routers, for some strange reason with the internet provider, I have to do something first with them to be able to access it. Crazy.

And yes, just for clarifying, other devices can connect without any problems to my home network.

Thanks for the reply!

MoonSwan · 2014-07-07 17:03:20

Welcome to the forums eipi! I may not be very helpful but I'm going to give it a shot anyway.

Are you plugging the netbook into the router directly through an ethernet cable or are you connecting through some other device, e.g. a network switch? If you're using a secondary device try plugging the netbook directly into the router. Try a different cable too if you have one.

Try to use the "wifi-menu" command perhaps before you start installing Arch after you first boot up the live usb/cd. It might help us to figure out if there's a manual error.

Your logs say you're using EAP encryption through WPA Supplicant. Is that correct or are you just using WPA2? If EAP is not in use you might want to look at /etc/wpa_supplicant.conf to see what's uncommented (in use that is). The file is huge but almost all of it will be commented out and you only need to uncomment or add what you need to use.

Could you try an Arch-derivative live USB key such as Manjaro* or (better perhaps) Arch Bang? If that worked you could at least see what they've done to get it functional.

I'm going to do something unusual and recommend you try a more "newbie-friendly" Arch re-spin** called TMXGTA Arch. Search the forums and you'll find a link for it. Try to use it and see if it helps you in case you missed a step during the networking phase of the installation.

* Please understand that I'm not endorsing Manjaro. In all honesty, from what I've seen of it, it's a ghastly distro but it's also one of the only ones I could come up with off the top of my head.

** I'm not suggesting you're a newbie here! I'm just suggesting that this particular installation method walks you through things step-by-step and can, at least in my experience, make sure I don't miss a step that needs to be done during the install. This little re-spin has saved my butt on a number of occaisions by forcing me to take the appropriate steps during an installation and making sure I don't do any stupid PEBKAC errors such as forgetting to generate an initramfs.

Last edited by MoonSwan (2014-07-07 17:04:44)

eipi · 2014-07-07 18:01:58

Thanks MoonSwan!

The times I've tried plugging the netbook to the router have been using directly an ethernet cable, so no secondary device in between. I've also tried with another cable I had, and same results; no wired internet

With wifi-menu I've been able to find the networks and create the network profiles, but in the end, it says the connection failed and asks me if I want to save the profile regardless. This happens both with my home network (wpa) and with my non-protected network provided by my android phone. So I really don't know what's going on. It baffles me that it cannot connect to an unprotected network (the phone).

About the EAP vs WPA2, I'm not sure, to be honest. Wifi-menu shows my home network is only wpa, but I didn't ask wpa_supplicant to use EAP explicitly. I'm going through the wpa_supplicant.conf, but I don't see clearly what I would need to comment out or uncomment. I see something about synamic EAP methods (commented), about EAP fast-authentication (uncommented) and something about EAPOL uncommented. I'm a little lost with this one, I'll do more research and report.

I'll try Manjaro, Arch Bang and TMXGTA Arch to see what happens. I'll update when I get them downloaded and I've tried. And no worries, I consider myself a newbie

Thanks a lot for the help MoonSwan! I'll report back soon with the new results

eipi · 2014-07-07 18:55:31

Quick update:

I've tried Arch bang and Manjaro. None of them could connect to the internet (home network (wpa), phone (unprotected) or wired).

On Manjaro, when I plugged the ethernet cable it still said that the cable was disconnected, don't know if that says something. The green light (for the ethernet on the laptop) was on, though.

Tomorrow I'll take a look into TMXGTA Arch and a closer look into the EAP thing. It's getting late over here

eipi · 2014-07-08 19:25:12

Ok, so I've been all day again trying to figure this out. This are the results:

The TMXGTA Arch iso seems to not be online, I couldn't download it. But as far as I understood it is the normal arch iso with tmux installed so that you can check the guides on the same computer while installing. I have another screen where I can be check the wiki, so no problem then

About the EAP thing and wpa_supplicant I think I have sort it out. wpa_supplicant was reading the wpa_supplicant.conf given as an example, i.e, the one with loads of networks defined (and uncommented). That's why it was going crazy. Now I have fixed that and it's reading from the proper configuration file. It manages to associate with the network, but then it fails to authenticate (it receives an AUTH_TIME_OUT event).

Log from wpa_supplicant:

# wpa_supplicant -i wlp2s0 -c /etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
wlp2s0: CTRL-EVENT-SCAN-STARTED
wlp2s0: SME: Trying to authenticate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: Trying to associate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: Associated with 00:1a:2b:b2:25:ce
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:1a:2b:b2:25:ce reason=4 locally_generated=1
wlp2s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WLAN_5E19" auth_failures=1 duration=10
wlp2s0: CTRL-EVENT-SCAN-STARTED
wlp2s0: CTRL-EVENT-SCAN-STARTED
...
...
wlp2s0: CTRL-EVENT-SCAN-STARTED
wlp2s0: CTRL-EVENT-SCAN-STARTED
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="WLAN_5E19"
wlp2s0: SME: Trying to authenticate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WLAN_5E19" auth_failures=7 duration=30
wlp2s0: CTRL-EVENT-TERMINATING

So, as we see there I'm getting a "4-Way Handshake failed - pre-shared key may be incorrect", but I have checked many times the psk to make sure I wrote it correctly. Why does it keep failing?

Also this event: CTRL-EVENT-DISCONNECTED bssid=00:1a:2b:b2:25:ce reason=4 locally_generated=1. Reason=4 I have read somewhere that it means the router is disconnecting me due to inactivity. Is this correct? And if so, why would that be? It doesn't seem to be taking a lot of time to get these messages

I'm guessing maybe this has something to do with the router being very picky. I'm going to try to get into the settings and see if I can make it be more patient.

I have som questions I've been thinking of but I haven't been able to find an answer. I'll put them here in the end so that it doesn't get mixed up with the above findings:

Ethernet

I have seen in the router that the plugs are for Gigaethernet, does it make any difference? I'm getting paranoid here, maybe my ethernet card is too old for these things and that's why it doesn't detect when I plug the cable?

lspci - Ethernet controller

lspci throws two Ethernet Controller, one for the wired and another one for the wireless. Shouldn't the wireless say something like Network Controller? Could this be making the computer confused and thus no wired nor wireless interfaces work properly?

I highly doubt this, but I'm running out of ideas.

rfkill

I was checking if there were any harware or software switches blocking the wireless, and when I run rfkill list all, I got this:

# rfkill list all
0: samsung-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

I was only expecting a phy0, not a samsung-wlan. Is this normal or could it be something? Again, I'm running out of ideas and I don't know very well how things are supposed to look

Still doesn't connect to an unprotected network

I've always tried to connect to the unprotected wireless network created by my phone and I haven't managed to connect to it. Why could this be? Could investigate this help in finding out what is going on with this internet problem?

When I run wifi-menu, I get this error (this is from another day, but it is the exact same error):

# systemctl status netctl@WLAN.service
● netctl@WLAN.service - Networking for netctl profile WLAN
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
Active: failed (Result: exit-code) since Sat 2014-07-05 20:45:15 UTC; 1min 0s ago
Docs: man:netctl.profile(5)
Process: 3514 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 3514 (code=exited, status=1/FAILURE)
Jul 05 20:44:57 archiso systemd[1]: Starting Networking for netctl profile WLAN...
Jul 05 20:44:57 archiso network[3514]: Starting network profile 'WLAN'...
Jul 05 20:45:14 archiso network[3514]: WPA association/authentication failed for interface 'wlp2s0'
Jul 05 20:45:15 archiso network[3514]: Failed to bring the network up for profile 'WLAN'
Jul 05 20:45:15 archiso systemd[1]: netctl@WLAN.service: main process exited, code=exited, status=1/FAILURE
Jul 05 20:45:15 archiso systemd[1]: Failed to start Networking for netctl profile WLAN.
Jul 05 20:45:15 archiso systemd[1]: Unit netctl@WLAN.service entered failed state.

I get the same for both profiles, the one from the phone (unprotected) and the one form the router (wpa). I'm completely clueless in here. How can something fail to authenticate when connecting to an unprotected network?

Typo in the wiki

Not all this will be in vain, at least I think I have found a typo in the wiki haha. It's in the Beginner's Guide ( https://wiki.archlinux.org/index.php/Be … e#Wireless ) in the Wireless setup > Without wifi-menu.

It says:

If that does not work, issue the following commands:
# echo 'ctrl_interface=DIR=/run/wpa_supplicant' > /etc/wpa_supplicant.conf
# wpa_passphrase ssid passphrase >> /etc/wpa_supplicant.conf
# ip link set interface up
# wpa_supplicant -B -D nl80211 -c /etc/wpa_supplicant.conf -i interface
# dhcpcd -A interface

And I think it should say:

If that does not work, issue the following commands:
# echo 'ctrl_interface=var/run/wpa_supplicant' > /etc/wpa_supplicant.conf
# wpa_passphrase ssid passphrase >> /etc/wpa_supplicant.conf
# ip link set interface up
# wpa_supplicant -B -D nl80211 -c /etc/wpa_supplicant.conf -i interface
# dhcpcd -A interface

I've seen it like that in the wpa_supplicant.conf in /etc/wpa_supplicant/wpa_supplicant.conf

I haven't changed the wiki and I don't know if I even have permission to do so.

-------------

And I think that's all for today. Mainly, it seems that my router rejects to accept my little laptop, I'm failing at the authentication part and I don't know why. I'm suspecting the router has one or two things to say about this wired and wireless not working thing. So my next attempts are going to be fiddling with the router and changing to an old router. If anyone has any ideas or can enlighten me, I would be extremely grateful

MoonSwan · 2014-07-09 00:03:23

eipi wrote:

Ok, so I've been all day again trying to figure this out. This are the results:
So, as we see there I'm getting a "4-Way Handshake failed - pre-shared key may be incorrect", but I have checked many times the psk to make sure I wrote it correctly. Why does it keep failing?

This has nothing to do with your key I think. I forgot to ask what method you're using to try to connect to the router? Netctl or Dhcpcd directly (manually), etc?

Also this event: CTRL-EVENT-DISCONNECTED bssid=00:1a:2b:b2:25:ce reason=4 locally_generated=1. Reason=4 I have read somewhere that it means the router is disconnecting me due to inactivity. Is this correct? And if so, why would that be? It doesn't seem to be taking a lot of time to get these messages

I don't know, sorry.

Ethernet

I have seen in the router that the plugs are for Gigaethernet, does it make any difference? I'm getting paranoid here, maybe my ethernet card is too old for these things and that's why it doesn't detect when I plug the cable?

This isn't relevant.

lspci - Ethernet controller
lspci throws two Ethernet Controller, one for the wired and another one for the wireless. Shouldn't the wireless say something like Network Controller? Could this be making the computer confused and thus no wired nor wireless interfaces work properly?

Rfkill is designed specifically test wireless network cards so it's not a surprise that it thinks your Ethernet (LAN) card is also a wifi card. Ignore the output of rfkill. I am glad that we have gotten rid of one more variable.

When I run wifi-menu, I get this error (this is from another day, but it is the exact same error):
# systemctl status netctl@WLAN.service.

Ignore this part for now. But it does make me wonder: are you trying to use netctl-auto@LAN_card_here and NOT just netctl as your output shows here: systemctl status netctl@WLAN.service.

Typo in the wiki

Not all this will be in vain, at least I think I have found a typo in the wiki haha. It's in the Beginner's Guide ( https://wiki.archlinux.org/index.php/Be … e#Wireless ) in the Wireless setup > Without wifi-menu.

It says:

If that does not work, issue the following commands:
# echo 'ctrl_interface=DIR=/run/wpa_supplicant' > /etc/wpa_supplicant.conf

The wiki is correct insofar as some people will use a custom path for various aspects of linux. Just ignore this too.

-------------

I've done my best to help you so far but I still need the output of lspci -v (please cut and paste the output here between code tags. I also still need you to clarify how you're trying to connect. All you've told me so far is that you've been messing with your router. I am glad you got wpa_supplicant.conf sorted too. Cut and paste your netctl.conf or whatever profile you're using to set up the wifi and lan card. Without this info I'm "blind." Equally, if someone else wants to chime in here, they will also need the information I've asked for.

ewaller · 2014-07-09 01:55:44

I'll take a stab at it With the Ethernet cable connected to your router, what is the output of ip link
?

jocheem67 · 2014-07-09 03:04:42

And just my sting:

It's not your machine, I'd suggest to take your machine to a friend and try to connect there.
Otherwise reset your router, check your bios ( again ).

It's just very suspicious that wired and wifi both won't do their thing here

eipi · 2014-07-09 18:09:14

MoonSwan wrote:

I forgot to ask what method you're using to try to connect to the router? Netctl or Dhcpcd directly (manually), etc?

MoonSwan wrote:

I also still need you to clarify how you're trying to connect. [...] Cut and paste your netctl.conf or whatever profile you're using to set up the wifi and lan card.

First I've tried using wifi-menu. It detects the wireless networks fine and I choose the one from home. It then asks for the password, I double check and then choose OK. I wait a few seconds and then a message pops up saying that connecting failed and asks me if I want to save the profile ("Connecting failed. Do you want to keep the generated profile ('WLAN')?"). I have saved it, here it is:

/etc/netctl/WLAN

Description='Automatically generated profile by wifi-menu'
Interface=wlp2s0
Connection=wireless
Security=wpa
ESSID=WLAN_5E19
IP=dhcp
Key=thewpakey

I try once more with wifi-menu. This time connecting with the wifi network provided by my phone (unprotected). Same steps (except for the password one, of course) and then the same message pops up "Connecting failed. Do you want to keep the generated profile ('AndroidAP')?". I save the profile:

/etc/netctl/AndroidAP

Description='Automatically generated profile by wifi-menu'
Interface=wlp2s0
Connection=wireless
Security=none
ESSID=AndroidAP
IP=dhcp

And then I have also tried connecting manually. I follow this: https://wiki.archlinux.org/index.php/Wi … nual_setup

I'll show exactly all the steps.

1. Check the driver status:

# lspci -k
...
...
02:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
	Subsystem: Foxconn International, Inc. Device e00c
	Kernel driver in use: ath5k
	Kernel modules: ath5k
03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Kernel driver in use: sky2
	Kernel modules: sky2

And I see that the driver in use is ath5k

2. Check kernel messages for firmware being loaded:

# dmesg | grep firmware

Nothing shows up, so according to the Beguinners' guide it may be concluded that the system's wireless chipset does not require firmware.

Regardless, I check also the messages for the module ath5k in case it could help:

# dmesg | grep ath5k
[   16.918523] ath5k 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[   16.918838] ath5k 0000:02:00.0: registered as 'phy0'
[   17.575492] ath5k: phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)

I don't understand much of it, but it seems to succeed at registering phy0 and finding the wireless chip. I don't know if something else should pop up

With all this, I guess the kernel module is loaded and that I don't need to do anything else, so I continue with the wiki.

3. Find name of the wireless interface:

# iw dev
phy#0
	Interface wlp2s0
		ifindex 3
		wdev 0x1
		addr 00:24:2c:23:d9:f5
		type managed

So I get that the interface is wlp2s0

4. Interface activation

# ip link set wlp2s0 up

Nothing shows up, no error messages. I verify that it's up:

# ip link show wlp2s0
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:24:2c:23:d9:f5 brd ff:ff:ff:ff:ff:ff

And yes, it's up according to that UP in <NO-CARRIER,BROADCAST...>

5. Access point discovery
I know the SSID is WLAN_5E19, but I run 'iw dev wlp2s0 scan | less' to make sure it can detect the network and it does.

# iw dev wlp2s0 scan
BSS 00:1a:2b:b2:25:ce(on wlp2s0)
	TSF: 189499139657 usec (2d, 04:38:19)
	freq: 2462
	beacon interval: 100 TUs
	capability: ESS Privacy ShortSlotTime (0x0411)
	signal: -58.00 dBm
	last seen: 116 ms ago
	Information elements from Probe Response frame:
	SSID: WLAN_5E19
	Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 
	DS Parameter set: channel 11
	ERP: Barker_Preamble_Mode
	ERP D4.0: Barker_Preamble_Mode
	Extended supported rates: 6.0 9.0 12.0 48.0 
	HT capabilities:
		Capabilities: 0x186c
			HT20
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			No RX STBC
			Max AMSDU length: 7935 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT RX MCS rate indexes supported: 0-15
		HT TX MCS rate indexes are undefined
	HT operation:
		 * primary channel: 11
		 * secondary channel offset: no secondary
		 * STA channel width: 20 MHz
		 * RIFS: 1
		 * HT protection: no
		 * non-GF present: 1
		 * OBSS non-GF present: 0
		 * dual beacon: 0
		 * dual CTS protection: 0
		 * STBC beacon: 0
		 * L-SIG TXOP Prot: 0
		 * PCO active: 0
		 * PCO phase: 0
	WPS:	 * Version: 1.0
		 * Wi-Fi Protected Setup State: 2 (Configured)
		 * Selected Registrar: 0x0
		 * Response Type: 3 (AP)
		 * UUID: 094c2fac-7593-4698-4190-6ce53545d404
		 * Manufacturer: Broadcom
		 * Model: Broadcom
		 * Model Number: 123456
		 * Serial Number: 1234
		 * Primary Device Type: 6-0050f204-1
		 * Device name: BroadcomAP
		 * Config methods: Display, PBC
	WPA:	 * Version: 1
		 * Group cipher: TKIP
		 * Pairwise ciphers: CCMP TKIP
		 * Authentication suites: PSK
		 * Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
	WMM:	 * Parameter version 1
		 * u-APSD
		 * BE: CW 15-1023, AIFSN 3
		 * BK: CW 15-1023, AIFSN 7
		 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
		 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS 02:1a:11:f0:fc:af(on wlp2s0)
	TSF: 29102927 usec (0d, 00:00:29)
	freq: 2437
	beacon interval: 100 TUs
	capability: ESS ShortPreamble ShortSlotTime (0x0421)
	signal: -25.00 dBm
	last seen: 23 ms ago
	Information elements from Probe Response frame:
	SSID: AndroidAP
	Supported rates: 1.0* 2.0* 5.5* 11.0* 
	DS Parameter set: channel 6
	ERP: <no flags>
	Extended supported rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 
	HT capabilities:
		Capabilities: 0x12c
			HT20
			SM Power Save disabled
			RX HT20 SGI
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			No DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: No restriction (0x00)
		HT RX MCS rate indexes supported: 0-7
		HT TX MCS rate indexes are undefined
	HT operation:
		 * primary channel: 6
		 * secondary channel offset: no secondary
		 * STA channel width: 20 MHz
		 * RIFS: 0
		 * HT protection: no
		 * non-GF present: 0
		 * OBSS non-GF present: 0
		 * dual beacon: 0
		 * dual CTS protection: 0
		 * STBC beacon: 0
		 * L-SIG TXOP Prot: 0
		 * PCO active: 0
		 * PCO phase: 0
	WMM:	 * Parameter version 1
		 * u-APSD
		 * BE: CW 15-1023, AIFSN 3
		 * BK: CW 15-1023, AIFSN 7
		 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
		 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
	VHT capabilities:
		VHT Capabilities (0x31800120):
			Max MPDU length: 3895
			Supported Channel Width: neither 160 nor 80+80
			short GI (80 MHz)
			RX antenna pattern consistency
		VHT RX MCS set:
			1 streams: MCS 0-7
			2 streams: not supported
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 434 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-7
			2 streams: not supported
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 434 Mbps
	VHT operation:
		 * channel width: 0 (20 or 40 MHz)
		 * center freq segment 1: 0
		 * center freq segment 2: 0
		 * VHT basic MCS set: 0xfffc

6. Operating mode
I have no idea if I have to do something here, so I don't do anything.

7. Association
Here I try to connect to the 'AndroidAP' network (the one that is unprotected and provided by my phone) and then to the home network (WPA-PSK).

Trying to connect to 'AndroidAP':

# iw dev wlp2s0 connect AndroidAP

No output shows up, so I go and check if I have associated succesfully:

# iw dev wlp2s0 link
Not connected.

So, failure. Next I try to connect to the home network, the one that has WPA protection.

I follow the instructions in the wiki and run this first:

# wpa_supplicant -i wlp2s0 -c <(wpa_passphrase "WLAN_5E19" "thewpakey")
Successfully initialized wpa_supplicant
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: SME: Trying to authenticate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: Trying to associate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: Associated with 00:1a:2b:b2:25:ce
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:1a:2b:b2:25:ce reason=4 locally_generated=1
wlp2s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WLAN_5E19" auth_failures=1 duration=10
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="WLAN_5E19"
wlp2s0: SME: Trying to authenticate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: Trying to associate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: SME: Trying to authenticate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: Trying to associate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: Associated with 00:1a:2b:b2:25:ce
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:1a:2b:b2:25:ce reason=4 locally_generated=1
wlp2s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WLAN_5E19" auth_failures=2 duration=20
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="WLAN_5E19"
wlp2s0: SME: Trying to authenticate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: Trying to associate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: Associated with 00:1a:2b:b2:25:ce
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:1a:2b:b2:25:ce reason=4 locally_generated=1
wlp2s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WLAN_5E19" auth_failures=3 duration=20
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="WLAN_5E19"
wlp2s0: SME: Trying to authenticate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WLAN_5E19" auth_failures=5 duration=20
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="WLAN_5E19"
wlp2s0: SME: Trying to authenticate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="WLAN_5E19" auth_failures=6 duration=30
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SCAN-STARTED 
wlp2s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="WLAN_5E19"
wlp2s0: SME: Trying to authenticate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: Trying to associate with 00:1a:2b:b2:25:ce (SSID='WLAN_5E19' freq=2462 MHz)
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:1a:2b:b2:25:ce reason=3 locally_generated=1
wlp2s0: CTRL-EVENT-TERMINATING

And it always fails to authenticate, so I never manage to get to the next and last step; running dhcpcd wlp2s0.

So those are all the steps I follow for trying to get the wireless working.

With the wired one I haven't been fiddling too much, but I've tried now fast to get it working and I got the error "No connection found on interface 'enp3s0' (timeout)". I don't want to make the post very boring to read, it's already really long (sorry for that ), but I can provide a more detailed one after if you find it appropiate, no problem with that. What I have done is set up a netctl profile for ethernet-dhcp and then tried to start it with netctl start.

MoonSwan wrote:

But it does make me wonder: are you trying to use netctl-auto@LAN_card_here and NOT just netctl as your output shows here: systemctl status netctl@WLAN.service

The output 'systemctl status netctl@WLAN.service' that I get is when I try to use wifi-menu for the second time with the 'WLAN' or 'AndroidAP' profile. The first time I use wifi-menu nothing pops up, but the second time (profile already created and saved during the first time) I try to connect to the same network I get:

Job for netctl@WLAN.service failed. See 'systemctl status netctl@WLAN.service' and 'journalctl -xn' for details

I get the same line if I try to connect to AndroidAP for the second time (changing @WLAN.service for @AndroidAP.service of course).

So then it's when I run 'systemctl status netctl@WLAN.service' to see what's going on, and this is what I get (I get the exact same thing with @WLAN.service and @AndroidAP.service, only the profile name changes):

- netctl@WLAN.service - Networking for netctl profile WLAN
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since Wed 2014-07-09 14:49:02 UTC; 8min ago
     Docs: man:netctl.profile(5)
  Process: 1678 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 1678 (code=exited, status=1/FAILURE)

Jul 09 14:48:44 archiso network[1678]: Starting network profile 'WLAN'...
Jul 09 14:49:02 archiso network[1678]: WPA association/authentication failed for interface 'wlp2s0'
Jul 09 14:49:02 archiso network[1678]: Failed to bring the network up for profile 'WLAN'
Jul 09 14:49:02 archiso systemd[1]: netctl@WLAN.service: main process exited, code=exited, status=1/FAILURE
Jul 09 14:49:02 archiso systemd[1]: Failed to start Networking for netctl profile WLAN.
Jul 09 14:49:02 archiso systemd[1]: Unit netctl@WLAN.service entered failed state.
Jul 09 14:53:28 archiso systemd[1]: Stopped Networking for netctl profile WLAN.

I also run 'journalctl -xn', but it doesn't seem to provide new information:

-- Logs begin at Wed 2014-07-09 12:01:45 UTC, end at Wed 2014-07-09 15:00:57 UTC. --
Jul 09 15:00:44 archiso kernel: cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Jul 09 15:00:44 archiso kernel: cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Jul 09 15:00:44 archiso kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Jul 09 15:00:44 archiso kernel: cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Jul 09 15:00:44 archiso kernel: cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Jul 09 15:00:56 archiso network[2792]: WPA association/authentication failed for interface 'wlp2s0'
Jul 09 15:00:57 archiso network[2792]: Failed to bring the network up for profile 'WLAN'
Jul 09 15:00:57 archiso systemd[1]: netctl@WLAN.service: main process exited, code=exited, status=1/FAILURE
Jul 09 15:00:57 archiso systemd[1]: Failed to start Networking for netctl profile WLAN.
-- Subject: Unit netctl@WLAN.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@WLAN.service has failed.
-- 
-- The result is failed.
Jul 09 15:00:57 archiso systemd[1]: Unit netctl@WLAN.service entered failed state.

So regarding if I'm trying to use netctl-auto, I'm not trying to use it explicitly at least. I don't know if wifi-menu uses it in the background, I don't have much clue about how wifi-menu works in the backstage

I don't know if that answers your question, but when I try to connect manually I don't get to call netctl, I call dhcpcd. But as I cannot authenticate with wpa_supplicant, I never get the chance to go to the next step and use dhcpcd for getting the IP.

MoonSwan wrote:

I've done my best to help you so far but I still need the output of lspci -v (please cut and paste the output here between code tags.

Sorry for not providing it earlier here it is:

00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller Hub (rev 03)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, fast devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=09 <?>
	Kernel driver in use: agpgart-intel
	Kernel modules: intel_agp

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at f0000000 (32-bit, non-prefetchable) [size=512K]
	I/O ports at 1800 [size=8]
	Memory at d0000000 (32-bit, prefetchable) [size=256M]
	Memory at f0300000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Kernel driver in use: i915
	Kernel modules: i915

00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, fast devsel, latency 0
	Memory at f0080000 (32-bit, non-prefetchable) [size=512K]
	Capabilities: [d0] Power Management version 2

00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, fast devsel, latency 0, IRQ 43
	Memory at f0340000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Virtual Channel
	Capabilities: [130] Root Complex Link
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: f0100000-f01fffff
	Prefetchable memory behind bridge: 0000000080000000-00000000801fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: Samsung Electronics Co Ltd Device ca00
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Root Complex Link
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 (rev 02) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: f0200000-f02fffff
	Prefetchable memory behind bridge: 0000000080200000-00000000803fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: Samsung Electronics Co Ltd Device ca00
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Root Complex Link
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0, IRQ 23
	I/O ports at 1820 [size=32]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0, IRQ 19
	I/O ports at 1840 [size=32]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0, IRQ 18
	I/O ports at 1860 [size=32]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0, IRQ 16
	I/O ports at 1880 [size=32]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0, IRQ 23
	Memory at f0544000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) (prog-if 01 [Subtractive decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	Capabilities: [50] Subsystem: Samsung Electronics Co Ltd Device ca00

00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	Kernel driver in use: lpc_ich
	Kernel modules: intel_rng, lpc_ich, leds_ss4200

00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] (rev 02) (prog-if 80 [Master])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19
	I/O ports at 01f0 [size=8]
	I/O ports at 03f4
	I/O ports at 0170 [size=8]
	I/O ports at 0374
	I/O ports at 1810 [size=16]
	Capabilities: [70] Power Management version 2
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix, pata_acpi, ata_generic

00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: medium devsel, IRQ 19
	I/O ports at 18a0 [size=32]
	Kernel modules: i2c_i801

02:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
	Subsystem: Foxconn International, Inc. Device e00c
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at f0100000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [40] Power Management version 2
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [60] Express Legacy Endpoint, MSI 00
	Capabilities: [90] MSI-X: Enable- Count=1 Masked-
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Kernel driver in use: ath5k
	Kernel modules: ath5k

03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, fast devsel, latency 0, IRQ 42
	Memory at f0200000 (64-bit, non-prefetchable) [size=16K]
	I/O ports at 2000 [size=256]
	Capabilities: [48] Power Management version 3
	Capabilities: [5c] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [c0] Express Legacy Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [130] Device Serial Number 2f-70-f5-ff-ff-77-13-00
	Kernel driver in use: sky2
	Kernel modules: sky2

ewaller wrote:

With the Ethernet cable connected to your router, what is the output of ip link?

Sure! Here it goes!

Output before connecting the Ethernet cable:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:13:77:f5:92:00 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:24:2c:23:d9:f5 brd ff:ff:ff:ff:ff:ff

And after connecting the cable

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:13:77:f5:92:00 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:24:2c:23:d9:f5 brd ff:ff:ff:ff:ff:ff

jocheem67 wrote:

It's not your machine, I'd suggest to take your machine to a friend and try to connect there.
Otherwise reset your router, check your bios ( again ).

Will try to do that during the weekend in the meanwhile I'm trying to use the wifi network created by my phone and I'm still failing to connect. Is it trickier to connect with the phone? Maybe they are pickier? Because I'm really struggling with that, I set it as an unprotected network and still fails to connect

I have double checked the BIOS again and everything is enabled. I reset the router and try to connect again to the network with wifi-menu and same result "Connecting Failed. Do you want to keep the generated profile ('WLAN')?". I also tried manually again, and it's still the same; failing to authenticate. Sigh...

------------------------

One more thing, I have tried connecting right now a laptop with windows 7 using the Ethernet cable and it worked fine, I could connect to the internet. That laptop also manages to connect to the wireless network.

Also, I've noticed that when I plug the Ethernet cable, the green light on the router for that plug goes on. After fiddling with the computer trying to get it to work I found that the light went off. After that it goes on when I plug and then off after a while, or sometimes it doesn't even go on at all. I'll investigate more about this to find a pattern.

I think that's it, if I've missed something just let me know Thanks a lot everyone for all the help!

ewaller · 2014-07-09 18:45:00

eipi wrote:

ewaller wrote:
With the Ethernet cable connected to your router, what is the output of ip link?
Sure! Here it goes!
Output before connecting the Ethernet cable:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:13:77:f5:92:00 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:24:2c:23:d9:f5 brd ff:ff:ff:ff:ff:ff
And after connecting the cable
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:13:77:f5:92:00 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:24:2c:23:d9:f5 brd ff:ff:ff:ff:ff:ff
...snip ...
One more thing, I have tried connecting right now a laptop with windows 7 using the Ethernet cable and it worked fine, I could connect to the internet. That laptop also manages to connect to the wireless network.
Also, I've noticed that when I plug the Ethernet cable, the green light on the router for that plug goes on. After fiddling with the computer trying to get it to work I found that the light went off. After that it goes on when I plug and then off after a while, or sometimes it doesn't even go on at all. I'll investigate more about this to find a pattern

That bit about NO-CARRIER is a problem. There is the link light on the router that seems to be intermittent. There should also be a link light on the computer itself. Does it illuminate when you connect the cable. Just for giggles, try sudo ip link set enp3s0 up and see if the NO-CARRIER message changes. But, you say the cable works with other OSes

ewaller · 2014-07-09 18:50:26

Want to try something else? Can you put your phone into wired tether mode while it is connected to you machine via USB? A new "Wired" interface may appear in ip link. If it does, run dhcpcd by hand (as root) and see what happens.

eipi · 2014-07-10 12:24:23

ewaller wrote:

That bit about NO-CARRIER is a problem. There is the link light on the router that seems to be intermittent. There should also be a link light on the computer itself. Does it illuminate when you connect the cable. Just for giggles, try sudo ip link set enp3s0 up and see if the NO-CARRIER message changes. But, you say the cable works with other OSes hmm

I've just checked now the lights on the computer. Before connecting any cable, there is a green light on (this one stays on all the time). After connecting the cable and waiting a few seconds, a second green light goes on (right at the same time as the green light on the router). Then it has stayed like that while I tried sudo ip link set enp3so and sudo dhcpcd enp3s0.

When I tired sudo ip link set enp3s0 I checked again ip link and the NO-CARRIER bit was still there. After that I tried sudo dhcpcd enp3s0 to see what happens and dhcpcd got stuck at enp3s0: waiting for carrier then it times out and exits.

# dhcpcd enp3s0
dhcpcd[1394]: version 6.4.0 starting
dhcpcd[1394]: enp3s0: waiting for carrier
dhcpcd[1394]: timed out
dhcpcd[1394]: exited

I have tried booting up with the cable plugged in, but the results are the same. All the green lights are on but ip link shows NO-CARRIER on enp3s0 and trying sudo ip link set enp3s0 up doesn't change that part. Trying sudo dhcpcd enp3s0 spits out the same messages (waiting for carrier, timed out, exited).

What is this NO-CARRIER thing?

ewaller wrote:

Want to try something else? Can you put your phone into wired tether mode while it is connected to you machine via USB? A new "Wired" interface may appear in ip link. If it does, run dhcpcd by hand (as root) and see what happens.

It worked! A new interface appeared in ip link and after trying dhcpcd as root on the new interface I got an internet connection, I could ping to google.

Right after putting the phone into wired tether mode:

# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:13:77:f5:50:00 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:24:2c:23:d9:f5 brd ff:ff:ff:ff:ff:ff
6: enp0s29f7u5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 2e:10:90:36:86:0d brd ff:ff:ff:ff:ff:ff

Then run dhcpcd on the new interface:

# dhcpcd enp0s29f7u5
dhcpcd[1154]: version 6.4.0 starting
dhcpcd[1154]: enp0s29f7u5: adding address fe80::6df2:d168:9fe0:f37f
dhcpcd[1154]: enp0s29f7u5: waiting for carrier
dhcpcd[1154]: enp0s29f7u5: carrier acquired
dhcpcd[1154]: DUID 00:01:00:01:1b:51:3b:a6:2e:10:90:36:86:0d
dhcpcd[1154]: enp0s29f7u5: IAID 90:36:86:0d
dhcpcd[1154]: enp0s29f7u5: rebinding lease of 192.168.42.233
dhcpcd[1154]: enp0s29f7u5: soliciting an IPv6 router
dhcpcd[1154]: enp0s29f7u5: leased 192.168.42.233 for 3600 seconds
dhcpcd[1154]: enp0s29f7u5: adding route to 192.168.42.0/24
dhcpcd[1154]: enp0s29f7u5: adding default route via 192.168.42.129
dhcpcd[1154]: forked to background, child pid 1274

Checking how ip link looks now:

# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:13:77:f5:50:00 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:24:2c:23:d9:f5 brd ff:ff:ff:ff:ff:ff
5: enp0s29f7u5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 2e:10:90:36:86:0d brd ff:ff:ff:ff:ff:ff

And finally try the new connection with ping:

# ping -c 3 www.google.com
PING www.google.com (173.194.41.243) 56(84) bytes of data.
64 bytes from mad01s15-in-f19.1e100.net (173.194.41.243): icmp_seq=1 ttl=55 time=5.12 ms
64 bytes from mad01s15-in-f19.1e100.net (173.194.41.243): icmp_seq=2 ttl=55 time=14.1 ms
64 bytes from mad01s15-in-f19.1e100.net (173.194.41.243): icmp_seq=3 ttl=55 time=10.6 ms

--- www.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 5.122/9.974/14.196/3.733 ms

ewaller · 2014-07-10 15:10:50

Good, at least using the phone you have some connectivity in case you have to install things.
Can we get a bit more specific as to which chip sets you have. Please post the output of lspci -nn
The double 'n' will provide vendor and product id numbers for each device.

The NO-CARRIER means that the driver thinks that the hardware layer is not connected to the router. Generally, this means the cable is unplugged. Most (many) Ethernet implementations at the hardware level consist of four different blocks. There are the MAC, the MII, the PHY and the magnetics block.

The MAC (Media Access Control) provides the logical level of an Ethernet Interface
The MII (Media independent Interface) provides a physical level of an Ethernet interface that is independent of the transport medium.
The PHY provides the interface to the physical media. Optical fiber, coax, RF. twisted pair copper, etc...
The magnetics block provides the transformers and inductors to provide galvanic isolation and signal conditioning.

The drivers all work at the MAC level. Somehow, the PHY, which provides the connection to the twisted pair cable you are using, sees the carrier from the router, but is unable to convince the MII that the link is working. On Ethernet over twisted copper, the hardware communicate continuously, even if the upper layers don't have any data traffic. Note that this may or may not apply to DSL or cable modems when talking to your ISP, but there are continuous packets sent between any modem you may have and your router, or anything else that uses CAT-5.

TL;DR The NO-CARRIER means the driver does not see that the cable is plugged in.
edit: Cleaned up some inaccuracies and decided to include the MAC level.
edit: For background only -- probably not relevant to your issue, here is a data sheet for a typical PHY chip. It talks about the carrier quite a bit. Your problem is probably a driver issue not understanding the PHY on your machine.

Last edited by ewaller (2014-07-10 15:26:02)

eipi · 2014-07-10 15:59:03

Absolutely, here it goes:

# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE Express Memory Controller Hub [8086:27ac] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 02)
00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 02)
00:1c.2 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 3 [8086:27d4] (rev 02)
00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 02)
00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 02)
00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 [8086:27ca] (rev 02)
00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 [8086:27cb] (rev 02)
00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller [8086:27cc] (rev 02)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 02)
00:1f.2 IDE interface [0101]: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] [8086:27c4] (rev 02)
00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus Controller [8086:27da] (rev 02)
02:00.0 Ethernet controller [0200]: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) [168c:001c] (rev 01)
03:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller [11ab:4354] (rev 13)

And wow, thanks a lot for all that information! I didn't have a clue about how these things work inside and I'm reading eagerly all the links you provided

ewaller · 2014-07-10 16:26:34

What kernel are you running? ( post the output of uname -a )
If you have a reasonable data plan on the phone, you should try updating your system ( pacman -Syu )
You may also be able to connect your phone's wifi to your router, then you don't need to worry about your data plan for your tether.

Can you post the output of dmeg | grep sky2 ? I want to see what messages, if anything the sky2 driver has posted. Do that after disconnecting and reconnecting the Ethernet cable.

eipi · 2014-07-10 17:30:44

# uname -a
Linux archiso 3.15.3-1-ARCH #1 SMP PREEMPT Tue Jul 1 07:34:20 CEST 2014 i686 GNU/Linux

I don't have arch installed yet, as I couldn't get the internet connection working. So I'm only able to boot the USB with the last arch image (archlinux-2014.07.03-dual.iso). Now that I can access the internet with the phone I'll try to install everything and do a pacman -Syu and see how it goes. I think the phone connects to the router, so no worries about the data plan, yay!

Anyways, the output of dmesg | grep sky2.

Right after booting, no cable plugged:

# dmesg | grep sky2
[    7.291234] sky2: driver version 1.30
[    7.291717] sky2 0000:03:00.0: Yukon-2 FE+ chip revision 0
[    7.292107] sky2 0000:03:00.0: irq 42 for MSI/MSI-X
[    7.296109] sky2 0000:03:00.0 eth0: addr 00:13:77:f5:92:00
[   18.283092] sky2 0000:03:00.0: enp3s0: phy read timeout
[   18.283973] sky2 0000:03:00.0 enp3s0: enabling interface

Right after plugging the cable:

# dmesg | grep sky2
[    7.291234] sky2: driver version 1.30
[    7.291717] sky2 0000:03:00.0: Yukon-2 FE+ chip revision 0
[    7.292107] sky2 0000:03:00.0: irq 42 for MSI/MSI-X
[    7.296109] sky2 0000:03:00.0 eth0: addr 00:13:77:f5:92:00
[   18.283092] sky2 0000:03:00.0: enp3s0: phy read timeout
[   18.283973] sky2 0000:03:00.0 enp3s0: enabling interface

Right after disconnecting the cable:

# dmesg | grep sky2
[    7.291234] sky2: driver version 1.30
[    7.291717] sky2 0000:03:00.0: Yukon-2 FE+ chip revision 0
[    7.292107] sky2 0000:03:00.0: irq 42 for MSI/MSI-X
[    7.296109] sky2 0000:03:00.0 eth0: addr 00:13:77:f5:92:00
[   18.283092] sky2 0000:03:00.0: enp3s0: phy read timeout
[   18.283973] sky2 0000:03:00.0 enp3s0: enabling interface

And finally, right after reconnecting the cable:

# dmesg | grep sky2
[    7.291234] sky2: driver version 1.30
[    7.291717] sky2 0000:03:00.0: Yukon-2 FE+ chip revision 0
[    7.292107] sky2 0000:03:00.0: irq 42 for MSI/MSI-X
[    7.296109] sky2 0000:03:00.0 eth0: addr 00:13:77:f5:92:00
[   18.283092] sky2 0000:03:00.0: enp3s0: phy read timeout
[   18.283973] sky2 0000:03:00.0 enp3s0: enabling interface

They are all exactly the same if I haven't misread anything.

Sidenote: I had to restart the computer, as the green lights on the computer weren't as usually. They were both off and then only one went on when I plugged the Ethernet cable. The dmesg outputs were the same though. Just in case is relevant.

Thanks a lot for all the help!

ewaller · 2014-07-11 02:48:20

I think that is a good plan. Install Arch using the Phone as you network interface, then lets debug an installed system.

eipi · 2014-07-11 17:50:43

Ok, I have installed arch succesfully on the little laptop (and did a pacman -Syu). I can still connect to the internet using the phone (USB tethering) but I cannot connect to the wireless network (home or phone) or to the wired one (home router).

There seems to be something different about the ethernet card though. At first, there was an error with sky2 and it said "unsupported chip" and there was no wired interface in ip link. After rebooting, this error went away and there was no trace of that error in dmesg. And not only that, the NO-CARRIER bit that appeared when running ip link has dissapeared (but I still cannot make the connection work). This error seems to be ramdom, doesn't always appear and I cannot find a pattern

So after the brief summary, I'll post now all the outputs.

First of all, the kernel version:

# uname -a
Linux nc10 3.15.5-1-ARCH #1 SMP PREEMPT Thu Jul 10 07:10:15 CEST 2014 i686 GNU/Linux

Then the lspci outputs:

# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE Express Memory Controller Hub [8086:27ac] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 02)
00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 02)
00:1c.2 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 3 [8086:27d4] (rev 02)
00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 02)
00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 02)
00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 [8086:27ca] (rev 02)
00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 [8086:27cb] (rev 02)
00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller [8086:27cc] (rev 02)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 02)
00:1f.2 IDE interface [0101]: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] [8086:27c4] (rev 02)
00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus Controller [8086:27da] (rev 02)
02:00.0 Ethernet controller [0200]: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) [168c:001c] (rev 01)
03:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller [11ab:4354] (rev 13)

# lcpci -v
00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller Hub (rev 03)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, fast devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=09 <?>
	Kernel driver in use: agpgart-intel
	Kernel modules: intel_agp

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at f0000000 (32-bit, non-prefetchable) [size=512K]
	I/O ports at 1800 [size=8]
	Memory at d0000000 (32-bit, prefetchable) [size=256M]
	Memory at f0300000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Kernel driver in use: i915
	Kernel modules: i915

00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, fast devsel, latency 0
	Memory at f0080000 (32-bit, non-prefetchable) [size=512K]
	Capabilities: [d0] Power Management version 2

00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, fast devsel, latency 0, IRQ 42
	Memory at f0340000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Virtual Channel
	Capabilities: [130] Root Complex Link
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: f0100000-f01fffff
	Prefetchable memory behind bridge: 0000000080000000-00000000801fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: Samsung Electronics Co Ltd Device ca00
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Root Complex Link
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 (rev 02) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: f0200000-f02fffff
	Prefetchable memory behind bridge: 0000000080200000-00000000803fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: Samsung Electronics Co Ltd Device ca00
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Root Complex Link
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0, IRQ 23
	I/O ports at 1820 [size=32]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0, IRQ 19
	I/O ports at 1840 [size=32]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0, IRQ 18
	I/O ports at 1860 [size=32]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0, IRQ 16
	I/O ports at 1880 [size=32]
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd

00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0, IRQ 23
	Memory at f0544000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) (prog-if 01 [Subtractive decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	Capabilities: [50] Subsystem: Samsung Electronics Co Ltd Device ca00

00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, medium devsel, latency 0
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	Kernel driver in use: lpc_ich
	Kernel modules: intel_rng, lpc_ich, leds_ss4200

00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] (rev 02) (prog-if 80 [Master])
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19
	I/O ports at 01f0 [size=8]
	I/O ports at 03f4
	I/O ports at 0170 [size=8]
	I/O ports at 0374
	I/O ports at 1810 [size=16]
	Capabilities: [70] Power Management version 2
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix, pata_acpi, ata_generic

00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: medium devsel, IRQ 19
	I/O ports at 18a0 [size=32]
	Kernel modules: i2c_i801

02:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
	Subsystem: Foxconn International, Inc. Device e00c
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at f0100000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [40] Power Management version 2
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [60] Express Legacy Endpoint, MSI 00
	Capabilities: [90] MSI-X: Enable- Count=1 Masked-
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Kernel driver in use: ath5k
	Kernel modules: ath5k

03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Memory at f0200000 (64-bit, non-prefetchable) [size=16K]
	I/O ports at 2000 [size=256]
	Capabilities: [48] Power Management version 3
	Capabilities: [5c] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [c0] Express Legacy Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [130] Device Serial Number 2f-70-f5-ff-ff-77-13-00
	Kernel driver in use: sky2
	Kernel modules: sky2

This is when the ethernet card loads properly (or at least, when the error doesn't pop up).

The output of dmesg | grep sky2 in this case:

# dmesg | grep sky2
[    5.427850] sky2: driver version 1.30
[    5.428353] sky2 0000:03:00.0: Yukon-2 FE+ chip revision 0
[    5.428756] sky2 0000:03:00.0: irq 42 for MSI/MSI-X
[    5.526802] sky2 0000:03:00.0: No interrupt generated using MSI, switching to INTx mode.
[    5.528214] sky2 0000:03:00.0 eth0: addr 00:13:77:f5:70:2f

The output of ip link:

# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:13:77:f5:70:2f brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:24:2c:23:d9:f5 brd ff:ff:ff:ff:ff:ff

When the sky2 driver doesn't load properly:

The last bit of lspci -v looks like this:

# lspci -v
...
...
02:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
	Subsystem: Foxconn International, Inc. Device e00c
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at f0100000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [40] Power Management version 2
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
	Capabilities: [60] Express Legacy Endpoint, MSI 00
	Capabilities: [90] MSI-X: Enable- Count=1 Masked-
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Kernel driver in use: ath5k
	Kernel modules: ath5k

03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13)
	Subsystem: Samsung Electronics Co Ltd Device ca00
	Flags: fast devsel, IRQ 18
	Memory at f0200000 (64-bit, non-prefetchable) [size=16K]
	I/O ports at 2000 [size=256]
	Capabilities: [48] Power Management version 3
	Capabilities: [5c] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [c0] Express Legacy Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [130] Device Serial Number 2f-70-f5-ff-ff-77-13-00
	Kernel modules: sky2

dmesg | grep sky2 shows this:

# dmesg | grep sky2
[    7.964431] sky2: driver version 1.30
[    7.964869] sky2 0000:03:00.0: unsupported chip type 0x80
[    7.965076] sky2: probe of 0000:03:00.0 failed with error -95

And the output of ip link:

# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:24:2c:23:d9:f5 brd ff:ff:ff:ff:ff:ff

When sky2 doesn't load properly, I do nothing. What comes now is what I've tried to do to get the wired and wireless connections working when I don't get any errors right after booting.

I have created profiles for the wired and wireless connections. The wired ones I have done them by hand (copying the examples in /etc/netctl/examples) and the wireless ones I have let wifi-menu deal with them. They are as follows:

Wired phone profile (USB tethering with phone)

# cat /etc/netctl/wired_phone
Description='Basic dhcp ethernet connection for phone USB tethering'
Interface=enp0s29f7u1
Connection=ethernet
IP=dhcp
## for DHCPv6
#IP6=dhcp
## for IPv6 autoconfiguration
#IP6=stateless

Wired home profile (home router ethernet)

# cat /etc/netctl/wired_home
Description='A basic dhcp ethernet connection - Home network'
Interface=enp3s0
Connection=ethernet
IP=dhcp
## for DHCPv6
#IP6=dhcp
## for IPv6 autoconfiguration
#IP6=stateless

Wireless home profile (home wifi network - WPA-PSK)

# cat /etc/netctl/wireless_home
Description='Automatically generated profile by wifi-menu'
Interface=wlp2s0
Connection=wireless
Security=wpa
ESSID=WLAN_5E19
IP=dhcp
Key=mywpakey

Wireless phone profile (phone hotspot - unprotected)

# cat /etc/netctl/AndroidAP
Description='Automatically generated profile by wifi-menu'
Interface=wlp2s0
Connection=wireless
Security=none
ESSID=AndroidAP
IP=dhcp

Of all those profiles, the only one that works is the first one (the USB tethering one). I just run netctl start wired_phone after plugging in the phone to the computer and I get a working internet connection. With the other ones I keep getting the same error messages. I'll show the outputs.

Ethernet

I start with the ethernet cable unplugged; no green lights are on on the computer.
I plug the cable and still no lights on. Not even on the router.

I run netctl start wired_home

# netctl start wired_home
Job for netctl@wired_home.service failed. See 'systemctl status netctl@wired_home.service' and 'journalctl -xn' for details.

So I check systemctl status netctl@wired_home.service to see what's going on:

# systemctl status netctl@wired_home.service
— netctl@wired_home.service - Networking for netctl profile wired_home
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since vie 2014-07-11 17:43:25 CEST; 28s ago
     Docs: man:netctl.profile(5)
  Process: 364 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 364 (code=exited, status=1/FAILURE)

jul 11 17:43:20 nc10 network[364]: Starting network profile 'wired_home'...
jul 11 17:43:25 nc10 network[364]: No connection found on interface 'enp3s0' (timeout)
jul 11 17:43:25 nc10 systemd[1]: netctl@wired_home.service: main process exited, code=exited, status=1/FAILURE
jul 11 17:43:25 nc10 systemd[1]: Failed to start Networking for netctl profile wired_home.
jul 11 17:43:25 nc10 systemd[1]: Unit netctl@wired_home.service entered failed state.
jul 11 17:43:25 nc10 network[364]: Failed to bring the network up for profile 'wired_home'

So no connection found...

I try one more thing, to see what happens:
- ip link set enp3s0 up -> One of the two lights on the laptop goes green but then immediately after goes off. The green light on the router goes green (the one where the cable is plugged in).
- I try to run dhcpcd manually (I'm logged in as root):
```
# dhcpcd enp3s0
dhcpcd[263]: version 6.4.0 starting
dhcpcd[263]: enp3s0: waiting for carrier
dhcpcd[263]: timed out
dhcpcd[263]: exited
```
  So no internet connection either.

Wireless
With the wireless networks I haven't been fiddling too much yet, I've just used wifi-menu. I'll try later to set it up manually so that this post doesn't get extremely huge.

So I've been running wifi-menu. I choose the network (first the one provided by the router (WPA-PSK) and later on the one provided by the phone (unprotected)) and it fails "Connecting Failed. Do you want to keep the generated profile ('wireless_home')?". I have saved the profiles (posted them above).

The first time I run wifi-menu right after booting an error pops up (but wifi-menu continues running regardless):

[   40.532825] [drm:i915_irq_handler] *ERROR* pipe A underrun

Then if I try to run wifi-menu again, that error doesn't show up, but a new message appears at the end, when it fails to connect:

Job for netctl@wireless_home.service failed. See 'systemctl status netctl@wireless_home.service' and 'journalctl -xn' for details.

Checking systemctl status netctl@wireless_home.service:

# systemctl status netctl@wireless_home.service
— netctl@wireless_home.service - Networking for netctl profile wireless_home
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since vie 2014-07-11 17:50:40 CEST; 52s ago
     Docs: man:netctl.profile(5)
  Process: 349 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 349 (code=exited, status=1/FAILURE)

jul 11 17:50:22 nc10 network[349]: Starting network profile 'wireless_home'...
jul 11 17:50:39 nc10 network[349]: WPA association/authentication failed for interface 'wlp2s0'
jul 11 17:50:40 nc10 network[349]: Failed to bring the network up for profile 'wireless_home'
jul 11 17:50:40 nc10 systemd[1]: netctl@wireless_home.service: main process exited, code=exited, status=1/FAILURE
jul 11 17:50:40 nc10 systemd[1]: Failed to start Networking for netctl profile wireless_home.
jul 11 17:50:40 nc10 systemd[1]: Unit netctl@wireless_home.service entered failed state.

The same thing happens when I try to connect using my phone network, same messages.

So to sum up, arch is installed on the machine now, the wireless seems to be behaving in the same way (I still have to try a manual set up) and the wired connection doesn't work either (but the NO-CARRIER bit seems to have dissappeared). I still can connect to the internet if I use the phone's USB tethering capabilities.

I've tried to be concise on this post because it had the potential of becoming huge if I've missed something, just let me know and I'll post it. Thanks everyone for all the help with this, I really appreciate it

Arch Linux

#1 2014-07-07 15:47:54