All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Finnegan <pat@computer-refuge.org>
To: sparclinux@vger.kernel.org
Subject: Re: Boot problems on a V880
Date: Thu, 03 Dec 2009 06:48:12 +0000	[thread overview]
Message-ID: <200912030148.12737.pat@computer-refuge.org> (raw)
In-Reply-To: <200911262202.45791.pat@computer-refuge.org>

On Tuesday 01 December 2009, David Miller wrote:
> From: Patrick Finnegan <pat@computer-refuge.org>
> Date: Mon, 30 Nov 2009 23:04:31 -0500
> 
> > I re-ran prtconf -pv under the 2.6.32-rc3 from your sparc git tree,
> > and have the output here (it looks like it has what you're looking
> > for):
> >
> > http://ned.cc.purdue.edu/prtconf-v880
> 
> Linus's tree has the fix, via my net-2.6 tree, so if you use a pure
> sparc-2.6 tree you won't have it.

Ok. this looks like it fixes the problem with the fiber-port gem, but 
the 10/100 TP gem just bounces back and forth between these messages, 
and never gets link:

[  174.260495] eth0: switching to forced 10bt             
[  194.660290] eth0: switching to forced 100bt            

Ideas?  It does this even with the interface not configured (down 
according to ifconfig), which is kinda annoying on the console... I have 
to do an "ethtool -s eth0 autoneg off" to make it stop.

Pat
-- 
Purdue University Research Computing ---  http://www.rcac.purdue.edu/
The Computer Refuge                  ---  http://computer-refuge.org

  parent reply	other threads:[~2009-12-03  6:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27  3:02 Boot problems on a V880 Patrick Finnegan
2009-11-27  7:30 ` David Miller
2009-11-28  1:52 ` Patrick Finnegan
2009-11-28  2:30 ` David Miller
2009-11-28  3:07 ` Patrick Finnegan
2009-11-30 21:02 ` Patrick Finnegan
2009-11-30 21:05 ` David Miller
2009-12-01  4:04 ` Patrick Finnegan
2009-12-01  5:48 ` David Miller
2009-12-03  6:48 ` Patrick Finnegan [this message]
2009-12-03  6:56 ` David Miller

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=200912030148.12737.pat@computer-refuge.org \
    --to=pat@computer-refuge.org \
    --cc=sparclinux@vger.kernel.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.