Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This system was originally running RH7.3 and I did not have these problems, I decided to wipe and install Fedora and now this very weird problem occurs:
I have two NICs installed, eth0 and eth1.
Upon bootup, eth0 will not recognize link. The nic itself indicates link on its external LED. NO amount of restarting network will get this interface up. I have to physically unplug the network cable and then plug back in for it to work.
I have tried all the standard testing for cabling or hardware problems. I have swapped cables, I have swapped nics, I changed the order of the nics physicaly on the Mainboard. Always, it is eth0 that will not recognize link, no matter which network card is used. I can even take the network cable from the eth0 and use in eth1 and move eth1's network cable to eth0 and eth0 still refuses to work, and eth1 is just fine.
So I'm thinking this is a bug of some sort in Fedora. Has anybody had this same or similar problem and have a solution?
http://www.linuxquestions.org/questi...367#post751367 That is my solution for the same problem with Mandy10 (2.6 kernel). Try putting your eth module in the /etc/modules file if you run 2.4 or what I did if you run 2.6
This is my /etc/sysconfig/network:
NETWORKING=yes
HOSTNAME=duly
Here are my messages related to eth0 during a reboot:
Feb 10 23:35:44 duly kernel: e100: eth0 NIC Link is Down
Feb 10 23:36:00 duly kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
Feb 10 23:39:48 duly kernel: e100: eth0: Intel(R) PRO/100 Network Connection
Feb 10 23:39:48 duly kernel: e100: eth0: Intel(R) PRO/100 Network Connection
Feb 10 23:39:48 duly kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
Feb 10 23:40:26 duly kernel: e100: eth0 NIC Link is Down
Feb 10 23:40:34 duly kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
It looks like the module has a problem with the hardware. These are onboard nics. I got the same problem with broadcom gigabit onboard nics.
Set the speed in your module.conf, maybe this helps.
option e100 e100_speed_duplex=4,4
DESCRIPTION:
e100_speed_duplex
Valid Range: 0-4 (1=10half;2=10full;3=100half;4=100full)
Default Value: 0
The default value of 0 sets the adapter to auto-negotiate. Other values
set the adapter to forced speed and duplex.
Example usage: insmod e100.o e100_speed_duplex=4,4 (for two adapters)
Originally posted by atticboy1 I added that to my modules.conf and rebooted. It didn't work.
lsmod? Is the module loaded? Can you load it manually? Are you running 2.4 kernel? If so, and the module is not loading at boot, put the name of the module in /etc/modules . Reboot and see. If 2.6, see my post above.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.