DGE-530T nic not found on 5.5 - Possibly solved

Derrick Ryalls ryallsd at gmail.com
Mon Dec 4 13:38:26 PST 2006


On 12/4/06, Derrick Ryalls <ryallsd at gmail.com> wrote:
> [Resending with more info]
>
> Greetings, I have a fileserver I installed this nic on but the device
> fails to show in ifconfig
>
> uname:
> 5.5-STABLE FreeBSD 5.5-STABLE #2: Sun Oct 29 14:12:46 PST 2006
> user at somewhere.com:/usr/obj/usr/src/sys/FRODO
>
> Except from FRODO kernel file (generic plus some):
>
> # PCI Ethernet NICs that use the common MII bus controller code.
> # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
> device          miibus          # MII bus support
> device          bfe             # Broadcom BCM440x 10/100 Ethernet
> device          bge             # Broadcom BCM570xx Gigabit Ethernet
> device          dc              # DEC/Intel 21143 and various workalikes
> device          fxp             # Intel EtherExpress PRO/100B (82557, 82558)
> device          lge             # Level 1 LXT1001 gigabit ethernet
> device          nge             # NatSemi DP83820 gigabit ethernet
> device          pcn             # AMD Am79C97x PCI 10/100 (precedence
> over 'lnc')
> device          re              # RealTek 8139C+/8169/8169S/8110S
> device          rl              # RealTek 8129/8139
> device          sf              # Adaptec AIC-6915 (``Starfire'')
> device          sis             # Silicon Integrated Systems SiS 900/SiS 7016
> device          sk              # SysKonnect SK-984x & SK-982x gigabit Ethernet
> device          ste             # Sundance ST201 (D-Link DFE-550TX)
> device          ti              # Alteon Networks Tigon I/II gigabit Ethernet
> device          tl              # Texas Instruments ThunderLAN
> device          tx              # SMC EtherPower II (83c170 ``EPIC'')
> device          vge             # VIA VT612x gigabit ethernet
> device          vr              # VIA Rhine, Rhine II
> device          wb              # Winbond W89C840F
> device          xl              # 3Com 3c90x (``Boomerang'', ``Cyclone'')
>
>
> dmesg except:
>
> pci0: <network, ethernet> at device 6.0 (no driver attached)
> vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xdc00-0xdcff mem
> 0xdfffbe00-0xdfffbeff
>  irq 23 at device 18.0 on pci0
> miibus0: <MII bus> on vr0
> ukphy0: <Generic IEEE 802.3u media interface> on miibus0
> ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> vr0: Ethernet address: xx:xx:xx:xx:xx:xx
>
> The reference to vr0 are for the onboard nic that it is currently
> running off of.
>
> ifconfig lists vr0, plip0, lo0
>
> ===[frodo][root] ~ # pciconf -l
> agp0 at pci0:0:0:  class=0x060000 card=0x00001106 chip=0x30991106 rev=0x00 hdr=0x00
> pcib1 at pci0:1:0: class=0x060400 card=0x00000080 chip=0xb0991106 rev=0x00 hdr=0x01
> none0 at pci0:6:0: class=0x020000 card=0x4b011186 chip=0x4b011186 rev=0x11 hdr=0x00
> uhci0 at pci0:16:0:        class=0x0c0300 card=0x76401462 chip=0x30381106
> rev=0x80 hdr=0x00
> uhci1 at pci0:16:1:        class=0x0c0300 card=0x76401462 chip=0x30381106
> rev=0x80 hdr=0x00
> uhci2 at pci0:16:2:        class=0x0c0300 card=0x76401462 chip=0x30381106
> rev=0x80 hdr=0x00
> ehci0 at pci0:16:3:        class=0x0c0320 card=0x76401462 chip=0x31041106
> rev=0x82 hdr=0x00
> isab0 at pci0:17:0:        class=0x060100 card=0x00001106 chip=0x31771106
> rev=0x00 hdr=0x00
> atapci0 at pci0:17:1:      class=0x01018a card=0x76401462 chip=0x05711106
> rev=0x06 hdr=0x00
> vr0 at pci0:18:0:  class=0x020000 card=0x01021106 chip=0x30651106 rev=0x74 hdr=0x00
> none1 at pci1:0:0: class=0x030000 card=0x000da0a0 chip=0x002d10de rev=0x15 hdr=0x00
>
>
>
> Doing some searching, someone posted this part of dmesg on a 5.4
> PRERELEASE system:
>
> skc0: <D-Link DGE-530T Gigabit Ethernet> port 0x7400-0x74ff mem
> 0xfb800000-0xfb803fff irq 18 at device 10.0 on pci2
> skc0: (null) rev. (0x1)
> sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
> sk0: Ethernet address: 00:0f:3d:f2:45:0c
> miibus0: <MII bus> on sk0
> e1000phy0: <Marvell 88E1000 Gigabit PHY> on miibus0
> e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX,
> auto
>
> I did check the hardware notes before buying this nic, and according
> to http://www.freebsd.org/releases/5.5R/hardware-i386.html it is
> supported.  Have I missed a switch somewhere?
>
> Thanks in advance.
>
> -Derrick
>

I found this in an archive:

http://www.freebsd.org/cgi/query-pr.cgi?pr=99903

I tried manually editing if_sk.c and if_skreg.h build/install kernel
(patch didn't work, possibly wrong version of file?), and then got
this in dmesg:

skc0: <D-Link DGE-530T Gigabit Ethernet> port 0xec00-0xecff mem 0xdfffc000-0xdff
fffff irq 17 at device 6.0 on pci0
skc0: unknown media type: 0x31
device_attach: skc0 attach returned 6

So then I did some searching for 0x31 and found this:

http://www.bsdforums.org/forums/archive/index.php/t-43153.html

I added the lines for 0x31 and now the nic shows up in ifconfig.  I am
not home so I can't plug in a patch cord to see if it is fully
functional.

If this does work, how would I create a patch file?  I saved the
original files before editing.  I definitely don't want to claim
ownership of the work that went into this, I was just hoping to get it
into the 5.x tree so if I happen to CVSup, I don't need to redo this.


More information about the freebsd-questions mailing list