Per your request, ifconfig -a yields
===================
eth1 Link encap:Ethernet HWaddr 00:02:55:1A:5D:7C
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)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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)
===================
I don't know why there is an eth1 and not an eth0; but now that I know that
there is one I modified /etc/network/interfaces to start eth1 instead of eth0
automatically. So I have ethernet now.
After installing the latest 2.6.22-12-generic kernel (which must have been
updated in the last 24 hours), I find that it is still eth1 that is available,
and not eth0. But the dmesg output is slightly different, including the lines
==============
[ 43.507328] e100: eth0: e100_probe: addr 0xee020000, irq 17, MAC addr
00:02:55:1A:5D:7C
...
[ 84.244033] e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
==============
so now there is some clue in the dmesg output that it is eth1 that is up
instead of eth0.
--
e100 module does not create /dev/ethx in gutsy beta1, kernel 2.6.22-12-generic
https://bugs.launchpad.net/bugs/147257
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
