D-Link DFE-530TX+ rtl8139.o
I have obtained the latest source for rtl8139.c. I have never compiled a
module before and I am getting a number of errors. It appears the source is
relying on a number of files being in the right place and they are not.
It sounds like a lot of people are using the driver that is automatically
installed without problems. It makes me wonder if it is some other problem.
I'm concerned that I could spend a week rewriting the source and makefile to
work on Debian then find out it was some other problem...
Has anyone else run into this problem and if so, did they modify the source
to work with a Debian install? If so would you share it? Am I just being a
whiner, because modifying the source is easy and I just need to look at the
right documentaton?
-----Original Message-----
From: Jason Gunthorpe [mailto:jgg@debian.org]
Sent: Monday, March 19, 2001 6:23 PM
To: David Carlile
Cc: Debian Users List; debian-boot@lists.debian.org
Subject: Re: FW: FW: D-Link DFE-530TX+ via-rhine.o module
On Mon, 19 Mar 2001, David Carlile wrote:
> I have been looking through the archive for references to the card and
> driver but all I come up with are posts about how easy it is to get this
> card running. People actually suggest this card to newbies because it is
so
Dlink changed the configuration of the realtek they were using during
later production runs. The particular card you have does not report itself
as a realtek, so the driver does not find it.
The only fix is to modify the kernel driver. The simplest route is to use
the donald becker drivers (http://www.scyld.com/network/) for the 8139
which has an entry, or you can modify the PCI probe of the linux drivers.
I would expect that the 2.4.2 kernels have this patch applied, but 2.4.0
did not..
It would be very nice if the next drop of the potato boot floopies
included an entry in the realtek driver code for this chip.
The update to the 2.4.0 8139too driver looks like this:
static struct pci_device_id rtl8139_pci_tbl[] __devinitdata = {
{0x10ec, 0x8139, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RTL8139 },
{0x10ec, 0x8138, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RTL8139_CB },
{0x1113, 0x1211, PCI_ANY_ID, PCI_ANY_ID, 0, 0, SMC1211TX },
/* {0x1113, 0x1211, PCI_ANY_ID, PCI_ANY_ID, 0, 0, MPX5030 },*/
{0x1500, 0x1360, PCI_ANY_ID, PCI_ANY_ID, 0, 0, DELTA8139 },
{0x4033, 0x1360, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ADDTRON8139 },
{0x1186, 0x1300, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RTL8139 }, // dlink
{0,}
};
A fix for the 2.2 kernel should be similar in nature, but the table looks
different IIRC.
Jason
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.230 / Virus Database: 111 - Release Date: 1/25/2001
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.230 / Virus Database: 111 - Release Date: 1/25/2001
Reply to: