netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mitchell Blank Jr <mitch@sfgoth.com>
To: sparclinux@vger.kernel.org
Cc: netdev@oss.sgi.com
Subject: sunhme stopped working somewhere in 2.6.0-test4
Date: Sat, 6 Sep 2003 21:31:51 -0700	[thread overview]
Message-ID: <20030907043151.GB33595@gaz.sfgoth.com> (raw)

I had been running 2.6.0-test4 on my Ultra 10 for the last week without
problems.  Tonight I tried upgrading it to 2.6.0-test4-bk8 (which works
fine on my i386 test box) and the builtin sunhme card no longer functions.
When you try to do a "ifconfig eth0 up" I get the following on this console...

  happy meal: Aieee, transceiver MIF write bolixed
  happy meal: Aieee, transceiver MIF read bolixed

...and the operation fails.  It looks like there's been a number of changes
to sunhme in the last week (ethtool stuff, maybe some other things).... does
anyone have a hunch what I should try to change (or has this already been
fixed in BK perhaps?)

-Mitch

             reply	other threads:[~2003-09-07  4:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-07  4:31 Mitchell Blank Jr [this message]
2003-09-07  4:45 ` sunhme stopped working somewhere in 2.6.0-test4 Mitchell Blank Jr

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=20030907043151.GB33595@gaz.sfgoth.com \
    --to=mitch@sfgoth.com \
    --cc=netdev@oss.sgi.com \
    --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 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).