Re: ethernet not working (FC4)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jerry Kazdan wrote:
I just updated my laptop from   Fedora Core 3 (kernel  2.6.9-1.667)
                           to   Fedora Core 4 (kernel: 2.6.11-1.1369_FC4)
Now eth0 (ethernet) does not correctly work, although it did work with FC3.
I am using a DHCP connection at this university with everything assigned
automatically. ==> On this laptop etho (ethernet) the identical connection works
perfectly with Knoppix 3.9 which uses kernel 2.6.11, so I know it is
not the hardware nor the DHCP server nor routers along the way.

Here are some details:

1. When I first booted to the new FC4, there was no ethernet.  The boot
screen said [eth0 failed] (although from dmesg it recognized the
ethernet card).  I had the identical problem earlier with the following FC3
update kernels: 2.6.12-1.1372_FC3
        2.6.11-1.35_FC3
        2.6.11-1.27_FC3
which is why I reverted to the older kernel 2.6.9-1.667, which did work. Note that eth0 works perfectly with Knoppix 3.9; it uses kernel 2.6.11.
2. Then I changed grub.conf, adding "acpi=ht" so the line reads:
  kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/1 vga=773 acpi=ht

This  helped a bit since now I DHCP _does work_ and I can connect to
the local sub-net, but NOT elsewhere.  The problem is not the
nameserver since if I use the numerical IP address I get the same
error, as the following test shows:
   > ssh 130.91.49.156
     ssh: connect to host 130.91.49.156 port 22: Network is unreachable

3.  When I use the Fedora menu item "Network" and look under "hosts",
it does not seem to be using my /etc/hosts file since my copy has a few
additional items (see below).
4.  I changed  gnome.conf to turn-off acpi and disable SELinus (so
"acpi=off selinux=0") and rebooted but that did not help.

Any suggestions?
	Jerry


See below for more data, particularly from dmesg, ifconfig and netstat.

My Hardware: Dell Inspiron 9300 (laptop).  See dmesg just below for the
ethernet card -- which as you can see this FC4 kernel does recognize.

I am NOT using the service "NetworkManager".

Here are items from dmesg (some of which may be irrelevant), ifconfig,
and netstat:

   -------------------- snips from dmesg ----------------------------------
eth0: Broadcom 4400 10/100BaseT Ethernet 00:11:43:77:ae:ab
ieee80211_crypt: registered algorithm 'NULL'
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.0
ipw2200: Copyright(c) 2003-2004 Intel Corporation

b44: eth0: Link is down.
codec_semaphore: semaphore is not ready [0x1][0x700300]
codec_write 1: semaphore is not ready for register 0x54
codec_semaphore: semaphore is not ready [0x1][0x700300]
b44: eth0: Link is up at 10 Mbps, half duplex.
b44: eth0: Flow control is off for TX and off for RX.

eth0: no IPv6 routers present
   -----------------------------------------------------

netstat -rn

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
157.181.226.0   0.0.0.0         255.255.254.0   U         0 0          0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth0

You don't have a default route, This should normally come from dhcp.

What's in /var/lib/dhcp/dhclient-eth0.leases?

Paul.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux