D-Link DFE-690TXD CardBus NIC driver hassle

Trying to get my Dell laptop connected to the net, and it just ain't
working.

First attempt: RedHat 7.0.

The NIC isn't recognized at installation time. D-Link provided a Linux
driver on the CD (in source form), but it won't compile. I finally
figure out that the provided instructions are wrong (gcc wasn't able to
find the kernel headers) and manage to build and install the damn thing.
It works, except for the fact that the system now tends to crash while
accessing the network. Oops.


Second attemp: Debian Woody (with the default kernel: 'uname -r' shows
'2.2.20-idepci')

During installation, I select the driver 8139too (which is supposedly
the right one). It won't load - I get the following message:

/lib/modules/2.2.20-idepci/net/8139too.o: init_module: Device or
resource busy

(I try it with a few other NIC drivers, just for the hell of it, and get
the exact same result.) Running 'modprobe 8139too' after installation
gives the same error message as above. Running 'lspci -v' with the card
plugged in shows this information:

23:00.0 Ethernet Controller: D-Link System Inc: Unknown device 1340 (rev
10)
Subsystem: D-Link System Inc: Unknown device 1340
Flags: medium devsel
I/O ports at <unassigned> [disabled]
Memory at <ignored> (32-bit, non-prefetchable)
Capabilities: [50] Power Management version 2

Anybody have any ideas?

-MB

--
http://macbuild.sourceforge.net/

On Mon, 29 Sep 2003 06:01:58 +0000, Mike Baranczak wrote:

> Trying to get my Dell laptop connected to the net, and it just ain't
> working.
>
> First attempt: RedHat 7.0.
>
> The NIC isn't recognized at installation time. D-Link provided a Linux
> driver on the CD (in source form), but it won't compile. I finally
> figure out that the provided instructions are wrong (gcc wasn't able to
> find the kernel headers) and manage to build and install the damn thing.
> It works, except for the fact that the system now tends to crash while
> accessing the network. Oops.
>
>
> Second attemp: Debian Woody (with the default kernel: 'uname -r' shows
> '2.2.20-idepci')
>
> During installation, I select the driver 8139too (which is supposedly
> the right one). It won't load - I get the following message:
>
> /lib/modules/2.2.20-idepci/net/8139too.o: init_module: Device or
> resource busy
>
> (I try it with a few other NIC drivers, just for the hell of it, and get
> the exact same result.) Running 'modprobe 8139too' after installation
> gives the same error message as above. Running 'lspci -v' with the card
> plugged in shows this information:
>
> 23:00.0 Ethernet Controller: D-Link System Inc: Unknown device 1340 (rev
> 10)
> Subsystem: D-Link System Inc: Unknown device 1340 Flags: medium devsel
> I/O ports at <unassigned> [disabled]
> Memory at <ignored> (32-bit, non-prefetchable) Capabilities: [50] Power
> Management version 2
>
> Anybody have any ideas?
>
> -MB
>
How did you pick the distributions you tested? I'd try Redhat 8.0,
Redhat 9.0 as a first try. The 2.4.x kernel series is much better than
2.2.x.

You seem to know what your doing. Slackware 9.1 is out and is very
stable (and cool!) It works with this PCMCIA network adapter with the
8139too module.

--Douglas Mayne

Douglas Mayne wrote:
> On Mon, 29 Sep 2003 06:01:58 +0000, Mike Baranczak wrote:
>
>
>>Trying to get my Dell laptop connected to the net, and it just ain't
>>working.
>>
>>First attempt: RedHat 7.0.
>>
>>The NIC isn't recognized at installation time. D-Link provided a Linux
>>driver on the CD (in source form), but it won't compile. I finally
>>figure out that the provided instructions are wrong (gcc wasn't able to
>>find the kernel headers) and manage to build and install the damn thing.
>>It works, except for the fact that the system now tends to crash while
>>accessing the network. Oops.
>>
>>
>>Second attemp: Debian Woody (with the default kernel: 'uname -r' shows
>>'2.2.20-idepci')
>>
>>During installation, I select the driver 8139too (which is supposedly
>>the right one). It won't load - I get the following message:
>>
>>/lib/modules/2.2.20-idepci/net/8139too.o: init_module: Device or
>>resource busy
>>
>>(I try it with a few other NIC drivers, just for the hell of it, and get
>>the exact same result.) Running 'modprobe 8139too' after installation
>>gives the same error message as above. Running 'lspci -v' with the card
>>plugged in shows this information:
>>
>>23:00.0 Ethernet Controller: D-Link System Inc: Unknown device 1340 (rev
>>10)
>>Subsystem: D-Link System Inc: Unknown device 1340 Flags: medium devsel
>>I/O ports at <unassigned> [disabled]
>>Memory at <ignored> (32-bit, non-prefetchable) Capabilities: [50] Power
>>Management version 2
>>
>>Anybody have any ideas?
>>
>>-MB
>>
>
> How did you pick the distributions you tested? I'd try Redhat 8.0,
> Redhat 9.0 as a first try. The 2.4.x kernel series is much better than
> 2.2.x.

Debian was my first choice, but I just happened to have the RedHat 7.0
CDs lying around.

>
> You seem to know what your doing. Slackware 9.1 is out and is very
> stable (and cool!) It works with this PCMCIA network adapter with the
> 8139too module.
>
> --Douglas Mayne

I gave up on the D-Link card, and exchanged it for a NetGear FA511. This
time, I took the laptop to the store with me, opened up
/etc/pcmcia/config and picked one of the cards that was listed there.
The new card worked right out of the box (I'm using it to post this).

Moral is: just because the box says "linux compatible", don't assume
anything.

-MB