Seems that it's a really HW issue.
I plugged it into windows PC and it was OK. After that I placed it in
FreeBSD box and it feels OK
So I will keep an eye on it
none0@pci0:5:1:0: class=0x02 card=0x4b011186 chip=0x4b011186
rev=0x11 hdr=0x00
vendor = 'D-Link System Inc'
device
On Fri, Nov 17, 2017 at 03:12:58PM +0300, Mike Black wrote:
> Hello
>
> VPD is
> none0@pci0:5:1:0: class=0x02 card=0x4b011086 chip=0x4b011086
> rev=0x11 hdr=0x00
> vendor = 'J. Bond Computer Systems'
> class = network
> subclass = ethernet
> bar [10] = type M
Hello,
On Fri, Nov 17, 2017 at 03:12:58PM +0300, Mike Black wrote:
> Hello
>
> VPD is
> none0@pci0:5:1:0: class=0x02 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
17.11.2017 15:12, Mike Black пишет:
> VPD ident = 'DGD-530T Ghgabht Ethernet @dapte'
So here we are (off by minus one errors):
---
D (44h) should be G (45h);
h (68h) -> i (69h);
@ (40h) -> A (41h).
---
And deltas in bytes between errors: 8, 4, 12.
Yep, looks like a hardware/power problem.
Hello again
PCI slot is 100% working, I just got another D-LINK PCI card (different
Chip, different driver) out of there that was working OK.
I spend some time and found this - some bootlog with exact this card. But I
think it does not really contain any useful information.
It was FreeBSD 9.1-STA
Hello
VPD is
none0@pci0:5:1:0: class=0x02 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/
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 t
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 star
On Wed, 15 Nov 2017 23:00:33 +0300 Mike Black 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
>
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 110
10 matches
Mail list logo
