Quoting Martin Husemann (martin@duskware.de):
> Hmmm,
> 
> >     i4b-L2 i4b_T202_timeout: unit 0, N202 = 3
> >     i4b-L3 T303_timeout: SETUP not answered, cr = 111
> >     i4b-L3 next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout!
> 
> This typically is explained by interrupt problems (the card causing interrupts
> which do not reach the driver).
> 
> But:
> 
> >     i4b-L1 isic_isac_irq: unit 0: CRC error
> >     i4b-L1 isic_isac_irq: unit 0: Receive Aborted error
> >     i4b-L2 i4b_ph_data_ind: ERROR, I-frame < 6 octetts!
> 
> This shows interrupts getting through (isic_isac_irq is the interrupt
> handler for the D-channel).
> 
> This looks very much like broken cables.
> 
> Can you verify this card/cabling/setup works at all with another OS?

I tried another cable on another S-Bus port: same problem.

> Does "vmstat -i" show some interrupts for the ISDN card?

Yes. The Number of irq requests increases, if i make phonecalls
or when my linux box connects.

Could this be a broken Card?

Would it be hard, to implement i4b on a NetBSD 1.5 (i.e. not -current)?
I don't want to install Linux or Windows on my new machine.

Thanks

Christoph

-- 
----------------------------------------------------------------------
Christoph Kaegi                                        ck@neverland.ch
----------------------------------------------------------------------