I've been working on getting my arch install up and running on my desktop. I'm having problems with the wired internet connection and unfortunately, I don't have a wireless card. I do have a ZyXEL usb wireless adapter, but I have had problems with linux compatibility in the past so, I haven't tried that yet, but I did try tethering to my iPhone with no luck. I'm saying all of this to emphasize that I have no simple way of posting logs on here.
Ok, so I completed my dual boot with windows last night and finally everything was going smoothly. However, after attempting to connect to the internet on the fresh install, my internet wasn't working.
I found a ton of references to issues with my ethernet controller online and tried every fix that I could find.
First of all, I realized that the device hadn't been loaded, trying to 'systemctl email@example.com', I was getting the error that eth0 does not exist. So, I tried the other method with net-auto-wired in the install wiki, which returned the same error output. So, I tried 'ip link set eth0 up' and it told me that it couldn't find the device "eth0". So, I thought well hey, there must be a problem with the driver or the kernel module. I found articles online about how the r8169 module wasn't working with 3.4.x+ kernels, note however most of what I could find was more than a year old. But I tried the fixes anyway. So, I installed the previous module with 'pacman -S r8168' and blacklisted the r8169 driver and wrote a script so that the r8169 driver fails on startup so that there would be no conflicts and the r8168 module would load my ethernet controller. This all did not work, so at around 3am I gave up.
This morning I decided to keep trying, and so, I booted into the livecd and installed net-tools, because I am more familiar with that package. After ifconfig -a in the chrooted environment, the output was normal for a working device, which is obvious since internet was working in the livecd env, but the output had the devices named lo and eth0.
I rebooted, and ran the same command 'ifconfig -a' on my install, and I found the problem. It listed 'lo' and 'enp2s0'. So, I edited the ethernet-dhcp example so that the INTERFACE variable was set to "enp2s0" instead of "eth0"and tried everything that I had previously tried with eth0, with enp2s0 (ip link set enp2s0 up, ifconfig enp2s0 up) and these returned no errors and after, 'ip addr' and 'ifconfig' both listed enp2s0,but the connection was still not there. So, I tried 'systemctl firstname.lastname@example.org and 'systemctl net-auto-wired.service', both to no avail. Then I realized that maybe the new kernel module would work with it now that I knew the device name had been changed. So, I undid everything that I had done with the r8169 and r8168 kernel modules and uninstalled the latter, and tried everything again to no avail. So now I am lost and don't know what to try to get it up and running.
'lspci -v' gives the standard output and says that the ethernet controller loaded with the kernel driver r8169.
ip addr 1: lo: <LOOPBACK, UP, LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qien 1000 link/ether 40:61:86:92:14:fb brd ff:ff:ff:ff:ff:ff inet6 fe80::4261:86ff:fe92:14fb/64 scope link valid_lft forever preferred_lft forever
dmesg | grep r8169 [ 11.205859] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 11.206077] r8169 0000:02:00.0: irq 47 for MSI/MSI-x [ 11.206204] r8169 0000:02:00.0 eth0: RTL8168d/8111d at 0xffffc90000c7a000, 40:61:86:92:14:fb, XID 081000c0 IRQ 47 [ 11.206207] r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [ 67.962301] r8169 0000:02:00.0 enp2s0: link down [ 67.962328] r8169 0000:02:00.0 enp2s0: link down [ 69.630421] r8169 0000:02:00.0 enp2s0: link up
dmesg | grep eth0: [ 8.744917] systemd: Expecting device sys-subsystem-net-devices-eth0.device... [ 11.206204] r8169 0000:02:00.0 eth0: RTL8168d/8111d at 0xffffc90000c7a000, 40:61:86:92:14:fb, XID 081000c0 IRQ 47 [ 11.206207] r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [ 11.322907] systemd-udevd: renamed network interface eth0 to enp2s0
dmesg | grep enp2s0: [ 11.322907] systemd-udevd: renamed network interface eth0 to enp2s0 [ 67.962301] r8169 0000:02:00.0 enp2s0: link down [ 67.962328] r8169 0000:02:00.0 enp2s0: link down [ 67.962334] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link is not ready [ 69.630421] r8169 0000:02:00.0 enp2s0: link up [ 69.630430] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
Sorry, I had to type these by hand. I am positive that there are no typos though.
Last edited by eroge008 (2013-01-18 19:30:07)
I found out what the problem was... I'm and idiot. I had to run the command 'dhcpcd enp2s0'
I'm having the exact same problem. But I don't understand your solution. After everything is booted you can just type 'dhcpcd' and dhcpcd will work. But how did you get this to work at boot i.e. without having to type 'dhcpcd' everytime you login?
But how did you get this to work at boot i.e. without having to type 'dhcpcd' everytime you login?
Please have a look: https://wiki.archlinux.org/index.php/Dh … IP_address
Arch_x64 on Thinkpad Edge E520 (Intel Core i5, 4 GB RAM, 128 GB Crucial M4 SSD) + ITX-Desktop (Asrock H77M-ITX, Intel Core i3-2120T, 8GB RAM, 64 GB Samsung 830 SSD)