Attansic L1 Gigabit ethernet problems.

Tomasu · 05-25-2008, 06:45 PM

I can't seem to get my gigabit port to run in Gigabit mode consistently. Now all I get when I try to set 1000 mode with ethtool is a dead nic, and ethtool reports "Speed: Unknown (65535)". Switching back to 100BaseTX brings the nic back up. It did work at one time.

I'm running Debian Sid, on 2.6.25.4 (vanila).

lspci:

Code:

02:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0)
        Subsystem: ASUSTeK Computer Inc. Device 8226
        Flags: bus master, fast devsel, latency 0, IRQ 1276
        Memory at febc0000 (64-bit, non-prefetchable) [size=256K]
        Expansion ROM at feba0000 [disabled] [size=128K]
        Capabilities: [40] Power Management version 2
        Capabilities: [48] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
        Capabilities: [58] Express Endpoint, MSI 00
        Kernel driver in use: atl1
        Kernel modules: atl1

ethtool eth0:

Code:

Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  Not reported
        Advertised auto-negotiation: No
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: umbg
        Wake-on: d
        Link detected: yes

stefan_nicolau · 05-27-2008, 09:04 AM

I have the same card running in gigabit (autonegotiated) mode on Ubuntu 2.6.24-16-generic amd64. I had the same problem as you at first, but changing the cable was all it took to fix it (even though the old cable was cat5, just like the new one).

Tomasu · 05-27-2008, 09:12 AM

Quote:

Originally Posted by stefan_nicolau

I have the same card running in gigabit (autonegotiated) mode on Ubuntu 2.6.24-16-generic amd64. I had the same problem as you at first, but changing the cable was all it took to fix it (even though the old cable was cat5, just like the new one).

Damn, I had a feeling it might be the cable. Checking the error count on the interface seems to suggest it (its one sided, only transmit has any errors). I guess I get to make a new cable