Re: alc(4) link handling [was: Re: ath(4) Atheros AR9285 support]

From: Pyun YongHyeon <pyunyh_at_gmail.com>
Date: Mon, 14 Sep 2009 10:38:05 -0700
On Sun, Sep 13, 2009 at 08:27:10PM +0400, Sergey Vinogradov wrote:
> В Tue, 8 Sep 2009 13:45:20 -0700
> Pyun YongHyeon <pyunyh_at_gmail.com> пишет:
> 
> [snip]
>  
> > Would you give more details on this? Showing me demsg(8) output
> > related with alc(4) and atphy(4) would be good help.
> > When I tried AR8132 sample board it had no such problems on my box.
> > AR8132 uses F1 PHY even if it support only 10/100Mbps link so this
> > might cause problems on your box, I guess. Does your link partner
> > support only 10/100Mbps?
> 
> Sorry for the delay. Well, the 10/100 seems to be working, I've used
> bad patch cord previous time. But gigabit link doesn't go up (at least

It's quite normal because your controller *is* fast ethernet. You
can't establish a gigabit link.

> in auto-negotiate mode, I'll try to set modes manually when I'll get

Hmm, AR8132 uses F1 gigabit PHY but Atheros changed its internal
circuit such that it operates as 10/100 PHY. I guess it's more
appropriate to disable advertisement of 1000baseT capability for
AR8132 case. Would you try attached patch?
In "ifconfig -m alc0" output you should not see 1000baseT
capability.

> to gigabit hardware again). Here is the 'pciconf -lv' outtake:
> 
> alc0_at_pci0:1:0:0:        class=0x020000 card=0x838a1043 chip=0x10621969 rev=0xc0 hdr=0x00
>     vendor     = 'Attansic (Now owned by Atheros)'
>     class      = network
>     subclass   = ethernet
> 
> And the 'dmesg | egrep (alc|atphy)' with verbose boot on:
> 
> alc0: <Atheros AR8132 PCIe Fast Ethernet> port 0xec00-0xec7f mem
> 0xf7fc0000-0xf7ffffff irq 19 at device 0.0 on pci1 alc0: Reserved
> 0x40000 bytes for rid 0x10 type 3 at 0xf7fc0000 alc0: Read request
> size : 512 bytes. alc0: TLP payload size : 128 bytes.
> alc0: RCB 64 bytes
> alc0: ASPM L1 enabled
> alc0: PCI device revision : 0x00c0
> alc0: Chip id/revision : 0xc002
> alc0: 15872 Tx FIFO, 15360 Rx FIFO
> alc0: MSIX count : 0
> alc0: MSI count : 1
> alc0: attempting to allocate 1 MSI vectors (1 supported)
> alc0: using IRQ 256 for MSI
> alc0: Using 1 MSI message(s).
> miibus0: <MII bus> on alc0
> atphy0: <Atheros F1 10/100/1000 PHY> PHY 0 on miibus0
> atphy0: OUI 0x001374, model 0x0001, rev. 11
> atphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX,
> auto alc0: bpf attached
> alc0: Ethernet address: 00:26:18:a1:f0:d0
> alc0: [MPSAFE]
> alc0: [FILTER]
> 

I don't see any problems from output above.

> -- 
> wbr,
> Boo



Received on Mon Sep 14 2009 - 15:39:01 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:55 UTC