Ethernet connection failed - Fedora

fvs

I can't get on the internet from the new install
of Fedora Core 5 and can't find my ethernet connection, When it boots up I see
that eth0 failed to load, How do I connect to the internet? Just starting out. Thanks:O

drasnor

I'm guessing this is on your Biostar board? I checked the Biostar site and they mentioned your NIC is a RealTek RTL8201BL. I checked RealTek's site and they mentioned that this chip is PHY only and that drivers for it aren't necessary. I'm guessing Biostar is using the on-board MAC in the nVidia chipset so you should try the forcedeth driver (modprobe forcedeth). If that doesn't work, post the output of lspci or cat /proc/pci.

What kernel version are you using?

EDIT: to load the driver, be root and type modprobe forcedeth from your console then type ifconfig -a to check if eth0 is defined. From there, Fedora's connection manager should be able to see the eth0.

-drasnor

fvs

Found ethernet (eth0) connection OK, Can't configure Network, Need step by step instruction, Thanks, fvs

drasnor

What have you tried so far? I need more information.

-drasnor

fvs

This the short version of the results, because I'm unable to print the whole result out, nor cut and paste because I'm using another computer to communicate with you, Hope you understand my postion.

Ido have an eth0 that shows up as a devise in my Network Configure in my Admin on the desktop.
When I configure the ethernet device, I have it set to Automaticlly obtain IP address settings with dhcp and Automatically obtain DNS, However when I click Activate button, it return failed?

....
/etc/resolv.config does not esit

Ok, Did it once more,
Link encap: Ethernet HWaddr
UP Broadcast Running Multicast
Rx packets:2 errors:0

Link encap: local loopback
fvs

drasnor

Open up a terminal and type su and give your root password if you aren't already logged in as root. Type ifconfig -a and hit enter. Type dmesg | grep eth0 and hit enter. Paste the output of these two commands in a new post here if you can. It will look something like this:

jormungand drasnor # ifconfig -a
ath0 Link encap:Ethernet HWaddr 00:11:95:BF:C2:52
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:UNSPEC HWaddr 00-02-3C-00-91-02-97-73-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth1 Link encap:Ethernet HWaddr 00:30:48:56:20:50
inet addr:192.168.42.2 Bcast:192.168.42.255 Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe56:2050/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29272696 errors:0 dropped:0 overruns:0 frame:0
TX packets:34360352 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13580336396 (12951.2 Mb) TX bytes:32476585686 (30972.0 Mb)
Interrupt:225 Base address:0xc000

eth2 Link encap:Ethernet HWaddr 00:30:48:56:20:51
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:74 Base address:0xe000

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:39201 errors:0 dropped:0 overruns:0 frame:0
TX packets:39201 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:97440517 (92.9 Mb) TX bytes:97440517 (92.9 Mb)

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
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wifi0 Link encap:Ethernet HWaddr 00:11:95:BF:C2:52
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:58 Memory:ffffc200104c0000-ffffc200104d0000

jormungand drasnor # dmesg | grep eth0
eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
jormungand drasnor # dmesg | grep eth1
eth1394: $Rev: 1312 $ Ben Collins <bcollins@debian.org>
eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
eth1: forcedeth.c: subsystem: 015d9:1011 bound to 0000:00:0a.0
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present

This will tell me a lot about what Fedora thinks it has.

-drasnor

drasnor

You can move this stuff over in a text file on a floppy or flash disk if you have one.

-drasnor

fvs

Hello drasnor,
This the short version of the results, because I'm unable to print the whole result out, nor cut and paste because I'm using another computer to communicate with you, Hope you understand my postion.

I do have an eth0 that shows up as a devise in my Network Configure in my Admin on the desktop.
When I configure the ethernet device, I have it set to Automaticlly obtain IP address settings with dhcp and Automatically obtain DNS, However when I click Activate button, it return failed?
Also I pinged All packages retuned no errors.
....
/etc/resolv.config does not esit

Ok, Did it once more,

Link encap: Ethernet HWaddr

---

UP Broadcast Running Multicast

---

Rx packets:2 errors:0

---

Link encap: local loopback

---

drasnor

I understand that you have an eth0 in your system. What I was trying to find out is whether or not it corresponds to the correct LAN interface. There's a possibility that Fedora has created additional interfaces for other connections you aren't using. I'm going to proceed as though you have the right one though.

On the command line as root, type dhcpcd -n eth0. This will tell your dhcp client to startup on eth0. Let me know if it works or returns something like "command not found" as you may use dhclient or something else for your dhcp client.

-drasnor

fvs

Thanks, I'll go and try it. fvs

fvs

drasnor wrote:

I understand that you have an eth0 in your system. What I was trying to find out is whether or not it corresponds to the correct LAN interface. There's a possibility that Fedora has created additional interfaces for other connections you aren't using. I'm going to proceed as though you have the right one though.

On the command line as root, type dhcpcd -n eth0. This will tell your dhcp client to startup on eth0. Let me know if it works or returns something like "command not found" as you may use dhclient or something else for your dhcp client.

-drasnor

Hope this helps;

bash: /etc/resolv.conf: Permission denied
[root@localhost /]# /sbin/ifconfig
eth0
Link encap:Ethernet HWaddr 00:E0:4C:F1:A3:FE

inet6 addr: fe80::2e0:4cff:fef1:a3fe/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Interrupt:17 Base address:0xe000

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:3553 errors:0 dropped:0 overruns:0 frame:0

TX packets:3553 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0
RX bytes:4405361 (4.2 MiB)
TX bytes:4405361 (4.2 MiB)





root@localhost /]# dmesg | grep eth0
eth0:
forcedeth.c: subsystem: 01565:2501 bound to 0000:00:14.0
eth0:
no IPv6 routers present
[root@localhost /]#

drasnor

Ok, the good news is that your ethernet interface has been properly detected and that it's 'up' meaning that a cable is plugged in and the connection is listed as active. It looks like there's a permissions problem; are you trying to configure your network logged in as root or a user?

-drasnor

fvs

When I go to Network, It ask for password I then put in my password. I also notice that upon booting in
as it loads it stops at eth0 and searches for awhile and the in red letters it say it failed?

fvs

drasnor wrote:

Ok, the good news is that your ethernet interface has been properly detected and that it's 'up' meaning that a cable is plugged in and the connection is listed as active. It looks like there's a permissions problem; are you trying to configure your network logged in as root or a user?

Here's the files; Can't see eth0?


[root@localhost /]# vi /etc/resolv.conf
[root@localhost /]# /sbin/ifup eth0

Determining IP information for eth0... failed.
[root@localhost /]# /sbin/lspci
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express Bridge (rev a2)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a2)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a2)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a2)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a2)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.2 Multimedia audio controller: nVidia Corporation MCP51 AC97 Audio Controller (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
[root@localhost /]#

fvs

Hi drasnor, Got it going, Got info off of linux HOWTO and with some luck it's working. I wanted to tell you that you've been a big help when I was really struggling, Thanks I'll need a whole lot more help in the future, I'm so new at this linux and willing to learn. Thanks once more. fvs

drasnor

Not a problem, always nice to see fresh faces. Also, your experiences will no doubt help others as they learn Linux. What ended up being the fix?

-drasnor

fvs

drasnor wrote:

I understand that you have an eth0 in your system. What I was trying to find out is whether or not it corresponds to the correct LAN interface. There's a possibility that Fedora has created additional interfaces for other connections you aren't using. I'm going to proceed as though you have the right one though.

On the command line as root, type dhcpcd -n eth0. This will tell your dhcp client to startup on eth0. Let me know if it works or returns something like "command not found" as you may use dhclient or something else for your dhcp client.

-drasnor

Hi drasnor, I guess you had it pegged a while back when you told me to get a new ethernet card, Sure enough I install a new nic and so far so good, I hope this is the last of my net problems.
PS I haven't dual booted over to XP, Keep your fingers crossed.
New subject what reference linux books are good to keep on my desk for future?
Where can I get the Red Hat icon, It dosen't come with Fedora 5?

drasnor

I'm always partial to the No BS Guide to Linux since that's where I got my start. You might be able to find that icon as part of a RedHat Gnome theme but realistically Fedora != RedHat so why paste the logo?

-drasnor

gprice

fvs wrote:

Hi drasnor, I guess you had it pegged a while back when you told me to get a new ethernet card, Sure enough I install a new nic and so far so good, I hope this is the last of my net problems.
PS I haven't dual booted over to XP, Keep your fingers crossed.
New subject what reference linux books are good to keep on my desk for future?
Where can I get the Red Hat icon, It dosen't come with Fedora 5?

Hi,
Just joined the forum to comment that I have what appears to be the same problem, using forcedeth.c with an onboard nVidea nForce Networking Controller. Problem here seems to be that eth0 is brought up without inet (TCP/IP) available; ifconfig shows it active, but with only an inet6 address. Taking eth0 down with ifconfig and back up with inet specified as an argument does not help. Cable is hooked to a NetGear router that apparently is old enough that it doesn't do v6. Any suggestions short of installing a network card?
-- Gary

drasnor

You're using Fedora? The IPV6 issue is wierd; are you seeing an extra long MAC address like this (with the really big hardware address):

eth0 Link encap:UNSPEC HWaddr 00-02-3C-00-91-02-97-73-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

or does it look like this (with a fully-defined inet6 address):

eth1 Link encap:Ethernet HWaddr 00:40:38:56:20:50
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx Mask:255.255.254.0
inet6 addr: ab80::230:48dd:ef56:2050/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44982205 errors:0 dropped:0 overruns:0 frame:0
TX packets:29611312 errors:31788 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:36190891487 (34514.3 Mb) TX bytes:6540263396 (6237.2 Mb)
Interrupt:225 Base address:0xa000

Also, what motherboard are you using and are you absolutely sure your network interface is the nVidia MAC and not one provided by Realtek, Marvell, or Broadcomm?

-drasnor

gprice

drasnor wrote:

You're using Fedora? The IPV6 issue is wierd; are you seeing an extra long MAC address like this (with the really big hardware address):

eth0 Link encap:UNSPEC HWaddr 00-02-3C-00-91-02-97-73-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

or does it look like this (with a fully-defined inet6 address):

eth1 Link encap:Ethernet HWaddr 00:40:38:56:20:50
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx Mask:255.255.254.0
inet6 addr: ab80::230:48dd:ef56:2050/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44982205 errors:0 dropped:0 overruns:0 frame:0
TX packets:29611312 errors:31788 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:36190891487 (34514.3 Mb) TX bytes:6540263396 (6237.2 Mb)
Interrupt:225 Base address:0xa000

Also, what motherboard are you using and are you absolutely sure your network interface is the nVidia MAC and not one provided by Realtek, Marvell, or Broadcomm?

-drasnor

Drasnor,
Yes, I'm using Fedora core 5, installed from iso images downloaded recently from their site. They are the 64-bit, dual-core version posted 15 March 2006 (if I remember the date stamp correctly). I infer forcedeth.c from dmesg, which reports it as Ver. 0.49, and also shows

eth0: forcedeth.c: subsystem: 0103c:2a34 bound to 0000:00:14.0

There is also some IP and TCP stuff. I've not installed any RPMs or other Linux software, so I presume forcedeth.c is that provided in the Fedora package.

The ifconfig output is:

eth0 Link encap:Ethernet HWaddr 00:17:31:BF:E4:F7
inet6 addr: fe80::217:31ff:febf:e4f7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:344 (344.0 b) TX bytes:0 (0.0 b)
Interrupt:18 Base address:0xa000

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:27 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1679 (1.6 KiB) TX bytes:1679 (1.6 KiB)

which I gather looks reasonable except for the absence of inet in the eth0: segment.

As to hardware, the machine is an HP a1540n Pavilion, with 64-bit Athalon dual-core CPU; HP's Motherboard Specifications identifies it as an ASUS A8M2N-LA board with onboard nic, there described as an 10/100 Marvell 883C031. It shows as an nVidea NForce Networking Controller under Windows XP, however.

Btw, the nic works fine in Windows XP.

Thanks for any light you can shed.

-- Gary

drasnor

It sounds like you're indeed using a machine with the nVidia MAC if that's how it shoes up under Windows. Are there any checkboxes in the GUI network configurator that might be helpful?

Also, a quick Google search turned up this. I have to admit my knowledge of Fedora is limited so I'm not sure how much help I can provide.

-drasnor

Omega-Blue

I have a similar problem.

I have installed FC5 on a computer with an Asus M2NPV-MX mbo, and the Ethernet controller is a nVidia MCP51. The device comes up okay, and I can ping local host and its own IP (it's a static IP setup LAN). However, I cannot connect to any other box over the network.

Any ideas?

drasnor

Make sure your gateway address and DNS servers are properly defined. If you have a machine routing network traffic, make sure your new machine is defined in its hosts file.

-drasnor

Omega-Blue

I can't ping anything outside of the box, not only those on the Net. The machine is on 192.168.6.x, and it cannot ping anything there with a numerical IP. Kept getting "destination host unreachable".

I have narrowed the problem by adding a realtek PCI ethernet card. The new nic card works as is, so I think it maybe a driver problem.

Further update: the problem is solved after I completely update the system. So it was either the kernel or the driver.

drasnor

Seems like a lot of people are having problems with Fedora and the forcedeth driver. Do you know what kernel version FC5 ships with?

-drasnor

Omega-Blue

Hi, I updated the system and now it works.

Cerisus

drasnor wrote:

Seems like a lot of people are having problems with Fedora and the forcedeth driver. Do you know what kernel version FC5 ships with?

-drasnor

I too have the same problem that the previous people have mentioned. FC5 ships with kernel 2.6.

drasnor

Which version of 2.6 though? For instance, my Gentoo machine runs 2.6.17, my Kubuntu machine is running 2.6.14, etc.

-drasnor

Cerisus

drasnor wrote:

Which version of 2.6 though? For instance, my Gentoo machine runs 2.6.17, my Kubuntu machine is running 2.6.14, etc.

-drasnor

2.6.15-1

drasnor

Can you stick in a PCI network card and try to run Fedora's updater?

-drasnor