Subject: Re: DGE-530T NIC support? (device not configured in dmesg output)
To: Tillman Hodgson <tillman@seekingfire.com>
From: Jeff Rizzo <riz@NetBSD.org>
List: netbsd-users
Date: 05/29/2006 22:38:45
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigCDD60A7C799BD8B9B9FA5799
Content-Type: multipart/mixed;
boundary="------------020100080301040601070503"
This is a multi-part message in MIME format.
--------------020100080301040601070503
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Jeff Rizzo wrote:
> Tillman Hodgson wrote:
> =20
>> On Mon, May 29, 2006 at 11:37:44PM -0500, Jonathan A. Kollasch wrote:
>> =20
>> =20
>>> Yes, "not configured" in a dmesg means that no driver was found to
>>> attach to that hardware. I'd attempt to modify src/sys/dev/pci/if_sk=
=2Ec
>>> to attempt an attachment.
>>> =20
>>> =20
>> Taking a look at the driver, it seems that maybe I should be modifying=
>> this section:
>>
>> /* D-Link Systems products */
>> product DLINK DL1002 0x1002 DL-1002 10/100 Ethernet
>> product DLINK DFE530TXPLUS 0x1300 DFE-530TXPLUS 10/100 Ethernet
>> product DLINK DFE690TXD 0x1340 DFE-690TXD 10/100 Ethernet
>> product DLINK DL4000 0x4000 DL-4000 Gigabit Ethernet
>> product DLINK DGE528T 0x4300 DGE-528T Gigabit Ethernet
>> product DLINK DGE530T 0x4c00 DGE-530T Gigabit Ethernet
>>
>> of src/sys/dev/pci/pcidevs?
>>
>> I'll try it and see how it goes.
>>
>> -T
>>
>>
>> =20
>> =20
>
> It would help to identify _which_ chipset it's actually using - it's
> conceivable that adding support is simple. Can you send me whatever
> information you can glean off the big chip on the board? Part numbers,=
> manufacturer, anything...
>
> +j
>
>
> =20
Looking at this a bit more closely, the product ID in your dmesg
(0x4b01) matches the "DGE560T_2", which might work with the sk(4) driver
as-is. As a quick test, you could try the patch attached - if it works,
I can cook up a real one.
+j
--------------020100080301040601070503
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
name="dge-patch"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline;
filename="dge-patch"
Index: if_sk.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /usr/mirror/main/src/sys/dev/pci/if_sk.c,v
retrieving revision 1.25
diff -u -r1.25 if_sk.c
--- if_sk.c 17 Apr 2006 13:02:01 -0000 1.25
+++ if_sk.c 30 May 2006 05:27:18 -0000
@@ -264,6 +264,7 @@
} sk_products[] =3D {
{ PCI_VENDOR_3COM, PCI_PRODUCT_3COM_3C940, },
{ PCI_VENDOR_DLINK, PCI_PRODUCT_DLINK_DGE530T, },
+ { PCI_VENDOR_DLINK, 0x4b01, },
{ PCI_VENDOR_LINKSYS, PCI_PRODUCT_LINKSYS_EG1064, },
{ PCI_VENDOR_SCHNEIDERKOCH, PCI_PRODUCT_SCHNEIDERKOCH_SKNET_GE, },
{ PCI_VENDOR_SCHNEIDERKOCH, PCI_PRODUCT_SCHNEIDERKOCH_SK9821v2, },
@@ -1716,12 +1717,14 @@
case PCI_PRODUCT_SCHNEIDERKOCH_SK9821v2:
case PCI_PRODUCT_3COM_3C940:
case PCI_PRODUCT_DLINK_DGE530T:
+ case 0x4b01:
case PCI_PRODUCT_LINKSYS_EG1032:
case PCI_PRODUCT_LINKSYS_EG1064:
case PCI_ID_CODE(PCI_VENDOR_SCHNEIDERKOCH,
PCI_PRODUCT_SCHNEIDERKOCH_SK9821v2):
case PCI_ID_CODE(PCI_VENDOR_3COM,PCI_PRODUCT_3COM_3C940):
case PCI_ID_CODE(PCI_VENDOR_DLINK,PCI_PRODUCT_DLINK_DGE530T):
+ case PCI_ID_CODE(PCI_VENDOR_DLINK,0x4b01):
case PCI_ID_CODE(PCI_VENDOR_LINKSYS,PCI_PRODUCT_LINKSYS_EG1032):
case PCI_ID_CODE(PCI_VENDOR_LINKSYS,PCI_PRODUCT_LINKSYS_EG1064):
sc->sk_name =3D sc->sk_vpd_prodname;
--------------020100080301040601070503--
--------------enigCDD60A7C799BD8B9B9FA5799
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBRHvaZbOuUtxCgar5AQOMBgP/a9Q8aPxnHmHYO5PBmzStJ3RWpqfla4NI
z8Bv1y3bWChywML2315a761HZxjtJchhS6diLa3Kn85p/AwrbCMiHlimDW89dNEw
I0xXQT3XbzckixhkGn/2IhGgCf3VhCXWoNYjlEc0ggIy1hiT8t8Eyf2kr5+EgpOC
SrOkt5BvS7c=
=t6q8
-----END PGP SIGNATURE-----
--------------enigCDD60A7C799BD8B9B9FA5799--