Date: Fri, 17 Nov 2017 14:51:07 +0100 From: Arrigo Marchiori <ardovm@yahoo.it> To: freebsd-stable@freebsd.org Subject: Re: D-Link DGE530T issue Message-ID: <20171117135107.GA70004@nuvolo> In-Reply-To: <CA%2BAz77OAc=bDK0iAx%2BuDyn8CE%2BphMewu_RSJwdFELmAgAeb5wQ@mail.gmail.com> References: <CA%2BAz77M35U1L-XiNeC63stkO-NLhi-U5VW2p88BBF9sQN%2BHUYA@mail.gmail.com> <CA%2BAz77Oi75A_m2DbWcwOV9g15Mt8nJyuffEcjE=5%2Bv5U38bOHA@mail.gmail.com> <20171117101954.GA1246@michelle.fasterthan.co.kr> <CA%2BAz77OAc=bDK0iAx%2BuDyn8CE%2BphMewu_RSJwdFELmAgAeb5wQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On Fri, Nov 17, 2017 at 03:12:58PM +0300, Mike Black wrote: > Hello >=20 > VPD is > none0@pci0:5:1:0: class=3D0x020000 card=3D0x4b011086 chip=3D0x4b0= 11086 > rev=3D0x11 hdr=3D0x00 > vendor =3D '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 =3D ethernet > bar [10] =3D type Memory, range 32, base 0xfebec000, size 16384, = enabled > bar [14] =3D type I/O Port, range 32, base 0xee00, size 512, enab= led > cap 01[48] =3D powerspec 2 supports D0 D1 D2 D3 current D3 > cap 03[50] =3D VPD > VPD ident =3D 'DGD-530T Ghgabht Ethernet @dapte' >=20 > But I see... it says some DGD-530T... Do not know why, because it's > DGE-530T for sure. >=20 > So you're saying this it hardware degradation? > I will try to find some windows host and plug it in there to check it. >=20 > 2017-11-17 13:19 GMT+03:00 YongHyeon PYUN <pyunyh@gmail.com>: >=20 > > 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 VI= D. How > > > can this be checked or fixed? > > > I use a loadable kernel module after a startup, so there is no usef= ul > > > 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 =D0=BD=D0=BE=D1=8F=D0=B1. 2017 =D0=B3. 11:00 PM =D0=BF=D0=BE=D0=BB= =D1=8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Mike Black" <amdm= iek@gmail.com> > > > =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > > > > > > > Hello > > > > > > > > I've got old PCI NIC D-Link DGE530T Rev 11 with SysKonnect chip o= n 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 M= SK > > 2017 > > > > amd_miek@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 a= md64 > > > > 1101502 1101502 > > > > > > > > But recently I plugged this card back and it's not being recogniz= ed by > > a > > > > driver. > > > > > > > > pciconf says that is > > > > none0@pci0:5:1:0: class=3D0x020000 card=3D0x4b011086 chip=3D= 0x4b011086 > > > > rev=3D0x11 hdr=3D0x00 > > > > vendor =3D 'J. Bond Computer Systems' > > > > class =3D network > > > > subclass =3D ethernet > > > > bar [10] =3D type Memory, range 32, base 0xfebec000, size 1= 6384, > > > > enabled > > > > bar [14] =3D type I/O Port, range 32, base 0xee00, size 512= , > > enabled > > > > cap 01[48] =3D powerspec 2 supports D0 D1 D2 D3 current D3 > > > > cap 03[50] =3D VPD > > > > > > > > According /usr/share/misc/pci_vendors this D-link should have 4b0= 11186 > > 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 y= ears > > > > So I'd like to know what's wrong - some changes in driver in a re= cent > > > > 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. > > >=20 >=20 >=20 > --=20 > amd_miek > Think different. > Just superior. --=20 rigo http://rigo.altervista.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171117135107.GA70004>