D-Link DGE530T issue

[Arrigo Marchiori]

Hello,

On Fri, Nov 17, 2017 at 03:12:58PM +0300, Mike Black wrote:

> Hello
> 
> VPD is
> none0 at pci0:5:1:0:       class=0x020000 card=0x4b011086 chip=0x4b011086
> rev=0x11 hdr=0x00
>     vendor     = 'J. Bond Computer Systems'

IMHO this is either a joke, or a reference to a company in California
that seems to have not produced much for 10 years (I just googled its
name).

I would speculate it is a sort of inside joke from D-Link engineers,
for a chip intended for development, that was inadvertently mounted on
a board for resale.

This would explain the other strange bits.

>     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
>     VPD ident  = 'DGD-530T Ghgabht Ethernet @dapte'
> 
> But I see... it says some DGD-530T... Do not know why, because it's
> DGE-530T for sure.
> 
> So you're saying this it hardware degradation?
> I will try to find some windows host and plug it in there to check it.
> 
> 2017-11-17 13:19 GMT+03:00 YongHyeon PYUN <pyunyh at gmail.com>:
> 
> > On Fri, Nov 17, 2017 at 09:55:03AM +0300, Mike Black wrote:
> > > Hello. I looked into svn code for 8.3R and 11.1R and there seems no
> > changes
> > > in descriptors/identifiers. So I think that NIC is being wrongly
> > identified
> > > during startup process - it is being recognized with a wrong PCI VID. How
> > > can this be checked or fixed?
> > > I use a loadable kernel module after a startup, so there is no useful
> > > messages during boot process.
> > >
> >
> > It seems it's single bit error but if it's dying there would no way
> > to get fixed.  Given that pciconf(8) says VPD capability, try to
> > read it(i.e. pciconf -lcbvV).  Generally VPD contains a readable
> > product string so you may be able to know whether there are other
> > errors.  If vendor ID is the only corrupted one, you can simply
> > patch the device ID in the driver.
> >
> > > 15 нояб. 2017 г. 11:00 PM пользователь "Mike Black" <amdmiek at gmail.com>
> > > написал:
> > >
> > > > 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 at 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 at 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.
> > > > 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.
> >
> 
> 
> 
> -- 
> amd_miek
> Think different.
> Just superior.

-- 
rigo

http://rigo.altervista.org