Hello Adam,
On Fri, Oct 06, 2006 at 03:45:18PM -0700, Adam D wrote:
> Yes, it had switched. Now the investigation goes to find out why
> eth0 is now eth1. Apparently, I have installed a package that is
Check the archives for various causes. Usually the order of the
detection matters nowadays.
G
Michael Schmitz wrote:
>> On an older 2.6.11.9 kernel I can use my eth0 port but on my newer 2.6.17.11
>> kernel I have not been able to use eth0 and get this error.
>
>> sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
>> PHY ID: 1410cc1, addr: 0
>> eth0: Sun GEM (PCI) 10/100/1000BaseT
> On an older 2.6.11.9 kernel I can use my eth0 port but on my newer 2.6.17.11
> kernel I have not been able to use eth0 and get this error.
> sungem.c:v0.98 8/24/03 David S. Miller (davem@redhat.com)
> PHY ID: 1410cc1, addr: 0
> eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:0d:93:35:91:44
> e
3 matches
Mail list logo
