Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Nov 2017 18:10:34 -0800
From:      "Chris H" <bsd-lists@bsdforge.com>
To:        <freebsd-stable@freebsd.org>
Subject:   Re: D-Link DGE530T issue
Message-ID:  <ac251435d7f38f820eda2434e9f46d33@ultimatedns.net>
In-Reply-To: <CA%2BAz77M35U1L-XiNeC63stkO-NLhi-U5VW2p88BBF9sQN%2BHUYA@mail.gmail.com>
References:  <CA%2BAz77M35U1L-XiNeC63stkO-NLhi-U5VW2p88BBF9sQN%2BHUYA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 15 Nov 2017 23:00:33 +0300 Mike Black <amdmiek@gmail.com> wrote

> Hello
> 
> I've got old PCI NIC D-Link DGE530T Rev 11 with SysKonnect chip on it.
> Years ago it worked in FreeBSD 8/9 Stable with if_sk driver.
> 
> Now I'm runnig
> 11.1-STABLE FreeBSD 11.1-STABLE #1 r323214: Sat Nov 11 19:06:20 MSK 2017
>  amd_miek@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64  amd64 1101502
> 1101502
> 
> But recently I plugged this card back and it's not being recognized by a
> driver.
> 
> pciconf says that is
> none0@pci0:5:1:0:       class=0x020000 card=0x4b011086 chip=0x4b011086
> rev=0x11 hdr=0x00
>     vendor     = 'J. Bond Computer Systems'
>     class      = network
>     subclass   = ethernet
>     bar   [10] = type Memory, range 32, base 0xfebec000, size 16384, enabled
>     bar   [14] = type I/O Port, range 32, base 0xee00, size 512, enabled
>     cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D3
>     cap 03[50] = VPD
> 
> According /usr/share/misc/pci_vendors this D-link should have 4b011186 not
> 4b011086.
Just a hunch; But maybe it was simply a typo?
You can probably omit the additional "1" on your local copy of the source,
and try to build it again. My guess is you'll have success.
NOTE: I'm not an authority on this driver. I'm only attempting to
provide a possible solution. :)

If you *are* successful. I would advise opening a PR for this. :)

--Chris
> I looked into driver code  (if_sk) and it expects 1186 card also.
> I googled about this issue but found no one similar in a recent years
> So I'd like to know what's wrong - some changes in driver in a recent years
> or smth going wrong while OS detecting this NIC. But that's confusing,
> because this exact NIC worked years ago...
> 
> -- 
> amd_miek
> Think different.
> Just superior.
> 
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaig
> n=sig-email&utm_content=webmail> Без
> вирусов. www.avast.ru
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaig
> n=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ac251435d7f38f820eda2434e9f46d33>