Eth1 init and link status

3 messages, 3 authors, 2007-09-19 · open the first message on its own page

Eth1 init and link status

From: - Reyneke <hidden>
Date: 2007-09-19 13:54:40

HI,

We've run into a bit of an odd problem and we are not sure where to go and 
look for the cause.

We have some 440EPx based hardware with two GIG-Ethernet ports using RGMII 
and 2x ET1011C PHY's. Problem is that eth1 will only initialise correctly 
(i.e. receive and transmit) if eth0 has a link. Eth0 always work OK, 
regardless of eth1 status. Eth1 will work OK if eth0 has a link (i.e. 
initialised) at time of setup. Once initialised, eth0 status is irrelevant. 
All this is during Linux boot process.

Any ideas?

We can access PHY registers via u-boot (mii commands). Same 1Gig link speed 
is used on both ports. Linux kernel is 2.6.19.

Regards
   Jan Reyneke

_________________________________________________________________
Can you see your house from the sky? Try Live Search Maps 
http://maps.live.com

Re: Eth1 init and link status

From: Josh Boyer <hidden>
Date: 2007-09-19 14:08:48

On Wed, 19 Sep 2007 13:54:35 +0000
"- Reyneke" [off-list ref] wrote:
HI,

We've run into a bit of an odd problem and we are not sure where to go and 
look for the cause.

We have some 440EPx based hardware with two GIG-Ethernet ports using RGMII 
and 2x ET1011C PHY's. Problem is that eth1 will only initialise correctly 
(i.e. receive and transmit) if eth0 has a link. Eth0 always work OK, 
regardless of eth1 status. Eth1 will work OK if eth0 has a link (i.e. 
initialised) at time of setup. Once initialised, eth0 status is irrelevant. 
All this is during Linux boot process.

Any ideas?

We can access PHY registers via u-boot (mii commands). Same 1Gig link speed 
is used on both ports. Linux kernel is 2.6.19.
Where did you get your kernel from?  2.6.19 doesn't have any 440EPx
support in it.  Maybe you should ask your vendor.

josh

Re: Eth1 init and link status

From: Jeyner Gil Caga <hidden>
Date: 2007-09-19 15:35:27

In you statement, initialise correctly (i.e. receive and transmit), did you
use like ping or ftp to do it?

What do you mean by the word initialise?
Are you saying that after Linux has completely booted up:
1. you have one computer pinging to eth0 and you can ping eth0?
2. if eth0 is connected to the network, you use the same computer to ping
eth1 and you can ping eth1?
3. while you are pinging eth1 and you disconnect eth0 from the network,you
can not ping eth1?

On 9/19/07, - Reyneke [off-list ref] wrote:
HI,

We've run into a bit of an odd problem and we are not sure where to go and
look for the cause.

We have some 440EPx based hardware with two GIG-Ethernet ports using RGMII
and 2x ET1011C PHY's. Problem is that eth1 will only initialise correctly
(i.e. receive and transmit) if eth0 has a link. Eth0 always work OK,
regardless of eth1 status. Eth1 will work OK if eth0 has a link (i.e.
initialised) at time of setup. Once initialised, eth0 status is
irrelevant.
All this is during Linux boot process.

Any ideas?

We can access PHY registers via u-boot (mii commands). Same 1Gig link
speed
is used on both ports. Linux kernel is 2.6.19.

Regards
  Jan Reyneke

_________________________________________________________________
Can you see your house from the sky? Try Live Search Maps
http://maps.live.com

_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help