Dlink DGE-530T not detected

evolvd

Thanks for looking through the dmesg output I posted. I see the NIC card in the BIOS and when I plug in a ethernet cable the light go active on the card. I'm downloading the latest version of Ubuntu to see if that recognizes my card.

evolvd

Yeah, Ubuntu was able to see the card.

stephenw10

Hmm,
Try Wallabybob's suggestion above, run:


pciconf -l -v

The card should show up there as a pci device.
Did you find out which chip is on the card? The revision number is not important other than to allow us to look up compatibility.

Steve

stephenw10

Out of curiosity I googled some more and found:

DGE-530T revision C1 (Realtek RTL8169 based, PCI ID 1186:4302)

So it seems that D-link may (if the above report is accurate) have changed to a completely different chipset whilst keeping the same model number. Nice!

This may be supported by the re(4) driver but possibly not the FreeBSD 8.1 release.

Non of this explains why it doesn't appear as an unknown device in the boot log though.

Steve

Edit: Yes, support for the rev C1 card was only added to the re driver in Aug 2011. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=159116

evolvd

I installed 2.1 just to see if it would make a difference (no luck) here is the output for pciconf -l -v

$ pciconf -l -v
hostb0@pci0:0:0:0:	class=0x060000 card=0x02941028 chip=0x29c08086 rev=0x0a hdr=0x00
    class      = bridge
    subclass   = HOST-PCI
pcib1@pci0:0:1:0:	class=0x060400 card=0x02941028 chip=0x29c18086 rev=0x0a hdr=0x01
    class      = bridge
    subclass   = PCI-PCI
vgapci0@pci0:0:2:0:	class=0x030000 card=0x02941028 chip=0x29c28086 rev=0x0a hdr=0x00
    class      = display
    subclass   = VGA
vgapci1@pci0:0:2:1:	class=0x038000 card=0x02941028 chip=0x29c38086 rev=0x0a hdr=0x00
    class      = display
none0@pci0:0:27:0:	class=0x040300 card=0x02941028 chip=0x27d88086 rev=0x01 hdr=0x00
    class      = multimedia
    subclass   = HDA
pcib2@pci0:0:28:0:	class=0x060400 card=0x02941028 chip=0x27d08086 rev=0x01 hdr=0x01
    class      = bridge
    subclass   = PCI-PCI
uhci0@pci0:0:29:0:	class=0x0c0300 card=0x02941028 chip=0x27c88086 rev=0x01 hdr=0x00
    class      = serial bus
    subclass   = USB
uhci1@pci0:0:29:1:	class=0x0c0300 card=0x02941028 chip=0x27c98086 rev=0x01 hdr=0x00
    class      = serial bus
    subclass   = USB
uhci2@pci0:0:29:2:	class=0x0c0300 card=0x02941028 chip=0x27ca8086 rev=0x01 hdr=0x00
    class      = serial bus
    subclass   = USB
uhci3@pci0:0:29:3:	class=0x0c0300 card=0x02941028 chip=0x27cb8086 rev=0x01 hdr=0x00
    class      = serial bus
    subclass   = USB
ehci0@pci0:0:29:7:	class=0x0c0320 card=0x02941028 chip=0x27cc8086 rev=0x01 hdr=0x00
    class      = serial bus
    subclass   = USB
pcib3@pci0:0:30:0:	class=0x060401 card=0x02941028 chip=0x244e8086 rev=0xe1 hdr=0x01
    class      = bridge
    subclass   = PCI-PCI
isab0@pci0:0:31:0:	class=0x060100 card=0x00000000 chip=0x27b88086 rev=0x01 hdr=0x00
    class      = bridge
    subclass   = PCI-ISA
atapci0@pci0:0:31:1:	class=0x01018a card=0x02941028 chip=0x27df8086 rev=0x01 hdr=0x00
    class      = mass storage
    subclass   = ATA
atapci1@pci0:0:31:2:	class=0x01018f card=0x02941028 chip=0x27c08086 rev=0x01 hdr=0x00
    class      = mass storage
    subclass   = ATA
none1@pci0:0:31:3:	class=0x0c0500 card=0x02941028 chip=0x27da8086 rev=0x01 hdr=0x00
    class      = serial bus
    subclass   = SMBus
bge0@pci0:2:0:0:	class=0x020000 card=0x02941028 chip=0x169814e4 rev=0x10 hdr=0x00
    class      = network
    subclass   = ethernet
none2@pci0:3:0:0:	class=0x020000 card=0x43021186 chip=0x43021186 rev=0x10 hdr=0x00
    class      = network
    subclass   = ethernet

I'm going to be ordering another card today but maybe this will help someone else.

stephenw10

Well at least it showed up!

none2@pci0:3:0:0: class=0x020000 card=0x43021186 chip=0x43021186 rev=0x10 hdr=0x00
class = network
subclass = ethernet

As you can see this is indeed the rev C1 hardware with the Realtek chip (device ID:4302).
The only build of 2.1 currently available (unless I missed some announcement) is still built on FreeBSD 8.1. 2.1 will be built on FreeBSD 9.X in future and this should include support for your card.

Steve

evolvd

ha yeah I'm glad I could see the problem. I'm ordering another card right now so I will just use this card for something else. I have a question about the card I was going to get. I made another thread about it. http://forum.pfsense.org/index.php/topic,43616.0.html

genic

fyi, those cards WILL fail randomly causing connectivity loss. :(

i learned this the hard way. you are much better off with an intel base card. like the intel pro-1000 mt (either desktop/or server models) …i have found the server models of the pro-1000 to be extremely solid.

the dlink (especially the rev. b's) on the other hand...they would just puke randomly and you would have to restart the whole firewall to bring them back to life.

you can find the pro-1000's on ebay for pretty cheap. i am running four in the PCI slots and have yet to have a single problem once i put the firewall back into production. my throughput is between 20mbps to 300mbps, and they handle it without breaking a sweat.

just an FYI is all. :D

pat1974

What I find about of pfsense is that the hardware is really important. This is not highlighted enough on their website.
When somebody is considering pfsense, it is important to consider the hardware.

Coming from a Microsoft background, you don't think hardware compatibility problem immediately when you setup your freeBsd box, but you should, especially with a pfsense box since it doesn't uses the last updated distro of freeBSD.

So when you buy brand new NIC, because pfsense is not the most recent distro it is quite possible your new hardware driver will not be available in the pfsense distro.

I'm just saying this from experience, as I figure that the hardware was really important after buying it, and starting to setup my pfsense. Then when it didn't work I start reading more about pfsense, and realize all the above explanation.

I think pfsense website should find a way to make it stand out on their home page.

Something like: "BEFORE YOU START BUYING PARTS FOR SETTING UP PFSENSE, MAKE SURE THE HARDWARE YOU WANT TO BUY IS COMPATIBLE WITH PFSENSE DISTRO"

Doing this type of warning will avoid a lot of headach, and maybe having the list of compatible hard drive easy to find :)

genic

100% correct. even though the dlink NIC will work, but you will have issues with them. drop connections, packet mangling, etc.

i learned this the hard way as well, but once spending time in the forums and reading the vast amount of information within…i have a very good understanding of the overall product and the in's/out's of pfsense. ...however, being a microsoft guy for the past 15+ years...it did take me a little longer than it should have. ;D

@pat1974:

What I find about of pfsense is that the hardware is really important. This is not highlighted enough on their website.
When somebody is considering pfsense, it is important to consider the hardware.

Coming from a Microsoft background, you don't think hardware compatibility problem immediately when you setup your freeBsd box, but you should, especially with a pfsense box since it doesn't uses the last updated distro of freeBSD.

So when you buy brand new NIC, because pfsense is not the most recent distro it is quite possible your new hardware driver will not be available in the pfsense distro.

I'm just saying this from experience, as I figure that the hardware was really important after buying it, and starting to setup my pfsense. Then when it didn't work I start reading more about pfsense, and realize all the above explanation.

I think pfsense website should find a way to make it stand out on their home page.

Something like: "BEFORE YOU START BUYING PARTS FOR SETTING UP PFSENSE, MAKE SURE THE HARDWARE YOU WANT TO BUY IS COMPATIBLE WITH PFSENSE DISTRO"

Doing this type of warning will avoid a lot of headach, and maybe having the list of compatible hard drive easy to find :)