From: Andrew Morton <akpm@osdl.org>
To: Brian Hall <brihall@pcisys.net>
Cc: linux-kernel@vger.kernel.org, linux@syskonnect.de
Subject: Re: Help: DGE-560T not recognized by Linux
Date: Fri, 17 Feb 2006 22:24:28 -0800 [thread overview]
Message-ID: <20060217222428.3cf33f25.akpm@osdl.org> (raw)
In-Reply-To: <20060217222720.a08a2bc1.brihall@pcisys.net>
Brian Hall <brihall@pcisys.net> wrote:
>
> I have just built a new system, based on an Asrock 939Dual-Sata
> motherboard. It only has 100MB built-in networking (uli526x), so I
> purchased a D-Link DGE-560T PCI-e gigabit NIC ($81 at Newegg) thinking
> it was supported by Linux. Looking at the card, it appears to be a
> Marvell chip, but neither the sk98lin or skge drivers worked. I tried
> other GBe drivers as well, they didn't recognize it either.
>
> Is there a place where I can just add this card's ID and use one of the
> sk* drivers? I paged through the source but didn't see an obvious place
> to add a card ID, but it must be in there somewhere.
>
> I'm not subscribed to linux-kernel, please CC: me on replies, thanks.
>
> Here's the info from the card:
> big M on the chip (Marvell I assume)
> 88E8052-NNC
> GMAA17011A1
> 0442 A2P
>
> and on the back of the card:
>
> 00005A708649 0592
> DLink
> 531CL00467 DGE-560T 70-13-001-001
>
> from lspci:
>
> 02:00.0 0200: 1186:4b00 (rev 11)
> Subsystem: 1186:4b00
See drivers/net/sk98lin/skge.c:skge_pci_tbl[]:
/* DLink card does not have valid VPD so this driver gags
* { PCI_VENDOR_ID_DLINK, 0x4c00, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
*/
That's your card, except yours is 0x4b00.
You can try it, but it might gag...
Also see drivers/net/skge.c:skge_id_table[]:
{ PCI_DEVICE(PCI_VENDOR_ID_DLINK, PCI_DEVICE_ID_DLINK_DGE510T), },
That's the same device as in sk98lin/skge.c. Try adding a line
{ PCI_DEVICE(PCI_VENDOR_ID_DLINK, 0x4b00), },
next prev parent reply other threads:[~2006-02-18 6:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 5:27 Brian Hall
2006-02-18 5:40 ` Randy.Dunlap
2006-02-18 6:24 ` Andrew Morton [this message]
2006-02-18 7:36 ` Brian Hall
2006-02-18 7:48 ` Andrew Morton
2006-02-18 15:54 ` Edgar Hucek
2006-02-18 17:01 ` Brian Hall
2006-02-18 19:29 ` Sergey Vlasov
2006-02-19 0:35 ` Stephen Hemminger
2006-02-19 1:04 ` Greg KH
2006-02-19 16:20 ` Brian Hall
2006-02-19 17:13 ` Andi Kleen
2006-02-28 15:08 ` Brian Hall
2006-02-20 11:43 ` Willy Tarreau
2006-02-20 12:56 ` Sergey Vlasov
2006-02-22 3:51 ` Brian Hall
2006-02-22 19:51 ` Stephen Hemminger
2006-02-19 2:55 ` Brian Hall
2006-02-19 7:41 ` jerome lacoste
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=20060217222428.3cf33f25.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=brihall@pcisys.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@syskonnect.de \
/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