mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernhard Rosenkraenzer <bero@arklinux.org>
To: linux-kernel@vger.kernel.org
Cc: dhollis@davehollis.com
Subject: 2.6.19-rc2-mm2: D-Link DUB-E100 Rev. B broken
Date: Mon, 23 Oct 2006 20:41:48 +0200	[thread overview]
Message-ID: <200610232041.48998.bero@arklinux.org> (raw)

Hi,
D-Link DUB-E100 Rev. B USB Ethernet adapters have worked ok in some recent 
kernels - in rc2-mm2, they're broken again; they're detected correctly and 
the asix module is autoloaded, but after "ifconfig eth0 192.168.0.15 netmask 
255.255.255.0", the box becomes unresponsive and keeps repeating

eth0: Failed to enable software MII access
eth0: Failed to enable hardware MII access
eth0: Failed to enable software MII access
eth0: Failed to enable hardware MII access
eth0: Failed to enable software MII access
eth0: Failed to enable hardware MII access
eth0: Failed to enable software MII access
eth0: Failed to enable hardware MII access
eth0: Failed to enable software MII access
eth0: Failed to enable hardware MII access
eth0: Failed to write Medium Mode to 0x0334: ffffff92

This loops infinitely.

Last known working is 2.6.17 with a patch to bring the asix driver up to the 
14-Jun-2006 revision, first known broken is 2.6.19-rc1-mm1. (I'll try to 
figure out what exact change broke it, but this will take forever on this 
hw).

             reply	other threads:[~2006-10-23 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23 18:41 Bernhard Rosenkraenzer [this message]
2006-10-23 19:05 ` David Hollis
2006-10-23 19:45   ` Bernhard Rosenkraenzer
2006-10-23 19:59     ` Bernhard Rosenkraenzer

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=200610232041.48998.bero@arklinux.org \
    --to=bero@arklinux.org \
    --cc=dhollis@davehollis.com \
    --cc=linux-kernel@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

Powered by JetHome