Date: Fri, 17 Nov 2017 09:55:03 +0300 From: Mike Black <amdmiek@gmail.com> To: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: D-Link DGE530T issue Message-ID: <CA%2BAz77Oi75A_m2DbWcwOV9g15Mt8nJyuffEcjE=5%2Bv5U38bOHA@mail.gmail.com> 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
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. 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" <amdmiek@gmai= l.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 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=3D0x020000 card=3D0x4b011086 chip=3D0x4b011= 086 > 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 16384, > enabled > bar [14] =3D type I/O Port, range 32, base 0xee00, size 512, enable= d > 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 4b011186 no= t > 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. > > > <https://www.avast.com/sig-email?utm_medium=3Demail&utm_source=3Dlink&utm= _campaign=3Dsig-email&utm_content=3Dwebmail> =D0=91=D0=B5=D0=B7 > =D0=B2=D0=B8=D1=80=D1=83=D1=81=D0=BE=D0=B2. www.avast.ru > <https://www.avast.com/sig-email?utm_medium=3Demail&utm_source=3Dlink&utm= _campaign=3Dsig-email&utm_content=3Dwebmail> > <#m_6570072101733768544_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BAz77Oi75A_m2DbWcwOV9g15Mt8nJyuffEcjE=5%2Bv5U38bOHA>