Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've had my machine running with ArchLinux for the past 4 months working great. I wanted to make my own custom Arch ISO following this tutorial:

I got to the end of step 2 and was installing my own packages when I gave up and exited.

Now, everything was working fine. System still running and ifconfig shows eth0 at this point. I rebooted the machine and did an ifconfig and eth0 was gone (even after running dhcpcd).

So I popped in an Arch live CD and did a ifconfig after running dhcpcd and eth0 was listed and able to ping

I'm pretty sure that this line:

mknod /dev/loop0 b 7 0

is what might have screwed me over here. The loopback interface is the only thing listed in ifconfig.

share|improve this question
loop0 should have nothing to do with it. use dmesg to see if eth0 got detected, or renamed. – johnshen64 May 10 '12 at 15:39
loop0 is a loopback block device, not a network interface. – grawity May 10 '12 at 16:09

You must log in to answer this question.

Browse other questions tagged .