I just did an ftp installation of arch onto my computer, now after the reboot networks fails to start.
for the ftp install i manually loaded the module for my network card (8139too) and used dhcp to get an ip address, all worked without problems.
the only setup i did for the network card is and 'alias eth0 8139too' in modprobe.conf and 'eth0="dhcp"' in rc.conf, however the module is not loaded on system start but instead the 8139cp modules is loaded which is clearly wrong, even leaving an error message in the log file to use the 8139too driver instead. loading the 8139too driver manually and unloading the 8139cp doesn't help to get the network to start either.
does anyone have an idea what might be going wrong or how to further diagnose this?
hmm..could hotplug be loading the incorrect module?
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
that could well be, this is the first installation with hotplug for me, last one was arch 0.6 with which i didn't have any problems at all (at least none i couldn't quickly attribute to my own incompetence).. how do i find out whether indeed hotplug is the culprit?
Remove the tulip driver from "modprobe.conf" and put it in "rc.conf" under "MODULES=8139too". Run depmod -A, modprobe 8139too, "/etc/rc.d/networ start".
In the past, using "aliases" in "modprobe.conf" and changing drivers will leave some stale kernel associations in there, thus maybe leading to it's confusion while loading.
It could be a udev issue though, but I don't use it.
 be sure to unload any net modules first before doing the above, ie. rmmod 8139cp[/edit]
Thanks a lot skoal, this did the trick, at least my network i working now and i can continue the installation, it's still loading the other driver though