>This is a 530TX+ we're talking about here, correct?
The box says DFE-538TX/R. The manual and disk omit the trailing "/R".
>About the only thing I can do is obtain a card like yours and play with
>it. If you can show me a link to the exact card that you have on the
>D-Link web site, I can see w
>
> Okay, tried this, same results. Still getting a 6 in the capabilities.
G
> I'm not familiar with the VIA Rhine. How can I check this?
It's a moot point. I realized that in your earlier mail, you claimed
that the card included a Linux driver called rtl8139.c, so it can't be
a VIA
>Fine. I'm including another patch with a slight change. I don't know if
>this will make a difference or not since I've never known this step to be
>necessary.
Okay, tried this, same results. Still getting a 6 in the capabilities.
>If this doesn't work, I suggest putting the card in a different
>
> Alas, that patch is exactly what I have already done. I was hoping you'd
> found somewhere that I missed an update, but I already had those three spots
> covered.
Fine. I'm including another patch with a slight change. I don't know if
this will make a difference or not since I've never kn
>Guh. Support for this card was added to -current, but the changes never
>made it back to -stable. The problem (I think) is that while you updated
>the device list, you overlooked a piece of code in rl_attach() that selects
>the driver behavior depending on the PCI device ID. Get back your origin
Guh. Support for this card was added to -current, but the changes never
made it back to -stable. The problem (I think) is that while you updated
the device list, you overlooked a piece of code in rl_attach() that selects
the driver behavior depending on the PCI device ID. Get back your original
ve
> >Are you sure the card is using the 8139 chipset? The 8139 can provide
PHY
> >information via the status register. Since we're obviously not getting
any
> >such data, I'm wondering if this card is based on something else.
>
> I'm pretty sure it is. The Linux driver source file is called
"rtl8
>Are you sure the card is using the 8139 chipset? The 8139 can provide PHY
>information via the status register. Since we're obviously not getting any
>such data, I'm wondering if this card is based on something else.
I'm pretty sure it is. The Linux driver source file is called "rtl8139.c",
> >[snip] Sorry 'bout that. I was working on the assumption that the driver
> >was working properly, and was just dying during userland init (ifconfig).
> >The "rlphy0: no media present" line tells us that the driver isn't 100%
> >healthy, at least with this card.
>
> Not a problem. Good learnin
>[snip] Sorry 'bout that. I was working on the assumption that the driver
>was working properly, and was just dying during userland init (ifconfig).
>The "rlphy0: no media present" line tells us that the driver isn't 100%
>healthy, at least with this card.
Not a problem. Good learning exercise
> Okay, I've managed to get the debug kernel built and save the core file.
> I'll include the output of some basic debugging below. If there's
anything
> else that would be helpful, let me know. The D-Link driver disk includes
C
> source for a Linux driver, so when the problem gets narrowed down
>Well, you're on the right track. More than likely the D-Link card has some
>flags that aren't being properly set during the driver init.
>
>In the meantime, it would be best if you built a debug kernel and enabled
>crashdumps. This would give you (and us) more details on where (and why)
>this t
> I'm setting up a system (200MHz) with 4.2-RELEASE, and the network card
that
> I have to go in it is a D-Link DFE-538TX/R PCI card, based on the RealTek
> 8139 chipset.
[ snip ]
> pci0: (vendor=0x1186, dev=0x1300) at 11.0 irq 11
>
> I know the unknown card here is the network card, since th
13 matches
Mail list logo
