From owner-freebsd-isdn@FreeBSD.ORG Tue Nov 18 09:33:28 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9115116A4CE for ; Tue, 18 Nov 2003 09:33:28 -0800 (PST) Received: from www.kukulies.org (www.kukulies.org [213.146.112.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2728343FDD for ; Tue, 18 Nov 2003 09:33:27 -0800 (PST) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (localhost [127.0.0.1]) by www.kukulies.org (8.12.10/8.12.6) with ESMTP id hAIHXOoR096375 for ; Tue, 18 Nov 2003 18:33:24 +0100 (CET) (envelope-from kuku@www.kukulies.org) Received: (from kuku@localhost) by www.kukulies.org (8.12.10/8.12.6/Submit) id hAIHXN4X096374 for freebsd-isdn@freebsd.org; Tue, 18 Nov 2003 18:33:23 +0100 (CET) Date: Tue, 18 Nov 2003 18:33:23 +0100 (CET) From: "C. Kukulies" Message-Id: <200311181733.hAIHXN4X096374@www.kukulies.org> To: freebsd-isdn@freebsd.org Subject: how dangerous would it be to switch to 5.1-current? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Nov 2003 17:33:28 -0000 With a gateway machine that runs 4.8 stable I'm considering to switch to 5.1-current (cvsup) at the danger of being off-net after the upgrade. Should I? ifpi0: port 0xd400-0 xd41f mem 0xef001000-0xef00101f irq 10 at device 9.0 on pci0 Oct 23 19:07:32 isdn-kukulies /kernel: ifpi0: ISAC 2085 Version A1/A2 or 2086/21 86 Version 1.1 (IOM-2) is my hardware. -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de From owner-freebsd-isdn@FreeBSD.ORG Tue Nov 18 12:37:01 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E941816A4CE for ; Tue, 18 Nov 2003 12:37:01 -0800 (PST) Received: from mailout11.sul.t-online.com (mailout11.sul.t-online.com [194.25.134.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8F3143FA3 for ; Tue, 18 Nov 2003 12:36:58 -0800 (PST) (envelope-from root@reifenberger.com) Received: from fwd03.aul.t-online.de by mailout11.sul.t-online.com with smtp id 1AMCam-0001n9-02; Tue, 18 Nov 2003 21:36:56 +0100 Received: from nihil.reifenberger.com (GQGvXcZDYeBrvEi+Xg+WOQwM1YncRO6kpJ0ar-BmebRuDzW-w68xov@[217.232.212.16]) by fmrl03.sul.t-online.com with esmtp id 1AMCaY-1dON4S0; Tue, 18 Nov 2003 21:36:42 +0100 Received: from nihil.reifenberger.com (localhost.reifenberger.com [127.0.0.1]) hAILadnI017977; Tue, 18 Nov 2003 22:36:39 +0100 (CET) (envelope-from root@reifenberger.com) Received: from localhost (root@localhost)hAILad44017974; Tue, 18 Nov 2003 22:36:39 +0100 (CET) Date: Tue, 18 Nov 2003 22:36:39 +0100 (CET) From: Michael Reifenberger To: "C. Kukulies" In-Reply-To: <200311181733.hAIHXN4X096374@www.kukulies.org> Message-ID: <20031118223226.T17712@nihil.reifenberger.com> References: <200311181733.hAIHXN4X096374@www.kukulies.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Seen: false X-ID: GQGvXcZDYeBrvEi+Xg+WOQwM1YncRO6kpJ0ar-BmebRuDzW-w68xov@t-dialin.net cc: freebsd-isdn@freebsd.org Subject: Re: how dangerous would it be to switch to 5.1-current? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Nov 2003 20:37:02 -0000 On Tue, 18 Nov 2003, C. Kukulies wrote: > Date: Tue, 18 Nov 2003 18:33:23 +0100 (CET) > From: C. Kukulies > To: freebsd-isdn@freebsd.org > Subject: how dangerous would it be to switch to 5.1-current? > > With a gateway machine that runs 4.8 stable I'm considering to > switch to 5.1-current (cvsup) at the danger of being off-net > after the upgrade. Should I? > Too dangerous. If you ask this question ('cause you havn't tried), you shouldn't upgrade. At least not to -current. Maybe RELENG_4. Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS FreeBSD is BSD, UNIX(tm) is a BSD-like OS From owner-freebsd-isdn@FreeBSD.ORG Tue Nov 18 13:02:00 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8F0216A4CE for ; Tue, 18 Nov 2003 13:02:00 -0800 (PST) Received: from www.kukulies.org (www.kukulies.org [213.146.112.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 160B943FA3 for ; Tue, 18 Nov 2003 13:01:59 -0800 (PST) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (localhost [127.0.0.1]) by www.kukulies.org (8.12.10/8.12.6) with ESMTP id hAIL1ooR098655; Tue, 18 Nov 2003 22:01:50 +0100 (CET) (envelope-from kuku@www.kukulies.org) Received: (from kuku@localhost) by www.kukulies.org (8.12.10/8.12.6/Submit) id hAIL1nL2098650; Tue, 18 Nov 2003 22:01:49 +0100 (CET) Date: Tue, 18 Nov 2003 22:01:48 +0100 From: "Christoph P. Kukulies" To: Michael Reifenberger Message-ID: <20031118210148.GA98520@gilberto.physik.rwth-aachen.de> References: <200311181733.hAIHXN4X096374@www.kukulies.org> <20031118223226.T17712@nihil.reifenberger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031118223226.T17712@nihil.reifenberger.com> User-Agent: Mutt/1.4.1i cc: "C. Kukulies" cc: freebsd-isdn@freebsd.org Subject: Re: how dangerous would it be to switch to 5.1-current? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Nov 2003 21:02:00 -0000 On Tue, Nov 18, 2003 at 10:36:39PM +0100, Michael Reifenberger wrote: > On Tue, 18 Nov 2003, C. Kukulies wrote: > > > Date: Tue, 18 Nov 2003 18:33:23 +0100 (CET) > > From: C. Kukulies > > To: freebsd-isdn@freebsd.org > > Subject: how dangerous would it be to switch to 5.1-current? > > > > With a gateway machine that runs 4.8 stable I'm considering to > > switch to 5.1-current (cvsup) at the danger of being off-net > > after the upgrade. Should I? > > > > Too dangerous. > If you ask this question ('cause you havn't tried), you shouldn't upgrade. > At least not to -current. Maybe RELENG_4. Well, I have gone through a couple of such situations in the past since 386bsd :-) It's just the question whether i4b still works or works again under -current. Under 5.0 there were problems due to timer changes in the kernel. Is anybody running i4b under -current? -- Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de From owner-freebsd-isdn@FreeBSD.ORG Tue Nov 18 14:10:15 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C15316A4CE for ; Tue, 18 Nov 2003 14:10:15 -0800 (PST) Received: from peedub.jennejohn.org (p213.54.222.144.tisdip.tiscali.de [213.54.222.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EFB243F3F for ; Tue, 18 Nov 2003 14:10:14 -0800 (PST) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.12.10/8.11.6) with ESMTP id hAIMA8cl001712; Tue, 18 Nov 2003 23:10:09 +0100 (CET) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200311182210.hAIMA8cl001712@peedub.jennejohn.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Alexander.Farber@t-online.de (Alexander Farber) In-Reply-To: Message from Alexander.Farber@t-online.de (Alexander Farber) <20031026191648.GE436@newhope.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Nov 2003 23:10:08 +0100 From: Gary Jennejohn cc: freebsd-isdn@freebsd.org Subject: Re: Why is bus_set_resource() rarely used? Docs for ISA cards X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Nov 2003 22:10:15 -0000 Alexander Farber writes: > Hi, > > I'm trying to learn how the i4b ISA drivers are > programmed by reading the "Arch Handbook" and looking > at i4b/capi/iavc/iavc_isa.c on my FreeBSD 4-stable PC > and wonder why doesn't iavc (and most other ISDN cards) > use bus_set_resource()? I only see bus_alloc_resource() > being called for SYS_RES_IOPORT and _IRQ in iavc_isa.c > Most of these drivers were written before the entire bus support was added to FBSD. Since they work as they are, why change them? > Also I have the following ISA cards: > > AVM ISA v3.0 > USR Sportster > Teles 16.3 > Siemens smth. > > Where did the people writing drivers for those cards > get the information on how to reset those cards, to > which ports to write what, etc.? Could someone please > point me to the docs? Thanks > I don't know for sure about these cards, but I suspect that the Linux driver was used as a reference. The Linux developers seem to be able to get documentation from the manufacturers more easily than we can :-( --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de From owner-freebsd-isdn@FreeBSD.ORG Tue Nov 18 14:11:27 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85E0216A4CF for ; Tue, 18 Nov 2003 14:11:27 -0800 (PST) Received: from peedub.jennejohn.org (p213.54.222.144.tisdip.tiscali.de [213.54.222.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3906843FCB for ; Tue, 18 Nov 2003 14:11:23 -0800 (PST) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.12.10/8.11.6) with ESMTP id hAIMBIcl001736; Tue, 18 Nov 2003 23:11:18 +0100 (CET) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200311182211.hAIMBIcl001736@peedub.jennejohn.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: "C. Kukulies" In-Reply-To: Message from "C. Kukulies" <200311181733.hAIHXN4X096374@www.kukulies.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Nov 2003 23:11:18 +0100 From: Gary Jennejohn cc: freebsd-isdn@freebsd.org Subject: Re: how dangerous would it be to switch to 5.1-current? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Nov 2003 22:11:27 -0000 "C. Kukulies" writes: > With a gateway machine that runs 4.8 stable I'm considering to > switch to 5.1-current (cvsup) at the danger of being off-net > after the upgrade. Should I? > > ifpi0: port 0xd400-0 > xd41f mem 0xef001000-0xef00101f irq 10 at device 9.0 on pci0 > Oct 23 19:07:32 isdn-kukulies /kernel: ifpi0: ISAC 2085 Version A1/A2 or 2086 > /21 > 86 Version 1.1 (IOM-2) > > is my hardware. > Should still work. My ifpi2 does. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de From owner-freebsd-isdn@FreeBSD.ORG Tue Nov 18 15:35:14 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5334716A4CF for ; Tue, 18 Nov 2003 15:35:14 -0800 (PST) Received: from mail-in-03.arcor-online.net (mail-in-03.arcor-online.net [151.189.21.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBD5A43F3F for ; Tue, 18 Nov 2003 15:35:12 -0800 (PST) (envelope-from markus@mdolze.de) Received: from mdolze.de (dialin-212-144-192-019.arcor-ip.net [212.144.192.19]) by mail-in-03.arcor-online.net (Postfix) with ESMTP id 299CC1B3BB9 for ; Wed, 19 Nov 2003 00:35:10 +0100 (CET) Message-ID: <3FBAACBA.7060603@mdolze.de> Date: Wed, 19 Nov 2003 00:35:22 +0100 From: Markus Dolze User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4.1) Gecko/20031008 X-Accept-Language: de-de, en-us, en MIME-Version: 1.0 To: freebsd-isdn@freebsd.org References: <200311181733.hAIHXN4X096374@www.kukulies.org> In-Reply-To: <200311181733.hAIHXN4X096374@www.kukulies.org> X-Enigmail-Version: 0.76.7.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/mixed; boundary="------------080005040001070003060803" Subject: Re: how dangerous would it be to switch to 5.1-current? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Nov 2003 23:35:14 -0000 This is a multi-part message in MIME format. --------------080005040001070003060803 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I have just tried to upgrade to 5.1-RELEASE (no patches yet). I use rbch to connect via user-land ppp (tun0). If I try to make a connection, I get the error: Nov 19 00:16:23 arwen kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 73 Nov 19 00:16:23 arwen kernel: i4b-L3 next_l3state: FSM illegal state, state = ST_U0 - Null, event = EV_T303EXP - T303 timeout! And the call is disconnected. PPP then tries to redial and the connection is established. Attached are hints (from device.hints), kernel and isdnd.rc config files. I use an old non-pnp AVM Fritz card (isic-driver). Any help? Bye Markus D. C. Kukulies wrote: > With a gateway machine that runs 4.8 stable I'm considering to > switch to 5.1-current (cvsup) at the danger of being off-net > after the upgrade. Should I? > > ifpi0: port 0xd400-0 > xd41f mem 0xef001000-0xef00101f irq 10 at device 9.0 on pci0 > Oct 23 19:07:32 isdn-kukulies /kernel: ifpi0: ISAC 2085 Version A1/A2 or 2086/21 > 86 Version 1.1 (IOM-2) > > is my hardware. > > -- > Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de > _______________________________________________ > freebsd-isdn@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isdn > To unsubscribe, send any mail to "freebsd-isdn-unsubscribe@freebsd.org" > > --------------080005040001070003060803 Content-Type: text/plain; name="log" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="log" Nov 19 00:16:23 arwen kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 73 Nov 19 00:16:23 arwen kernel: i4b-L3 next_l3state: FSM illegal state, state = ST_U0 - Null, event = EV_T303EXP - T303 timeout! Nov 19 00:16:28 arwen login: ROOT LOGIN (root) ON ttyv0 --------------080005040001070003060803 Content-Type: text/plain; name="hints" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="hints" hint.isic.0.at="isa" hint.isic.0.port="0x300" hint.isic.0.irq="5" hint.isic.0.flags="4" --------------080005040001070003060803 Content-Type: text/plain; name="isdnd.rc" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="isdnd.rc" #--------------------------------------------------------------------------- # system section (generated Wed Nov 12 23:25:56 2003) #--------------------------------------------------------------------------- system useacctfile = on # update accounting information file acctall = on # put all events into accounting file acctfile = /var/log/isdnd.acct # accounting information file ratesfile = /etc/isdn/isdnd.rates # charging rates database file rtprio = 25 # isdnd runs at realtime priority monitor-allowed = on # remote isdnd monitoring allowed monitor-port = 451 # TCP/IP port number used for remote monitoring monitor = "/var/run/isdnmonitor" # local socket name for monitoring monitor-access = fullcmd,channelstate,callin,callout,logevents # monitor access rights monitor = "192.168.1.0/24" # host (net/mask) allowed to connect for monitoring monitor-access = fullcmd,channelstate,callin,callout,logevents # monitor access rights #--------------------------------------------------------------------------- # entry section 0 #--------------------------------------------------------------------------- entry name = I4Axxxx # name for this entry section isdncontroller = 0 # ISDN card number used for this entry isdnchannel = 0 # any ISDN B-channel may be used usrdevicename = rbch # name of userland ISDN B-channel device usrdeviceunit = 0 # unit number of userland ISDN B-channel device b1protocol = hdlc # B-channel layer 1 protocol is HDLC direction = out # only outgoing connections allowed remote-phone-dialout = xxxxxxx # telephone number for dialing out to remote local-phone-dialout = xxxxxxx # show this number to remote when dialling out dialout-type = normal # i am not called back by remote idletime-outgoing = 900 # outgoing call idle timeout idle-algorithm-outgoing = fix-unit-size # outgoing call idle algorithm unitlengthsrc = conf # using unitlength specified by unitlength-keyword unitlength = 0 # fixed unitlength earlyhangup = 0 # early hangup safety time dialretries = 3 # number of dialing retries recoverytime = 5 # time to wait between dialling retries dialrandincr = off # use random dialing time addon usedown = off # no device switchoff on excessive dial failures --------------080005040001070003060803 Content-Type: text/plain; name="ARWEN" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ARWEN" # Kernel configuration file for ARWEN include GENERIC ident ARWEN # Driver for ISDN card device isic options AVM_A1 # I4B base configuration device "i4bq921" device "i4bq931" device "i4b" device "i4btrc" 4 device "i4bctl" device "i4brbch" 2 device "i4btel" 2 device "i4bisppp" 2 --------------080005040001070003060803-- From owner-freebsd-isdn@FreeBSD.ORG Tue Nov 18 23:51:32 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FBA816A4CE for ; Tue, 18 Nov 2003 23:51:32 -0800 (PST) Received: from mail1.arcor-ip.de (mail1.arcor-ip.de [145.253.2.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 044F843FE5 for ; Tue, 18 Nov 2003 23:51:31 -0800 (PST) (envelope-from Lutz.Kittler@sse-erfurt.de) Received: from mail.sse-erfurt.de (145.253.64.194) by mail1.arcor-ip.de (5.5.034) id 3FB88EDE00051417 for freebsd-isdn@freebsd.org; Wed, 19 Nov 2003 08:51:29 +0100 Received: from master.sse-erfurt.de (mailhost.sse-erfurt.de [192.105.75.4]) by mail.sse-erfurt.de (Postfix) with ESMTP id 7703812C83 for ; Wed, 19 Nov 2003 08:51:28 +0100 (CET) Received: from tycho.sse-erfurt.de (kittler@tycho.sse-erfurt.de [192.105.75.11])id IAA28162 for ; Wed, 19 Nov 2003 08:51:28 +0100 From: Lutz Kittler To: freebsd-isdn@freebsd.org Date: Wed, 19 Nov 2003 08:51:27 +0100 User-Agent: KMail/1.5 References: <200311181733.hAIHXN4X096374@www.kukulies.org> <20031118223226.T17712@nihil.reifenberger.com> <20031118210148.GA98520@gilberto.physik.rwth-aachen.de> In-Reply-To: <20031118210148.GA98520@gilberto.physik.rwth-aachen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311190851.27401.Lutz.Kittler@sse-erfurt.de> Subject: Re: how dangerous would it be to switch to 5.1-current? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 07:51:32 -0000 Am Dienstag, 18. November 2003 22:01 schrieb Christoph P. Kukulies: > On Tue, Nov 18, 2003 at 10:36:39PM +0100, Michael Reifenberger wrote: > > On Tue, 18 Nov 2003, C. Kukulies wrote: > > > Date: Tue, 18 Nov 2003 18:33:23 +0100 (CET) > > > From: C. Kukulies > > > To: freebsd-isdn@freebsd.org > > > Subject: how dangerous would it be to switch to 5.1-current? > > > > > > With a gateway machine that runs 4.8 stable I'm considering to > > > switch to 5.1-current (cvsup) at the danger of being off-net > > > after the upgrade. Should I? > > > > Too dangerous. > > If you ask this question ('cause you havn't tried), you shouldn't > > upgrade. At least not to -current. Maybe RELENG_4. > > Well, I have gone through a couple of such situations in the past since > 386bsd :-) > > It's just the question whether i4b still works or works again > under -current. Under 5.0 there were problems due to timer changes > in the kernel. > > Is anybody running i4b under -current? > > -- > Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de Hi, I am running 5.1 current with AVM Fritz PCI. No problems so far. lutz From owner-freebsd-isdn@FreeBSD.ORG Wed Nov 19 00:42:09 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EE7516A4CE for ; Wed, 19 Nov 2003 00:42:09 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 534B844047 for ; Wed, 19 Nov 2003 00:41:10 -0800 (PST) (envelope-from martin@duskware.de) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng3.kundenserver.de with esmtp (Exim 3.35 #1) id 1AMNtc-0007Uk-00; Wed, 19 Nov 2003 09:41:08 +0100 Received: from [217.82.84.54] (helo=drowsy.duskware.de) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1AMNtb-0007zh-00; Wed, 19 Nov 2003 09:41:07 +0100 Received: by drowsy.duskware.de (Postfix, from userid 205) id 3EDB333ADF; Wed, 19 Nov 2003 09:41:06 +0100 (CET) Date: Wed, 19 Nov 2003 09:41:05 +0100 From: Martin Husemann To: Gary Jennejohn Message-ID: <20031119084105.GA10208@drowsy.duskware.de> References: <20031026191648.GE436@newhope.my.domain> <200311182210.hAIMA8cl001712@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200311182210.hAIMA8cl001712@peedub.jennejohn.org> User-Agent: Mutt/1.4.1i cc: freebsd-isdn@freebsd.org Subject: Re: Why is bus_set_resource() rarely used? Docs for ISA cards X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 08:42:09 -0000 On Tue, Nov 18, 2003 at 11:10:08PM +0100, Gary Jennejohn wrote: > I don't know for sure about these cards, but I suspect that the Linux > driver was used as a reference. The german USR branch actually provided documentation on the Sportster card to (at least) Hellmuth and me. Back in those days neither AVM nor Teles would give away any information about their cards, not to us and not to the Linux people. There was "common knowledge" how their cards were designed floating around all over the ISDN scene, I guess most people looked at the provided DOS drivers. And actually, those cards are pretty simple, once you figure out their register mapping and any additional reset/config tricks. Later AVM made up their mind and became more open, AFAICT Teles never reached this stage. Later, when ISA PnP cards became common, register mapping was easy to guess form the PnP info, and most drivers probably were done by trial & error. Martin From owner-freebsd-isdn@FreeBSD.ORG Wed Nov 19 01:16:38 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9ED2D16A4CE for ; Wed, 19 Nov 2003 01:16:38 -0800 (PST) Received: from peedub.jennejohn.org (p213.54.240.227.tisdip.tiscali.de [213.54.240.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35BB143F85 for ; Wed, 19 Nov 2003 01:16:37 -0800 (PST) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.12.10/8.11.6) with ESMTP id hAJ9GXRV002217; Wed, 19 Nov 2003 10:16:33 +0100 (CET) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200311190916.hAJ9GXRV002217@peedub.jennejohn.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Markus Dolze In-Reply-To: Message from Markus Dolze of "Wed, 19 Nov 2003 00:35:22 +0100." <3FBAACBA.7060603@mdolze.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Nov 2003 10:16:33 +0100 From: Gary Jennejohn cc: freebsd-isdn@freebsd.org Subject: Re: how dangerous would it be to switch to 5.1-current? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 09:16:38 -0000 Markus Dolze writes: > I have just tried to upgrade to 5.1-RELEASE (no patches yet). > > I use rbch to connect via user-land ppp (tun0). If I try to make a > connection, I get the error: > > Nov 19 00:16:23 arwen kernel: i4b-L3 T303_timeout: SETUP not > answered, cr = 73 > Nov 19 00:16:23 arwen kernel: i4b-L3 next_l3state: FSM > illegal state, state = ST_U0 - Null, event = EV_T303EXP - T303 timeout! > > And the call is disconnected. PPP then tries to redial and the > connection is established. > > Attached are hints (from device.hints), kernel and isdnd.rc config > files. I use an old non-pnp AVM Fritz card (isic-driver). > > Any help? > Does this happen _every_ time? Are you using rbch and ppp for channel bonding? If not I'd suggest using an isp interface. That's the way I do it. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de From owner-freebsd-isdn@FreeBSD.ORG Wed Nov 19 03:10:57 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A950116A4CE for ; Wed, 19 Nov 2003 03:10:57 -0800 (PST) Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7812F43FAF for ; Wed, 19 Nov 2003 03:10:54 -0800 (PST) (envelope-from Alexander@Leidinger.net) Received: from fwd01.aul.t-online.de by mailout06.sul.t-online.com with smtp id 1AMQEX-00044W-06; Wed, 19 Nov 2003 12:10:53 +0100 Received: from Andro-Beta.Leidinger.net (ZejaI-ZOYeAOhETn1SpMynQustMVwqQ6LlBuBe27UrQCXjfj9vXf8e@[217.83.25.153]) by fmrl01.sul.t-online.com with esmtp id 1AMQER-0A4U4G0; Wed, 19 Nov 2003 12:10:47 +0100 Received: from Magelan.Leidinger.net (Magellan [192.168.1.1]) hAJBAk94095567; Wed, 19 Nov 2003 12:10:46 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Magelan.Leidinger.net (netchild@localhost [127.0.0.1]) hAJBAkUr006869; Wed, 19 Nov 2003 12:10:46 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Wed, 19 Nov 2003 12:10:45 +0100 From: Alexander Leidinger To: Gary Jennejohn Message-Id: <20031119121045.7ddbf125.Alexander@Leidinger.net> In-Reply-To: <200311182210.hAIMA8cl001712@peedub.jennejohn.org> References: <20031026191648.GE436@newhope.my.domain> <200311182210.hAIMA8cl001712@peedub.jennejohn.org> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Seen: false X-ID: ZejaI-ZOYeAOhETn1SpMynQustMVwqQ6LlBuBe27UrQCXjfj9vXf8e@t-dialin.net cc: freebsd-isdn@freebsd.org Subject: Re: Why is bus_set_resource() rarely used? Docs for ISA cards X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 11:10:57 -0000 On Tue, 18 Nov 2003 23:10:08 +0100 Gary Jennejohn wrote: > > I'm trying to learn how the i4b ISA drivers are > > programmed by reading the "Arch Handbook" and looking > > at i4b/capi/iavc/iavc_isa.c on my FreeBSD 4-stable PC > > and wonder why doesn't iavc (and most other ISDN cards) > > use bus_set_resource()? I only see bus_alloc_resource() > > being called for SYS_RES_IOPORT and _IRQ in iavc_isa.c > > > > Most of these drivers were written before the entire bus support was > added to FBSD. Since they work as they are, why change them? http://www.freebsd.org/projects/busdma/index.html Bye, Alexander. -- Intel: where Quality is job number 0.9998782345! http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 From owner-freebsd-isdn@FreeBSD.ORG Wed Nov 19 05:06:36 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C210616A4CE for ; Wed, 19 Nov 2003 05:06:36 -0800 (PST) Received: from peedub.jennejohn.org (p213.54.240.227.tisdip.tiscali.de [213.54.240.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5355443F3F for ; Wed, 19 Nov 2003 05:06:35 -0800 (PST) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.12.10/8.11.6) with ESMTP id hAJD6VRV013688; Wed, 19 Nov 2003 14:06:32 +0100 (CET) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200311191306.hAJD6VRV013688@peedub.jennejohn.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Alexander Leidinger In-Reply-To: Message from Alexander Leidinger <20031119121045.7ddbf125.Alexander@Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Nov 2003 14:06:31 +0100 From: Gary Jennejohn cc: freebsd-isdn@freebsd.org Subject: Re: Why is bus_set_resource() rarely used? Docs for ISA cards X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 13:06:36 -0000 Alexander Leidinger writes: > On Tue, 18 Nov 2003 23:10:08 +0100 > Gary Jennejohn wrote: > > > > I'm trying to learn how the i4b ISA drivers are > > > programmed by reading the "Arch Handbook" and looking > > > at i4b/capi/iavc/iavc_isa.c on my FreeBSD 4-stable PC > > > and wonder why doesn't iavc (and most other ISDN cards) > > > use bus_set_resource()? I only see bus_alloc_resource() > > > being called for SYS_RES_IOPORT and _IRQ in iavc_isa.c > > > > > > > Most of these drivers were written before the entire bus support was > > added to FBSD. Since they work as they are, why change them? > > http://www.freebsd.org/projects/busdma/index.html > No i4b stuff listed on that page ;-) I suppose it would be a worthy effort in any case, but testing could be difficult. I personally don't even own a motherboard with ISA slots and gave away all my ISA-based ISDN cards long ago. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de From owner-freebsd-isdn@FreeBSD.ORG Wed Nov 19 05:24:07 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAB2416A4CE for ; Wed, 19 Nov 2003 05:24:07 -0800 (PST) Received: from mailout11.sul.t-online.com (mailout11.sul.t-online.com [194.25.134.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C24F43F93 for ; Wed, 19 Nov 2003 05:24:06 -0800 (PST) (envelope-from Alexander@Leidinger.net) Received: from fwd04.aul.t-online.de by mailout11.sul.t-online.com with smtp id 1AMSJP-00044u-01; Wed, 19 Nov 2003 14:24:03 +0100 Received: from Andro-Beta.Leidinger.net (rxTOl6ZaoeJ7FC8vBDfOP06HaOEUIbwEHpJBmCUELIIpXRpDob6x0V@[217.83.25.153]) by fmrl04.sul.t-online.com with esmtp id 1AMSJH-1CtLqi0; Wed, 19 Nov 2003 14:23:55 +0100 Received: from Magelan.Leidinger.net (Magellan [192.168.1.1]) hAJDNq94014548; Wed, 19 Nov 2003 14:23:52 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Magelan.Leidinger.net (netchild@localhost [127.0.0.1]) hAJDNpUr023982; Wed, 19 Nov 2003 14:23:51 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Wed, 19 Nov 2003 14:23:51 +0100 From: Alexander Leidinger To: Gary Jennejohn Message-Id: <20031119142351.2a339841.Alexander@Leidinger.net> In-Reply-To: <200311191306.hAJD6VRV013688@peedub.jennejohn.org> References: <20031119121045.7ddbf125.Alexander@Leidinger.net> <200311191306.hAJD6VRV013688@peedub.jennejohn.org> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Seen: false X-ID: rxTOl6ZaoeJ7FC8vBDfOP06HaOEUIbwEHpJBmCUELIIpXRpDob6x0V@t-dialin.net cc: freebsd-isdn@freebsd.org Subject: Re: Why is bus_set_resource() rarely used? Docs for ISA cards X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 13:24:08 -0000 On Wed, 19 Nov 2003 14:06:31 +0100 Gary Jennejohn wrote: > > http://www.freebsd.org/projects/busdma/index.html > > > > No i4b stuff listed on that page ;-) I know. But the goals of this project describe why it would be beneficial. > I suppose it would be a worthy effort in any case, but testing could be > difficult. I personally don't even own a motherboard with ISA slots and > gave away all my ISA-based ISDN cards long ago. ---snip--- isic0 at port 0xb00-0xb1f,0x300-0x31f,0x1300-0x131f,0xee0-0xeff,0x6e0-0x6ff,0x16e0-0x16ff,0x1b00-0x1b1f irq 3 flags 0x4 on isa0 isic0: passive stack unit 0 isic0: AVM A1 or Fritz!Card Classic ---snip--- I don't use it to dial out anymore (but I still have it configured, so it would be possible just by executing a little command), but it's always nice to see the number (or name) of the caller pop up on my desktop. Feel free to send patches you want to have tested. :-) Bye, Alexander. -- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 From owner-freebsd-isdn@FreeBSD.ORG Wed Nov 19 10:04:58 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E438116A4CE for ; Wed, 19 Nov 2003 10:04:58 -0800 (PST) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id C73B043F85 for ; Wed, 19 Nov 2003 10:04:56 -0800 (PST) (envelope-from un1du2el@gmx.net) Received: (qmail 28219 invoked by uid 0); 19 Nov 2003 18:04:55 -0000 Received: from 212.144.190.60 by www61.gmx.net with HTTP; Wed, 19 Nov 2003 19:04:55 +0100 (MET) Date: Wed, 19 Nov 2003 19:04:55 +0100 (MET) From: "Markus D." To: Gary Jennejohn MIME-Version: 1.0 References: <200311190916.hAJ9GXRV002217@peedub.jennejohn.org> X-Priority: 3 (Normal) X-Authenticated: #931807 Message-ID: <24686.1069265095@www61.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit cc: freebsd-isdn@freebsd.org Subject: Re: how dangerous would it be to switch to 5.1-current? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 18:04:59 -0000 > > Markus Dolze writes: > > I have just tried to upgrade to 5.1-RELEASE (no patches yet). > > > > I use rbch to connect via user-land ppp (tun0). If I try to make a > > connection, I get the error: > > > > Nov 19 00:16:23 arwen kernel: i4b-L3 T303_timeout: SETUP not > > answered, cr = 73 > > Nov 19 00:16:23 arwen kernel: i4b-L3 next_l3state: FSM > > illegal state, state = ST_U0 - Null, event = EV_T303EXP - T303 timeout! > > > > And the call is disconnected. PPP then tries to redial and the > > connection is established. > > > > Attached are hints (from device.hints), kernel and isdnd.rc config > > files. I use an old non-pnp AVM Fritz card (isic-driver). > > > > Any help? > > > > Does this happen _every_ time? > > Are you using rbch and ppp for channel bonding? If not I'd suggest > using an isp interface. That's the way I do it. > > --- > Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de > As far as I can tell, yes! I've used isppp until a few days and switched to rbch and ppp because ppp can filter which packets keep the connection alive. With this NetBIOS and p2p crap the idle timer of isdnd does not run out. And the connection is not closed. With ppp I can filter these packets. Markus From owner-freebsd-isdn@FreeBSD.ORG Wed Nov 19 14:29:41 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00A3E16A4CE for ; Wed, 19 Nov 2003 14:29:41 -0800 (PST) Received: from mail-in-03.arcor-online.net (mail-in-03.arcor-online.net [151.189.21.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id C40DB43F85 for ; Wed, 19 Nov 2003 14:29:39 -0800 (PST) (envelope-from un1du2el@gmx.net) Received: from gmx.net (dialin-212-144-062-229.arcor-ip.net [212.144.62.229]) by mail-in-03.arcor-online.net (Postfix) with ESMTP id A34D21C8A98; Wed, 19 Nov 2003 23:29:37 +0100 (CET) Date: Wed, 19 Nov 2003 23:29:52 +0100 From: "un1du2el" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: de-de, en-us, en MIME-Version: 1.0 To: Gary Jennejohn References: <200311190916.hAJ9GXRV002217@peedub.jennejohn.org> In-Reply-To: <200311190916.hAJ9GXRV002217@peedub.jennejohn.org> Content-Type: multipart/mixed; boundary="------------070907010909060109070302" Message-Id: <20031119222937.A34D21C8A98@mail-in-03.arcor-online.net> cc: freebsd-isdn@freebsd.org Subject: Re: how dangerous would it be to switch to 5.1-current? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2003 22:29:41 -0000 This is a multi-part message in MIME format. --------------070907010909060109070302 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I've just tried to use an isppp setup with 5.1-R and the same thing happens. In fact it fails on first attempt, dials a second time, the connection is closed from the other side and the nothing ever happens again (no dialouts etc.). Attached is a redirected log output from isdnd. I use this card: isic0 at port 0x1b00-0x1b1f,0x16e0-0x16ff,0x6e0-0x6ff,0xee0-0xeff, 0x1300-0x131f,0x300-0x31f,0xb00-0xb1f irq 5 flags 0x4 on isa0 isic0: passive stack unit 0 isic0: AVM A1 or Fritz!Card Classic The same setup works perfectly with 4.9-R. Markus D. Gary Jennejohn wrote: > *This message was transferred with a trial version of CommuniGate(tm) Pro* > > Markus Dolze writes: > >>I have just tried to upgrade to 5.1-RELEASE (no patches yet). >> >>I use rbch to connect via user-land ppp (tun0). If I try to make a >>connection, I get the error: >> >>Nov 19 00:16:23 arwen kernel: i4b-L3 T303_timeout: SETUP not >>answered, cr = 73 >>Nov 19 00:16:23 arwen kernel: i4b-L3 next_l3state: FSM >>illegal state, state = ST_U0 - Null, event = EV_T303EXP - T303 timeout! >> >>And the call is disconnected. PPP then tries to redial and the >>connection is established. >> >>Attached are hints (from device.hints), kernel and isdnd.rc config >>files. I use an old non-pnp AVM Fritz card (isic-driver). >> >>Any help? >> > > > Does this happen _every_ time? > > Are you using rbch and ppp for channel bonding? If not I'd suggest > using an isp interface. That's the way I do it. > > --- > Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de > > _______________________________________________ > freebsd-isdn@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-isdn > To unsubscribe, send any mail to "freebsd-isdn-unsubscribe@freebsd.org" > > --------------070907010909060109070302 Content-Type: text/plain; name="isdnd" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="isdnd" 19.11.2003 23:10:08 DMN init_controller_state: controller 0 is AVM A1 or Fritz!Card 19.11.2003 23:10:08 DMN i4b isdn daemon started (pid = 203) 19.11.2003 23:10:10 DBG msg_dialout: dial req from isp, unit 0 19.11.2003 23:10:10 DBG setup_dialout: entry I4ARCOR ok! 19.11.2003 23:10:10 DBG find_by_device_for_dialout: found entry 0! 19.11.2003 23:10:10 DBG FSM event [msg-dialout]: [idle => dialing] 19.11.2003 23:10:10 DBG F_DIAL: local dial out request 19.11.2003 23:10:10 DBG select_first_dialno: only one no, no = 0192071 19.11.2003 23:10:10 CHD 00001 I4ARCOR rate 0 sec/unit (conf) 19.11.2003 23:10:10 DBG sendm_connect_req: ctrl = 0, chan = -1 19.11.2003 23:10:10 DBG decr_free_channels: ctrl 0, now 1 chan free 19.11.2003 23:10:10 CHD 00001 I4ARCOR dialing out from 8868907 to 0192071 19.11.2003 23:10:10 DBG msg_teiasg_ind: unit 0, tei = 70 19.11.2003 23:10:10 DBG msg_l12stat_ind: unit 0, layer 2, state 1 19.11.2003 23:10:11 CHD 00001 I4ARCOR outgoing call disconnected (remote) 19.11.2003 23:10:11 CHD 00001 I4ARCOR cause 43: Access information discarded (Q.850) 19.11.2003 23:10:11 ERR set_channel_busy: controller [0] invalid channel [-1]! 19.11.2003 23:10:11 DBG incr_free_channels: ctrl 0, now 2 chan free 19.11.2003 23:10:11 DBG F_DFL: dial fail, dial retry 19.11.2003 23:10:11 DBG select_next_dialno: only one no, no = 0192071 19.11.2003 23:10:11 DBG FSM (SUSE) event [msg-disc-ind]: [dialing => waitdialretry] 19.11.2003 23:10:16 DBG handle_reserved: entry I4ARCOR, dial retry request! 19.11.2003 23:10:16 DBG setup_dialout: entry I4ARCOR ok! 19.11.2003 23:10:16 CHD 00002 I4ARCOR rate 0 sec/unit (conf) 19.11.2003 23:10:16 DBG sendm_connect_req: ctrl = 0, chan = -1 19.11.2003 23:10:16 DBG decr_free_channels: ctrl 0, now 1 chan free 19.11.2003 23:10:16 CHD 00002 I4ARCOR dialing out from 8868907 to 0192071 19.11.2003 23:10:16 DBG set_channel_busy: controller [0] channel B1 set to BUSY! 19.11.2003 23:10:16 CHD 00002 I4ARCOR outgoing call proceeding (ctl 0, ch 0) 19.11.2003 23:10:17 DBG set_channel_busy: controller [0] channel B1 already busy! 19.11.2003 23:10:17 CHD 00002 I4ARCOR outgoing call active (ctl 0, ch 0, isp0) 19.11.2003 23:10:17 DBG FSM event [msg-con-act-ind]: [dialretry => connected] 19.11.2003 23:10:17 DBG F_DOK: dial out ok 19.11.2003 23:10:17 DBG select_this_dialno: index = 0, no = 0192071 19.11.2003 23:10:17 CHD 00002 I4ARCOR outgoing call disconnected (remote) 19.11.2003 23:10:17 CHD 00002 I4ARCOR cause 16: Normal call clearing (Q.850) 19.11.2003 23:10:17 CHD 00002 I4ARCOR charging: 0 units, 0 seconds 19.11.2003 23:10:17 CHD 00002 I4ARCOR accounting: in 133, out 103 (in 0, out 0) 19.11.2003 23:10:17 DBG set_channel_idle: controller [0] channel B1 set to IDLE! 19.11.2003 23:10:17 DBG incr_free_channels: ctrl 0, now 2 chan free 19.11.2003 23:10:17 DBG FSM event [msg-disc-ind]: [connected => idle] 19.11.2003 23:10:17 DBG F_IDIS: disconnect indication 19.11.2003 23:11:00 DMN daemon terminating, exitval = 0 --------------070907010909060109070302-- From owner-freebsd-isdn@FreeBSD.ORG Wed Nov 19 16:02:06 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 298AE16A4CE for ; Wed, 19 Nov 2003 16:02:06 -0800 (PST) Received: from peedub.jennejohn.org (p213.54.248.40.tisdip.tiscali.de [213.54.248.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD97E43FBD for ; Wed, 19 Nov 2003 16:02:04 -0800 (PST) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.12.10/8.11.6) with ESMTP id hAK0204n001670; Thu, 20 Nov 2003 01:02:00 +0100 (CET) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200311200002.hAK0204n001670@peedub.jennejohn.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: "un1du2el" In-Reply-To: Message from "un1du2el" <20031119222937.A34D21C8A98@mail-in-03.arcor-online.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 20 Nov 2003 01:02:00 +0100 From: Gary Jennejohn cc: freebsd-isdn@freebsd.org cc: garyj@jennejohn.org Subject: Re: how dangerous would it be to switch to 5.1-current? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Nov 2003 00:02:06 -0000 "un1du2el" writes: > I've just tried to use an isppp setup with 5.1-R and the same thing > happens. In fact it fails on first attempt, dials a second time, the > connection is closed from the other side and the nothing ever happens > again (no dialouts etc.). > > Attached is a redirected log output from isdnd. > > I use this card: > isic0 at port 0x1b00-0x1b1f,0x16e0-0x16ff,0x6e0-0x6ff,0xee0-0xeff, > 0x1300-0x131f,0x300-0x31f,0xb00-0xb1f irq 5 flags 0x4 on isa0 > isic0: passive stack unit 0 > isic0: AVM A1 or Fritz!Card Classic > > The same setup works perfectly with 4.9-R. > If you do spppcontrol does it show the correct values for your access information (password, user-name, etc.)? I just used my ifpi2 under -current yesterday with no problems whatsoever. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de From owner-freebsd-isdn@FreeBSD.ORG Wed Nov 19 23:52:33 2003 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BB5316A4CE for ; Wed, 19 Nov 2003 23:52:33 -0800 (PST) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id B780143FA3 for ; Wed, 19 Nov 2003 23:52:32 -0800 (PST) (envelope-from un1du2el@gmx.net) Received: from gmx.net (dialin-145-254-185-191.arcor-ip.net [145.254.185.191]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id 5F5691C8847; Thu, 20 Nov 2003 08:52:30 +0100 (CET) Date: Thu, 20 Nov 2003 08:52:43 +0100 From: "un1du2el" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: de-de, en-us, en MIME-Version: 1.0 To: Gary Jennejohn References: <200311200002.hAK0204n001670@peedub.jennejohn.org> In-Reply-To: <200311200002.hAK0204n001670@peedub.jennejohn.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <20031120075230.5F5691C8847@mail-in-01.arcor-online.net> cc: freebsd-isdn@freebsd.org Subject: SOLVED! Re: how dangerous would it be to switch to 5.1-current? X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Nov 2003 07:52:33 -0000 It's working! But I don't know exactly why... I did the following: 1. Change setup to isppp 2. Test => failed 3. Put in an AVM Fritz PCI v2 4. Rebuild kernel with new device ifpi2, reboot 5. Test => failed 6. Removed AVM Fritz PCI v2 7. Rebuild kernel with old device isic, reboot 8. Change BIOS setting "PNP OS = no" 9. Change BIOS setting "Resource configuration = auto" 10. Change setup to tun0 11. Test => passed So what I actually did was to change two BIOS settings (which I changed to "PNP=YES", "configuration=manual, reserve irq5 for isa" after the first test yesterday failed) and recompile the kernel one more time. Markus D. Gary Jennejohn wrote: > *This message was transferred with a trial version of CommuniGate(tm) Pro* > > "un1du2el" writes: > >>I've just tried to use an isppp setup with 5.1-R and the same thing >>happens. In fact it fails on first attempt, dials a second time, the >>connection is closed from the other side and the nothing ever happens >>again (no dialouts etc.). >> >>Attached is a redirected log output from isdnd. >> >>I use this card: >>isic0 at port 0x1b00-0x1b1f,0x16e0-0x16ff,0x6e0-0x6ff,0xee0-0xeff, >>0x1300-0x131f,0x300-0x31f,0xb00-0xb1f irq 5 flags 0x4 on isa0 >>isic0: passive stack unit 0 >>isic0: AVM A1 or Fritz!Card Classic >> >>The same setup works perfectly with 4.9-R. >> > > > If you do spppcontrol does it show the correct values for your > access information (password, user-name, etc.)? I just used my > ifpi2 under -current yesterday with no problems whatsoever. > > --- > Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de >