This card was auto-detected and configured for DHCP like you would expect so it seemed like it would work at first.

I tried using several cross-over cables to get two of these cards working between a DamnSmall node and a Windows 2003 server. It would grab a DHCP IP OK and seem to be alive and working but would not communicate properly. PING's to or from the 2003 server would lock up the DamnSmallLinux node.

Thinking it was an OS glitch of some sort, I tried the same configuration with two DamnSmallLinux clients. I got the same results so I tried 5 other cards paired differently between the nodes. I also tried it on Knoppix 3.7. And finally gave up after recompiling my debian 2.6.10 to include support for this card and it still would freeze the machine on a PING.

This card worked right out of the box.

The only problem I had was when I upgrade the kernel using built-in Fedora updater, the card no longer recieves power from my mother board (Asus K7V), I don't know why. It could be a driver issue with the kernel or with my motherboard, and the board is 5 years old so that could very well be the case.

There must have been a typo... I wouldn't recommend this card.

doh!... I see the drop down yes/no now... No! x 3.

Still does not get auto detected, is not on the fedora drop down list for manuall config, now i have to get a router, my ISP does not utilize DHCP.

I read that this card was supported by the skge driver in 2.6 kernels, so I bought one. It turns out, D-Link has secretly changed their card. I actually got a D-Link 530T (rev 11) which is sufficiently different from a "normal" D-Link 530T that it doesn't work (pci id is 1186,4b01 instead of 1186,4c00)

[root@www ~]# lspci
03:06.0 Ethernet controller: D-Link System Inc Gigabit Ethernet Adapter (rev 11)

[root@www ~]# lspci -n
03:06.0 Class 0200: 1186:4c00 (rev 11)

[root@www ~]# dmesg
skge eth0: enabling interface
skge eth0: Link is up at 1000 Mbps, full duplex, flow control tx and rx

[root@www etc]# cat modprobe.conf
alias eth0 skge

eth0 Link encap:Ethernet HWaddr xxxxxx
inet addr:xxxxxx Bcast:xxxxx Mask:255.255.255.0
inet6 addr: xxxxxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11738587 errors:0 dropped:0 overruns:0 frame:0
TX packets:6720425 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2568087037 (2.3 GiB) TX bytes:3320361771 (3.0 GiB)
Interrupt:209

CentOS likes to use the SKGE driver and RedHat ES likes to use the sk98lin driver. Everything seems to be OK so far.. no major problems with anything.

Instructions/Documentation: Good

I receive an obscure error while trying to install via the package that came with the product. However when I did wht I should have (go out to the site and get the latest version of the sk98lin drivers :P) everything worked like a charm.

I purchased a revision 11 version of this card, and it would not work with any linux drivers. I think it was a Class 0200: 1186:4b00 (rev 11).

I am using CentOS 4 U4, and I tried the drivers that came with the kernel, namely, skge and sk98lin. Neither of them worked. Then, I tried downloading the linux driver from DLink and installing that. I got compile errors. So, that one would not work either.

I called DLink support, and they said that they are not supporting this card on Linux. I returned the card.

By the way, kudzu recognized the card, but it tried to load the sky2 driver for this card. This failed with errors.

Just got this card and installed it on a fresh machine 0 problems.
BUT it only runs at 100Mbps. I cant get it up to 1G. :(

ethtool -s eth0 speed 1000 duplex full

I've had 3 cards of this type, and all the time I've had a wide range of problems.
DHCP not working properly, packet loss and no DHCP recieved ip over (3 different) hubs and switches.
I've tried several kernels and the problems persists. After changeing it to an OLD card I had lying around the problems vanished!
So I would NOT recommend this cheap crap! I've been yelling at my poor ISP for 2 years because of these problems, as I thought there was not a chance that 3 cards could have the same problem.

Newer versions of this card do not seem to work with Linux.