You are not logged in.
Just did a pacman -Syu to get the kde updates and such ... and when I rebooted, my NIC was changed from eth0 to eth2 ... I saw that ipw2200 was among the updates... could that cause this?
Offline
No, most likely udev:
http://wiki.archlinux.org/index.php/Ude … _Each_Boot
Offline
Thanks. I will try to make a udev rules file. I'll see what happens next reboot.
Offline
Well ... now I think that my NIC gets eth0, and my wlan NIC gets eth1 every time, but sometimes none of them gets set up at all.
I boot, and when I do en ifconfig, the only thing that shows up is 'lo'. If I try 'ifconfig eth0 up' and 'dhcpcd eth0', eth0 does not get set up correctly. I then try a reboot, and usually the NICs work after the reboot.
I added an 10-network.rules in the /etc/udev/rules.d/ folder which contains the following lines:
<code>SUBSYSTEM=="net", SYSFS{address}=="00:0b:5d:77:b3:aa", NAME="eth0"
SUBSYSTEM=="net", SYSFS{address}=="00:0e:35:da:97:36", NAME="eth1"</code>
In /etc/rc.conf I have:
<code>lo="lo 127.0.0.1"
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo eth0 !eth1)</code>
Anyone who can help me out here?
Offline
In some cases, reassigning the standard names (ethX) was unsuccessful. Instead, try names like "lan0", "wlan0", "foo", "bar" or "noodle" for your interfaces. This always worked so far.
Offline
yep, naming them eth0, eth1 isn't a good idea (I found out the hard way). I named them lan0 and lan1 after that, but some crappy program required me to have an eth0 to activate it, so I had to resort to listing the modules manually in rc.conf to get the order fixed.
You like cheese? You like peas? You'll love cheezy peas!
Offline