eth1 not working. HW or Fedora?

[Martín Marqués]

I have a network interface on my laptop which was working (don't know
when it stopped cause I mainly use WIFI) and now fails to connect. I
have NM for network and when I plug the UTP cable (doesn't matter
where I do this, it's always the same) I get this on
/var/log/messages:

Mar 25 15:51:05 xxx kernel: [  570.065930] TCP: lp registered
Mar 25 15:51:07 xxx kernel: [  571.722755] forcedeth 0000:00:0a.0: eth1: link up
Mar 25 15:51:07 xxx kernel: [  571.723094] IPv6:
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Mar 25 15:51:07 xxx NetworkManager[871]: <info> (eth1): carrier now ON
(device state 20)
Mar 25 15:51:07 xxx NetworkManager[871]: <info> (eth1): device state
change: unavailable -> disconnected (reason 'carrier-changed') [20 30
40]

NM says "Not connected".

At boot time I have these relevant lines.

Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): carrier is OFF
Mar 25 15:41:57 xxx kernel: [   22.397119] 8021q: 802.1Q VLAN Support v1.8
Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): new Ethernet
device (driver: 'forcedeth' ifindex: 2)
Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): exported as
/org/freedesktop/NetworkManager/Devices/0
Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): now managed
Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): device state
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): bringing up device.
Mar 25 15:41:57 xxx kernel: [   22.402806] forcedeth 0000:00:0a.0:
eth1: MSI enabled
Mar 25 15:41:57 xxx kernel: [   22.403016] forcedeth 0000:00:0a.0:
eth1: no link during initialization
Mar 25 15:41:57 xxx kernel: [   22.403741] IPv6: ADDRCONF(NETDEV_UP):
eth1: link is not ready
Mar 25 15:41:57 xxx dbus-daemon[884]: modem-manager[951]: <info>
ModemManager (version 0.5.3.96-1.fc16) starting...
Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): preparing device.
Mar 25 15:41:57 xxx NetworkManager[871]: <info> (eth1): deactivating
device (reason 'managed') [2]


What can the problem be?

-- 
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Administrador