net.eth1 wont start at bootup

Vlad · Posted: Fri Mar 10, 2006 3:05 am Post subject: net.eth1 wont start at bootup

Alright, I just did a clean install on a system of Gentoo 2006.0. I have two network cards, an onboard one and a PCI gigabit one. When activated independently of the init scripts, both work fine. My goal is to use eth1 and not eth0 (eth0 is infact unplugged).

I've linked net.lo to both net.eth1 and net.eth0. I've setup my /etc/conf.d/net file according to my needs. net.lo starts up just fine. The modules are loaded while it's booting, and I can see them as soon as I log in.

As I said, I use eth1, so I've added net.eth1 to the default runlevel. When I reboot my machine, however, it only brings up the lo interface, and ignores eth1 completely. If I try to start it immediately after booting and logging in,

TheRAt · Veteran Joined: 03 Jun 2002 Posts: 1580

Do you get any messages when you are booting up with respect to net.eth1 (ie. maybe that it is trying to get the IP address in the backgroud, etc)??
Also, are the drivers for the card you are trying to use compiled into the kernel, or built as module?
If module, is it listed in your /etc/modules.autoload.d/kernel-2.6 ??
_________________
All reality is the construct of the observer.

Get Firefox and rediscover the web!

BOFH Excuse #295:
The Token fell out of the ring. Call us when you find it.

Vlad · Posted: Fri Mar 10, 2006 5:09 am Post subject:

Should have given some more details about the kernel.

The drivers are compiled as modules and are loaded while the system is booting (they show up in dmesg). They are not in the autoload file.

Absolutely *nothing* is printed about eth1 starting, no error message, no notification, nadda (that sure would make this a hell of a lot easier though).

TheRAt · Veteran Joined: 03 Jun 2002 Posts: 1580

Are you sure that /etc/init.d/net.eth1 is a link to /etc/init.d/net.lo, and it is in the default runlevel

Pete M · Apprentice Joined: 30 Apr 2005 Posts: 154

Vlad

Does your board have firewire

Check dmesg and lsmod see if eth1394 is loaded, if so add this module to /etc/hotplug/blacklist then try a reboot

Sometimes this module takes control of your network interface

Pete

Vlad · Posted: Fri Mar 10, 2006 9:30 am Post subject:

Nope. Firewire has neither been included in my kernel or built as a module, nor is the hardware present on my system.

TheRAt · Veteran Joined: 03 Jun 2002 Posts: 1580

could you post your ifconfig -a after your restart..
post output also from lsmod
_________________
All reality is the construct of the observer.

Get Firefox and rediscover the web!

BOFH Excuse #295:
The Token fell out of the ring. Call us when you find it.

UberLord · Posted: Sat Mar 11, 2006 1:51 pm Post subject:

Try upgrading to dhcpcd-2.0.3
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool

Vlad · Posted: Sat Mar 11, 2006 8:16 pm Post subject:

I'm absolutely positive net.eth0 and net.eth1 are symlinks to net.lo. I'm absolutely positive that they're added to the default run level. I've been using Gentoo since before these forums opened =/ I don't think that this is a firmware issue, as this machine had a ~6 month old Gentoo install on it that worked without issue (I don't think any of the modules load firmware, anyways).

I first tried install dhcpcd-2.0.3. That had no effect.

Now, ifconfig -a shows that the interface *did* recieve an IP address. But there's absolutely no mention of it being started (net.lo is shown however). On a hunch, I tried removing the forcedeth module and reverting to a single network card configuration. My problems remain mostly unchanged, however, after booting up, I do not see anything about net.eth0 starting, syslog-ng, nfsmount, and sshd all fail because net.eth0 was not started. After logging in, I can ping the internet, the device shows up in ifconfig as I would expect it to (has an IP address, etc), and rc-status shows net.eth0 as started! Very strange. Smells like somethings amiss with baselayout-1.20.0_pre16-r3.

And yes, all the config files are updated. I've also checked to make sure that kernel level autoconfiguration is off, even though that shouldn't be an issue on this network.

Here's the output of ifconfig -a, minus the loopback:

TheRAt · Veteran Joined: 03 Jun 2002 Posts: 1580

Do you by any chance have RC_PARALLEL_STARTUP="yes" in your /etc/conf.d/rc..
I had some strange issues with that on startup, including how it dealt with my wireless on startup..
_________________
All reality is the construct of the observer.

Get Firefox and rediscover the web!

BOFH Excuse #295:
The Token fell out of the ring. Call us when you find it.

Vlad · Posted: Sat Mar 11, 2006 8:29 pm Post subject:

ewie · Posted: Sun Apr 09, 2006 8:08 am Post subject:

Just wanted to add a "me too" post.

My setup is a little different, with a via-rhine (eth0) and a rt2570 (rausb0), but the rt2570 never shows anything on boot. Only after a manual restart the interface comes up correctly.

I suspect coldplug or udev or both, my baselayout is stable.

/me Will be hacking initscripts now...

b-s-a · Posted: Tue Apr 11, 2006 2:03 pm Post subject:

Tomorrow I try to upgrade baselayout (from 1.11.14-r7 to 1.12.0_pre17) on my server (router) and receive same problem. When system is booting eth0 and eth2 do not receive any address. But they state is up. I can manually restart /etc/net.eth0 (for example). But when I restart other net.* interface eth0 lose address.
With baselayout-1.11.14-r7 no this problem.

/etc/conf.d/net: