eth0/eth1 suddenly renamed because of eth1394 ? eth1_rename?
Another user of a Realtec 8139 ethenet card noticed that his
card was "not working".
Others reported it was related to a eth1394 device conflict.
I report a similar occurence.
i have a ibook g4 running sid with kernel linux-image 2.6.17-2
uname -a
Linux debian 2.6.17-2-powerpc #1 Thu Aug 31 12:31:26 CEST 2006 ppc GNU/Linux
I always referred to the ethernet card as eth0 and the
wireless airport card as eth1 in /etc/network/interfaces.
I had no problem till recently when I could not connect to my network.
here is
dmesg|grep eth
eth1: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:4b:96:5a
eth1: Found BCM5221 PHY
eth1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
eth1_rename: Link is up at 100 Mbps, full-duplex.
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth1_rename: suspending, WakeOnLan disabled
eth1_rename: resuming
eth1_rename: Link is up at 100 Mbps, full-duplex.
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth1_rename: Link is up at 100 Mbps, full-duplex.
eth1_rename: Pause is disabled
eth1_rename: no IPv6 routers present
Now if I rename ethernet card to eth1_rename in
/etc/network/interfaces I can
bring up the network.
what is going on with the eth1394?
what does this mean? What changed.
Mitchell Laks
Reply to: