public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Ryan S. Upton" <rupton@pobox.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: DFE-580TX problems you posted on 05-24-02
Date: Tue, 23 Jul 2002 14:39:56 -0700	[thread overview]
Message-ID: <3D3DCD2C.1050004@candelatech.com> (raw)
In-Reply-To: 20020723203037.GA29459@pobox.com

Ryan S. Upton wrote:
> I apologise for this imposition. I'm sending you mail that only asks for help. I was hoping you found a solution to the problems you were seeing about the Dlink DEF-580tx. I say the message you sent into kernel.org. 
> 
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0205.3/0013.html
> 
> I've been looking for three days for a solution to the same problems iyou described. I am seeing these with a newly compiled 2.4.18 kernel. Have you had any success since May? 
> 
> Thanks,
> -R
> 

I'm CC'ing LMKL in hopes that this gets in the search engines so that I
quit getting 5 of these mails a day :)

The fix for the DFE-580tx in Linux is to either download the driver
from dlink's site (I don't have the exact URL, but you can find it if
you look.), or perhaps use Becker's latest driver from www.scyld.com.

I hear the kernel will be updated with a working driver very soon (maybe
it has already??)

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



       reply	other threads:[~2002-07-23 21:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020723203037.GA29459@pobox.com>
2002-07-23 21:39 ` Ben Greear [this message]
2002-07-24 15:25   ` DFE-580TX problems you posted on 05-24-02 Jason Lunz
2002-09-05 21:35   ` Ryan S. Upton
2002-09-09 16:42     ` Stephan von Krawczynski

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=3D3DCD2C.1050004@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rupton@pobox.com \
    /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