linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Late Broadcom link detection makes IP config (bootp) fail
Date: Mon, 22 Oct 2001 10:31:49 +0800	[thread overview]
Message-ID: <3BD38515.40808@metaparadigm.com> (raw)


Hi,

I just compiled up 2.4.13-pres-benh0 and am trying to netboot my iMac.
I am using the following commandline:

     ip=bootp nfsroot=10.1.0.7:/nb/root,rw

The boot messages show that the broadcom is found:

     eth0: Found broadcom BCM5201 PHY

IP-Config initialises but doesn't send any request as I suspect the link
on eth0 is down. Root NFS then runs and fails due to network being down.

Later in the logs after unable to mount root kernel panic I see:

     eth0:    Link up ! BCM5201/5221 aux_stat: 0x003e
     eth0:    Full duplex: 0, Speed: 100

Why does the eth0 link come up so late? Is it possible to make the
broadcom driver wait for link before returning from the initialisation
function?

~mc


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

             reply	other threads:[~2001-10-22  2:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22  2:31 Michael Clark [this message]
2001-10-22  2:57 ` Late Broadcom link detection makes IP config (bootp) fail Tom Rini
2001-10-22  3:17   ` Michael Clark
2001-10-22  3:28     ` Tom Rini
2001-10-22  3:24   ` Michael Clark
2001-10-22  3:28     ` Tom Rini
2001-10-22  4:31       ` Michael Clark
2001-10-22 13:17         ` Benjamin Herrenschmidt
2001-10-22 13:16     ` Benjamin Herrenschmidt
2001-10-22 15:41       ` Tom Rini
2001-10-22 15:46         ` Geert Uytterhoeven
2001-10-22 16:42         ` Michael Clark

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=3BD38515.40808@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).