Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
[root@localhost dev]# ifconfig eth0
eth0: error fetching interface information: Device not found
Below is the configuration of eth0
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
I am new to linux. could somebody please help me?
Last edited by othergoodboy; 12-19-2008 at 12:50 AM.
Well let's see if it's a hardware issue or a network issue. It seems that your system detects the hardware for your ethernet card. Do you see lights on the device when it is connected? There should be a green light indicating power and an amber light when data is being communicated.
Secondly, I'm not clear on how accurate your network settings are - they seem to be fine - but have you tried attaining address information from DHCP?
Yes I could see the green light. But it doesn't blink. I tried DHCP too. Just curious, why do you think the system detects the ethernet card? because, I tried the GUI to configure the Card and whenever i try to activate it says it didn't find eth0 and will delay initialization.
also wanted to add that the ifconfig -a gives me lo and sit0 no eth0!
So I'm assuming the MCP73 is the Ethernet card in question. The fact that lspci finds the card but ifconfig doesn't is very confusing. Is there any chance you have the card disabled in the BIOS or do you have the card administratively down like using the command ifdown or ifconfig eth0 down? I'm going to google while you read my reply.
you have a static connection ?. or are you using ppoe. or adsl. . if so do you have a built in wifi also.. ifconfig eth0 up. then type dmesg and see the out put then type ifconfig and see if the eth0 is up. i had a wifi card in once and it just decided it wanted to be eth0 instead of eth1 or ath0 or wkan0 but that happen when bios see it it first. go into bios set it to none windows operating system now bios can let linux read them linux is not very good at controlling
the bios they like to read them then set up to them. now we know it is not a irq problem. as root or sudo ifconfig eth0 up . then type ifconfig and if you see it that tells you the /etc/rc.d/rc.init1 is not being loaded. a few reasons but lets just see if this helps. if ifconfig eth0 up and it works if you now you may have to sigh in through you gateway. or do a dhcpcd.
if it does not connect type dmesg read the out put. now do a /etc/rc.d/rc.init1 restarts. then typ if config nothing then type dmesg read the out put . nothing this will tell you the rc.init1 file not the the conf. file. is not set to executable bug one. the scripts are suposed to do this for you when you put all that info in the gui interface.
I tried the dhcp connection too. Also I don't have any other network device other than the lan card.
the ifcgf-eth0 now looks like this:
I then tried ifconfig same problems:
[root@oraapps network-scripts]# ifconfig eth0
eth0: error fetching interface information: Device not found
[root@oraapps network-scripts]# ifconfig eth0 up
eth0: unknown interface: No such device
One thing i noticed is the lsmod shows ipv6. is this a problem? does that mean the ipv6 is enabled?
I have had manny problems with that chipset also, tried manny dists, but when i installed ubuntu everything just worked, debian suse redhat and manny others all had problems either with the nic or the sata controler.
this is a coppy of mine check it out.
# Config information for eth0:
this tells the scripts to look for a live eth0 and start pinging for it.
as root type lsmod make sure you module is loaded. if it is type ifconfig
if nothing type ifconfig up. then type dhcpd this run the sript that ask your conection to connect. once it is up you still need to do your gatway through your browser.
tell us what your hooking up to like a router or a dsl modem cable modem etc etc.
Output to ifconfig (with out -a) shows the lo only. No eth0 or eth1. But ifconfig -a show sit0 in addition to lo.
Here is the output of ifconfig -a:
[root@oraapps ~]# ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:926 errors:0 dropped:0 overruns:0 frame:0
TX packets:926 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:1907044 (1.8 MiB) TX bytes:1907044 (1.8 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
The modprobe.conf looks like this:
alias scsi_hostadapter ahci
alias scsi_hostadapter1 usb-storage
alias eth0 forcedeth
It also doesn't give me any errors while i load forcedeth:
[root@oraapps network-scripts]# modprobe forcedeth
Does any body have any diagnostics program that I could run to get more info on the error?
Last edited by othergoodboy; 12-21-2008 at 12:06 PM.
1. try to disable wake on lan in BIOS if you can; here is the article and solution for realtek cards, maybe it's similar problem since you dual boot: http://ubuntuforums.org/showthread.php?t=538448
2. use other distros liveCD as diagnostic - maybe it's distro specific problem.