from:"Dariusz Swiderski"

Re: kernel panic

2015-10-10 Thread Dariusz Swiderski

> On 9 paÅº 2015, at 13:54, Mike Larkin  wrote:
>
> On Fri, Oct 09, 2015 at 04:35:48AM -0700, Mike Larkin wrote:
>> On Fri, Oct 09, 2015 at 09:53:16AM +0200, Holger Glaess wrote:
 On Fri, Oct 09, 2015 at 06:22:53AM +0200, Holger Glaess wrote:
> hi
>
> what kind of information you need more ?
>

 uhm. this machine is very very strange. It has devices I've never
 seen before and many other devices not even recognized. Without access
 to the hardware there's not much we can do here.

 You've posted about this machine in the past, and we've done our best
 to help you but I think this may be a losing battle.

>>>
>>> hi
>>> you mean physikal access or is connection by ssh also ok ?
>>>
>>> ssh access  i can give you.
>>>
>>
>> I meant getting one of these boards in hand.
>>
>
> PS that wasn't me volunteering. It was just a statement that debugging
strange
> hardware usually goes faster with physical access.
>

Hi,

I know that iâm late to the party, but could you describe what you did? Or
does this just trigger
with -current?

greets
--
Maciej 'sfires' Swiderski
---
SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
---
A mouse is a device used to point at the xterm you want to type in.

>>>
>>> Holger
>>>
>>>
> holger
>
>
> Stopped at  0:ehci0: unrecoverable error, controller halted
> panic: kernel diagnostic assertion "ci->ci_fpcurproc == p" failed: file
> "../../../../arch/i386/isa/npx.c", line 881
>  Stopped at  Debugger+0x7:   leave
>   TIDPIDUID PRFLAGS PFLAGS  CPU  COMMAND
> Debugger(d09fe02c,f51cfdd4,d09d8f30,f51cfdd4,d709bfc8) at Debugger+0x7
> panic(d09d8f30,d0957746,d0b0522f,d0b0532c,371) at panic+0x71
> __assert(d0957746,d0b0532c,371,d0b0522f,d0bbb160) at __assert+0x2e
> npxsave_proc(d7216744,0,f51cfe58,d03b9029,40) at npxsave_proc+0x5a
> cpu_exit(d7216744,d7215000,d709b00c,0,1) at cpu_exit+0x2a
> exit1(d7216744,4,1,d03b3844,40,4,1,0) at exit1+0x22c
> sigexit(d7216744,4,0,0,21fc000) at sigexit+0x76
> postsig(4,0,808f05d0,63,21de800) at postsig+0x28a
> userret(d7216744) at userret+0x49
> alltraps(,,,,) at alltraps+0x2e
> uvm_fault(0xd0bbb0a0, 0xd000, 0, 1) -> e
> kernel: page fault trap, code=0
> Stopped at  trap+0x18:  movl0x2c(%esi),%edi
>   TIDPIDUID PRFLAGS PFLAGS  CPU  COMMAND
> trap() at trap+0x18
> --- trap (number 32) ---
> 0:
> http://www.openbsd.org/ddb.html describes the minimum info required in
> bug
> reports.  Insufficient info makes it difficult to find and fix bugs.
> ddb>
>
>
> OpenBSD 5.8-current (GENERIC) #1219: Thu Oct  8 07:55:22 MDT 2015
>dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Genuine Intel(R) processor 1.20GHz ("GenuineIntel" 686-class)
1.21
> GHz
> cpu0:
>
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,A
CPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,PERF
> real mem  = 1072041984 (1022MB)
> avail mem = 1038999552 (990MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: date 07/06/09, BIOS32 rev. 0 @ 0xfa530, SMBIOS rev.
> 2.2 @
> 0xf0800 (39 entries)
> bios0: vendor Phoenix Technologies, LTD version "ANSA 3020 R01
> Jul,2,2009" date 07/06/2009
> acpi0 at bios0: rev 0
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP MCFG APIC
> acpi0: wakeup devices EPA0(S3) EPA1(S3) PEX0(S5) PEX1(S5) PEX2(S5)
> PEX3(S5)
> HUB0(S5) PCI0(S5)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimcfg0 at acpi0 addr 0xe000, bus 0-255
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 133MHz
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 2 (EPA1)
> acpiprt2 at acpi0: bus -1 (BR10)
> acpiprt3 at acpi0: bus -1 (BR11)
> acpiprt4 at acpi0: bus -1 (BR12)
> acpiprt5 at acpi0: bus -1 (BR13)
> acpiprt6 at acpi0: bus -1 (BR14)
> acpiprt7 at acpi0: bus 3 (P0P1)
> acpiprt8 at acpi0: bus -1 (PEX0)
> acpiprt9 at acpi0: bus -1 (PEX1)
> acpiprt10 at acpi0: bus -1 (PEX2)
> acpiprt11 at acpi0: bus -1 (PEX3)
> acpiprt12 at acpi0: bus -1 (HUB0)
> acpicpu0 at acpi0: C1(@1 halt!)
> acpitz0 at acpi0: critical temperature is 75 degC
> acpibtn0 at acpi0: PWRB
> bios0: ROM list: 0xc8000/0x4000! 0xcc000/0x2200! 0xef000/0x1000!
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0

Re: Adding a NIC into cramped micro itx board for firewall

2015-05-20 Thread Dariusz Swiderski

> On 21 maj 2015, at 00:01, Armin Tanzarian  wrote:
> 
>> Does it have to be a NIC or would VLANs and a smart switch cover your
>>> needs?
>>> 
>> 
>>- Aner
>> 
>> 
> After great debate, we have settled on adding another nic as the only
> option.
> 
> So far the only option seems to be a pci express mini ribbon cable to pci
> express full size adapter.
> 
> Connect the ribbon to the mobo onboard mini adapter, hang ribbon out the
> case and add a full sized Intel full sized nic hidden behind.  Not very
> elegant at all :-(
> 


dunno the full dimensions inside, have you checked if a low profile NIC fits?


greets
-- 
Maciej 'sfires' Swiderski
---
SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
---
A mouse is a device used to point at the xterm you want to type in.

Re: not known intel ethernet card

2015-04-20 Thread Dariusz Swiderski

Hi

Could you to apply the attached diff on a clean tree and send me full
dmesg output? it seems there are 2 problems to be fixed:

1. link detection does not work well on th original box i developped the
support for.
2. the first phy on your hardware seems to behave wierdly, and i need to
find out why.

greets


On Sat, 18 Apr 2015, Holger Glaess wrote:

> hi
>
> dont worry , i'm happy that you care about this problem so fast.
>
> holger
>
> Am 17.04.2015 um 22:18 schrieb Dariusz Swiderski:
> > Hi,
> >
> > was not quite expecting that, new diff is being cooked up, but expect it
> > later this night
> >
> > greets
> > --
> > Maciej 'sfires' Swiderski
> > ---
> > SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
> > 193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
> > ---
> > A mouse is a device used to point at the xterm you want to type in.
> >
> > > On 17 kwi 2015, at 18:45, Holger Glaess  > > <mailto:gla...@glaessixs.de>> wrote:
> > >
> > > hi
> > >
> > > Am 17.04.2015 um 13:28 schrieb Dariusz Swiderski:
> > > > hi
> > > >
> > > > is this only on em1?
> > > yes just em1
> > > > and can you try plugging each of this port to a switch and see in
> > > > ifconfig if
> > > > media gets
> > > > negotiated?
> > > i did and no negoation ,
> > > ifconfig says no link because the link led is on.
> > >
> > > if i do an "ifconfig em3 up"
> > >
> > > em3: flags=8843 mtu 1500
> > >lladdr 00:14:b7:00:61:66
> > >priority: 0
> > >media: Ethernet autoselect (1000baseT full-duplex)
> > >status: active
> > >
> > > if i pull the cable
> > >
> > > same result like ahead.
> > >
> > > holger
> > >
> > >
> > >
> > > >
> > > > greets
> > > > --
> > > > Maciej 'sfires' Swiderski
> > > > ---
> > > > SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
> > > > 193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
> > > > ---
> > > > A mouse is a device used to point at the xterm you want to type in.
> > > >
> > > > > On 17 kwi 2015, at 13:21, Holger Glaess  > > > > <mailto:gla...@glaessixs.de>> wrote:
> > > > >
> > > > > hi
> > > > >
> > > > > looks good , but this "unable to read" is coming from
> > > > > not connected port ?
> > > > >
> > > > > Holger
> > > > >
> > > > >
> > > > > # dmesg | grep "^em"
> > > > > em0 at pci1 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address
> > > > > 00:14:b7:00:61:63
> > > > > em1 at pci3 dev 0 function 0 "Intel EP80579 LAN" rev 0x01: apic 2
int
> > > > > 16,
> > > > > address 00:14:b7:00:61:64
> > > > > em2 at pci3 dev 1 function 0 "Intel EP80579 LAN" rev 0x01: apic 2
int
> > > > > 17,
> > > > > address 00:14:b7:00:61:65
> > > > > em3 at pci3 dev 2 function 0 "Intel EP80579 LAN" rev 0x01: apic 2
int
> > > > > 18,
> > > > > address 00:14:b7:00:61:66
> > > > > em1: unable to read phy 0 reg 2
> > > > > em1: unable to read phy 0 reg 3
> > > > > em1: unable to read phy 0 reg 2
> > > > > em1: unable to read phy 0 reg 3
> > > > > em1: unable to read phy 0 reg 2
> > > > > em1: unable to read phy 0 reg 3
> > > > > em1: unable to read phy 0 reg 1
> > > > > em1: unable to read phy 0 reg 1
> > > > > em1: unable to read phy 0 reg 1
> > > > > em1: unable to read phy 0 reg 1
> > > > >
> > > > >
> > > > >
> > > > > > hi
> > > > > >
> > > > > > please apply attached patch on top of the previous one, build and
> > > > > > reboot
> > > > > > :)
> > > > > >
> > > > > > greets
> > > > > > dms
> > > > > >
> > > > > > On Fri, 17 Apr 2015, Holger Glaes

Re: not known intel ethernet card

2015-04-17 Thread Dariusz Swiderski

Hi,

was not quite expecting that, new diff is being cooked up, but expect it later
this night

greets
--
Maciej 'sfires' Swiderski
---
SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
---
A mouse is a device used to point at the xterm you want to type in.

> On 17 kwi 2015, at 18:45, Holger Glaess mailto:gla...@glaessixs.de>> wrote:
>
> hi
>
> Am 17.04.2015 um 13:28 schrieb Dariusz Swiderski:
>> hi
>>
>> is this only on em1?
> yes just em1
>> and can you try plugging each of this port to a switch and see in ifconfig
if
>> media gets
>> negotiated?
> i did and no negoation ,
> ifconfig says no link because the link led is on.
>
> if i do an "ifconfig em3 up"
>
> em3: flags=8843 mtu 1500
>lladdr 00:14:b7:00:61:66
>priority: 0
>media: Ethernet autoselect (1000baseT full-duplex)
>status: active
>
> if i pull the cable
>
> same result like ahead.
>
> holger
>
>
>
>>
>> greets
>> --
>> Maciej 'sfires' Swiderski
>> ---
>> SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
>> 193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
>> ---
>> A mouse is a device used to point at the xterm you want to type in.
>>
>>> On 17 kwi 2015, at 13:21, Holger Glaess mailto:gla...@glaessixs.de>> wrote:
>>>
>>> hi
>>>
>>> looks good , but this "unable to read" is coming from
>>> not connected port ?
>>>
>>> Holger
>>>
>>>
>>> # dmesg | grep "^em"
>>> em0 at pci1 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address
>>> 00:14:b7:00:61:63
>>> em1 at pci3 dev 0 function 0 "Intel EP80579 LAN" rev 0x01: apic 2 int 16,
>>> address 00:14:b7:00:61:64
>>> em2 at pci3 dev 1 function 0 "Intel EP80579 LAN" rev 0x01: apic 2 int 17,
>>> address 00:14:b7:00:61:65
>>> em3 at pci3 dev 2 function 0 "Intel EP80579 LAN" rev 0x01: apic 2 int 18,
>>> address 00:14:b7:00:61:66
>>> em1: unable to read phy 0 reg 2
>>> em1: unable to read phy 0 reg 3
>>> em1: unable to read phy 0 reg 2
>>> em1: unable to read phy 0 reg 3
>>> em1: unable to read phy 0 reg 2
>>> em1: unable to read phy 0 reg 3
>>> em1: unable to read phy 0 reg 1
>>> em1: unable to read phy 0 reg 1
>>> em1: unable to read phy 0 reg 1
>>> em1: unable to read phy 0 reg 1
>>>
>>>
>>>
>>>> hi
>>>>
>>>> please apply attached patch on top of the previous one, build and reboot
>>>> :)
>>>>
>>>> greets
>>>> dms
>>>>
>>>> On Fri, 17 Apr 2015, Holger Glaess wrote:
>>>>
>>>>> hi
>>>>>
>>>>> after build and boot the a patched kernel
>>>>> i see now the em interface but
>>>>> he show an eeprom error.
>>>>>
>>>>>
>>>>> see demsg
>>>>>
>>>>> Holger
>>>>>
>>>>> OpenBSD 5.7-stable (GENERIC) #10: Fri Apr 17 10:48:45 CEST 2015
>>>>>root@DAF.rocki.intern
<mailto:root@DAF.rocki.intern>:/usr/src/sys/arch/i386/compile/GENERIC
>>>>> cpu0: Genuine Intel(R) processor 1.20GHz ("GenuineIntel" 686-class)
1.21
>>>> GHz
>>>>> cpu0:
>>>>>
>>
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,A
>>>> CPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,PERF
>>>>> real mem  = 1072041984 (1022MB)
>>>>> avail mem = 1042157568 (993MB)
>>>>> mpath0 at root
>>>>> scsibus0 at mpath0: 256 targets
>>>>> mainbus0 at root
>>>>> bios0 at mainbus0: date 07/06/09, BIOS32 rev. 0 @ 0xfa530, SMBIOS rev.
>>>>> 2.2
>>>>> @ 0xf0800 (39 entries)
>>>>> bios0: vendor Phoenix Technologies, LTD version "ANSA 3020  R01
>>>>> Jul,2,2009" date 07/06/2009
>>>>> acpi0 at bios0: rev 0
>>>>> acpi0: sleep states S0 S3 S4 S5
>>>>> acpi0: tables DSDT FACP MCFG APIC
>>>>> acpi0: wakeup devices EPA0(S3) EPA1(S3) PEX0(S5) PEX1(S5) PEX2(S5)
>>>>> PEX3(S5) HUB0(S5) PCI0(S5)
>>>>> acpitimer0

Re: not known intel ethernet card

2015-04-17 Thread Dariusz Swiderski

gt; ppb1 at pci0 dev 3 function 0 "Intel EP80579 PCIE" rev 0x01: apic 2 int
>>> 16
>>> pci2 at ppb1 bus 2
>>> ppb2 at pci0 dev 4 function 0 "Intel EP80579" rev 0x01
>>> pci3 at ppb2 bus 3
>>> em1 at pci3 dev 0 function 0 "Intel EP80579 LAN" rev 0x01em1: Unknown
>>> MAC
>>> Type
>>> : apic 2 int 16em1: The EEPROM Checksum Is Not Valid
>>> em1: Unable to initialize the hardware
>>> em2 at pci3 dev 1 function 0 "Intel EP80579 LAN" rev 0x01em2: Unknown
>>> MAC
>>> Type
>>> : apic 2 int 17em2: The EEPROM Checksum Is Not Valid
>>> em2: Unable to initialize the hardware
>>> em3 at pci3 dev 2 function 0 "Intel EP80579 LAN" rev 0x01em3: Unknown
>>> MAC
>>> Type
>>> : apic 2 int 18em3: The EEPROM Checksum Is Not Valid
>>> em3: Unable to initialize the hardware
>>> gcu0 at pci3 dev 3 function 0 "Intel EP80579 GCU" rev 0x01
>>> "Intel EP80579 CANbus" rev 0x01 at pci3 dev 4 function 0 not configured
>>> "Intel EP80579 CANbus" rev 0x01 at pci3 dev 5 function 0 not configured
>>> "Intel EP80579 Serial" rev 0x01 at pci3 dev 6 function 0 not configured
>>> "Intel EP80579 1588" rev 0x01 at pci3 dev 7 function 0 not configured
>>> "Intel EP80579 LEB" rev 0x01 at pci3 dev 8 function 0 not configured
>>> vendor "Intel", unknown product 0x502d (class processor subclass
>>> Co-processor, rev 0x01) at pci3 dev 9 function 0 not configured
>>> "Intel EP80579 Reserved" rev 0x01 at pci3 dev 10 function 0 not
>>> configured
>>> vendor "Intel", unknown product 0x504c (class processor subclass
>>> Co-processor, rev 0x01) at pci3 dev 11 function 0 not configured
>>> "Intel EP80579 Reserved" rev 0x01 at pci3 dev 12 function 0 not
>>> configured
>>> uhci0 at pci0 dev 29 function 0 "Intel EP80579 USB" rev 0x01: apic 2 int
>>> 23
>>> ehci0 at pci0 dev 29 function 7 "Intel EP80579 USB" rev 0x01: apic 2 int
>>> 23
>>> usb0 at ehci0: USB revision 2.0
>>> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
>>> pcib0 at pci0 dev 31 function 0 "Intel EP80579 LPC" rev 0x01
>>> ahci0 at pci0 dev 31 function 2 "Intel EP80579 AHCI" rev 0x01: msi, AHCI
>> 1.1
>>> scsibus1 at ahci0: 32 targets
>>> sd0 at scsibus1 targ 0 lun 0:  SCSI3
>>> 0/direct
>>> fixed t10.ATA_TOSHIBA_MK6037GSX_676FTD3DT
>>> sd0: 57231MB, 512 bytes/sector, 117210240 sectors
>>> ichiic0 at pci0 dev 31 function 3 "Intel EP80579 SMBus" rev 0x01: apic 2
>>> int 19
>>> iic0 at ichiic0
>>> spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM
>>> usb1 at uhci0: USB revision 1.0
>>> uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
>>> isa0 at pcib0
>>> isadma0 at isa0
>>> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
>>> com0: console
>>> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
>>> pckbc0 at isa0 port 0x60/5
>>> pckbd0 at pckbc0 (kbd slot)
>>> pckbc0: using irq 1 for kbd slot
>>> wskbd0 at pckbd0: console keyboard
>>> pcppi0 at isa0 port 0x61
>>> spkr0 at pcppi0
>>> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
>>> vscsi0 at root
>>> scsibus2 at vscsi0: 256 targets
>>> softraid0 at root
>>> scsibus3 at softraid0: 256 targets
>>> root on sd0a (f67e7646a5f64b3f.a) swap on sd0b dump on sd0b
>>>
>>>> hi
>>>>
>>>>
>>>> Am 16.04.2015 um 21:16 schrieb Dariusz Swiderski:
>>>>> hi
>>>>
>>>> yes i will  do today , i et you know if done.
>>>>
>>>> holger
>>>>
>>>>> Hi,
>>>>>
>>>>> can you test the attahced diff?
>>>>>
>>>>> greets
>>>>> dms
>>>>>
>>>>> On Thu, 16 Apr 2015, Dariusz Swiderski wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> more noise, iç¥ stupid for not noticing changed pci dev idç´.
>>>>>> Expect a diff.
>>>>>>
>>>>>> greets
>>>>>> --
>>>>>> Maciej 'sfires' Swiderski
>>>>>> ---
>>>>>> SysAdm | Sec

Re: not known intel ethernet card

2015-04-17 Thread Dariusz Swiderski

 pci0 dev 31 function 2 "Intel EP80579 AHCI" rev 0x01: msi, AHCI
1.1
> scsibus1 at ahci0: 32 targets
> sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct
> fixed t10.ATA_TOSHIBA_MK6037GSX_676FTD3DT
> sd0: 57231MB, 512 bytes/sector, 117210240 sectors
> ichiic0 at pci0 dev 31 function 3 "Intel EP80579 SMBus" rev 0x01: apic 2
> int 19
> iic0 at ichiic0
> spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM
> usb1 at uhci0: USB revision 1.0
> uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> isa0 at pcib0
> isadma0 at isa0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com0: console
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> vscsi0 at root
> scsibus2 at vscsi0: 256 targets
> softraid0 at root
> scsibus3 at softraid0: 256 targets
> root on sd0a (f67e7646a5f64b3f.a) swap on sd0b dump on sd0b
>
> > hi
> >
> >
> > Am 16.04.2015 um 21:16 schrieb Dariusz Swiderski:
> >> hi
> >
> > yes i will  do today , i et you know if done.
> >
> > holger
> >
> >> Hi,
> >>
> >> can you test the attahced diff?
> >>
> >> greets
> >> dms
> >>
> >> On Thu, 16 Apr 2015, Dariusz Swiderski wrote:
> >>
> >>> Hi,
> >>>
> >>> more noise, im stupid for not noticing changed pci dev ids.
> >>> Expect a diff.
> >>>
> >>> greets
> >>> --
> >>> Maciej 'sfires' Swiderski
> >>> ---
> >>> SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
> >>> 193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
> >>> ---
> >>> A mouse is a device used to point at the xterm you want to type in.
> >>>
> >>>> On 16 kwi 2015, at 21:55, Dariusz Swiderski  wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> Sorry for the noise, fixed in latest builds. #784 works as expected
> >>>> for me
> >>> on same hardware.
> >>>> Sent from my iPhone
> >>>>
> >>>>> On 16 kwi 2015, at 20:31, Holger Glaess  wrote:
> >>>>>
> >>>>>> Am 16.04.2015 um 20:21 schrieb Dariusz Swiderski:
> >>>>>> Hi,
> >>>>>>
> >>>>>> Could you provide output of
> >>>>>> pcidump -v
> >>>>>>
> >>>>>> Sent from my iPhone
> >>>>>>
> >>>>>> On 16 kwi 2015, at 18:59, Holger Glaess  >>>>>> <mailto:gla...@glaessixs.de>> wrote:
> >>>>>>
> >>>>>>> hi
> >>>>>>>
> >>>>>>> can help someone ?
> >>>>>>> the 3 other intel ethernet card are also gigabit .
> >>>>>>>
> >>>>>>> holger
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> # dmesg
> >>>>>>> OpenBSD 5.7-current (GENERIC) #759: Wed Apr  1 14:25:18 MDT 2015
> >>>>>>> dera...@i386.openbsd.org
> >>>>>>>
<mailto:dera...@i386.openbsd.org>:/usr/src/sys/arch/i386/compile/GENERIC
> >>>>>>> cpu0: Genuine Intel(R) processor 1.20GHz ("GenuineIntel" 686-class)
> >>>>>>> 1.21 GHz
> >>>>>>> cpu0:
> >>>>>>>
> >>>
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,A
> >>> CPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,PERF
> >>>>>>> real mem  = 1072041984 (1022MB)
> >>>>>>> avail mem = 1042243584 (993MB)
> >>>>>>> mpath0 at root
> >>>>>>> scsibus0 at mpath0: 256 targets
> >>>>>>> mainbus0 at root
> >>>>>>> bios0 at mainbus0: date 07/06/09, BIOS32 rev. 0 @ 0xfa530, SMBIOS
> >>>>>>> rev. 2.2 @ 0xf0800 (39 entries)
> >>>>>>> bios0: vendor Phoenix Technologies, LTD version "ANSA 3020 R01
> >>>>>>> Jul,2,2009" date 07/06/2009

Re: not known intel ethernet card

2015-04-17 Thread Dariusz Swiderski

0 "Intel EP80579 USB" rev 0x01: apic 2 int 23
> ehci0 at pci0 dev 29 function 7 "Intel EP80579 USB" rev 0x01: apic 2 int 23
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> pcib0 at pci0 dev 31 function 0 "Intel EP80579 LPC" rev 0x01
> ahci0 at pci0 dev 31 function 2 "Intel EP80579 AHCI" rev 0x01: msi, AHCI
1.1
> scsibus1 at ahci0: 32 targets
> sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct
> fixed t10.ATA_TOSHIBA_MK6037GSX_676FTD3DT
> sd0: 57231MB, 512 bytes/sector, 117210240 sectors
> ichiic0 at pci0 dev 31 function 3 "Intel EP80579 SMBus" rev 0x01: apic 2
> int 19
> iic0 at ichiic0
> spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM
> usb1 at uhci0: USB revision 1.0
> uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> isa0 at pcib0
> isadma0 at isa0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com0: console
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard
> pcppi0 at isa0 port 0x61
> spkr0 at pcppi0
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> vscsi0 at root
> scsibus2 at vscsi0: 256 targets
> softraid0 at root
> scsibus3 at softraid0: 256 targets
> root on sd0a (f67e7646a5f64b3f.a) swap on sd0b dump on sd0b
>
>> hi
>>
>>
>> Am 16.04.2015 um 21:16 schrieb Dariusz Swiderski:
>>> hi
>>
>> yes i will  do today , i et you know if done.
>>
>> holger
>>
>>> Hi,
>>>
>>> can you test the attahced diff?
>>>
>>> greets
>>> dms
>>>
>>> On Thu, 16 Apr 2015, Dariusz Swiderski wrote:
>>>
>>>> Hi,
>>>>
>>>> more noise, iç¥ stupid for not noticing changed pci dev idç´.
>>>> Expect a diff.
>>>>
>>>> greets
>>>> --
>>>> Maciej 'sfires' Swiderski
>>>> ---
>>>> SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
>>>> 193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
>>>> ---
>>>> A mouse is a device used to point at the xterm you want to type in.
>>>>
>>>>> On 16 kwi 2015, at 21:55, Dariusz Swiderski  wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Sorry for the noise, fixed in latest builds. #784 works as expected
>>>>> for me
>>>> on same hardware.
>>>>> Sent from my iPhone
>>>>>
>>>>>> On 16 kwi 2015, at 20:31, Holger Glaess  wrote:
>>>>>>
>>>>>>> Am 16.04.2015 um 20:21 schrieb Dariusz Swiderski:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Could you provide output of
>>>>>>> pcidump -v
>>>>>>>
>>>>>>> Sent from my iPhone
>>>>>>>
>>>>>>> On 16 kwi 2015, at 18:59, Holger Glaess >>>>>> <mailto:gla...@glaessixs.de>> wrote:
>>>>>>>
>>>>>>>> hi
>>>>>>>>
>>>>>>>> can help someone ?
>>>>>>>> the 3 other intel ethernet card are also gigabit .
>>>>>>>>
>>>>>>>> holger
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> # dmesg
>>>>>>>> OpenBSD 5.7-current (GENERIC) #759: Wed Apr  1 14:25:18 MDT 2015
>>>>>>>> dera...@i386.openbsd.org
>>>>>>>>
<mailto:dera...@i386.openbsd.org>:/usr/src/sys/arch/i386/compile/GENERIC
>>>>>>>> cpu0: Genuine Intel(R) processor 1.20GHz ("GenuineIntel" 686-class)
>>>>>>>> 1.21 GHz
>>>>>>>> cpu0:
>>>>>>>>
>>>>
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,A
>>>> CPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,PERF
>>>>>>>> real mem  = 1072041984 (1022MB)
>>>>>>>> avail mem = 1042243584 (993MB)
>>>>>>>> mpath0 at root
>>>>>>>> scsibus0 at mpath0: 256 targets
>>>>>>>> mainbus0 at root
>>>>>>>> bios0 at mainbus0: date 07/06/09, BIOS32 rev. 0

Re: not known intel ethernet card

2015-04-16 Thread Dariusz Swiderski

Hi,

can you test the attahced diff?

greets
dms

On Thu, 16 Apr 2015, Dariusz Swiderski wrote:

> Hi,
>
> more noise, iâm stupid for not noticing changed pci dev idâs.
> Expect a diff.
>
> greets
> --
> Maciej 'sfires' Swiderski
> ---
> SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
> 193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
> ---
> A mouse is a device used to point at the xterm you want to type in.
>
> > On 16 kwi 2015, at 21:55, Dariusz Swiderski  wrote:
> >
> > Hi,
> >
> > Sorry for the noise, fixed in latest builds. #784 works as expected for
me
> on same hardware.
> >
> > Sent from my iPhone
> >
> >> On 16 kwi 2015, at 20:31, Holger Glaess  wrote:
> >>
> >>> Am 16.04.2015 um 20:21 schrieb Dariusz Swiderski:
> >>> Hi,
> >>>
> >>> Could you provide output of
> >>> pcidump -v
> >>>
> >>> Sent from my iPhone
> >>>
> >>> On 16 kwi 2015, at 18:59, Holger Glaess  >>> <mailto:gla...@glaessixs.de>> wrote:
> >>>
> >>>> hi
> >>>>
> >>>> can help someone ?
> >>>> the 3 other intel ethernet card are also gigabit .
> >>>>
> >>>> holger
> >>>>
> >>>>
> >>>>
> >>>> # dmesg
> >>>> OpenBSD 5.7-current (GENERIC) #759: Wed Apr  1 14:25:18 MDT 2015
> >>>> dera...@i386.openbsd.org
> >>>>
<mailto:dera...@i386.openbsd.org>:/usr/src/sys/arch/i386/compile/GENERIC
> >>>> cpu0: Genuine Intel(R) processor 1.20GHz ("GenuineIntel" 686-class)
> >>>> 1.21 GHz
> >>>> cpu0:
> >>>>
>
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,A
> CPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,PERF
> >>>> real mem  = 1072041984 (1022MB)
> >>>> avail mem = 1042243584 (993MB)
> >>>> mpath0 at root
> >>>> scsibus0 at mpath0: 256 targets
> >>>> mainbus0 at root
> >>>> bios0 at mainbus0: date 07/06/09, BIOS32 rev. 0 @ 0xfa530, SMBIOS
> >>>> rev. 2.2 @ 0xf0800 (39 entries)
> >>>> bios0: vendor Phoenix Technologies, LTD version "ANSA 3020 R01
> >>>>Jul,2,2009" date 07/06/2009
> >>>> acpi0 at bios0: rev 0
> >>>> acpi0: sleep states S0 S3 S4 S5
> >>>> acpi0: tables DSDT FACP MCFG APIC
> >>>> acpi0: wakeup devices EPA0(S3) EPA1(S3) PEX0(S5) PEX1(S5) PEX2(S5)
> >>>> PEX3(S5) HUB0(S5) PCI0(S5)
> >>>> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> >>>> acpimcfg0 at acpi0 addr 0xe000, bus 0-255
> >>>> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> >>>> cpu0 at mainbus0: apid 0 (boot processor)
> >>>> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> >>>> cpu0: apic clock running at 133MHz
> >>>> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
> >>>> acpiprt0 at acpi0: bus 0 (PCI0)
> >>>> acpiprt1 at acpi0: bus 2 (EPA1)
> >>>> acpiprt2 at acpi0: bus -1 (BR10)
> >>>> acpiprt3 at acpi0: bus -1 (BR11)
> >>>> acpiprt4 at acpi0: bus -1 (BR12)
> >>>> acpiprt5 at acpi0: bus -1 (BR13)
> >>>> acpiprt6 at acpi0: bus -1 (BR14)
> >>>> acpiprt7 at acpi0: bus 3 (P0P1)
> >>>> acpiprt8 at acpi0: bus -1 (PEX0)
> >>>> acpiprt9 at acpi0: bus -1 (PEX1)
> >>>> acpiprt10 at acpi0: bus -1 (PEX2)
> >>>> acpiprt11 at acpi0: bus -1 (PEX3)
> >>>> acpiprt12 at acpi0: bus -1 (HUB0)
> >>>> acpicpu0 at acpi0
> >>>> acpitz0 at acpi0: critical temperature is 75 degC
> >>>> acpibtn0 at acpi0: PWRB
> >>>> bios0: ROM list: 0xc8000/0x4000! 0xcc000/0x2200! 0xef000/0x1000!
> >>>> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> >>>> pchb0 at pci0 dev 0 function 0 "Intel EP80579 Host" rev 0x01
> >>>> "Intel EP80579 Memory" rev 0x01 at pci0 dev 0 function 1 not
configured
> >>>> "Intel EP80579 EDMA" rev 0x01 at pci0 dev 1 function 0 not configured
> >>>> ppb0 at pci0 dev 2 function 0 "Intel EP80579 PCIE" rev 0x01: apic 2
> >>>> int 16
> >>>> pci1 at ppb0 bus 1
> >>>> em0 at pci1 dev 0

Re: not known intel ethernet card

2015-04-16 Thread Dariusz Swiderski

Hi,

more noise, iâm stupid for not noticing changed pci dev idâs.
Expect a diff.

greets
--
Maciej 'sfires' Swiderski
---
SysAdm | SecOff  | DS14145-RIPE| DS11-6BONE
193.178.161.0/24 | 3ffe:8010:7:2a::/64 | AS16288
---
A mouse is a device used to point at the xterm you want to type in.

> On 16 kwi 2015, at 21:55, Dariusz Swiderski  wrote:
>
> Hi,
>
> Sorry for the noise, fixed in latest builds. #784 works as expected for me
on same hardware.
>
> Sent from my iPhone
>
>> On 16 kwi 2015, at 20:31, Holger Glaess  wrote:
>>
>>> Am 16.04.2015 um 20:21 schrieb Dariusz Swiderski:
>>> Hi,
>>>
>>> Could you provide output of
>>> pcidump -v
>>>
>>> Sent from my iPhone
>>>
>>> On 16 kwi 2015, at 18:59, Holger Glaess >> <mailto:gla...@glaessixs.de>> wrote:
>>>
>>>> hi
>>>>
>>>> can help someone ?
>>>> the 3 other intel ethernet card are also gigabit .
>>>>
>>>> holger
>>>>
>>>>
>>>>
>>>> # dmesg
>>>> OpenBSD 5.7-current (GENERIC) #759: Wed Apr  1 14:25:18 MDT 2015
>>>> dera...@i386.openbsd.org
>>>> <mailto:dera...@i386.openbsd.org>:/usr/src/sys/arch/i386/compile/GENERIC
>>>> cpu0: Genuine Intel(R) processor 1.20GHz ("GenuineIntel" 686-class)
>>>> 1.21 GHz
>>>> cpu0:
>>>>
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,A
CPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,PERF
>>>> real mem  = 1072041984 (1022MB)
>>>> avail mem = 1042243584 (993MB)
>>>> mpath0 at root
>>>> scsibus0 at mpath0: 256 targets
>>>> mainbus0 at root
>>>> bios0 at mainbus0: date 07/06/09, BIOS32 rev. 0 @ 0xfa530, SMBIOS
>>>> rev. 2.2 @ 0xf0800 (39 entries)
>>>> bios0: vendor Phoenix Technologies, LTD version "ANSA 3020 R01
>>>>Jul,2,2009" date 07/06/2009
>>>> acpi0 at bios0: rev 0
>>>> acpi0: sleep states S0 S3 S4 S5
>>>> acpi0: tables DSDT FACP MCFG APIC
>>>> acpi0: wakeup devices EPA0(S3) EPA1(S3) PEX0(S5) PEX1(S5) PEX2(S5)
>>>> PEX3(S5) HUB0(S5) PCI0(S5)
>>>> acpitimer0 at acpi0: 3579545 Hz, 24 bits
>>>> acpimcfg0 at acpi0 addr 0xe000, bus 0-255
>>>> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
>>>> cpu0 at mainbus0: apid 0 (boot processor)
>>>> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
>>>> cpu0: apic clock running at 133MHz
>>>> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
>>>> acpiprt0 at acpi0: bus 0 (PCI0)
>>>> acpiprt1 at acpi0: bus 2 (EPA1)
>>>> acpiprt2 at acpi0: bus -1 (BR10)
>>>> acpiprt3 at acpi0: bus -1 (BR11)
>>>> acpiprt4 at acpi0: bus -1 (BR12)
>>>> acpiprt5 at acpi0: bus -1 (BR13)
>>>> acpiprt6 at acpi0: bus -1 (BR14)
>>>> acpiprt7 at acpi0: bus 3 (P0P1)
>>>> acpiprt8 at acpi0: bus -1 (PEX0)
>>>> acpiprt9 at acpi0: bus -1 (PEX1)
>>>> acpiprt10 at acpi0: bus -1 (PEX2)
>>>> acpiprt11 at acpi0: bus -1 (PEX3)
>>>> acpiprt12 at acpi0: bus -1 (HUB0)
>>>> acpicpu0 at acpi0
>>>> acpitz0 at acpi0: critical temperature is 75 degC
>>>> acpibtn0 at acpi0: PWRB
>>>> bios0: ROM list: 0xc8000/0x4000! 0xcc000/0x2200! 0xef000/0x1000!
>>>> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>>>> pchb0 at pci0 dev 0 function 0 "Intel EP80579 Host" rev 0x01
>>>> "Intel EP80579 Memory" rev 0x01 at pci0 dev 0 function 1 not configured
>>>> "Intel EP80579 EDMA" rev 0x01 at pci0 dev 1 function 0 not configured
>>>> ppb0 at pci0 dev 2 function 0 "Intel EP80579 PCIE" rev 0x01: apic 2
>>>> int 16
>>>> pci1 at ppb0 bus 1
>>>> em0 at pci1 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address
>>>> 00:14:b7:00:61:63
>>>> ppb1 at pci0 dev 3 function 0 "Intel EP80579 PCIE" rev 0x01: apic 2
>>>> int 16
>>>> pci2 at ppb1 bus 2
>>>> ppb2 at pci0 dev 4 function 0 "Intel EP80579" rev 0x01
>>>> pci3 at ppb2 bus 3
>>>> vendor "Intel", unknown product 0x5041 (class network subclass
>>>> ethernet, rev 0x01) at pci3 dev 0 function 0 not configured
>>>> vendor "Intel", unknown product 0x50

Re: not known intel ethernet card

2015-04-16 Thread Dariusz Swiderski

Hi,

Sorry for the noise, fixed in latest builds. #784 works as expected for me on 
same hardware.

Sent from my iPhone

> On 16 kwi 2015, at 20:31, Holger Glaess  wrote:
> 
>> Am 16.04.2015 um 20:21 schrieb Dariusz Swiderski:
>> Hi,
>> 
>> Could you provide output of
>> pcidump -v
>> 
>> Sent from my iPhone
>> 
>> On 16 kwi 2015, at 18:59, Holger Glaess > <mailto:gla...@glaessixs.de>> wrote:
>> 
>>> hi
>>> 
>>> can help someone ?
>>> the 3 other intel ethernet card are also gigabit .
>>> 
>>> holger
>>> 
>>> 
>>> 
>>> # dmesg
>>> OpenBSD 5.7-current (GENERIC) #759: Wed Apr  1 14:25:18 MDT 2015
>>> dera...@i386.openbsd.org 
>>> <mailto:dera...@i386.openbsd.org>:/usr/src/sys/arch/i386/compile/GENERIC
>>> cpu0: Genuine Intel(R) processor 1.20GHz ("GenuineIntel" 686-class) 
>>> 1.21 GHz
>>> cpu0: 
>>> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,PERF
>>> real mem  = 1072041984 (1022MB)
>>> avail mem = 1042243584 (993MB)
>>> mpath0 at root
>>> scsibus0 at mpath0: 256 targets
>>> mainbus0 at root
>>> bios0 at mainbus0: date 07/06/09, BIOS32 rev. 0 @ 0xfa530, SMBIOS 
>>> rev. 2.2 @ 0xf0800 (39 entries)
>>> bios0: vendor Phoenix Technologies, LTD version "ANSA 3020 R01 
>>> Jul,2,2009" date 07/06/2009
>>> acpi0 at bios0: rev 0
>>> acpi0: sleep states S0 S3 S4 S5
>>> acpi0: tables DSDT FACP MCFG APIC
>>> acpi0: wakeup devices EPA0(S3) EPA1(S3) PEX0(S5) PEX1(S5) PEX2(S5) 
>>> PEX3(S5) HUB0(S5) PCI0(S5)
>>> acpitimer0 at acpi0: 3579545 Hz, 24 bits
>>> acpimcfg0 at acpi0 addr 0xe000, bus 0-255
>>> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
>>> cpu0 at mainbus0: apid 0 (boot processor)
>>> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
>>> cpu0: apic clock running at 133MHz
>>> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
>>> acpiprt0 at acpi0: bus 0 (PCI0)
>>> acpiprt1 at acpi0: bus 2 (EPA1)
>>> acpiprt2 at acpi0: bus -1 (BR10)
>>> acpiprt3 at acpi0: bus -1 (BR11)
>>> acpiprt4 at acpi0: bus -1 (BR12)
>>> acpiprt5 at acpi0: bus -1 (BR13)
>>> acpiprt6 at acpi0: bus -1 (BR14)
>>> acpiprt7 at acpi0: bus 3 (P0P1)
>>> acpiprt8 at acpi0: bus -1 (PEX0)
>>> acpiprt9 at acpi0: bus -1 (PEX1)
>>> acpiprt10 at acpi0: bus -1 (PEX2)
>>> acpiprt11 at acpi0: bus -1 (PEX3)
>>> acpiprt12 at acpi0: bus -1 (HUB0)
>>> acpicpu0 at acpi0
>>> acpitz0 at acpi0: critical temperature is 75 degC
>>> acpibtn0 at acpi0: PWRB
>>> bios0: ROM list: 0xc8000/0x4000! 0xcc000/0x2200! 0xef000/0x1000!
>>> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>>> pchb0 at pci0 dev 0 function 0 "Intel EP80579 Host" rev 0x01
>>> "Intel EP80579 Memory" rev 0x01 at pci0 dev 0 function 1 not configured
>>> "Intel EP80579 EDMA" rev 0x01 at pci0 dev 1 function 0 not configured
>>> ppb0 at pci0 dev 2 function 0 "Intel EP80579 PCIE" rev 0x01: apic 2 
>>> int 16
>>> pci1 at ppb0 bus 1
>>> em0 at pci1 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address 
>>> 00:14:b7:00:61:63
>>> ppb1 at pci0 dev 3 function 0 "Intel EP80579 PCIE" rev 0x01: apic 2 
>>> int 16
>>> pci2 at ppb1 bus 2
>>> ppb2 at pci0 dev 4 function 0 "Intel EP80579" rev 0x01
>>> pci3 at ppb2 bus 3
>>> vendor "Intel", unknown product 0x5041 (class network subclass 
>>> ethernet, rev 0x01) at pci3 dev 0 function 0 not configured
>>> vendor "Intel", unknown product 0x5045 (class network subclass 
>>> ethernet, rev 0x01) at pci3 dev 1 function 0 not configured
>>> vendor "Intel", unknown product 0x5049 (class network subclass 
>>> ethernet, rev 0x01) at pci3 dev 2 function 0 not configured
>>> gcu0 at pci3 dev 3 function 0 "Intel EP80579 GCU" rev 0x01
>>> "Intel EP80579 CANbus" rev 0x01 at pci3 dev 4 function 0 not configured
>>> "Intel EP80579 CANbus" rev 0x01 at pci3 dev 5 function 0 not configured
>>> "Intel EP80579 Serial" rev 0x01 at pci3 dev 6 function 0 not configured
>>> "Intel EP80579 1588" rev 0x01 at pci3 dev 7 function 0 not configured
>>> "Intel EP80579 LEB" rev 0x01 at pci3 dev 8 function 0 not config

Re: not known intel ethernet card

2015-04-16 Thread Dariusz Swiderski

Hi,

Could you provide output of
pcidump -v

Sent from my iPhone

> On 16 kwi 2015, at 18:59, Holger Glaess  wrote:
>
> hi
>
> can help someone ?
> the 3 other intel ethernet card are also gigabit .
>
> holger
>
>
>
> # dmesg
> OpenBSD 5.7-current (GENERIC) #759: Wed Apr  1 14:25:18 MDT 2015
>dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Genuine Intel(R) processor 1.20GHz ("GenuineIntel" 686-class) 1.21
GHz
> cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,A
CPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,PERF
> real mem  = 1072041984 (1022MB)
> avail mem = 1042243584 (993MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: date 07/06/09, BIOS32 rev. 0 @ 0xfa530, SMBIOS rev. 2.2 @
0xf0800 (39 entries)
> bios0: vendor Phoenix Technologies, LTD version "ANSA 3020 R01
Jul,2,2009" date 07/06/2009
> acpi0 at bios0: rev 0
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP MCFG APIC
> acpi0: wakeup devices EPA0(S3) EPA1(S3) PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5)
HUB0(S5) PCI0(S5)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimcfg0 at acpi0 addr 0xe000, bus 0-255
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 133MHz
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 2 (EPA1)
> acpiprt2 at acpi0: bus -1 (BR10)
> acpiprt3 at acpi0: bus -1 (BR11)
> acpiprt4 at acpi0: bus -1 (BR12)
> acpiprt5 at acpi0: bus -1 (BR13)
> acpiprt6 at acpi0: bus -1 (BR14)
> acpiprt7 at acpi0: bus 3 (P0P1)
> acpiprt8 at acpi0: bus -1 (PEX0)
> acpiprt9 at acpi0: bus -1 (PEX1)
> acpiprt10 at acpi0: bus -1 (PEX2)
> acpiprt11 at acpi0: bus -1 (PEX3)
> acpiprt12 at acpi0: bus -1 (HUB0)
> acpicpu0 at acpi0
> acpitz0 at acpi0: critical temperature is 75 degC
> acpibtn0 at acpi0: PWRB
> bios0: ROM list: 0xc8000/0x4000! 0xcc000/0x2200! 0xef000/0x1000!
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel EP80579 Host" rev 0x01
> "Intel EP80579 Memory" rev 0x01 at pci0 dev 0 function 1 not configured
> "Intel EP80579 EDMA" rev 0x01 at pci0 dev 1 function 0 not configured
> ppb0 at pci0 dev 2 function 0 "Intel EP80579 PCIE" rev 0x01: apic 2 int 16
> pci1 at ppb0 bus 1
> em0 at pci1 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address
00:14:b7:00:61:63
> ppb1 at pci0 dev 3 function 0 "Intel EP80579 PCIE" rev 0x01: apic 2 int 16
> pci2 at ppb1 bus 2
> ppb2 at pci0 dev 4 function 0 "Intel EP80579" rev 0x01
> pci3 at ppb2 bus 3
> vendor "Intel", unknown product 0x5041 (class network subclass ethernet, rev
0x01) at pci3 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x5045 (class network subclass ethernet, rev
0x01) at pci3 dev 1 function 0 not configured
> vendor "Intel", unknown product 0x5049 (class network subclass ethernet, rev
0x01) at pci3 dev 2 function 0 not configured
> gcu0 at pci3 dev 3 function 0 "Intel EP80579 GCU" rev 0x01
> "Intel EP80579 CANbus" rev 0x01 at pci3 dev 4 function 0 not configured
> "Intel EP80579 CANbus" rev 0x01 at pci3 dev 5 function 0 not configured
> "Intel EP80579 Serial" rev 0x01 at pci3 dev 6 function 0 not configured
> "Intel EP80579 1588" rev 0x01 at pci3 dev 7 function 0 not configured
> "Intel EP80579 LEB" rev 0x01 at pci3 dev 8 function 0 not configured
> vendor "Intel", unknown product 0x502d (class processor subclass
Co-processor, rev 0x01) at pci3 dev 9 function 0 not configured
> "Intel EP80579 Reserved" rev 0x01 at pci3 dev 10 function 0 not configured
> vendor "Intel", unknown product 0x504c (class processor subclass
Co-processor, rev 0x01) at pci3 dev 11 function 0 not configured
> "Intel EP80579 Reserved" rev 0x01 at pci3 dev 12 function 0 not configured
> uhci0 at pci0 dev 29 function 0 "Intel EP80579 USB" rev 0x01: apic 2 int 23
> ehci0 at pci0 dev 29 function 7 "Intel EP80579 USB" rev 0x01: apic 2 int 23
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
> pcib0 at pci0 dev 31 function 0 "Intel EP80579 LPC" rev 0x01
> ahci0 at pci0 dev 31 function 2 "Intel EP80579 AHCI" rev 0x01: msi, AHCI
1.1
> ahci0: port 0: 3.0Gb/s
> scsibus1 at ahci0: 32 targets
> sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct
fixed t10.ATA_TOSHIBA_MK6037GSX_676FTD3DT
> sd0: 57231MB, 512 bytes/sector, 117210240 sectors
> ichiic0 at pci0 dev 31 function 3 "Intel EP80579 SMBus" rev 0x01: apic 2 int
19
> iic0 at ichiic0
> spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM
> usb1 at uhci0: USB revision 1.0
> uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
> isa0 at pcib0
> isadma0 at isa0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com0: console
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> pckbc0 at isa0 port 0x60/5
> pckbc0: using irq 12 for aux slot
> pckbd0 at

Re: not known intel ethernet card

2015-04-16 Thread Dariusz Swiderski

I think this was broker by dlg@ recent commit, one that I had no chance to 
test. Will work on the diff.

Sent from my iPhone

> On 16 kwi 2015, at 20:31, Holger Glaess  wrote:
> 
>> Am 16.04.2015 um 20:21 schrieb Dariusz Swiderski:
>> Hi,
>> 
>> Could you provide output of
>> pcidump -v
>> 
>> Sent from my iPhone
>> 
>> On 16 kwi 2015, at 18:59, Holger Glaess > <mailto:gla...@glaessixs.de>> wrote:
>> 
>>> hi
>>> 
>>> can help someone ?
>>> the 3 other intel ethernet card are also gigabit .
>>> 
>>> holger
>>> 
>>> 
>>> 
>>> # dmesg
>>> OpenBSD 5.7-current (GENERIC) #759: Wed Apr  1 14:25:18 MDT 2015
>>> dera...@i386.openbsd.org 
>>> <mailto:dera...@i386.openbsd.org>:/usr/src/sys/arch/i386/compile/GENERIC
>>> cpu0: Genuine Intel(R) processor 1.20GHz ("GenuineIntel" 686-class) 
>>> 1.21 GHz
>>> cpu0: 
>>> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,PERF
>>> real mem  = 1072041984 (1022MB)
>>> avail mem = 1042243584 (993MB)
>>> mpath0 at root
>>> scsibus0 at mpath0: 256 targets
>>> mainbus0 at root
>>> bios0 at mainbus0: date 07/06/09, BIOS32 rev. 0 @ 0xfa530, SMBIOS 
>>> rev. 2.2 @ 0xf0800 (39 entries)
>>> bios0: vendor Phoenix Technologies, LTD version "ANSA 3020 R01 
>>> Jul,2,2009" date 07/06/2009
>>> acpi0 at bios0: rev 0
>>> acpi0: sleep states S0 S3 S4 S5
>>> acpi0: tables DSDT FACP MCFG APIC
>>> acpi0: wakeup devices EPA0(S3) EPA1(S3) PEX0(S5) PEX1(S5) PEX2(S5) 
>>> PEX3(S5) HUB0(S5) PCI0(S5)
>>> acpitimer0 at acpi0: 3579545 Hz, 24 bits
>>> acpimcfg0 at acpi0 addr 0xe000, bus 0-255
>>> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
>>> cpu0 at mainbus0: apid 0 (boot processor)
>>> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
>>> cpu0: apic clock running at 133MHz
>>> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
>>> acpiprt0 at acpi0: bus 0 (PCI0)
>>> acpiprt1 at acpi0: bus 2 (EPA1)
>>> acpiprt2 at acpi0: bus -1 (BR10)
>>> acpiprt3 at acpi0: bus -1 (BR11)
>>> acpiprt4 at acpi0: bus -1 (BR12)
>>> acpiprt5 at acpi0: bus -1 (BR13)
>>> acpiprt6 at acpi0: bus -1 (BR14)
>>> acpiprt7 at acpi0: bus 3 (P0P1)
>>> acpiprt8 at acpi0: bus -1 (PEX0)
>>> acpiprt9 at acpi0: bus -1 (PEX1)
>>> acpiprt10 at acpi0: bus -1 (PEX2)
>>> acpiprt11 at acpi0: bus -1 (PEX3)
>>> acpiprt12 at acpi0: bus -1 (HUB0)
>>> acpicpu0 at acpi0
>>> acpitz0 at acpi0: critical temperature is 75 degC
>>> acpibtn0 at acpi0: PWRB
>>> bios0: ROM list: 0xc8000/0x4000! 0xcc000/0x2200! 0xef000/0x1000!
>>> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>>> pchb0 at pci0 dev 0 function 0 "Intel EP80579 Host" rev 0x01
>>> "Intel EP80579 Memory" rev 0x01 at pci0 dev 0 function 1 not configured
>>> "Intel EP80579 EDMA" rev 0x01 at pci0 dev 1 function 0 not configured
>>> ppb0 at pci0 dev 2 function 0 "Intel EP80579 PCIE" rev 0x01: apic 2 
>>> int 16
>>> pci1 at ppb0 bus 1
>>> em0 at pci1 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address 
>>> 00:14:b7:00:61:63
>>> ppb1 at pci0 dev 3 function 0 "Intel EP80579 PCIE" rev 0x01: apic 2 
>>> int 16
>>> pci2 at ppb1 bus 2
>>> ppb2 at pci0 dev 4 function 0 "Intel EP80579" rev 0x01
>>> pci3 at ppb2 bus 3
>>> vendor "Intel", unknown product 0x5041 (class network subclass 
>>> ethernet, rev 0x01) at pci3 dev 0 function 0 not configured
>>> vendor "Intel", unknown product 0x5045 (class network subclass 
>>> ethernet, rev 0x01) at pci3 dev 1 function 0 not configured
>>> vendor "Intel", unknown product 0x5049 (class network subclass 
>>> ethernet, rev 0x01) at pci3 dev 2 function 0 not configured
>>> gcu0 at pci3 dev 3 function 0 "Intel EP80579 GCU" rev 0x01
>>> "Intel EP80579 CANbus" rev 0x01 at pci3 dev 4 function 0 not configured
>>> "Intel EP80579 CANbus" rev 0x01 at pci3 dev 5 function 0 not configured
>>> "Intel EP80579 Serial" rev 0x01 at pci3 dev 6 function 0 not configured
>>> "Intel EP80579 1588" rev 0x01 at pci3 dev 7 function 0 not configured
>>> "Intel EP80579 LEB" rev 0x01 at pci3 dev 8 function 0 not config

Re: network interface not recognized on Intel S3420GPLC board

2010-03-02 Thread Dariusz Swiderski

hi,

the second onboard interface:
 0:25:0: Intel unknown  

 
0x: Vendor ID: 8086 Product ID: 10ef

is the latest intel chipset-integrated MAC, called PCH, support for it is 
being worked on. i hope to have a working patch in 2-3 days.

dms@

On Tue, 2 Mar 2010, Ross Davis wrote:

> Thank you, here they are:
> 
> # pcidump -v
> Domain /dev/pci0:
>  0:0:0: Intel unknown
> 0x: Vendor ID: 8086 Product ID: d130
> 0x0004: Command:  Status ID: 0810
> 0x0008: Class: 06 Subclass: 00 Interface: 00 Revision: 11
> 0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line
> Size: 00
> 0x0010: BAR empty ()
> 0x0014: BAR empty ()
> 0x0018: BAR empty ()
> 0x001c: BAR empty ()
> 0x0020: BAR empty ()
> 0x0024: BAR empty ()
> 0x0028: Cardbus CIS: 
> 0x002c: Subsystem Vendor ID: 8086 Product ID: 
> 0x0030: Expansion ROM Base Address: 
> 0x0038: 
> 0x003c: Interrupt Pin: 00 Line: ff Min Gnt: 00 Max Lat: 00
> 0x0040: Capability 0x00: Reserved
>  0:5:0: Intel unknown
> 0x: Vendor ID: 8086 Product ID: d13a
> 0x0004: Command: 0007 Status ID: 0010
> 0x0008: Class: 06 Subclass: 04 Interface: 00 Revision: 11
> 0x000c: BIST: 00 Header Type: 01 Latency Timer: 00 Cache Line
> Size: 00
> 0x0010: 
> 0x0014: 
> 0x0018: Primary Bus: 0 Secondary Bus: 1 Subordinate Bus: 1
> Secondary Latency Timer: 00
> 0x001c: I/O Base: 20 I/O Limit: 20 Secondary Status: 2000
> 0x0020: Memory Base: b1a0 Memory Limit: b1a0
> 0x0024: Prefetch Memory Base: fff1 Prefetch Memory Limit: 0001
> 0x0028: Prefetch Memory Base Upper 32 Bits: 
> 0x002c: Prefetch Memory Limit Upper 32 Bits: 
> 0x0030: I/O Base Upper 16 Bits:  I/O Limit Upper 16 Bits: 
> 0x0038: Expansion ROM Base Address: 
> 0x003c: Interrupt Pin: 01 Line: 0a Bridge Control: 
> 0x0040: Capability 0x0d: PCI-PCI
> 0x0060: Capability 0x05: Message Signaled Interrupts (MSI)
> 0x0090: Capability 0x10: PCI Express
> 0x00e0: Capability 0x01: Power Management
>  0:8:0: Intel unknown
> 0x: Vendor ID: 8086 Product ID: d155
> 0x0004: Command:  Status ID: 0010
> 0x0008: Class: 08 Subclass: 80 Interface: 00 Revision: 11
> 0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line
> Size: 00
> 0x0010: BAR empty ()
> 0x0014: BAR empty ()
> 0x0018: BAR empty ()
> 0x001c: BAR empty ()
> 0x0020: BAR empty ()
> 0x0024: BAR empty ()
> 0x0028: Cardbus CIS: 
> 0x002c: Subsystem Vendor ID:  Product ID: 
> 0x0030: Expansion ROM Base Address: 
> 0x0038: 
> 0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
> 0x0040: Capability 0x10: PCI Express
>  0:8:1: Intel unknown
> 0x: Vendor ID: 8086 Product ID: d156
> 0x0004: Command:  Status ID: 0010
> 0x0008: Class: 08 Subclass: 80 Interface: 00 Revision: 11
> 0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line
> Size: 00
> 0x0010: BAR empty ()
> 0x0014: BAR empty ()
> 0x0018: BAR empty ()
> 0x001c: BAR empty ()
> 0x0020: BAR empty ()
> 0x0024: BAR empty ()
> 0x0028: Cardbus CIS: 
> 0x002c: Subsystem Vendor ID:  Product ID: 
> 0x0030: Expansion ROM Base Address: 
> 0x0038: 
> 0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
> 0x0040: Capability 0x10: PCI Express
>  0:8:2: Intel unknown
> 0x: Vendor ID: 8086 Product ID: d157
> 0x0004: Command:  Status ID: 0010
> 0x0008: Class: 08 Subclass: 80 Interface: 00 Revision: 11
> 0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line
> Size: 00
> 0x0010: BAR empty ()
> 0x0014: BAR empty ()
> 0x0018: BAR empty ()
> 0x001c: BAR empty ()
> 0x0020: BAR empty ()
> 0x0024: BAR empty ()
> 0x0028: Cardbus CIS: 
> 0x002c: Subsystem Vendor ID:  Product ID: 
> 0x0030: Expansion ROM Base Address: 
> 0x0038: 
> 0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00
> 0x0040: Capability 0x10: PCI Express
>  0:8:3: Intel unknown
> 0x: Vendor ID: 8086 Prod

Re: OpenBSD + Nehalem: Now or Later?

2009-10-02 Thread Dariusz Swiderski

On Fri, 2 Oct 2009, Toni Mueller wrote:

> Hi,
> 
> I'm considering to purchase Supermicro servers with one or two Nehalem
> CPUs and a 5520 chipset. Has anyone already tried these, and/or how
> much breakage should I expect?

i have a server based on 5500 chipset, most stuff works on -current,
no bigmem support yet, so you will be imited to around 3GB, but its stable

> My reading of /plus.html suggests that it may be too early to jump onto
> this train, but if some devs want a few weeks play with it, remotely,
> that may be possible (please contact me off-list).

regards
dms@

Re: kernel panic

Re: Adding a NIC into cramped micro itx board for firewall

Re: not known intel ethernet card

Re: not known intel ethernet card

Re: not known intel ethernet card

Re: not known intel ethernet card

Re: not known intel ethernet card

Re: not known intel ethernet card

Re: not known intel ethernet card

Re: not known intel ethernet card

Re: not known intel ethernet card

Re: not known intel ethernet card

Re: network interface not recognized on Intel S3420GPLC board

Re: OpenBSD + Nehalem: Now or Later?

14 matches

Site Navigation

Mail list logo

Footer information