From owner-freebsd-isdn Mon Jan 4 05:41:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14319 for freebsd-isdn-outgoing; Mon, 4 Jan 1999 05:41:32 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from vestein.arb-phys.uni-dortmund.de (vestein.arb-phys.uni-dortmund.de [192.109.44.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14308 for ; Mon, 4 Jan 1999 05:41:17 -0800 (PST) (envelope-from wb@vestein.arb-phys.uni-dortmund.de) Received: (from wb@localhost) by vestein.arb-phys.uni-dortmund.de (8.8.5/8.8.5) id OAA09726 for freebsd-isdn@FreeBSD.ORG; Mon, 4 Jan 1999 14:40:19 +0100 (MET) Date: Mon, 4 Jan 1999 14:40:19 +0100 (MET) From: "Wilhelm B. Kloke" Message-Id: <199901041340.OAA09726@vestein.arb-phys.uni-dortmund.de> To: freebsd-isdn@FreeBSD.ORG Subject: problem with Creatix PnP Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a problem getting my Creatix PnP card to work with FreeBSD-3.0-Current (i4bipr). I verified the usability of the card and the line in Windoze. Then I used a copy of my working 2.2.2-setup for a Teles card to my new system. It does not work as expected. The card seems to be accepted on ports 0x120 0x180 irq 12. Though I am irritated by the bootup messages that AddrA is on 0x160. ... Probing for PnP devices: CSN 1 Vendor ID: CMI0001 [0x0100a90d] Serial 0x01000100 Comp ID: @@@0000 [0x00000000] CSN 2 Vendor ID: CTX0000 [0x0000980e] Serial 0x000091a2 Comp ID: @@@0000 [0x00000000] isic0: Creatix ISDN S0-16 P&P isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x100) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x160, AddrB=0x180) isic0 (i4b_pnp sn 0x000091a2) at 0x120 irq 12 flags 0x6 on isa Probing for devices on the ISA bus: ... Here is an excerpt of the debug messages I got after trying to connect: ... da0 at ncr0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da0: 1006MB (2061108 512 byte sectors: 64H 32S/T 1006C) i4b-L1-timer3_expired: state = F4 Awaiting Signal i4b-L1-isic_recover: HSCX B: ISTA = 0x0 i4b-L1-isic_recover: ISAC: ISTA = 0x95 i4b-L1-isic_recover: ISAC: EXIR = 0x10 i4b-L1-isic_recover: ISAC: CISQ = 0x12 i4b-L1-isic_recover: HSCX B: IMASK = 0xff i4b-L1-isic_recover: HSCX A: IMASK = 0xf8 i4b-L1-isic_recover: ISAC: IMASK = 0x2a i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 i4b-L1-ph_data_req: still in state F3! i4b-L3-T303_timeout: SETUP not answered, cr = 57 i4b-L3-next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV _T303EXP - T303 timeout! i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 i4b-L1-ph_data_req: No Space in TX FIFO, state = F4 Awaiting Signal i4b-L1-timer3_expired: state = F4 Awaiting Signal ... The dialling does not seem to be successful, as the remote system log does not show the connection trial. Does anybody have a hint what to try next? Some other strange event is that after putting the line back, my other system running i4b-0.5x refuses to connect also, until reboot. Thanx for any help in advance. And thanks for the software to Helmut and the other helpers. wb -- Dipl.-Math. Wilhelm Bernhard Kloke Institut fuer Arbeitsphysiologie an der Universitaet Dortmund Ardeystrasse 67, D-44139 Dortmund, Tel. 0231-1084-257 montags und dienstags To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message