| 1 |
Sorry for not replying earlier. Yes, I found it to be a fireware |
| 2 |
ethernet. Why udev would put that first makes no sense. |
| 3 |
|
| 4 |
I found another email on the list where someone had the same problem. |
| 5 |
|
| 6 |
Thanks. |
| 7 |
|
| 8 |
On 5/2/07, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 9 |
> On Wed, 2 May 2007 21:43:13 -0600, Trenton Adams wrote: |
| 10 |
> |
| 11 |
> > I have an ethernet controller that worked until I updated my udev to |
| 12 |
> > the latest version. |
| 13 |
> |
| 14 |
> > It shows up as follows from ifconfig |
| 15 |
> > eth0 Link encap:UNSPEC HWaddr |
| 16 |
> > 00-11-D8-00-00-7D-66-26-00-00-00-00-00-00-00-00 |
| 17 |
> > inet addr:192.168.20.2 Bcast:192.168.20.255 |
| 18 |
> |
| 19 |
> > I don't understand what is happening. It sets my IP just fine, but |
| 20 |
> > the MAC address is WEIRD and there's no link. |
| 21 |
> |
| 22 |
> That MAC address looks like it could be a Firewire ethernet interface. |
| 23 |
> Does ifconfig -a show your correct MAC address on another interface? If |
| 24 |
> so, it is probably your persistent net rules messing things up, but if |
| 25 |
> you don't use Firewire for ethernet, it's probably easiest to disable the |
| 26 |
> eth1394 module. |
| 27 |
> |
| 28 |
> |
| 29 |
> -- |
| 30 |
> Neil Bothwick |
| 31 |
> |
| 32 |
> Drive not ready: (R)etry (G)o to Impulse (C)all Engineering |
| 33 |
> |
| 34 |
> |
| 35 |
-- |
| 36 |
gentoo-user@g.o mailing list |
Archives