Arch Linux

fishonadish

Member

Registered: 2006-11-04

Posts: 125

Have to manually start network . . .[solved]

Hi,
For some reason my network doesn't start when I boot, but works fine when I run dhcpcd after logging in.  I presume this is something simple, but would appreciate some help.

The module I need is 8139too.  mkinticpio's autodetect gives 8139cp and 8139too for some reason, so I sorted that out in rc.conf.  (It didn't work when I left the modules alone, either).
Here the relevant parts:

MOD_BLACKLIST=(pcspkr 8139cp)
. . .
MODULES=(8139too )
. . .
lo="lo 127.0.0.1"
eth0="DHCP"
eth1="DHCP"
INTERFACES=(lo eth0 eth1)
. . .
#gateway="default gw 192.168.0.254"
ROUTES=(!gateway)
. . .
DAEMONS=(syslog-ng !hotplug !pcmcia hal network @fam @portmap @netfs @crond @alsa)

I have network in the daemons array, but on startup it says 'cannot find device' (can't remember the exact wording) when trying to connect the network, as if the module isn't loaded yet, perhaps?  Should something be loaded before network in the daemons?

The other thing is that I have eth0 and eth1 despite having only one network device (insofar as I'm aware) - ought this be the case?  I just stuck eth1 into rc.conf blindly since it existed.

Any ideas on how to fix this?

Thanks.
Fishonadish

dtw

Forum Fellow

From: UK

Registered: 2004-08-03

Posts: 4,439

Website

Re: Have to manually start network . . .[solved]

You might be having issues with your network devices being dynamically named.  Have a look at this wiki page and see if setting up the static naming helps:

http://wiki.archlinux.org/index.php/Ude … _Each_Boot

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Have to manually start network . . .[solved]

You could also have a look in dmesg to identify and blacklist the module responsible for the second network interface.

harlekin

Member

From: Germany

Registered: 2006-07-13

Posts: 408

Re: Have to manually start network . . .[solved]

Don't know wether it belongs to rc.conf, too.

But UNIX is case-sensitive. Try to replace this line:

eth0="DHCP" 

by

erh0="dhcp"

And all others that contain capitalized "DHCP".

And why do you connect via dhcp through two network interfaces?

---

Hail to the thief!

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: Have to manually start network . . .[solved]

If lsmod shows you an eth1394 module, add it to the blacklist.

---

1000

fishonadish

Member

Registered: 2006-11-04

Posts: 125

Re: Have to manually start network . . .[solved]

Blacklisting eth1394 seems to have done the trick.  Network is starting fine by itself now.

Thanks for the help.
Fishonadish