From owner-freebsd-isdn Sun Jun 18 1:22:57 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 8B6D737B852 for ; Sun, 18 Jun 2000 01:22:52 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-250-160.netcologne.de [195.14.250.160]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id KAA15531; Sun, 18 Jun 2000 10:22:49 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.1/8.10.1) with ESMTP id e5I8Lsq00421; Sun, 18 Jun 2000 10:21:54 +0200 (CEST) Date: Sun, 18 Jun 2000 10:21:54 +0200 (CEST) From: Paul Herman To: Gerhard Sittig Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: <20000617155609.X9883@speedy.gsinet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 17 Jun 2000, Gerhard Sittig wrote: > The Linux driver (HiSax) had a similar problem in a former version > -- it hung at load time when the Elsa card was plugged into an > active bus. Do I remember right that you saw the very same > symptom? Maybe it's helpful to browse the Changelog of the Linux > driver from, say 2.2.10 up to now (2.2.16). Yes, that does indeed sound like the same problem I'm having. Thanks Gerhard, for the tip. I'm looking at the current i4linux code and the main difference I see is that the their loop bails out after five tries. I tried that in i4b, but the interrupts still keep coming (even after the function exits.) I must be missing something. Is anyone familiar with this problem (i.e. ELSA PCI hanging on an active bus)? I really have _zero_ clue about ISDN hardware, and I could use a little direction. I will continue to search through CVS trees and mailing lists, but due to my lack of expertise in this area, I can very easily overlook something. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 18 2:46:39 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F3E.dip.t-dialin.net [62.155.143.62]) by hub.freebsd.org (Postfix) with ESMTP id 2914837B957 for ; Sun, 18 Jun 2000 02:46:37 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id LAA01642; Sun, 18 Jun 2000 11:40:52 +0200 (CEST) Message-Id: <200006180940.LAA01642@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: Paul Herman Cc: Gerhard Sittig , freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 18 Jun 2000 10:21:54 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Jun 2000 11:40:52 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Paul Herman writes: >On Sat, 17 Jun 2000, Gerhard Sittig wrote: > >> The Linux driver (HiSax) had a similar problem in a former version >> -- it hung at load time when the Elsa card was plugged into an >> active bus. Do I remember right that you saw the very same >> symptom? Maybe it's helpful to browse the Changelog of the Linux >> driver from, say 2.2.10 up to now (2.2.16). > >Yes, that does indeed sound like the same problem I'm having. > >Thanks Gerhard, for the tip. I'm looking at the current i4linux code >and the main difference I see is that the their loop bails out after >five tries. I tried that in i4b, but the interrupts still keep coming >(even after the function exits.) I must be missing something. > >Is anyone familiar with this problem (i.e. ELSA PCI hanging on an >active bus)? I really have _zero_ clue about ISDN hardware, and I >could use a little direction. I will continue to search through CVS >trees and mailing lists, but due to my lack of expertise in this area, >I can very easily overlook something. > It looks like the card has a problem in the early stages of startup when the cable is plugged in. It's generating interrupts which don't seem to be getting cleared in the interrupt handler. I'm not familiar with this card, so I can't really help. Actually, the Linux driver does quite a bit more. It reads the interrupt register on the card (in FreeBSD parlance iobase1 + 0x4c) and checks whether the card actually interrupted. This is missing from i4b. Unfortunately, iobase1 is never saved anywhere that I can see, so it would be difficult to do the same thing, but IMO necessary. And there's also the limitation on how often the code goes through the loop in Linux. The driver should be modified so that the interrupt routine is actually in i4b_elsa_qs1p.c. This routine could then call isic_pci_intr_sc in i4b_isic_pci.c. Or, even better, clone the code from i4b_isic_pci.c. That would be a much cleaner solution. That's the way I did it in the Fritz!PCI driver. And save iobase1 so that it can be reused in the interrupt routine. --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 18 5:28: 1 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id CF18037B92E for ; Sun, 18 Jun 2000 05:27:54 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA21647; Sun, 18 Jun 2000 13:25:28 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA66509; Sun, 18 Jun 2000 13:25:14 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200006181225.NAA66509@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Joerg Bornschein Cc: freebsd-isdn@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: OpenBSD 2.7 and i4b In-Reply-To: Message from Joerg Bornschein of "Sat, 17 Jun 2000 13:36:24 +0200." <20000617133624.A718@disorder.ruhr.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Jun 2000 13:25:14 +0100 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org BAD signature made 2000-06-17 11:36 GMT by key: 1024 bits, Key ID FF42DB59, Created 2000-01-03 "Joerg Bornschein " "Joerg Bornschein " > > --Qxx1br4bt0+wmkIi > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: quoted-printable > > =20 > Hi, > =20 > Those willing to setup a OpenBSD router may find these patches > useful: http://www.zilium.de/joerg > =20 > Everything seems stable -- im running a 64/128kbit line for about 2 > weeks without problems. > =20 > I did not do any serious development -- just made sure evrything > applies cleanly. > =20 > =20 > thanks for listening > =20 > =20 > Joerg > =20 > > --Qxx1br4bt0+wmkIi > Content-Type: application/pgp-signature > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.1 (FreeBSD) > Comment: For info see http://www.gnupg.org > > iD8DBQE5S2K4RIjNbP9C21kRAfCVAKCZ5X3S8jkYisHq+LkLngQGC6avKQCfWKxh > fOMBDJ8TzMOkPoPd9U5PlDI= > =cFVi > -----END PGP SIGNATURE----- > > --Qxx1br4bt0+wmkIi-- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 18 11:39: 1 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 71BF737B619 for ; Sun, 18 Jun 2000 11:38:58 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-226-44.netcologne.de [195.14.226.44]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id UAA00371; Sun, 18 Jun 2000 20:38:54 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.1/8.10.1) with ESMTP id e5IIcXM00559; Sun, 18 Jun 2000 20:38:33 +0200 (CEST) Date: Sun, 18 Jun 2000 20:38:33 +0200 (CEST) From: Paul Herman To: Gary Jennejohn Cc: Gerhard Sittig , freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: <200006180940.LAA01642@peedub.muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 18 Jun 2000, Gary Jennejohn wrote: > Actually, the Linux driver does quite a bit more. It reads the > interrupt register on the card (in FreeBSD parlance iobase1 + 0x4c) > and checks whether the card actually interrupted. This is missing > from i4b. I did see this, but I didn't think it would have changed things, because the i4b interrupt function keeps getting called over and over and all it does is read registers. I would think some sort of solution would somehow intail telling the card politely "shut up already" i.e. some sort of write. Mind you I'm speaking from no experience whatsoever, so reality is most likely a very different story. I will hack around tomorrow and move iobase1 into the sc struct, just to test to check the card interrupt and see if that gets me anywhere. If that does the trick, then your idea with moving the interrupt routine to i4b_elsa_qs1p.c will definately be the way to go. Thanks for the suggestion Gary. As always, you da man! :) Regards, -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 18 13:17:39 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id 78D6437B574 for ; Sun, 18 Jun 2000 13:17:36 -0700 (PDT) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (IDENT:root@rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id WAA08149; Sun, 18 Jun 2000 22:17:55 +0200 Received: (from martin@localhost) by rumolt.teuto.de (8.10.2/8.10.1) id e5IK1JW00447; Sun, 18 Jun 2000 22:01:19 +0200 (MEST) From: Martin Husemann Message-Id: <200006182001.e5IK1JW00447@rumolt.teuto.de> Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: <200006180940.LAA01642@peedub.muc.de> from Gary Jennejohn at "Jun 18, 2000 11:40:52 am" To: garyj@muc.de (Gary Jennejohn) Date: Sun, 18 Jun 2000 22:01:19 +0200 (MEST) Cc: pherman@frenchfries.net (Paul Herman), Gerhard.Sittig@gmx.net (Gerhard Sittig), freebsd-isdn@FreeBSD.ORG Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > And save iobase1 so that it can be reused in the interrupt routine. If you'd take votes on it: redo all the autoconfiguration stuff for FreeBSD ;-) Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 18 13:21:53 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F5F.dip.t-dialin.net [62.155.143.95]) by hub.freebsd.org (Postfix) with ESMTP id CA3A537B574 for ; Sun, 18 Jun 2000 13:21:42 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id WAA02488; Sun, 18 Jun 2000 22:15:55 +0200 (CEST) Message-Id: <200006182015.WAA02488@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: Martin Husemann Cc: pherman@frenchfries.net (Paul Herman), Gerhard.Sittig@gmx.net (Gerhard Sittig), freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 18 Jun 2000 22:17:43 +0200." <200006182001.e5IK1JW00447@rumolt.teuto.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Jun 2000 22:15:55 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Martin Husemann writes: >> And save iobase1 so that it can be reused in the interrupt routine. > >If you'd take votes on it: redo all the autoconfiguration stuff for FreeBSD ;- >) > But it's all new in the developer relesae. That doesn't help him much since he's trying to use 0.90-beta. --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 18 14:41:16 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from SouthFayette.Org (pD4B898D5.dip.t-dialin.net [212.184.152.213]) by hub.freebsd.org (Postfix) with ESMTP id ECD4C37B715 for ; Sun, 18 Jun 2000 14:41:04 -0700 (PDT) (envelope-from janek@SouthFayette.Org) Received: (from janek@localhost) by SouthFayette.Org (8.10.2/8.10.2) id e5ILec809685; Sun, 18 Jun 2000 23:40:38 +0200 (CEST) Date: Sun, 18 Jun 2000 23:40:38 +0200 From: Janek Richter To: Joerg Bornschein Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: OpenBSD 2.7 and i4b Message-ID: <20000618234038.A9663@solariz.globe> References: <20000617133624.A718@disorder.ruhr.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000617133624.A718@disorder.ruhr.de>; from joerg@zilium.de on Sat, Jun 17, 2000 at 01:36:24PM +0200 X-Operating-System: FreeBSD/4.0-STABLE (i386) X-Crypto: GnuPG/1.0.1 http://www.gnupg.org X-GPG-Fingerprint: FD15 D4E8 BB17 86F8 0BB4 EB3D B72F 0CD5 EA65 25D5 X-Uptime: 11:40PM up 9:17, 5 users, load averages: 0.00, 0.00, 0.00 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Joerg Bornschein (joerg@zilium.de) wrote: > > Hi, > > Those willing to setup a OpenBSD router may find these patches > useful: http://www.zilium.de/joerg > > Everything seems stable -- im running a 64/128kbit line for about 2 > weeks without problems. > > I did not do any serious development -- just made sure evrything > applies cleanly. > > > thanks for listening > > > Joerg > is it possible to run a Fritz!PCI Card with this patches... etc? Regards, Janek Richter -- )\_)\ Janek Richter - 0xEA6525D5(GnuPG) (o,o) __ \~/ freebsd the power to serve.. http://www.freebsd.org -->====\/ http://ukug.uk.freebsd.org/~janek/ ~~ d d To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 18 15:11: 4 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F06.dip.t-dialin.net [62.155.143.6]) by hub.freebsd.org (Postfix) with ESMTP id 416ED37B92B for ; Sun, 18 Jun 2000 15:10:58 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id XAA02652; Sun, 18 Jun 2000 23:36:00 +0200 (CEST) Message-Id: <200006182136.XAA02652@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: Paul Herman Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 18 Jun 2000 20:38:33 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Jun 2000 23:36:00 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Paul Herman writes: >On Sun, 18 Jun 2000, Gary Jennejohn wrote: > >> Actually, the Linux driver does quite a bit more. It reads the >> interrupt register on the card (in FreeBSD parlance iobase1 + 0x4c) >> and checks whether the card actually interrupted. This is missing >> from i4b. > >I did see this, but I didn't think it would have changed things, >because the i4b interrupt function keeps getting called over and over >and all it does is read registers. I would think some sort of >solution would somehow intail telling the card politely "shut up >already" i.e. some sort of write. Mind you I'm speaking from no >experience whatsoever, so reality is most likely a very different >story. > >I will hack around tomorrow and move iobase1 into the sc struct, just >to test to check the card interrupt and see if that gets me anywhere. >If that does the trick, then your idea with moving the interrupt >routine to i4b_elsa_qs1p.c will definately be the way to go. > >Thanks for the suggestion Gary. As always, you da man! :) > There's is a possibility of setting a clrirq (pointer to a) routine in the attach routine. This would require adding some code to test whether this pointer is set in isic_intr_sc and then calling it to tell the card to shutup already :) Unfortunately, I don't know how to do that for your card :( There's actually one card which uses the clrirq thingey. Just grep around in the source and you'll see how it's used. --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Jun 18 15:22:48 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F0E.dip.t-dialin.net [62.155.143.14]) by hub.freebsd.org (Postfix) with ESMTP id BAF7637BA83 for ; Sun, 18 Jun 2000 15:22:31 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id AAA02943; Mon, 19 Jun 2000 00:14:44 +0200 (CEST) Message-Id: <200006182214.AAA02943@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: Janek Richter Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: OpenBSD 2.7 and i4b Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 18 Jun 2000 23:40:38 +0200." <20000618234038.A9663@solariz.globe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Jun 2000 00:14:44 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Janek Richter writes: >Joerg Bornschein (joerg@zilium.de) wrote: >> >> Hi, >> >> Those willing to setup a OpenBSD router may find these patches >> useful: http://www.zilium.de/joerg >> >> Everything seems stable -- im running a 64/128kbit line for about 2 >> weeks without problems. >> >> I did not do any serious development -- just made sure evrything >> applies cleanly. >> > >is it possible to run a Fritz!PCI Card with this patches... etc? > Joerg told me in private mail that there isn't any PCI support in the patch. So, no. --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jun 19 3: 3: 7 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from web4903.mail.yahoo.com (web4903.mail.yahoo.com [216.115.106.28]) by hub.freebsd.org (Postfix) with SMTP id DD4C437BCBA for ; Mon, 19 Jun 2000 03:03:02 -0700 (PDT) (envelope-from james_eth0@yahoo.co.uk) Message-ID: <20000619100301.11207.qmail@web4903.mail.yahoo.com> Received: from [193.237.210.181] by web4903.mail.yahoo.com; Mon, 19 Jun 2000 11:03:01 BST Date: Mon, 19 Jun 2000 11:03:01 +0100 (BST) From: =?iso-8859-1?q?James=20Jeffrey?= Reply-To: james@eth0.co.uk Subject: Multilink To: freebsd-isdn@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I have searched the archives and I cant find any up to date information. I have an Elsa Microlink PCI and FreeBSD 4.0. Can I use both channels for my internet connection somehow? James. ____________________________________________________________ Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jun 19 9: 1: 4 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F58.dip.t-dialin.net [62.155.143.88]) by hub.freebsd.org (Postfix) with ESMTP id 050AC37B82D for ; Mon, 19 Jun 2000 09:01:01 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id RAA05452; Mon, 19 Jun 2000 17:55:24 +0200 (CEST) Message-Id: <200006191555.RAA05452@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: james@eth0.co.uk Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Multilink Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 19 Jun 2000 11:03:01 BST." <20000619100301.11207.qmail@web4903.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Jun 2000 17:55:24 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org =?iso-8859-1?q?James=20Jeffrey?= writes: >Hi. > >I have searched the archives and I cant find any >up to date information. > >I have an Elsa Microlink PCI and FreeBSD 4.0. >Can I use both channels for my internet connection >somehow? > Yes, with /usr/sbin/ppp. Read the man page and look at the examples in /usr/share/examples/ppp/. --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jun 19 12:19: 4 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 5FB5537B730 for ; Mon, 19 Jun 2000 12:18:57 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 17804 invoked by uid 0); 19 Jun 2000 19:18:55 -0000 Received: from p3ee0b323.dip.t-dialin.net (HELO speedy.gsinet) (62.224.179.35) by mail.gmx.net with SMTP; 19 Jun 2000 19:18:55 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id UAA10988 for freebsd-isdn@freebsd.org; Mon, 19 Jun 2000 20:31:12 +0200 Date: Mon, 19 Jun 2000 20:31:12 +0200 From: Gerhard Sittig To: freebsd-isdn@freebsd.org Subject: Re: Multilink Message-ID: <20000619203111.G9883@speedy.gsinet> Mail-Followup-To: freebsd-isdn@freebsd.org References: <20000619100301.11207.qmail@web4903.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000619100301.11207.qmail@web4903.mail.yahoo.com>; from james_eth0@yahoo.co.uk on Mon, Jun 19, 2000 at 11:03:01AM +0100 Organization: System Defenestrators Inc. Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jun 19, 2000 at 11:03 +0100, James Jeffrey wrote: > > I have searched the archives and I cant find any > up to date information. > > I have an Elsa Microlink PCI and FreeBSD 4.0. > Can I use both channels for my internet connection > somehow? Have you tried reading "man 8 ppp"? Does searching for "mrru" give hints? What about /usr/share/examples? Sometimes the solution is already on your harddisk. :) virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Jun 20 3:20:30 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from gate.consol.de (gate.consol.de [194.221.87.10]) by hub.freebsd.org (Postfix) with ESMTP id 92C9F37BE40 for ; Tue, 20 Jun 2000 03:20:24 -0700 (PDT) (envelope-from Thorsten.Greiner@consol.de) X-Envelope-Sender-Is: Thorsten.Greiner@consol.de (at relayer gate.consol.de) Received: from msgsrv.bb.consol.de (msgsrv.bb.consol.de [10.250.0.100]) by gate.consol.de (8.9.3/8.9.3) with ESMTP id MAA30357 for ; Tue, 20 Jun 2000 12:20:21 +0200 (CEST) (envelope-from Thorsten.Greiner@consol.de) Received: from vscanner.bb.consol.de (root@vscanner.bb.consol.de [10.250.0.120]) by msgsrv.bb.consol.de (8.8.8/8.8.8) with ESMTP id MAA13854 for ; Tue, 20 Jun 2000 12:20:21 +0200 Received: from bonn.rtg.consol.de (bonn.rtg.consol.de [10.2.204.3]) by vscanner.bb.consol.de (8.9.3/8.9.3) with SMTP id MAA28455 for ; Tue, 20 Jun 2000 12:19:43 +0200 Received: from hilden by bonn.rtg.consol.de (SMI-8.6/SMI-SVR4) id NAA23345; Tue, 20 Jun 2000 13:20:19 +0200 Message-Id: <200006201120.NAA23345@bonn.rtg.consol.de> X-Amavis-approved: Yes Date: Tue, 20 Jun 2000 12:19:41 +0200 (MET DST) From: Thorsten Greiner Reply-To: Thorsten Greiner Subject: Creatix S0 PnP To: freebsd-isdn@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: eOkGcJSbCCbnH8oeDhBnzQ== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi everybody, I found this mail in the archive: > > When I updated to 4.0, I tried to change from configuring my card > via kernel.config to PnP. The resulting kernel crashes after > saying: > ... could not get io area 3 for Creatix/Teles PnP ... I do have exactly the same problem. I even upgraded my system to 4.0-STABLE, but to no avail. I tracked down the problem a little bit and found that this is caused by the following code from src/sys/i4b/layer1 (well, this FIXME stuff looks suspicious anyway): ... /*XXX*/ /* FIXME !!!! * the width of the resource is too small, there are accesses * to it with an offset of 0x3e into the next resource. anyway, * it seems to work and i have no idea how to do 2 resources * overlapping each other. */ bus_set_resource(dev, SYS_RES_IOPORT, 3, iobase2-0x20, 0x20); if(!(sc->sc_resources.io_base[3] = bus_alloc_resource(dev,SYS_RES_IOPORT, &sc->sc_resources.io_rid[3], 0ul,~0ul, 1, RF_ACTIVE))) { printf("isic%d: Could not get io area 3 for Creatix / Teles PnP! \n", unit); isic_detach_common(dev); return ENXIO; } ... The panic seems to be caused by the isic_detach_common(dev), which reports something like area is not busy (Sorry, I am at my office and did not write it down). Looking at a working configuration (without the isic driver configured), the ata1 driver has its iobase set at 0x170, while isic has iobase1=0x120 and iobase2=0x180. This seems to be the reason why isic1 cannot be configured (iobase2-0x20 = 0x160 and this conflicts with the iobase of ata1). If memory serves correctly, under FreeBSD 3.x there was a different ata driver which avoided this problem. Is there any way to tell the isic0 driver to use a different iobase2? Or maybe ata1 can use a different iobase? BTW, Linux has no problems... Please, cc me on reply since I am not subscribed to this list. THANKS! Best Regards -Thorsten To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Jun 20 3:58: 7 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 1F6D137BE67 for ; Tue, 20 Jun 2000 03:58:04 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-235-147.netcologne.de [195.14.235.147]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id MAA05765; Tue, 20 Jun 2000 12:58:01 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.1/8.10.1) with ESMTP id e5KAvda00644; Tue, 20 Jun 2000 12:57:39 +0200 (CEST) Date: Tue, 20 Jun 2000 12:57:39 +0200 (CEST) From: Paul Herman To: Gary Jennejohn Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: <200006180940.LAA01642@peedub.muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 18 Jun 2000, Gary Jennejohn wrote: > It looks like the card has a problem in the early stages of startup > when the cable is plugged in. It's generating interrupts which don't > seem to be getting cleared in the interrupt handler. > > [...] > > Actually, the Linux driver does quite a bit more. It reads the > interrupt register on the card (in FreeBSD parlance iobase1 + 0x4c) > and checks whether the card actually interrupted. This is missing > from i4b. So. Update on what I've found. I saved iobase1 in a sc->sc_iobase1 when the card was attached, and during interrupt I checked: inb(sc->iobase1 + 0x4c) & 0x04 It was allways nonzero. In fact, inb() allways returned a 0x45 off the card (with the same interrupt loop.) So, no luck there. :( Not ready for defeat, I persued the clrirq idea, and found a clrirq function, for elsa ISA cards which solely consisted of the line: outb(sc->sc_iobase1 + 0x07, 0x00) Which hapens to be TRIGGER register, at least on the ISA card (?). I put that in the interrupt function, which called outb() if it looped more than 5 times. Still the same lock up during boot. :( I'm out of ideas. Does anybody have a tech contact at ELSA? No email addresses on their web site. Maybe I'll ask the i4linux crowd. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Jun 20 11:46:26 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F14.dip.t-dialin.net [62.155.143.20]) by hub.freebsd.org (Postfix) with ESMTP id E9D6037BFB9 for ; Tue, 20 Jun 2000 11:46:19 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id SAA07217; Tue, 20 Jun 2000 18:34:44 +0200 (CEST) Message-Id: <200006201634.SAA07217@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: Paul Herman Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 20 Jun 2000 12:58:08 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Jun 2000 18:34:44 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Paul Herman writes: >On Sun, 18 Jun 2000, Gary Jennejohn wrote: > >> It looks like the card has a problem in the early stages of startup >> when the cable is plugged in. It's generating interrupts which don't >> seem to be getting cleared in the interrupt handler. >> >> [...] >> >> Actually, the Linux driver does quite a bit more. It reads the >> interrupt register on the card (in FreeBSD parlance iobase1 + 0x4c) >> and checks whether the card actually interrupted. This is missing >> from i4b. > >So. Update on what I've found. > >I saved iobase1 in a sc->sc_iobase1 when the card was attached, and >during interrupt I checked: > > inb(sc->iobase1 + 0x4c) & 0x04 > >It was allways nonzero. In fact, inb() allways returned a 0x45 off >the card (with the same interrupt loop.) So, no luck there. :( > >Not ready for defeat, I persued the clrirq idea, and found a clrirq >function, for elsa ISA cards which solely consisted of the line: > > outb(sc->sc_iobase1 + 0x07, 0x00) > >Which hapens to be TRIGGER register, at least on the ISA card (?). I >put that in the interrupt function, which called outb() if it looped >more than 5 times. Still the same lock up during boot. :( > >I'm out of ideas. Does anybody have a tech contact at ELSA? No email >addresses on their web site. Maybe I'll ask the i4linux crowd. > Hmmm, ugly hack time. You say the card works if you wait to plug the cable in until after everything is up. This line outb(iobase1 + 0x4c, 0x41); /* enable card interrupt */ is in the attach routine. Seems like, if this enables the interrupts, the same register should disable/clear the interrupts. Try writing a 0 followed by 0x41 to the register in clrirq. The other thing which occurs to me is to not enable the interrupts in attach, but rather to do a timeout with a callback to another routine. Set the timeout fairly long to start with (maybe 60 seconds) and turn on the interrupt in the callback routine. You can then experiment to find the shortest timeout. Even better would be to this after isdnd does its first open of the card, but the routines which handle that are unfortunately not in the driver :( Maybe you can figure out a way to do it with appropriate ifdef's for your card. Ick. --- Gary Jennejohn / garyj@muc.de gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Jun 21 1:41:49 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id E0CAA37B787 for ; Wed, 21 Jun 2000 01:41:46 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-194-8-205-1.netcologne.de [194.8.205.1]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id KAA01237; Wed, 21 Jun 2000 10:41:44 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.1/8.10.1) with ESMTP id e5L8fI300509; Wed, 21 Jun 2000 10:41:18 +0200 (CEST) Date: Wed, 21 Jun 2000 10:41:18 +0200 (CEST) From: Paul Herman To: Gary Jennejohn Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: <200006201634.SAA07217@peedub.muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 20 Jun 2000, Gary Jennejohn wrote: > You say the card works if you wait to plug the cable in until after > everything is up. Yes, which is strange. It just hangs if the cable is plugged in before the i4b devices (i4bctl, i4brbch, i4btrc, etc...) are attached. > Try writing a 0 followed by 0x41 to the register in clrirq. Didn't help. After 0x41, the bad interrupts come back. Of course, only a 0x00 (no 0x41 afterwards) works, but then the card was also unusable. :) I'd like to find the real reason for this. I read something somewhere that these cards have some kind of an "automatic S0 bus detection" capability and I'd bet my bottom dollar it has something to do with that. However, without specs, I'll be compiling new kernels until I'm blue in the face. Speaking of which, I need a break from this. I think I'll get back to this in a week. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Jun 21 5:39: 5 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from castelan.in.skynet.cz (gate.in.skynet.cz [193.165.192.32]) by hub.freebsd.org (Postfix) with SMTP id C04F837BE21 for ; Wed, 21 Jun 2000 05:39:01 -0700 (PDT) (envelope-from josef.pojsl@skynet.cz) Received: (qmail 23985 invoked from network); 21 Jun 2000 12:38:59 -0000 Received: from regent.in.skynet.cz (192.168.192.14) by hub.freebsd.org with SMTP; 21 Jun 2000 12:38:59 -0000 Received: (qmail 3358 invoked by uid 1000); 21 Jun 2000 12:38:56 -0000 From: "Josef Pojsl" Date: Wed, 21 Jun 2000 14:38:56 +0200 To: freebsd-isdn@freebsd.org Subject: Q: status of Winbond W6692CF support Message-ID: <20000621143856.F2296@regent.in.skynet.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello list, sorry if this issue has been discussed - I have searched through the archives but haven't found a clear answer. I have got a noname ISDN PCI card with Winbond W6692CF chip. Q: Is it supported in isdn4bsd? I have got FreeBSD 3.4-RELEASE and the isic driver does not find the card :-( Would an upgrade to 4.0 help? Would a manual upgrade to isdn4bsd 0.90 help? (I must admit i don't know what version of isdn4bsd is integrated with my FBSD 3.4 box). Any clue would be appreciated. TIA, Josef To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Jun 21 10:16:58 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from c187104187.telekabel.chello.nl (c187104187.telekabel.chello.nl [212.187.104.187]) by hub.freebsd.org (Postfix) with SMTP id 2613137B6D0 for ; Wed, 21 Jun 2000 10:16:51 -0700 (PDT) (envelope-from ernst@c187104187.telekabel.chello.nl) Received: (qmail 40977 invoked by uid 1000); 21 Jun 2000 17:16:47 -0000 Date: Wed, 21 Jun 2000 19:16:47 +0200 From: Ernst de Haan To: Josef Pojsl Cc: freebsd-isdn@freebsd.org Subject: Re: Q: status of Winbond W6692CF support Message-ID: <20000621191646.A40958@c187104187.telekabel.chello.nl> References: <20000621143856.F2296@regent.in.skynet.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000621143856.F2296@regent.in.skynet.cz>; from josef.pojsl@skynet.cz on Wed, Jun 21, 2000 at 02:38:56PM +0200 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The Winbond W6692CF ? Is that the chip that is on the Dynalink IS64PPH(+) ? Because I have discussed support for that card several times, and I even offered my card for development at some stage, and offered my help with the driver, but no luck... So I more or less gave up. But I do have (a less reliable) cable connection which can be a lot faster. Ernst Josef Pojsl wrote: > > Hello list, > > sorry if this issue has been discussed - I have searched through > the archives but haven't found a clear answer. > > I have got a noname ISDN PCI card with Winbond W6692CF chip. > Q: Is it supported in isdn4bsd? I have got FreeBSD 3.4-RELEASE > and the isic driver does not find the card :-( > > Would an upgrade to 4.0 help? Would a manual upgrade to > isdn4bsd 0.90 help? (I must admit i don't know what version > of isdn4bsd is integrated with my FBSD 3.4 box). > > Any clue would be appreciated. TIA, > Josef > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Jun 21 12: 0:15 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id 4EC2B37BA16 for ; Wed, 21 Jun 2000 12:00:10 -0700 (PDT) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (IDENT:root@rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id VAA02994; Wed, 21 Jun 2000 21:00:38 +0200 Received: (from martin@localhost) by rumolt.teuto.de (8.10.2/8.10.1) id e5LIoNJ00675; Wed, 21 Jun 2000 20:50:23 +0200 (MEST) From: Martin Husemann Message-Id: <200006211850.e5LIoNJ00675@rumolt.teuto.de> Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: from Paul Herman at "Jun 20, 2000 12:57:39 pm" To: pherman@frenchfries.net (Paul Herman) Date: Wed, 21 Jun 2000 20:50:23 +0200 (MEST) Cc: garyj@muc.de (Gary Jennejohn), freebsd-isdn@FreeBSD.ORG Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Not ready for defeat, I persued the clrirq idea, and found a clrirq > function, for elsa ISA cards which solely consisted of the line: > > outb(sc->sc_iobase1 + 0x07, 0x00) We've been told by the ELSA people that this is absolutley necessary on that card - and it works. > Which hapens to be TRIGGER register, at least on the ISA card (?). I > put that in the interrupt function, which called outb() if it looped > more than 5 times. Still the same lock up during boot. :( This is a complete different card, so that won't work for it, of course. > I'm out of ideas. Does anybody have a tech contact at ELSA? No email > addresses on their web site. Maybe I'll ask the i4linux crowd. Yes, me (and some others) have. ELSA has been very helpful and supportive. In fact I'm running the ELSA Quickstep PCI card in one of our main servers (but of course using NetBSD) and randomly see the problem there too, so I actually have motivation to dig into this further. But I don't have time right now (but will have in a few days). Have you ever tried booting with the ISDN connection unpluged and then plugging it in later? This should eliminate the hard problem, but keeps the potential for random lockups. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Wed Jun 21 23:21:30 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from castelan.in.skynet.cz (gate.in.skynet.cz [193.165.192.32]) by hub.freebsd.org (Postfix) with SMTP id 6192937B604 for ; Wed, 21 Jun 2000 23:21:26 -0700 (PDT) (envelope-from josef.pojsl@skynet.cz) Received: (qmail 7661 invoked from network); 22 Jun 2000 06:21:24 -0000 Received: from regent.in.skynet.cz (192.168.192.14) by hub.freebsd.org with SMTP; 22 Jun 2000 06:21:24 -0000 Received: (qmail 4764 invoked by uid 1000); 22 Jun 2000 06:21:24 -0000 From: "Josef Pojsl" Date: Thu, 22 Jun 2000 08:21:24 +0200 To: Ernst de Haan Cc: freebsd-isdn@freebsd.org Subject: Re: Q: status of Winbond W6692CF support Message-ID: <20000622082124.A4731@regent.in.skynet.cz> Mail-Followup-To: Ernst de Haan , freebsd-isdn@freebsd.org References: <20000621143856.F2296@regent.in.skynet.cz> <20000621191646.A40958@c187104187.telekabel.chello.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <20000621191646.A40958@c187104187.telekabel.chello.nl>; from ernst@jollem.com on Wed, Jun 21, 2000 at 07:16:47PM +0200 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org No. I learned meanwhile that my card is a copy of Asuscom P-IN100 card. I have come through several mails mentioning support of this type of PCI card (with the Windond chip) in the archive but the results were unclear. Someone even noticed that the driver is being developped but the author has not commited it into the i4b distribution. Can anyone confirm/deny? TIA, Josef On Wed, Jun 21, 2000 at 07:16:47PM +0200, Ernst de Haan wrote: > The Winbond W6692CF ? Is that the chip that is on the Dynalink > IS64PPH(+) ? Because I have discussed support for that card several > times, and I even offered my card for development at some stage, and > offered my help with the driver, but no luck... So I more or less gave > up. But I do have (a less reliable) cable connection which can be a lot > faster. > > Ernst To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Jun 22 2:44:14 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 7138437C27D for ; Thu, 22 Jun 2000 02:44:09 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-226-194.netcologne.de [195.14.226.194]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id LAA11526; Thu, 22 Jun 2000 11:43:33 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.1/8.10.1) with ESMTP id e5M9fHt00946; Thu, 22 Jun 2000 11:42:03 +0200 (CEST) Date: Thu, 22 Jun 2000 11:41:17 +0200 (CEST) From: Paul Herman To: Martin Husemann Cc: Gary Jennejohn , freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: <200006211850.e5LIoNJ00675@rumolt.teuto.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 21 Jun 2000, Martin Husemann wrote: > Yes, me (and some others) have. ELSA has been very helpful and > supportive. In fact I'm running the ELSA Quickstep PCI card in one > of our main servers (but of course using NetBSD) and randomly see > the problem there too I don't have random problems (ELSA Microlink PCI), my card hangs consistently. You can depend on my card. :) > Have you ever tried booting with the ISDN connection unpluged and > then plugging it in later? This should eliminate the hard problem, > but keeps the potential for random lockups. Yes, with my card this is the *only* way to get it running. After that, I have no random lockups. In fact, I have no problems whatsoever and am very happy with it's performance -- until I have to boot, anyway. I think the key is finding out how to properly integrate the S0 bus detection into i4b. That's my hunch, anyway. I'm downloading data sheets from infineon right now as we speak, and will look around the web for other info. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Jun 22 3: 6:37 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id 1D2EE37C230 for ; Thu, 22 Jun 2000 03:06:29 -0700 (PDT) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (IDENT:root@rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id MAA04908; Thu, 22 Jun 2000 12:06:58 +0200 Received: (from martin@localhost) by rumolt.teuto.de (8.10.2/8.10.1) id e5M9uNK03012; Thu, 22 Jun 2000 11:56:23 +0200 (MEST) From: Martin Husemann Message-Id: <200006220956.e5M9uNK03012@rumolt.teuto.de> Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: from Paul Herman at "Jun 22, 2000 11:41:17 am" To: pherman@frenchfries.net (Paul Herman) Date: Thu, 22 Jun 2000 11:56:23 +0200 (MEST) Cc: garyj@muc.de (Gary Jennejohn), freebsd-isdn@FreeBSD.ORG Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I don't have random problems (ELSA Microlink PCI), my card hangs > consistently. You can depend on my card. :) Thats realy good: I didn't dig into it, because it was not easy to reproduce for me. I'll send you a patch to try in a few days, maybe earlier... The problem depends on the S0 bus. Ours seems to be quiet at least for half a minute while booting. If your PBX is realy busy or sends random stuff always, you'll receive a packet. If that comes in between attach and !cold you're lost. I think this actually is a bug in the generic IPAC interrupt handler - it may be triggered later too, that's what I'm experiencing: random lockups. > I think the key is finding out how to properly integrate the S0 bus > detection into i4b. Don't think so. See above. But of course the activation of the card itself should be postponed to /dev/i4b open time (and it should be suspended on close or power management events or pc-card eject or...) But thats something to do later. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Jun 22 4:43:44 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 519AE37B983 for ; Thu, 22 Jun 2000 04:43:38 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-194-8-196-23.netcologne.de [194.8.196.23]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id NAA22735; Thu, 22 Jun 2000 13:43:35 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.1/8.10.1) with ESMTP id e5MBhEJ01839; Thu, 22 Jun 2000 13:43:14 +0200 (CEST) Date: Thu, 22 Jun 2000 13:43:14 +0200 (CEST) From: Paul Herman To: Martin Husemann Cc: Gary Jennejohn , freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: <200006220956.e5M9uNK03012@rumolt.teuto.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 22 Jun 2000, Martin Husemann wrote: > The problem depends on the S0 bus. Ours seems to be quiet at least > for half a minute while booting. If your PBX is realy busy or > sends random stuff always, you'll receive a packet. If that comes > in between attach and !cold you're lost. Sounds reasonable, but how is that different from an ethernet card that gets packets between pci_map_int() and when the system comes up? (Bear with me, driver programming is not my strength...) My problem is, I don't exactly understand the problem. Why does just one interrupt between card attachment and /dev/i4b activation make the card generate infinite repeated ISAC interrupts with 0x00 values for ISAC_READ(I_ISTA)? This happens to me when my card locks up. I want to understand the card psychology. :) -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Jun 22 6:45:44 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from emout3.wish.net (emout3.wish.net [212.123.141.30]) by hub.freebsd.org (Postfix) with ESMTP id 2F13E37C2B4 for ; Thu, 22 Jun 2000 06:45:40 -0700 (PDT) (envelope-from sokon@dds.nl) Received: from mail4.inside.servers (mail4.INSIDE.servers [10.1.0.8]) by emout3.wish.net (Postfix) with SMTP id 297A922508 for ; Thu, 22 Jun 2000 15:45:46 +0200 (CEST) Received: (qmail 822 invoked from network); 22 Jun 2000 13:45:38 -0000 Received: from p10585.nl.wish.net (HELO lair.wish.net) ([212.123.179.89]) (envelope-sender ) by mail4.outside.servers (qmail-ldap-1.03) with SMTP for ; 22 Jun 2000 13:45:38 -0000 From: Sokon Reply-To: sokon@dds.nl To: freebsd-isdn@FreeBSD.ORG Subject: i4b CRC / Recieve Aborted error, user PPP Date: Thu, 22 Jun 2000 15:48:42 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <0006221548570F.00357@lair.wish.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I use FreeBSD 4.0-RELEASE and userland PPP with isdn (AVM Fritz!Card PCI). I took the isdn config examples from /usr/share/examples/ppp and changed telephone nr's etc. Everything seems to work, but I get these error messages every few minutes: i4b-L1-isic_isac_irq: unit 0: CRC error i4b-L1-isic_isac_irq: unit 0: Receive Aborted error and when I connect: isdnd[166]: DMN date/time from exchange = 000622143354 ppp[173]: Warning: Add route failed: default already exists Part of my problems resemble Gunnar Kedenburg's problems with the Teles 16.3pnp from previous postings. But for me everything else seems to work OK (connection is 64 kb/s), except for the errors ;( Can anybody help? Thanks, Sokon. KERNEL: ------ #isdn4bsd options "AVM_A1_PCI" device isic0 pseudo-device "i4bq921" pseudo-device "i4bq931" pseudo-device "i4b" pseudo-device "i4btrc" 4 pseudo-device "i4bctl" pseudo-device "i4brbch" 4 pseudo-device "i4btel" 4 pseudo-device "i4bipr" 4 pseudo-device "i4bisppp" 4 pseudo-device sppp 4 options IPR_VJ options IPR_LOG=5 from dmesg.today: ------------ isic0: port 0x500-0x51f mem 0x81000000-0x8100001f irq 11 at device 7.0 on pci0 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) .. ii4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4btel: 4 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached .. ii4b-L1-isic_isac_irq: unit 0: CRC error i4b-L1-isic_isac_irq: unit 0: Receive Aborted error i4b-L1-isic_isac_irq: unit 0: CRC error i4b-L1-isic_isac_irq: unit 0: Receive Aborted error i4b-L1-isic_isac_irq: unit 0: CRC error i4b-L1-isic_isac_irq: unit 0: Receive Aborted error i4b-L1-isic_isac_irq: unit 0: CRC error i4b-L1-isic_isac_irq: unit 0: Receive Aborted error i4b: unit 0, assigned TEI = 65 = 0x41 i4b-L4-i4b_l4_setup_timeout: 961630274: ERROR: idletime[900]+earlyhup[5] > unitlength[60]! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Jun 22 8:24:28 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 28C8D37C302 for ; Thu, 22 Jun 2000 08:24:25 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id QAA55328; Thu, 22 Jun 2000 16:24:20 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id QAA02857; Thu, 22 Jun 2000 16:24:17 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200006221524.QAA02857@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: sokon@dds.nl Cc: freebsd-isdn@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: i4b CRC / Recieve Aborted error, user PPP In-Reply-To: Message from Sokon of "Thu, 22 Jun 2000 15:48:42 +0200." <0006221548570F.00357@lair.wish.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Jun 2000 16:24:17 +0100 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > ppp[173]: Warning: Add route failed: default already exists Change your ``add'' to ``add!'' in ppp.conf if you want to force the default route. Otherwise remove the defaultrouter setting in rc.conf. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Jun 23 2:50: 6 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id F303337B8D6 for ; Fri, 23 Jun 2000 02:50:03 -0700 (PDT) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id LAA04396; Fri, 23 Jun 2000 11:50:36 +0200 Received: (from martin@localhost) by rumolt.teuto.de (8.10.2/8.10.1) id e5N9dVZ00620; Fri, 23 Jun 2000 11:39:31 +0200 (MEST) From: Martin Husemann Message-Id: <200006230939.e5N9dVZ00620@rumolt.teuto.de> Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: from Paul Herman at "Jun 22, 2000 01:43:14 pm" To: pherman@frenchfries.net (Paul Herman) Date: Fri, 23 Jun 2000 11:39:31 +0200 (MEST) Cc: garyj@muc.de (Gary Jennejohn), freebsd-isdn@FreeBSD.ORG Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Sounds reasonable, but how is that different from an ethernet card > that gets packets between pci_map_int() and when the system comes up? It's a bug in the interrupt service routine. It's not a problem per se, but you are the first to have it reproducible. Until now it was hard to fix, with you as a tester it's realy easy. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jun 24 3:49:49 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id B4D2C37B893; Sat, 24 Jun 2000 03:49:41 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-226-207.netcologne.de [195.14.226.207]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id MAA21012; Sat, 24 Jun 2000 12:49:39 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.1/8.10.1) with ESMTP id e5OAmxK00590; Sat, 24 Jun 2000 12:48:59 +0200 (CEST) Date: Sat, 24 Jun 2000 12:48:59 +0200 (CEST) From: Paul Herman To: freebsd-isdn@FreeBSD.ORG Cc: Gary Jennejohn , Hellmuth Michaelis Subject: Request for patch review Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1524932673-961842598=:337" Content-ID: Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1524932673-961842598=:337 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Hello, As a result of the thread: "Re: i4b hangs during boot with ELSA Microlink" I found a sollution to my problem of an ELSA Microlink PCI ISDN Card hanging upon boot when an ISDN cable is plugged in and packets come in before the system comes up. This patch should be tested by people who: a) have an ELSA PCI ISDN Card (definately!) b) have a PCI card that uses IPAC rather than HSCX/ISAC (in 'dmesg' something like "isic0: IPAC PSB2115 Version 1.x") c) like to take risks or are just curious to test bleeding edge patches :) The patch should actually be harmless (code taken from similar i4b_isic.c file) and if it has no bad side effects, then I would like to get it commited to the current i4b tree as soon as possible. This is patched against i4b-0.83, but patches cleanly against 0.90 too. If you try this patch (attached) please send me an email with your results: Paul Herman Thanks go out to Gary Jennejohn and Martin Husemann for their help in tracking this down. I'm so happy I can boot now!!! :) -Paul. --0-1524932673-961842598=:337 Content-Type: APPLICATION/octet-stream; name="ELSA_Microlink_IPAC.patch.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="ELSA_Microlink_IPAC.patch.gz" H4sICJCJVDkCA0VMU0FfTWljcm9saW5rX0lQQUMucGF0Y2gAhVJra5xAFP08 /oqbQINGzfraUpWE3ewuxDQp7RpoCgUxE3UHRO2MlpQ0/z3zMF0MKfkwz3vv OeeeGdu2oc7/FNSdkeAuI4zgrMPkBJ+0lFToum3gS/sb3Dl4fhQ4kfcJ3DAM NdM0365Dad7D5dCAF4DrRU4Y+SF4juNoiwXYge9ZrgNm4AeW68JioQF64qOo WYFmx5B8Xa6ANH1B6dD1QNuhJ00BxzOe88gHokVFGA/DkOFdToF0Oc4I/ZWx Pu9jzURIXuN2aPgRNBuhsqV6HBsiJrYydDqP5XrmqNW2DYEuKYSOquihqtu7 vAYODgJ8YEoGQnKaEMMp6EJ6tt0s12qXpDdLw4AjcB78MlbNz0PLDXjzHz3L 81TzAkl4t2P4QcDpDFtwka5uFZTcrS6yc36pIC1VhNA+9HIzlXQE/3Rkm9tz I5ZpT8IRREr9dfJedZas1vB3Ur02pH1v1U3KpImji/I508lzjv6pjglTQLJj kTiaNzr3IvddWqFOZj3KWdDyZ8bFa/Jd3tzXpKmECvNdFekePhFiTCkGRkWk BP1AfhwDFG1HOVOpHwrQD/cRJNtvcNW23cHP5tAChu0zhrOhIf0eS6DJNr5v k5uN8v96mX62+JcpS2XAenO1/KHPHXX6XzYW8WcrM6lBygMAAA== --0-1524932673-961842598=:337-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jun 24 4:15:21 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from widukind.bi.teuto.net (widukind.bi.teuto.net [212.8.197.28]) by hub.freebsd.org (Postfix) with ESMTP id 2F31337BB5B; Sat, 24 Jun 2000 04:15:17 -0700 (PDT) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (IDENT:root@rumolt.teuto.de [212.8.203.81]) by widukind.bi.teuto.net (8.9.3/8.9.3) with ESMTP id NAA06310; Sat, 24 Jun 2000 13:15:52 +0200 Received: (from martin@localhost) by rumolt.teuto.de (8.10.2/8.10.1) id e5OBEqT00622; Sat, 24 Jun 2000 13:14:52 +0200 (MEST) From: Martin Husemann Message-Id: <200006241114.e5OBEqT00622@rumolt.teuto.de> Subject: Re: Request for patch review In-Reply-To: from Paul Herman at "Jun 24, 2000 12:48:59 pm" To: pherman@frenchfries.net (Paul Herman) Date: Sat, 24 Jun 2000 13:14:52 +0200 (MEST) Cc: freebsd-isdn@FreeBSD.ORG, garyj@muc.de (Gary Jennejohn), hm@FreeBSD.ORG (Hellmuth Michaelis) Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This patch should be tested by people who: > > a) have an ELSA PCI ISDN Card (definately!) > b) have a PCI card that uses IPAC rather than HSCX/ISAC > (in 'dmesg' something like "isic0: IPAC PSB2115 Version 1.x") > c) like to take risks or are just curious to test bleeding edge > patches :) And: d) are running FreeBSD :-) Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jun 24 4:52:54 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from rannoch.demon.co.uk (rannoch.demon.co.uk [158.152.110.117]) by hub.freebsd.org (Postfix) with ESMTP id 18BB837B825 for ; Sat, 24 Jun 2000 04:52:47 -0700 (PDT) (envelope-from apbran@rannoch.demon.co.uk) Received: from localhost (apbran@localhost) by rannoch.demon.co.uk (8.9.3/8.9.3) with ESMTP id MAA08216 for ; Sat, 24 Jun 2000 12:51:59 +0100 Date: Sat, 24 Jun 2000 12:51:59 +0100 (BST) From: Paul Branston To: freebsd-isdn@freebsd.org Subject: Not connecting Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is my first posting to this list and I'm a newbie with FreeBSD although I've run solaris boxes for a living for many years and used Linux at home for since 1994. I have FreeBSD 4.0 with a Fritz PCI card, I compiled a new kernel with ISDN support and the card is recognised at boot time and the devices configured. When I try to connect to my ISP (demon) I see the following in dmesg and get no connection. Can anyone suggest what I have missed please ? i4b-L1-timer3_expired: state = F5 Identifying Input i4b-L1-isic_recover: HSCX B: ISTA = 0x0 i4b-L1-isic_recover: ISAC: ISTA = 0x0 i4b-L1-isic_recover: HSCX B: IMASK = 0x0 i4b-L1-isic_recover: HSCX A: IMASK = 0x0 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 = 43 i4b-L3-next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! i4b-L1-timer3_expired: state = F5 Identifying Input i4b-L1-isic_recover: HSCX B: ISTA = 0x0 i4b-L1-isic_recover: ISAC: ISTA = 0x0 i4b-L1-isic_recover: HSCX B: IMASK = 0x0 i4b-L1-isic_recover: HSCX A: IMASK = 0x0 i4b-L1-isic_recover: ISAC: IMASK = 0x2a i4b: unit 0, assigned TEI = 74 = 0x4a i4b: unit 0, assigned TEI = 74 = 0x4a i4b: unit 0, assigned TEI = 74 = 0x4a The output from isdntrace implies that it has dialed as does running isdnd in debugging mode. ---------------------------- isdntrace ------------------------------ Q931: pd=Q.931/I.451, cr=0x40 (from origination), message=SETUP: [sending complete] [bearer capability: cap=unrestricted digital information std=CCITT rate=64 kbit/s mode=circuit] [channel id: channel=any channel (preferred)] [calling party number: 01226396208 (type=unknown, plan=ISDN)] [called party number: 08450798667 (type=unknown, plan=ISDN)] -- NT->TE - unit:0 - frame:000087 - time:24.06 12:33:06.528902 - length:4 ------ Dump:000 00 95 01 02 .... Q921: SAP=0 (Call Control), R, TEI=74, S-Frame: RR N(R) 1 PF 0 -- NT->TE - unit:0 - frame:000088 - time:24.06 12:33:06.928907 - length:11 ----- Dump:000 02 95 00 02 .... Q921: SAP=0 (Call Control), C, TEI=74, I-Frame: N(S) 0 N(R) 1 P 0 Dump:004 08 01 c0 02 18 01 89 ....... -------------------------------------------------------------------------- ------------------------------ isdnd -d0xf9 -F -------------------------- isdnd[32099]: DBG msg_dialout: dial req from isp, unit 0 isdnd[32099]: DBG setup_dialout: entry I4BIP ok! isdnd[32099]: DBG find_by_device_for_dialout: found entry 0! isdnd[32099]: DBG FSM event [msg-dialout]: [idle => dialing] isdnd[32099]: DBG F_DIAL: local dial out request isdnd[32099]: DBG select_first_dialno: only one no, no = 08450798667 isdnd[32099]: CHD 00004 I4BIP rate 296 sec/unit (rate) isdnd[32099]: CHD 00004 I4BIP dialing out from 01226396208 to 08450798667 isdnd[32099]: CHD 00004 I4BIP outgoing call proceeding (ctl 0, ch 0) isdnd[32099]: DBG msg_charging: 1 unit(s) (estimated) isdnd[32099]: CHD 00004 I4BIP outgoing call active (ctl 0, ch 0, isp0) isdnd[32099]: DBG FSM event [msg-con-act-ind]: [dialing => connected] isdnd[32099]: DBG F_DOK: dial out ok isdnd[32099]: DBG select_this_dialno: index = 0, no = 08450798667 isdnd[32099]: DBG msg_charging: 2 unit(s) (estimated) isdnd[32099]: DBG msg_charging: 3 unit(s) (estimated) isdnd[32099]: CHD 00004 I4BIP outgoing call disconnected (remote) isdnd[32099]: CHD 00004 I4BIP cause 16: Normal call clearing (Q.850) isdnd[32099]: CHD 00004 I4BIP charging: 3 units, 601 seconds isdnd[32099]: CHD 00004 I4BIP accounting: in 621625, out 414423 (in 620977, out To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message