You are not logged in.
First off, yesterday was my first day with GNU/linux. I never touched the insides of it before this, so my knowledge is minimal.
So when installing Arch Linux, everything goes fine until I try and ping a server to see if my network works. The ping doesn't work, When I use the ip addr command it shows that I have the localhost, eth0 and eth1. Both eth0 and eth1 say they are down.
After a lot of frustration and trying to research the problem. I caved in and went with a more straight forward install with mint.
In mint, I checked to see what the network says
Wired Network (Intel 82579V Gigabit)
Auto eth2Wired Network (Realtek RTL8111/81685 PCI-Express Gigabit Ethernet Controller)
(disconnected)
what got my curiosity is that mint was able to connect to my network, but not on eth0 or eth1, but eth2 which wasn't in the ip addr listing.
So I was wondering if anyone would be able to help me out with solving this? I followed their beginner wiki multiple times and still no luck.
Thanks a lot!
edit, after some looking. Mint uses "network manager" would this help arch finding my network a little better?
Last edited by clandest (2012-03-17 01:06:41)
Offline
what got my curiosity is that mint was able to connect to my network, but not on eth0 or eth1, but eth2 which wasn't in the ip addr listing.
But you ran `ip addr` on Arch, right? Not on your Mint install? I would expect eth2 to show up in Mint (use `ifconfig` if Mint doesn't have iproute2).
You say you followed the Beginners' guide, so what exactly did you do when you got to the "setup network" part? The installer script should offer to bring the interface up and run dhcpcd (as the guide explains), but I'm not sure if you are asked to select the desired interface (maybe it just tries one or all of them).
Alternatively, you can do this manually, using `ip link set ethX up` (replace X by 0 or 1 or ...) and `dhcpcd`.
Last edited by Raynman (2012-03-16 19:34:30)
Offline
yes, I ran ip addr on arch not mint.
Ok, I am in Arch right now and re-doing the install..
so when I test for a ping I get this
ping -c 3 google.com
ping: unknown host google.com
ok, so its not pinging. So then I see if my ethernet is listed with ip addr. and I get
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 1636 qdisc noqueue state UNKNOW
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo2: eth0: <NO CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether f4:6d:04:af:6f:05 brd ff:ff:ff:ff:ff:ff2: eth0: <NO CARRIER,BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether f4:6d:04:af:67:f2 brd ff:ff:ff:ff:ff:ff
Then I tried
dhcpcd eth0
version 5.2.12 starting
eth0: waiting for carrier
timed out
and then I tried
lspci -v
dmesg |grep r8169
Gigabit Ethernet driver 2.3LK-NAPI loaded
sooo thats everything that I have done and still no connection...
Thanks again for any help.
also in my research I found this link http://forums.fedoraforum.org/showthread.php?t=250807 but my ignorance of GNU/Linux I don't know if this is a fix, and if it is how to implement it.
Last edited by clandest (2012-03-16 20:31:38)
Offline
I think I solved it... I've been focusing on eth0 and not on the other eth1... I type dhcpcd eth1 and it loading everything.... and pinged properly.
haha I feel dumb.
Offline
So eth0 was the one with no cable, and eth1 was the one with the cable. ![]()
Something to watch out for - these device names are not alaways assgned in the same order, so next time you reboot, your current eth0 could be eth1 and vice versa. As you're not using both interfaces, I'd suggest you disable one, so you don't have to worry about the device name changing. There are various ways to disable it - blacklist the driver, disable it in the bios, physically remove it.
Offline
So eth0 was the one with no cable, and eth1 was the one with the cable.
Something to watch out for - these device names are not alaways assgned in the same order, so next time you reboot, your current eth0 could be eth1 and vice versa. As you're not using both interfaces, I'd suggest you disable one, so you don't have to worry about the device name changing. There are various ways to disable it - blacklist the driver, disable it in the bios, physically remove it.
Thanks! ill look into that.
Offline