Opened 5 years ago

Last modified 4 years ago

#12433 new defect

Broken PHY on Compex WPE72 in Barrier Breaker

Reported by: eric.larson@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: Cc:


I'm running r34065 on a Compex WPE72.

During boot, both eth0 and eth1 is properly discovered, as well as the 8216 switch. swconfig works, as does all the IP addresses I set. I can ping the IP addresses using the OpenWrt console connected to the serial port on the board, and I see either port go into a forwarding state if I plug in an ethernet cable connected to my network, but I can never get the two leds on either ethernet connector to illuminate, nor can I ping the network from OpenWrt, or vice versa.

Let me know if you need this board.

Thank you.

Attachments (0)

Change History (3)

comment:1 Changed 5 years ago by anonymous

I am running Revision: 34398 on the same hardware, both Ethernet ports work and I can communicate, the issue that I am having which is similar is that ethtool does not understand eth1:

ethtool eth1

Settings for eth1:
Cannot get device settings: No such device

Current message level: 0x000000ff (255)

drv probe link timer ifdown ifup rx_err tx_err

Link detected: no

The eth1 port can not be seen in /sys/ either

root@-m71:/sys/devices/platform/ag71xx.1/net/eth1# cat speed
cat: read error: Invalid argument

comment:2 Changed 5 years ago by anonymous

I am seeing the same thing. When I look at dmesg in the boot it is actually registering the generic phy. Are you guys actually getting the 8216 registered?

dmeg | grep eth1

[ 2.770000] eth0: Atheros AG71xx at 0xb9000000, irq 4
[ 3.400000] ag71xx ag71xx.0: eth0: connected to PHY at ag71xx-mdio.0:04 [uid=004dd041, driver=Generic PHY]

comment:3 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

as new .

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.