Review your favorite Linux distribution.
Go Back > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.


  Search this Thread
Old 07-22-2006, 11:19 AM   #1
Registered: Mar 2005
Location: Arkansas
Distribution: Mandy 2006, FC5
Posts: 154

Rep: Reputation: 30
Eth0 is not active after boot

This is a continuation of my previous thread at
but specific to the latest problem.

My eth0 is not active after startup (or during startup, for that matter). I have to set the card up after each fresh boot through the Mandy Control Center network wizard. These problems began after switching back to ethernet from wireless.

Some things I've tried, and places I've looked:

The card uses the tulip module, and this is does not show in lsmod after boot.

Removed an entry from /etc/modules.conf for eth1. eth1 may have been the second nic installed originally.

Commented out ndiswrapper entry in /etc/modprobe.preload

Commented out ndiswrapper entry in /etc/modules

Changed GATEWAYDEV in /etc/sysconfig/network to eth0 from wlan0

Here's my /etc/sysconfig/ifcfg-eth0 file:
I'm still digging, but some direction would be appreciated.
Old 07-23-2006, 08:43 AM   #2
LQ Addict
Registered: Jul 2002
Location: East Centra Illinois, USA
Distribution: Debian stable
Posts: 5,908

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
Some questions for you.

1) When you use the Mandy Control Center network wizard, it should create a config file somewhere. Is that file still there when you reboot?
a) if no, then you have a problem with the wizard and I can't help.
b) if yes, then there is no need to do it again at each boot. The problem lies elsewhere.

2) lsmod doesn't show the module as being loaded on boot. Have you tried simply "/sbin/modprobe tulip" from a console? Does that get the network up and running without first doing the wizard thing?
a) if no, then the problem is more than just the module not loading, and I can't help.
b) if yes, then find the script that lets you include modules to load at boot. Something like an rc.local script, and add "/sbin/modprobe tulip" to that script. Or, take the time to figure out what to put in /etc/modules.conf to load it.

Note: it might have been better to comment out the eth1 line in modules.conf instead to deleting it. That way you could restore the line by uncommenting it. It might also have been possible to get eth0 working by simply changeing the reference from eht1 to eht0.
Old 07-23-2006, 04:57 PM   #3
Registered: Mar 2005
Location: Arkansas
Distribution: Mandy 2006, FC5
Posts: 154

Original Poster
Rep: Reputation: 30
Thanks for the reply!

Regarding Q-1, I'm not having any luck tracking down the exact config file where changes are made. Will try looking for info on that again.

Q-2 got me digging in the right direction, I think. Short answer: no, modprobe tulip does not bring the network up by itself. Longer answer: I tried doing 'ifconfig eth0 netmask up' after the modprobe. That allowed me to ping the router, but not anything outside. However, I noticed ifup while digging through the network script in rc5.d and gave it a shot after a reboot and it works. So now I'm down to 2 steps to get it up: a) 'modprobe tulip', b) 'ifup eth0'. (The 'ifup eth0 boot' command also works.)

If I understand the boot sequence correctly, the 'ifup eth0 boot' command is run automatically during startup. So is the problem that the tulip module isn't being loaded where it should be? Seems like a good possibility since it isn't loading at all. I'll dig into the modprobe/modules side a bit more and see where it leads.

Thanks for the shove in the right direction.

By the way, I can reproduce the eth1 line in modules.conf as I have a backup. I wasn't sure of the proper comment character for the file, so I just removed the entire line. Here is the backup file:
probeall scsi_hostadapter imm ppa
probeall usb-interface usb-uhci
alias eth1 8139too
above snd-via82xx snd-pcm-oss
alias eth0 tulip
alias sound-slot-0 via82cxxx_audio
The only difference between that and the live file is the eth1 line (note the different module).

Last edited by toes; 07-23-2006 at 05:04 PM.
Old 07-23-2006, 05:34 PM   #4
Registered: Mar 2005
Location: Arkansas
Distribution: Mandy 2006, FC5
Posts: 154

Original Poster
Rep: Reputation: 30

File /etc/modprobe.conf had the error. It contained the line 'alias eth0:9 tulip', but should not have had the ':9' component. After removing that and a reboot, network back as good as new.

Odd that those characters were appended. I also saw those occasionally in the Mandriva Control Center when having problems with the wireless (as in wlan0:9). Perhaps there is a purpose for them, but they seem to always mean error here.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Cannot ping self ??? eth0 not active ??? Wynand1 Linux - Networking 2 06-29-2006 01:11 AM
interface eth0 is not (yet?) active jorcas SUSE / openSUSE 1 11-22-2004 07:53 PM
Network card wil not active on eth0 berryseyx Linux - Laptop and Netbook 5 12-16-2003 08:45 AM
eth0 not active on startup rocket84 Linux - Networking 6 07-21-2003 02:09 AM
no www name resolution when eth0 active vance Linux - Networking 8 12-08-2002 06:11 PM > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 11:44 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration