SOLVED Supported DFE 538 TX not detected i 8.3.1 RC1

[termtheworm]

Hi,

after having my old AMD-box runnning 8.3.1 RC1 for a while, I managed to get it to 'idle-shutdown' and WOL
suddenly seemed like a good idea, but, the onboard NIC (RTL 8139-based) doesnt support WOL.

Rummaging a bit uncovered a WOLable DLINK DFE-538 TX (rev D1), based on (a newer rev. of) the same chipset,
but freenas doesn't detect it. I've tried disabling the onboard NIC in BIOS, to no avail; I can't find a trace of detection
in any logs, and I've verified that the board actually works.

Output from pciconf (rl0 is the onboard NIC)
rl0@pci0:0:19:0: class=0x020000 card=0xd0071631 chip=0x813910ec rev=0x10
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'Realtek RTL8139 Family PCI Fast Ethernet NIC (RTL-8139/8139C/8
139D)'
class = network
subclass = ethernet


Any help would be appreciated; I'm loath to pony up for a new NIC, if all it takes is some console-labour.

Sincerely
Termtheworm

 

[William Grzybowski]

Where did you see that DFE 538 TX is supported by FreeNAS/FreeBSD?

 

[termtheworm]

Where did you see that DFE 538 TX is supported by FreeNAS/FreeBSD?

Thx for putting up with newbie questions! :0)

I just re-checked my sources and I must admit I might've made an assumption,
based on this list
http://www.freebsd.org/releases/8.2R/hardware.html and the fact that the onboard NIC,
based on the same chipset, works, per the 'rl' driver.
Unless this particular hw revision (D1) isn't covered.

dlink har sources, along with a makefile, that enables me to compile a binary,
but I'm not sure how to install it, and reluctant to do so, if it's unnessesary.

What really gets me, though, is that I haven't been able to spot it, when running
pciconf -lv or dmesg. I should add, that although the NIC works, it's never been
used in this particular pc. Could it be, that having to NICs, based on the same,
but slightly differing, chipset, might pose a problem in itself?

/Termtheworm

 

[William Grzybowski]

Well, if pciconf -vl does not show it ,even with a detached driver, then it is a hardware issue.

 

[termtheworm]

Well, if pciconf -vl does not show it ,even with a detached driver, then it is a hardware issue.

Hi,

thx for taking the time - I'm going to postpone further trials until I've got my hand on another
NIC.

Sincerely
Termtheworm

 

[termtheworm]

Solved. And I've only got an inkling as to why.

Yesterday I tried all three pci ports. Checked the output from pciconf, both manually and with 'grep -i ethernet',
rebooted, tried with onboard NIC enabled/disabled (without cable, as I've read that having both plugged in is A
Bad Thing), and I sorta gave up.
Today i thought 'heck', inserted the NIC, plugged it in and waited, somewhat discouraged, at the console, when
suddenly I thought i spotted the line rl1 scroll by. Quickly into the shell, pciconf|more and yep, both nic's where there;
rl0@pci0:0:11:0: class=0x020000 card=0x13001186 chip=0x13001186 rev=0x10 hdr=0x00
vendor = 'D-Link System Inc'
device = 'DFE-528TX/530TX+/538TX Fast Ethernet Adapter (DL 10038C Chipset)'
class = network
subclass = ethernet
Rebooted, disabled the onboard dev. in BIOS, and yup!, still works.

In conclusion: I must've done something wrong, in my initial attempts, despite my previous claim
to the opposite - and I've learned, that the 538TX is in fact supported.

And now, I can sit back and enjoy my coffe - and a slice of humble-pie :o.

Sincerely
TermTheWorm