Can anyone help get my ethernet port working using the sky2 module?

Can anyone help get my ethernet port working using the sky2 module?

[Georgina Joyce]

Hi All 

I purchased a new machine recently and liked it that much I purchased a
slightly different one but the motherboards appear to be the same.  Just
for completeness they are shuttles the K45 and K48.

The two machines are called orchid and magnolia.  I'm writing this email
from orchid and other than a reboot problem I'm very happy with her.
But whatever I attempt I can't get maggies ethernet port to work.
Reading around I found that someone had asked for output from ethtool.
So I installed this on both machines and could see strate away that
maggies speed and duplex settings are null.  (See below).  Both machines
have debian Lenny kernel 2.6.26-2-686.  Orchid from a new install but
maggie has been upgraded over several years.  Maggie seems to remap the
ethernet device to eth1 via udev for some reason.  How can I undo this?
What do I need to do to kick this thing into life?

Whoops I forgot the output from lspci for magnolia.  But they are the
same rev 12.

orchid:~# lspci | grep Ethernet
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E
Gigabit Ethernet Controller (rev 12)

magnolia:~# ethtool -i eth1
driver: sky2
version: 1.21
firmware-version: N/A
bus-info: 0000:02:00.0

orchid:~# ethtool -i eth0
driver: sky2
version: 1.21
firmware-version: N/A
bus-info: 0000:02:00.0

magnolia:~# dmesg | grep eth1
[    1.538612] udev: renamed network interface eth0 to eth1
[   16.637768] sky2 eth1: enabling interface
[   88.345542] ADDRCONF(NETDEV_UP): eth1: link is not ready

orchid:~# dmesg | grep eth0
[    1.221865] sky2 eth0: addr 00:30:1b:bd:82:a8
[   11.195644] sky2 eth0: enabling interface
[   12.756760] sky2 eth0: Link is up at 100 Mbps, full duplex, flow
control rx
[   34.038696] eth0: no IPv6 routers present

magnolia:~# ethtool eth1
Settings for eth1:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: Unknown! (65535)
        Duplex: Unknown! (255)
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pg
        Wake-on: d
        Current message level: 0x000000ff (255)
        Link detected: no

orchid:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pg
        Wake-on: d
        Current message level: 0x000000ff (255)
        Link detected: yes

 

-- 
Gena

M0EBP

http://ready2golinux.com 

Re: Can anyone help get my ethernet port working using the sky2 module?

[Joseph C. Lininger]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

My original reply to got held for moderation because of too many
recipients. Well, I canceled it and readdressed this one. Let's try again.

Good morning,
Before we go any further, let me just let you know I'm a Gentoo user,
not a Debian user. However, I feel the issue is for the most part
related as is the fix to it.
The renaming of eth0 to eth1 by udev is most likely something in your
udev rules. Many distros will do this so that devices won't change
device name. I'll bet what you did was to take an existing Linux install
from one machine (orchid, perhaps?) and slap it on magnolia. In that
case, the old machine's MAC would be registered with udev as eth0, and
the current one in magnolia would be assigned eth1. Don't worry though,
this assignment can be corrected.
To fix it, you just have to find the set of rules in your udev
configuration that mapps your ethernet interfaces based on MAC address.
On my system, that file is:
/etc/udev/rules.d/70-persistent-net.rules
There is one line for each of my network interfaces. If you just delete
these lines, then udev will remap the interfaces next time you reboot,
which will result in your actual interface getting eth0. You could
probably even remove the file entirely and it would forget all mappings
and create new ones when you reboot. That's how I handle things when it
does this. Let me stress once again that the file might be in a
different place under Debian, or it may not be set up like this at all.
But have a poke around /etc/udev and see if maybe you can find a similar
file.
Ok, that's how you fix your current problem. There is a little more
information below for anyone interested in disabling the persistent
network interface naming behavior altogether. It's completely optional
in this context, so you can simply skip it if you're not interested.
If you don't like this persistent network interface behavior (I really
don't myself) you can disable it altogether by removing the set of rules
which generates these persistent interface names. Be careful if you
decide to do this. On my system, that file is:
/etc/udev/rules.d/75-persistent-net-generator.rules
If I were to remove this file, as well as
/etc/udev/rules.d/70-persistent-net.rules it would completely disable
that behavior.
Joe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBCAAGBQJKNVG5AAoJEMh8jNraUiwqBXAIAI+YvKBCHYviyuTGdIcsOr6g
hFP2+WXjDwZsrsOLsWWGhLNdCzZBAeRjnSegtGMH5oQre5HCAbfBWP4YxKtilfFf
PMJDDWHoHjQGDGA/UDefoMPsF3XcSwcXrNXbMWzqzK3BEIhU+1q5kHVW6TjEidrZ
G8HbVhJXdnSZwbtPs6xCiP5UFeEWurZ/O7wyiqoNbhYxLEn6e5TANYB6xBdNRAF7
k7D1JoTIcBBmTzzVlWtk74MUMWZcCrfD9rxj87S134hrvf7Yj2jVEy39gW+s6DQJ
XpQCh4wuKrnd7+AFREjmrELbzz42iAOngWwNx29EXG2EextxYKDi1UjcBRa+G9o=
=1XYa
-----END PGP SIGNATURE-----

Re: Can anyone help get my ethernet port working using the sky2 module?

[Christopher Moore]

Hello,
Aside from the renaming from eth0 to eth1, the real problem is that you 
don't have a link on the port.
Is your cable connected to the network?  You could try a different cable 
or hook it to the orcid connection.  You could also hook orcid to the 
magnolia connection to see what happens.

What does the output of ifconfig look like?
Try bringing up the network with:
ifconfig eth1 up

If you still have prlbmes, then perhaps there is a newer version of the 
sky2 driver which will work with the network controller.  

Chris