fcc_enet Phy detection

fcc_enet Phy detection

[Adam Wozniak]

(solved previous problem, Dan Malek was right; it was an incorrect DRAM
refresh parameter)

Is this normal?

eth0: FCC ENET Version 0.2, 08:00:22:70:70:63
fec: Phy @ 0x0, type 0x00000000
fec: Phy @ 0x1, type 0x00000000
fec: Phy @ 0x2, type 0x00000000
fec: Phy @ 0x3, type 0x00000000
fec: Phy @ 0x4, type 0x00000000
fec: Phy @ 0x5, type 0x00000000
fec: Phy @ 0x6, type 0x00000000
fec: Phy @ 0x7, type 0x00000000
fec: Phy @ 0x8, type 0x00000000
fec: Phy @ 0x9, type 0x00000000
fec: Phy @ 0xa, type 0x00000000
fec: Phy @ 0xb, type 0x00000000
fec: Phy @ 0xc, type 0x00000000
fec: Phy @ 0xd, type 0x00000000
fec: Phy @ 0xe, type 0x00000000
fec: Phy @ 0xf, type 0x00000000
fec: Phy @ 0x10, type 0x00000000
fec: Phy @ 0x11, type 0x00000000
fec: Phy @ 0x12, type 0x00000000
fec: Phy @ 0x13, type 0x00000000
fec: Phy @ 0x14, type 0x00000000
fec: Phy @ 0x15, type 0x00000000
fec: Phy @ 0x16, type 0x00000000
fec: Phy @ 0x17, type 0x00000000
fec: Phy @ 0x18, type 0x00000000
fec: Phy @ 0x19, type 0x00000000
fec: Phy @ 0x1a, type 0x00000000
fec: Phy @ 0x1b, type 0x00000000
fec: Phy @ 0x1c, type 0x00000000
fec: Phy @ 0x1d, type 0x00000000
fec: Phy @ 0x1e, type 0x00000000
fec: Phy @ 0x1f, type 0x00000000

--
Adam Wozniak (KG6GZR)   COM DEV Wireless - Digital and Software Systems
awozniak@comdev.cc      3450 Broad St. 107, San Luis Obispo, CA 93401
                        http://www.comdev.cc
                        Voice: (805) 544-1089       Fax: (805) 544-2055

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: fcc_enet Phy detection

[Adam Wozniak]

Is this normal?


eth0      Link encap:Ethernet  HWaddr 08:00:22:70:70:63
          inet addr:192.168.67.56  Bcast:192.168.67.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9586 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6231 errors:43 dropped:0 overruns:43 carrier:6188
          collisions:7 txqueuelen:100
          RX bytes:4919915 (4.6 Mb)  TX bytes:741495 (724.1 kb)
          Base address:0x8600

I'm getting a "carrier lost" for every sent packet.
When I telnet in, the telnet session hangs, usually after a few
commands,
and the "overruns" (typo? should be underruns?) and "errors" increment
by either 2 (typical) or 1 (sometimes).

Any help is appreciated.

--Adam
--
Adam Wozniak (KG6GZR)   COM DEV Wireless - Digital and Software Systems
awozniak@comdev.cc      3450 Broad St. 107, San Luis Obispo, CA 93401
                        http://www.comdev.cc
                        Voice: (805) 544-1089       Fax: (805) 544-2055

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: fcc_enet Phy detection

[Dan Malek]

Adam Wozniak wrote:
>
> Is this normal?

No. I seems your hardware pin configuration to the PHY doesn't
match the driver configuration, or the PHY configuration doesn't
match the hub at the other end.


	-- Dan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/