All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Danter <richard.danter@ntlworld.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: linux-2.6.10, ppc8280, odd ARP request - solved
Date: Thu, 12 May 2005 12:31:39 +0100	[thread overview]
Message-ID: <42833E9B.3090608@ntlworld.com> (raw)
In-Reply-To: <427F553A.1060506@ntlworld.com>

Richard Danter wrote:
> 
> My board boots using U-Boot. It tftp loads the kernel image via FCC2, so 
> I know the FCC's are working (I have tested the others too). This part 
> is fine, but once the kernel has loaded it tries to NFS mount the root 
> filesystem. When it gets to the point of looking up the RPC port it 
> first sends an ARP request for the server. When eth0 is any of the FCC's 
> I see a 59 byte packet on the wire (using ethereal). The server either 
> does not see the packet or just ignores it so there is no reply to the 
> board.
> 
> When I boot using SCC1 as eth0 the ARP request sent is 60 bytes long. It 
> is replied to and the NFS mount works.
> 
> I noticed that U-Boot also sends an ARP request before the tftp download 
> starts and it is 60 bytes long using both SCC and FCC ports. But as far 
> as I know, ARP requests can be varying length (the last few bytes seem 
> to be just padding).

Looks like the problem may be with the setup of the FCC, particularly 
with working out what speed to run at. I connected my board to a 
100BaseT hub and it worked perfectly. It was failing when I was using an 
older 10BaseT hub. In both cases the hub is a Netgear and I have never 
had a problem with any other board or PC.

Odd how it effects Linux but not U-Boot. Seems to indicate a driver 
issue anyway.

Rich

      reply	other threads:[~2005-05-12 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 12:19 linux-2.6.10, ppc8280, odd ARP request Richard Danter
2005-05-12 11:31 ` Richard Danter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42833E9B.3090608@ntlworld.com \
    --to=richard.danter@ntlworld.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.