On Wed, Feb 25, 2009 at 8:25 PM, Mike Ditto <mdi...@consentry.com> wrote:
> Daniel Ng wrote:
>>> f0010d40:00 not found
>>> eth0: Could not attach to PHY
> These messages are typical of having the wrong GPIO pins in the mdio
> node or the wrong MDIO address (reg property) in the ethernet-phy node.
>
>>> Currently, our PHY
>>> attributes eg. 'auto-negotiate' are not changeable, so we aren't
>>> actually using MDC+MDIO even though the MDC+MDIO lines exist.
>
> The driver definitely tries to talk to the PHY using the GPIO pins
> and address specified and if it doesn't respond, it won't attach.
>
Thanks Mike. I pulled out the PHY-dependancies in the fs-enet code and
I'm *almost* there!
Here's the relevant boot output with some additional debug:
fs_init(): start
fs_enet_probe() start
fs_enet_get_stats() start
eth0: fs_enet: 7e:13:12:53:a1:75
fs_enet_probe(): registered. dev: eth0
...
dev_open(): calling dev_activate for dev: lo
dev_open(): finishing for dev: lo
fs_enet_open(): start. dev: eth0
dev_open(): calling dev_activate for dev: eth0
dev_open(): finishing for dev: eth0
fs_enet_get_stats()
IP-Config: Complete:
device=eth0, addr=192.168.1.75, mask=255.255.255.0, gw=255.255.255.255,
host=xxx, domain=, nis-domain=(none),
bootserver=192.168.1.133, rootserver=192.168.1.133, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.133
dev_hard_start_xmit(): start. dev: lo
dev_hard_start_xmit(): about to call c015baa0
dev_hard_start_xmit(): start. dev: lo
dev_hard_start_xmit(): about to call c015baa0
rpcbind: server 192.168.1.133 not responding, timed out
As you can see from the above, the NFS client tries to contact the
server on the lo interface rather than eth0.
This is despite IP-Config reporting 'Complete' for eth0.
If I set the Gateway parameter for the NFS client to 192.168.1.133 I get this:
fs_init(): start
fs_enet_probe() start
fs_enet_get_stats() start
eth0: fs_enet: 7e:13:12:53:a1:75
fs_enet_probe(): registered. dev: eth0
...
dev_open(): calling dev_activate for dev: lo
dev_open(): finishing for dev: lo
fs_enet_open(): start. dev: eth0
dev_open(): calling dev_activate for dev: eth0
dev_open(): finishing for dev: eth0
fs_enet_get_stats()
IP-Config: Gateway not on directly connected network.
Looking up port of RPC 100003/2 on 192.168.1.133
dev_hard_start_xmit(): start. dev: lo
dev_hard_start_xmit(): about to call c015baa0
dev_hard_start_xmit(): start. dev: lo
dev_hard_start_xmit(): about to call c015baa0
rpcbind: server 192.168.1.133 not responding, timed out
-IP-Config complains the Gateway (192.168.1.133) is not on a
directly-connected network, even though the IP address of eth0 is
192.168.1.75/24.
So this implies eth0 is not 100% up.
Would someone be able to suggest why this is so? What else could I do
to check the state of eth0?
Cheers,
Daniel
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
