From: kwijibo@zianet.com
To: Donald Becker <becker@scyld.com>
Cc: Matthew Hall <matt@ecsc.co.uk>,
Kernel <linux-kernel@vger.kernel.org>,
jgarzik@mandrakesoft.com
Subject: Re: [PROBLEM] sundance on d-link dfe-580tx
Date: Thu, 11 Jul 2002 20:41:47 -0600 [thread overview]
Message-ID: <3D2E41EB.6040504@zianet.com> (raw)
In-Reply-To: Pine.LNX.4.33.0206112336340.2253-100000@presario
Just to give some confirmation of the operation of this new driver.
I had had the same error messages as Matthew did. I followed
the instructions on Donald's site on making the new drivers and
it works great now. It found everything correctly with the following
output:
sundance.c:v1.07 7/3/2002 Written by Donald Becker <becker@scyld.com>
http://www.scyld.com/network/sundance.html
eth0: OEM Sundance Technology ST201 at 0xdc00, 00:05:5d:e6:2b:19, IRQ 11.
eth0: MII PHY found at address 0, status 0x782d advertising 01e1.
eth0: MII PHY found at address 1, status 0x782d advertising 01e1.
eth1: OEM Sundance Technology ST201 at 0xd880, 00:05:5d:e6:2b:1a, IRQ 10.
eth1: MII PHY found at address 0, status 0x7809 advertising 01e1.
eth1: MII PHY found at address 1, status 0x7809 advertising 01e1.
eth2: OEM Sundance Technology ST201 at 0xd800, 00:05:5d:e6:2b:1b, IRQ 9.
eth2: MII PHY found at address 0, status 0x7809 advertising 01e1.
eth2: MII PHY found at address 1, status 0x7809 advertising 01e1.
eth3: OEM Sundance Technology ST201 at 0xd480, 00:05:5d:e6:2b:1c, IRQ 11.
eth3: MII PHY found at address 0, status 0x7809 advertising 01e1.
eth3: MII PHY found at address 1, status 0x7809 advertising 01e1.
I am now sending this message over it.
Any idea when this will be merged into mainstream kernel?
Thanks,
Steven
Donald Becker wrote:
>On 11 Jun 2002, Matthew Hall wrote:
>
>
>
>>To: Kernel <linux-kernel@vger.kernel.org>
>>Cc: becker@scyld.com, jgarzik@mandrakesoft.com
>>
>>
>...
>
>
>>I have been testing the D-Link DFE-580TX Quad channel server card (4
>>port nic), on kernel 2.4.18 with little success.
>>
>>Attached are the appropriate results of dmesg, ifconfig, lspci and
>>modules.conf; aswell as the results of the pci-testing tool found on
>>scyld.com, however the card does not support mii testing, claiming to
>>have no MII transceiver.
>>
>>
>
>Please provide the full detection message.
>
>It appears that you are using a driver that doesn't correctly read the
>EEPROM, and has additional problems. Try a current driver from
> http://www.scyld.com/network/ethercard.html
> ftp://www.scyld.com/pub/network/sundance.c
> http://www.scyld.com/network/updates.html
>
>and run diagnostic program from
> http://www.scyld.com/diag/index.html
>
>
>
>
next prev parent reply other threads:[~2002-07-12 2:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 12:43 [PROBLEM] sundance on d-link dfe-580tx Matthew Hall
2002-06-12 3:39 ` Donald Becker
2002-06-13 14:57 ` Matthew Hall
2002-06-13 15:34 ` Ben Greear
2002-06-13 16:12 ` Donald Becker
2002-06-14 16:06 ` Matthew Hall
2002-06-14 21:52 ` Donald Becker
2002-06-21 5:27 ` Jeff Garzik
2002-06-21 12:17 ` Matthew Hall
2002-07-12 2:41 ` kwijibo [this message]
2002-06-14 10:15 ` Marcus Sundberg
[not found] ` <1024070521.973.48.camel@smelly.dark.lan>
[not found] ` <vevg8l25uq.fsf@inigo.ingate.se>
2002-06-17 14:58 ` Matthew Hall
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=3D2E41EB.6040504@zianet.com \
--to=kwijibo@zianet.com \
--cc=becker@scyld.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@ecsc.co.uk \
/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