From owner-freebsd-isdn Sun Jun 25 3: 2: 2 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F3B.dip.t-dialin.net [62.155.143.59]) by hub.freebsd.org (Postfix) with ESMTP id 38E8737B6C7 for ; Sun, 25 Jun 2000 03:01:57 -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 LAA52481; Sun, 25 Jun 2000 11:56:01 +0200 (CEST) Message-Id: <200006250956.LAA52481@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: Paul Herman Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Request for patch review Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 24 Jun 2000 12:49:46 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jun 2000 11:56:01 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Paul Herman writes: >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. > Bummer ! In my first mail I'd intended to suggest using the code from i4b_isic.c, since I'd noticed it was different, but I got side-tracked and didn't. Could have saved a lot of time and eMails. Well, you found the fix, anyway :) --- 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 25 3: 2: 5 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F3B.dip.t-dialin.net [62.155.143.59]) by hub.freebsd.org (Postfix) with ESMTP id CE06037B56B for ; Sun, 25 Jun 2000 03:02: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 LAA47329; Sun, 25 Jun 2000 11:48:37 +0200 (CEST) Message-Id: <200006250948.LAA47329@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Josef Pojsl" Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Q: status of Winbond W6692CF support Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 21 Jun 2000 14:38:56 +0200." <20000621143856.F2296@regent.in.skynet.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jun 2000 11:48:37 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Josef Pojsl" writes: > >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). > Support for this chip will be in the next beta release. Can't say exactly when that will happen. --- 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 25 7:34: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 3C8D437B64E; Sun, 25 Jun 2000 07:34:11 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-250-42.netcologne.de [195.14.250.42]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id QAA05855; Sun, 25 Jun 2000 16:34:09 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.2/8.10.1) with ESMTP id e5PEXkw12305; Sun, 25 Jun 2000 16:33:46 +0200 (CEST) Date: Sun, 25 Jun 2000 16:33:46 +0200 (CEST) From: Paul Herman To: Martin Husemann Cc: freebsd-isdn@FreeBSD.ORG, Gary Jennejohn , Hellmuth Michaelis Subject: Re: Request for patch review In-Reply-To: <200006241114.e5OBEqT00622@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 Sat, 24 Jun 2000, Martin Husemann wrote: > > 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 Make that FreeBSD-3.x. As I found out when cvsuping, changes in i4b since then have gotten rid of the problem file (layer1/i4b_isic_pci.c), so FreeBSD 4.x and 5.x (post 0.83?) don't need this patch. -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 25 17:32:18 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9624737B630 for ; Sun, 25 Jun 2000 17:32:10 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id CAA30320; Mon, 26 Jun 2000 02:32:05 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id CAA27674; Mon, 26 Jun 2000 02:31:53 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Mon, 26 Jun 2000 02:31:53 +0200 (CEST) From: Leif Neland To: Gerhard Sittig Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: reject In-Reply-To: <20000615180028.M9883@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 I'm back from vacation... On Thu, 15 Jun 2000, Gerhard Sittig wrote: > On Wed, Jun 14, 2000 at 23:05 +0200, Gary Jennejohn wrote: > > David Wetzel writes: > > >> From: Gary Jennejohn > > > > > >> Wait a second. If you have 2 devices on an S0 bus responding > > >> to the same number then I would expect a race condition to > > >> result. It doesn't seem reasonable to me to expect isdnd to > > >> reject calls for other devices on the bus. In fact, I would > > >> suspect that it would violate some standard. IMHO that's a > > >> function which a PBX should carry out. > > > > > >No. i4b/the anwering machine should answer the call and hang > > >up. > > Accepting the call with an AM and immediately hanging up is one > solution. But regarding immediate _rejection_ this *is* possible > (and we've been through that a few years ago in another project). > > AFAICT (I'm not an communications expert and might use the wrong > terms, but you surely get the idea) an incoming call is just > signalled to the internal bus(ses). *Every* device has the > opportunity to > - ignore the call ("not mine, I don't care") > - accept the call ("I _could_ handle this" in the meaning of "I > apply for getting this job"!) > - reject the call ("not for me _and_for_nobody_else_ I can think > of") > > There's a chance for multiple devices to accept the signalled > call (not to get them, that's something the PBX will handle due > to the packets' serialisation on the bus). And I consider this > to be a feature. Think of signalling a voice call on many phones > and have the user decide where to pick up the receiver. Or have > a few remote control computers sit there and have them choose > whether it's their working hour and whom they respond to. That's > where they can share a MSN quite well. > > To summarize: There is a rejection message a device can emit > speaking for *everyone* on the bus. It's just rarely used and > might not be available at a userland command level. And it's > very rare cases where this message is appropriate. In the linux-isdn stuff there is a note of NOT to reject a call if it might be for another device, so that also signify the existance of a global reject command. I have a few MSN's on my line: One for me, one for my wife, one for the computer (also acting as fax) and one extra, just in case... Mine and my wife's number each has "transfer call if no answer (after 4 rings)" to each our cell-phone. When going on vacation, I took out these two MSN's of the phones, so the house-sitter wouldn't be disturbed by calls to us, but still be able to be called on the extra MSN. But, as no device would accept the call for our numbers, the exhance just reported "no such number", and the calls would never be transferred. I had to put a phone in the computer-room accepting our numbers, to have the calls accepted. BTW, it is possible to have two phones on one ISDN2, and have both accepting calls for the same number. It is also possible to have more ISDN2-lines marked together, and when the first one is busy, the next one recieves the call. But is it possible to have say 2 ISDN2-lines, and 4 phones, and all 4 ring when a call comes in? Or does that require a pbx? > See above. We really suffered from this and it took quite some > time to find out there's even such a feature and it's used in the > software. Actually this tough rejection completely prevented the > neighbour machines from getting any call (although they *saw* > them). But this sounds like it absolutely is what's wanted here. > > (Mis)using the AM will accept the connection for a moment and > lead to cost and a blocked B channel (i.e. data channel in > contrast to the rejection completely handled in D channel > messages). This should be considered -- unless one wants to > "punish" the to be banned caller. > Well, we're back on speaking terms again, so this isn't nessecary anymore :-) Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Jun 26 14:22: 3 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F40.dip.t-dialin.net [62.155.143.64]) by hub.freebsd.org (Postfix) with ESMTP id A9BB637B5E8 for ; Mon, 26 Jun 2000 14:21:57 -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 XAA59632; Mon, 26 Jun 2000 23:12:35 +0200 (CEST) Message-Id: <200006262112.XAA59632@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: sokon@dds.nl Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: i4b CRC / Recieve Aborted error, user PPP Reply-To: Gary Jennejohn In-reply-to: Your message 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: Mon, 26 Jun 2000 23:12:35 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sokon writes: >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 > Really every few minutes ? All day long ? Strange, I've never seen anything like that with my card and, although I wrote the driver, I haven't the foggiest idea why you're seeing it. >and when I connect: >isdnd[166]: DMN date/time from exchange = 000622143354 >ppp[173]: Warning: Add route failed: default already exists > This is normal. I also see this with ppp. It's more a warning than an error. --- 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 26 14:22:11 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F40.dip.t-dialin.net [62.155.143.64]) by hub.freebsd.org (Postfix) with ESMTP id 4B8D637BD82 for ; Mon, 26 Jun 2000 14:22:06 -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 XAA59620; Mon, 26 Jun 2000 23:08:35 +0200 (CEST) Message-Id: <200006262108.XAA59620@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gerald Heinig Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: TA PCI passive card questions Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 05 Jun 2000 23:47:06 +0200." <393C1FDA.D391B622@post.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Mon, 26 Jun 2000 23:08:35 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gerald Heinig writes: >Hi all, > >I recently (yesterday) acquired a TA ISDN card and I'd like to know >whether anyone has any info on this beast. >It has the Cologne Chip Designs chip on it - the exact number is CCD >9914E. >I had a look through the i4b archives and it seems someone (Hellmuth?) >is writing a driver for this thing, or wants to, or has finished and >wants to test or whatever. >If the driver work is still ongoing, I=B4d like to offer to help. I have= a >bit of time spare at the moment and if I could contribute something and >learn a thing or two that would be cool. >First of all, though, I don=B4t have any docs for this chip and I don=B4= t >even know what company the card is from. All it says on the box is "ISDN= >128k TA card" and the exact card number is TAS106H-C if that=B4s of any >help to anyone. > >As for the chip, I had a look for www.ccd.de, ccd.com, searched for >"Cologne Chip Design" on Yahoo but turned up nothing. Where do I get the= >doco for this thing from? > >Any pointers much appreciated. > >If there already *is* a driver for this then sorry to waste your time. >I=B4m still on 3.4 Release with (IIRC) the stock i4b and there was no >mention of this card in the "Cards" file. If it=B4s already in the 4.0 i= 4b >I=B4ll have missed it. > This is kind of old. Did anyone ever answer it ? Anyway... CCD has a web site at www.colognechip.de. Is this the HFC-S PCI chip ? (looks at data sheet...) I guess not. I have no idea which chip this is and I've never seen numbers like this on a CCD chip. They tend to use labels like HFC-S PCI or HFC-SP. There are some CCD chips supported in the next beta releasae. Don't know when that will be. The driver for the HFC-S PCI chip is in a rather incomplete state right now. Obviously, it's a PCI based card. If you have one of those then you might also have this chip. I started the driver and got it fairly far along, but I never finished it. I sent Hellmuth what I had, but he didn't have time to finish it. If you're interested, I could send you what I have. But you have to develop in the context of the next release, which is *completely* different from the old stuff. Could be difficult to get up to speed. It's probably better to wait for me or Hellmuth to get on the stick and finish the driver. --- 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 26 14:45:52 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id B903237BD23 for ; Mon, 26 Jun 2000 14:45:44 -0700 (PDT) (envelope-from Gerald.Heinig@post.rwth-aachen.de) Received: from post.rwth-aachen.de (s4m017.dialup.RWTH-Aachen.DE [137.226.8.17]) by nets5.rz.rwth-aachen.de (8.10.1/8.10.1/5) with ESMTP id e5QLjg325439; Mon, 26 Jun 2000 23:45:42 +0200 (MET DST) Message-ID: <3957CEB4.6587AFC3@post.rwth-aachen.de> Date: Mon, 26 Jun 2000 23:44:20 +0200 From: Gerald Heinig X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: Gary Jennejohn Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: TA PCI passive card questions References: <200006262108.XAA59620@peedub.muc.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gary Jennejohn wrote: > Gerald Heinig writes: > >Hi all, > > > >I recently (yesterday) acquired a TA ISDN card and I'd like to know > >whether anyone has any info on this beast. > >It has the Cologne Chip Designs chip on it - the exact number is CCD > >9914E. > >I had a look through the i4b archives and it seems someone (Hellmuth?) > >is writing a driver for this thing, or wants to, or has finished and > >wants to test or whatever. > >If the driver work is still ongoing, Iīd like to offer to help. I have a > >bit of time spare at the moment and if I could contribute something and > >learn a thing or two that would be cool. > >First of all, though, I donīt have any docs for this chip and I donīt > >even know what company the card is from. All it says on the box is "ISDN > >128k TA card" and the exact card number is TAS106H-C if thatīs of any > >help to anyone. > > > >As for the chip, I had a look for www.ccd.de, ccd.com, searched for > >"Cologne Chip Design" on Yahoo but turned up nothing. Where do I get the > >doco for this thing from? > > > >Any pointers much appreciated. > > > >If there already *is* a driver for this then sorry to waste your time. > >Iīm still on 3.4 Release with (IIRC) the stock i4b and there was no > >mention of this card in the "Cards" file. If itīs already in the 4.0 i4b > >Iīll have missed it. > > > > This is kind of old. Did anyone ever answer it ? Yeah. I got a reply from Hellmuth a week or two back with a pointer to http://www.colognechip.de and I've downloaded the doco. > > > Anyway... CCD has a web site at www.colognechip.de. > > Is this the HFC-S PCI chip ? (looks at data sheet...) I guess not. > I have no idea which chip this is and I've never seen numbers like > this on a CCD chip. They tend to use labels like HFC-S PCI or HFC-SP. Erm, yes. [embarrassment]. It's actually an HFC-S PCI. I didn't look at the right numbers. > > > There are some CCD chips supported in the next beta releasae. Don't > know when that will be. > > The driver for the HFC-S PCI chip is in a rather incomplete state > right now. Obviously, it's a PCI based card. If you have one of > those then you might also have this chip. The chip is the HFC-S PCI. Hellmuth said he was keen on a driver being available for the next release. I'd be happy to give things a try, but all my driver experience is from Solaris, and even that isn't all that much. What I'm really lacking is good doco for the FreeBSD way to probe and attach a card to the system and The Right Way (tm) of doing things. It's kind of hard to find docs like that for BSD. > > > I started the driver and got it fairly far along, but I never > finished it. I sent Hellmuth what I had, but he didn't have time > to finish it. If you're interested, I could send you what I have. Cool. I'd definitely be interested. > But you have to develop in the context of the next release, which is > *completely* different from the old stuff. *sigh*. So I _will_ have to upgrade to 4.0 pronto, then? I was sort of hoping I'd get round that, but ah, what the heck.... :-) > Could be difficult to get > up to speed. It's probably better to wait for me or Hellmuth to get > on the stick and finish the driver. You're right on that one. It'll take me a while to work out what goes where, but I'm still interested in the code. You never know, I might even be able to help.... :-) Cheers, Gerald > > --- > 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 26 22:56:44 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F43.dip.t-dialin.net [62.155.143.67]) by hub.freebsd.org (Postfix) with ESMTP id D0E5A37BE36 for ; Mon, 26 Jun 2000 22:56:40 -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 HAA60328; Tue, 27 Jun 2000 07:51:27 +0200 (CEST) Message-Id: <200006270551.HAA60328@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: sokon@dds.nl Cc: freebsd-isdn@freebsd.org Subject: Re: i4b CRC / Recieve Aborted error, user PPP Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 27 Jun 2000 02:59:06 +0200." <00062703021000.09465@lair.wish.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Jun 2000 07:51:27 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sokon writes: >On Mon, 26 Jun 2000, Gary Jennejohn wrote: > >> Really every few minutes ? All day long ? Strange, I've never seen >> anything like that with my card and, although I wrote the driver, >> I haven't the foggiest idea why you're seeing it. > >Yes, almost every minute or so (drives me nuts), except when I'm actually >connected. I know the card is OK (tried it in a win2k machine). Might be interesting to run isdntrace while the line is idle and see just what the NT is sending to cause this message. >> Warning: Add route failed: default already exists > >This is not a normal warning. I forgot to remove an 'add route' from my >ppp.linkup (ps: thanks Brian). > I see this all the time with PPPoE, and I don't have any linkup script. That's why I said it was normal. --- 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 26 22:56:51 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F43.dip.t-dialin.net [62.155.143.67]) by hub.freebsd.org (Postfix) with ESMTP id 29CC037BE3C for ; Mon, 26 Jun 2000 22:56:44 -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 HAA60315; Tue, 27 Jun 2000 07:45:31 +0200 (CEST) Message-Id: <200006270545.HAA60315@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gerald Heinig Cc: freebsd-isdn@freebsd.org Subject: Re: TA PCI passive card questions Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 26 Jun 2000 23:45:44 +0200." <3957CEB4.6587AFC3@post.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Tue, 27 Jun 2000 07:45:31 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gerald Heinig writes: >Gary Jennejohn wrote: [big snip] >> There are some CCD chips supported in the next beta releasae. Don't >> know when that will be. >> >> The driver for the HFC-S PCI chip is in a rather incomplete state >> right now. Obviously, it's a PCI based card. If you have one of >> those then you might also have this chip. > >The chip is the HFC-S PCI. Hellmuth said he was keen on a driver being = availab >le for the next release. >> [snip] >> I started the driver and got it fairly far along, but I never >> finished it. I sent Hellmuth what I had, but he didn't have time >> to finish it. If you're interested, I could send you what I have. > >Cool. I'd definitely be interested. > >> But you have to develop in the context of the next release, which is >> *completely* different from the old stuff. > >*sigh*. So I _will_ have to upgrade to 4.0 pronto, then? I was sort of = hoping >I'd get round that, but ah, what the >heck.... :-) > Actually, -current would be better, but 4.0 has the newbus stuff, so it would be OK. The driver already probes and attaches the card fine, so you don't need to worry about that. What's missing is the dirty stuff - managing the FIFOs and tracking the state of the S0 bus (ISDN phases). The chip does not fit at all into the existing i4b way of doing things, so the driver has to do all the gory phase tracking itself. What I meant with "context of the next release" was that Hellmuth has split up the way that the layers interact. The new stuff is only in the developer's release of the code. You'd have to get ahold of that (not hard) and familiarize yourself with it before you could finish the driver off. Would take a while to get up to speed. I know that Hellmuth really wants to get this driver in before he makes the next release since the CCD chips are used on so many newer, inexpensive cards now. And they're pretty darn good chips, too. I'll clean it up a little and send it to you. May be a few days. Who knows ? Once I get started I may just finish it :) --- 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 Tue Jun 27 9:23:32 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 1B3F537B627 for ; Tue, 27 Jun 2000 09:23:26 -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 RAA57323; Tue, 27 Jun 2000 17:23:15 +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 RAA49408; Tue, 27 Jun 2000 17:22:52 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200006271622.RAA49408@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gary Jennejohn Cc: sokon@dds.nl, freebsd-isdn@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: i4b CRC / Recieve Aborted error, user PPP In-Reply-To: Message from Gary Jennejohn of "Mon, 26 Jun 2000 23:12:35 +0200." <200006262112.XAA59632@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Jun 2000 17:22:52 +0100 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >and when I connect: > >isdnd[166]: DMN date/time from exchange = 000622143354 > >ppp[173]: Warning: Add route failed: default already exists > > > > This is normal. I also see this with ppp. It's more a warning than > an error. You can ``add! default HISADDR'' if you want to override whatever's already set. > --- > Gary Jennejohn / garyj@muc.de gj@freebsd.org -- 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 Tue Jun 27 11:11:58 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from unity.copyleft.no (unity.copyleft.no [212.71.72.23]) by hub.freebsd.org (Postfix) with ESMTP id EE08C37B7FD for ; Tue, 27 Jun 2000 11:11:52 -0700 (PDT) (envelope-from vegard@unity.copyleft.no) Received: from vegard (helo=localhost) by unity.copyleft.no with local-esmtp (Exim 3.03 #1) id 136zpv-00061M-00 for freebsd-isdn@freebsd.org; Tue, 27 Jun 2000 20:11:51 +0200 Date: Tue, 27 Jun 2000 20:11:51 +0200 (CEST) From: Vegard Munthe To: freebsd-isdn@freebsd.org Subject: Troubleshooting 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 I'm setting up i4b on an OpenBSD 2.7, and have run into remarkably few problems, until now. To this point I've compiled and installed i4b, compiled and installed a new kernel supporting my Teles S0/16.3, compiled and installed the freebsd userland ppp, and somewhat configured isdnd.conf and ppp.conf. Everything seemed to go smoothly until I started it all up with high debugging priorities and got a "No Carrier" error in ppp... Therefore I have two questions I hope someone can help me with; First I'm wondering if there is any way to 'talk' to the ISDN card directly to see if the driver is at all comunicating with the card? This is my first wrestling match with ISDN, so I'm used to sounds and blinking light to tell me I'm getting somewhere (read R2D2)... But my card is as silent and passive as a NY policedepartment on a minoritymarch rampage... The only reassurance I get are the few lines of kerneloutput on startup: --- isic0 at isa0 port 0xd80/8 irq 11 isic0: Teles S0/16.3 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) isic0: HSCX 82525 or 21525 Version 2.1 --- I.e. is there any way I can make sure communication between isdnd and the Teles card is up and running? My second question is more elaborate, as I'm asking for general guidance. Here is what works on my system: I get isdnd up and running nicely with 'isdnd -d0xf9 -f' and monitor things from there. I then get ppp up nicely and try out a good 'dial', regretfully without results. My log/ppp shows: --- Phase: 1: closed -> opening Phase: 1: Connected! Phase: 1: opening -> dial Phase: 1: dial -> carrier Phase: 1: /dev/i4brbch0: No carrier Phase: 1: Disconnected! --- And my isdnd shows: --- DBG msg_dialoutnumber: dial req from rbch, unit 0 DBG setup_dialout: entry userppp0 ok! DBG find_by_device_for_dialoutnumber: found entry 0! DBG FSM event [msg-dialout]: [idle => dialing] DBG F_DIAL: local dial out request DBG select_first_dialno: only one no, no = 22179080 CHD 00003 userppp0 rate 360 sec/unit (rate) CHD 00003 userppp0 dialing out from 22175582 to 22179080 CHD 00003 userppp0 outgoing call disconnected (remote) DBG msg_dialoutnumber: dial req from rbch, unit 0 DBG find_by_device_for_dialoutnumber: entry 0, cdid in use DBG msg_dialoutnumber: config entry reserved or no match DBG msg_dialoutnumber: dial req from rbch, unit 0 DBG find_by_device_for_dialoutnumber: entry 0, cdid in use DBG msg_dialoutnumber: config entry reserved or no match --- My ISDN line is fully functional as I have an ISDN telephone on a split plug for testing, and I've tested the cables. My problem is finding where the communication glitch is. My fear is that the kernel driver isn't communicating with the card properly, but as the first question suggests, I havn't found a way to test this yet. Any suggestions of getting this fixed would help greatly. What to do now? :) Best regards, -- Vegard Munthe Copyleft Software Tel: 22232521 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Jun 27 11:46: 8 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F20.dip.t-dialin.net [62.155.143.32]) by hub.freebsd.org (Postfix) with ESMTP id BBEFE37C0AB for ; Tue, 27 Jun 2000 11:46:04 -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 UAA61245; Tue, 27 Jun 2000 20:36:03 +0200 (CEST) Message-Id: <200006271836.UAA61245@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Somers Cc: sokon@dds.nl, freebsd-isdn@FreeBSD.org Subject: Re: i4b CRC / Recieve Aborted error, user PPP Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 27 Jun 2000 18:23:40 +0200." <200006271622.RAA49408@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Jun 2000 20:36:02 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brian Somers writes: >> >and when I connect: >> >isdnd[166]: DMN date/time from exchange = 000622143354 >> >ppp[173]: Warning: Add route failed: default already exists >> > >> >> This is normal. I also see this with ppp. It's more a warning than >> an error. > >You can ``add! default HISADDR'' if you want to override whatever's >already set. > I have that in the conf file. But HISADDR is written hisaddr, as it appears in one of the examples. It doesn't seem to matter whether it's written in CAPS or not, I've tried both. Maybe PPPoE has different behavior ? --- 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 Tue Jun 27 16:37:45 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 ED17F37C458 for ; Tue, 27 Jun 2000 16:37:25 -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 AAA82847; Wed, 28 Jun 2000 00:35:14 +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 AAA19229; Wed, 28 Jun 2000 00:35:10 +0100 (BST) (envelope-from brian@Awfulhak.org) Message-Id: <200006272335.AAA19229@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gary Jennejohn Cc: Brian Somers , sokon@dds.nl, freebsd-isdn@FreeBSD.org, brian@hak.lan.awfulhak.org Subject: Re: i4b CRC / Recieve Aborted error, user PPP In-Reply-To: Message from Gary Jennejohn of "Tue, 27 Jun 2000 20:36:02 +0200." <200006271836.UAA61245@peedub.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Jun 2000 00:35:10 +0100 From: Brian Somers Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Brian Somers writes: > >> >and when I connect: > >> >isdnd[166]: DMN date/time from exchange = 000622143354 > >> >ppp[173]: Warning: Add route failed: default already exists > >> > > >> > >> This is normal. I also see this with ppp. It's more a warning than > >> an error. > > > >You can ``add! default HISADDR'' if you want to override whatever's > >already set. > > > > I have that in the conf file. But HISADDR is written hisaddr, as it > appears in one of the examples. It doesn't seem to matter whether > it's written in CAPS or not, I've tried both. Maybe PPPoE has > different behavior ? The hisaddr bit can be upper or lower case. If you have ``add!'' instead of ``add'' it'll ``just do it'', so if it gets an already exists error from the SIOCAIFADDR it replaces the route. This shouldn't ever moan about an already existing route though. (or did you miss the ``!'' ?) > --- > Gary Jennejohn / garyj@muc.de gj@freebsd.org Cheers. -- 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 Tue Jun 27 22:35:22 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 33F3537BA85 for ; Tue, 27 Jun 2000 22:35:06 -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 GAA13175; Wed, 28 Jun 2000 06:34:52 +0100 Date: Wed, 28 Jun 2000 06:34:51 +0100 (BST) From: Paul Branston To: Vegard Munthe Cc: freebsd-isdn@freebsd.org Subject: Re: Troubleshooting In-Reply-To: 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, 27 Jun 2000, Vegard Munthe wrote: > > I'm setting up i4b on an OpenBSD 2.7, and have run into remarkably few > problems, until now. To this point I've compiled and installed i4b, > compiled and installed a new kernel supporting my Teles S0/16.3, compiled > and installed the freebsd userland ppp, and somewhat configured isdnd.conf > and ppp.conf. > > Everything seemed to go smoothly until I started it all up with high > debugging priorities and got a "No Carrier" error in ppp... > > Therefore I have two questions I hope someone can help me with; > > First I'm wondering if there is any way to 'talk' to the ISDN card > directly to see if the driver is at all comunicating with the card? This isdntrace will listen to the card and you can see constant traffic if the card is working at all. > > --- > DBG msg_dialoutnumber: dial req from rbch, unit 0 > DBG setup_dialout: entry userppp0 ok! > DBG find_by_device_for_dialoutnumber: found entry 0! > DBG FSM event [msg-dialout]: [idle => dialing] > DBG F_DIAL: local dial out request > DBG select_first_dialno: only one no, no = 22179080 > CHD 00003 userppp0 rate 360 sec/unit (rate) > CHD 00003 userppp0 dialing out from 22175582 to 22179080 > CHD 00003 userppp0 outgoing call disconnected (remote) > DBG msg_dialoutnumber: dial req from rbch, unit 0 > DBG find_by_device_for_dialoutnumber: entry 0, cdid in use > DBG msg_dialoutnumber: config entry reserved or no match > DBG msg_dialoutnumber: dial req from rbch, unit 0 > DBG find_by_device_for_dialoutnumber: entry 0, cdid in use > DBG msg_dialoutnumber: config entry reserved or no match > --- > > My ISDN line is fully functional as I have an ISDN telephone on a split > plug for testing, and I've tested the cables. My problem is finding where > the communication glitch is. My fear is that the kernel driver isn't > communicating with the card properly, but as the first question suggests, > I havn't found a way to test this yet. Any suggestions of getting this > fixed would help greatly. What to do now? :) > > Best regards, > > -- Vegard Munthe > Copyleft Software > Tel: 22232521 > > > > 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 28 6:44:30 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (p3E9B8F56.dip.t-dialin.net [62.155.143.86]) by hub.freebsd.org (Postfix) with ESMTP id A947E37B8AA for ; Wed, 28 Jun 2000 06:44:27 -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 CAA61905; Wed, 28 Jun 2000 02:37:21 +0200 (CEST) Message-Id: <200006280037.CAA61905@peedub.muc.de> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Somers Cc: freebsd-isdn@freebsd.org Subject: Re: i4b CRC / Recieve Aborted error, user PPP Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 28 Jun 2000 01:37:38 +0200." <200006272335.AAA19229@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Jun 2000 02:37:21 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brian Somers writes: >> >You can ``add! default HISADDR'' if you want to override whatever's >> >already set. >> > >> >> I have that in the conf file. But HISADDR is written hisaddr, as it >> appears in one of the examples. It doesn't seem to matter whether >> it's written in CAPS or not, I've tried both. Maybe PPPoE has >> different behavior ? > >The hisaddr bit can be upper or lower case. If you have ``add!'' >instead of ``add'' it'll ``just do it'', so if it gets an already >exists error from the SIOCAIFADDR it replaces the route. > >This shouldn't ever moan about an already existing route though. > >(or did you miss the ``!'' ?) > No, the bang is in there. It still moans: PPp ON peedub> Warning: Add route failed: default already exists It does replace the default route, though. --- 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 28 12:38:43 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 2C44A37BFE1 for ; Wed, 28 Jun 2000 12:38:34 -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 VAA13151; Wed, 28 Jun 2000 21:38:52 +0200 Received: (from martin@localhost) by rumolt.teuto.de (8.10.2/8.10.2) id e5SJajC00813; Wed, 28 Jun 2000 21:36:45 +0200 (MEST) From: Martin Husemann Message-Id: <200006281936.e5SJajC00813@rumolt.teuto.de> Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: <200006201634.SAA07217@peedub.muc.de> from Gary Jennejohn at "Jun 20, 2000 06:34:44 pm" To: garyj@muc.de (Gary Jennejohn) Date: Wed, 28 Jun 2000 21:36:45 +0200 (MEST) Cc: pherman@frenchfries.net (Paul Herman), 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 So, I told you about random lockups on one of our systems which I blamed an interrupt handler bug in the IPAC code for: I was wrong. While one might be conserative and call an unbound loop in an interrupt handler a bug anyway, it's not going to harm while the hardware (in this case: the ELSA PCI card) works OK. It did not do any harm to our system and it wasn't the cause for the random lockups. Don't ask, I've been through PC-hardware-crap hell several times in the last days. It seems to be fixed now, with neither replacing the ELSA ISDN card nor patching anything in I4B. Next time I'll buy an Ultra Sparc Server, running Solaris 8, with support contract! Or anything else which makes someone else but me responsible for fixing it... Just FYI. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Jun 30 5: 8:55 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 5B12937B99D for ; Fri, 30 Jun 2000 05:08:52 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1462 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Fri, 30 Jun 2000 14:08:50 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 19859388F; Fri, 30 Jun 2000 14:08:40 +0200 (METDST) Subject: Re: Q: status of Winbond W6692CF support In-Reply-To: <20000622082124.A4731@regent.in.skynet.cz> from Josef Pojsl at "Jun 22, 0 08:21:24 am" To: josef.pojsl@skynet.cz (Josef Pojsl) Date: Fri, 30 Jun 2000 14:08:39 +0200 (METDST) Cc: ernst@jollem.com, freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 553 Message-Id: <20000630120840.19859388F@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Josef Pojsl: > Someone even noticed that the driver is being developped but the author > has not commited it into the i4b distribution. Can anyone confirm/deny? This is true. hellmuth (reading mail #1000 of ~5000) -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Jun 30 5:12:40 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 84AEA37B99D for ; Fri, 30 Jun 2000 05:12:37 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1976 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Fri, 30 Jun 2000 14:12:36 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 1ABA2388F; Fri, 30 Jun 2000 14:12:18 +0200 (METDST) Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: from Paul Herman at "Jun 22, 0 11:41:17 am" To: pherman@frenchfries.net (Paul Herman) Date: Fri, 30 Jun 2000 14:12:17 +0200 (METDST) Cc: martin@rumolt.teuto.de, garyj@muc.de, freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 988 Message-Id: <20000630121218.1ABA2388F@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Paul Herman: > > 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. :) A looooong time someone had exactly this problem on NetBSD and sent in a patch. Because noone could reproduce the problem, i did not apply the patch. Since i'm still (sort of) on vacation, i can search through my archives to find it and sent it out to you in a week or so. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Jun 30 5:35:30 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 4969C37C572 for ; Fri, 30 Jun 2000 05:35:25 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-250-72.netcologne.de [195.14.250.72]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id OAA04257; Fri, 30 Jun 2000 14:35:22 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.2/8.10.2) with ESMTP id e5UCZ8l01451; Fri, 30 Jun 2000 14:35:08 +0200 (CEST) Date: Fri, 30 Jun 2000 14:35:07 +0200 (CEST) From: Paul Herman To: Hellmuth Michaelis Cc: martin@rumolt.teuto.de, garyj@muc.de, freebsd-isdn@FreeBSD.ORG Subject: Re: i4b hangs during boot with ELSA Microlink In-Reply-To: <20000630121218.1ABA2388F@hcswork.hcs.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 Fri, 30 Jun 2000, Hellmuth Michaelis wrote: > >From the keyboard of Paul Herman: > > A looooong time someone had exactly this problem on NetBSD and sent in > a patch. > > Because noone could reproduce the problem, i did not apply the patch. > > Since i'm still (sort of) on vacation, i can search through my archives > to find it and sent it out to you in a week or so. No need. This was in my case a bug in layer1/i4b_isic_pci.c which has since 0.83 been whisked away to the cornfield. The i4b_isic.c code in 4.0-STABLE (i4b 0.90) is fine and works for me. Thanks anyway. Enjoy the rest of your vacation, -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Jul 1 0:34:44 2000 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 2353637B6E5 for ; Sat, 1 Jul 2000 00:34:41 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1357 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sat, 1 Jul 2000 09:34:39 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id BE36D3FE9; Sat, 1 Jul 2000 09:34:29 +0200 (METDST) Subject: Re: TA PCI passive card questions In-Reply-To: <200006270545.HAA60315@peedub.muc.de> from Gary Jennejohn at "Jun 27, 0 07:45:31 am" To: garyj@muc.de Date: Sat, 1 Jul 2000 09:34:29 +0200 (METDST) Cc: Gerald.Heinig@post.rwth-aachen.de, freebsd-isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 456 Message-Id: <20000701073429.BE36D3FE9@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Gary Jennejohn: > Who knows ? Once I get started I may just finish it :) Go, go, go, go, goooooo ...... ;-) hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message