From owner-freebsd-isdn Sun Dec 23 9:42:46 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailgate.originative.co.uk (mailgate.originative.co.uk [62.232.68.68]) by hub.freebsd.org (Postfix) with ESMTP id D4BAD37B405 for ; Sun, 23 Dec 2001 09:42:41 -0800 (PST) Received: from lobster.originative.co.uk (lobster [62.232.68.81]) by mailgate.originative.co.uk (Postfix) with ESMTP id 108001D169; Sun, 23 Dec 2001 17:42:39 +0000 (GMT) Date: Sun, 23 Dec 2001 17:42:38 -0000 From: Paul Richards To: Juha-Matti Liukkonen , David Cc: freebsd-isdn@freebsd.org Subject: Re: Driver f. Asustek Cards Message-ID: <263330000.1009129358@lobster.originative.co.uk> In-Reply-To: References: X-Mailer: Mulberry/2.1.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --On Sunday, December 23, 2001 00:29:40 +0200 Juha-Matti Liukkonen wrote: > Hi, > > Asustek cards come in two flavors, which are unfortunately impossible to > tell apart from the box or the card type code. But you can look at the > biggest square black chip on the card: if it reads "Winbond", it is > supported with the iwic driver from I guess FreeBSD 4.0 onwards, but if > the chip reads "2HFC" or something to that effect, the support is not yet > ready (it is in the works, though, but not with great urgency). > > Asus should be sued for consumer misdirection, IMO, for selling two > completely different cards under the same model and make number. > > Br, > Jussi > > On Sat, 22 Dec 2001, David wrote: > >> Hi, >> >> I've a Asustek ISDN Card (passive/PCI), and the www.de.freebsd.org told >> me that it isn't supported (4.3 release). Are there another drivers that >> support that card? Asus itself doesn't list this card on their site :-( BT have done exactly the same with their ISDN card, i.e. changed the chipset but not changed any of the product branding. Since Asus and BT were two of the manufacturers we used to rely on as being supported it's causing us some headaches getting working cards. I tried to make a start on converting the isa driver to use PCI probing but there was too much ISDN knowledge required that I don't have. The separation of the ISDN attaching and the newbus attaching isn't as clean as it should be and I couldn't unravel the two. I'll happily spend some time after christmas trying to get these cards working though if someone is willing to help me with the ISDN side of it. Paul Richards FreeBSD Services Ltd http://www.freebsd-services.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Dec 24 14:51: 5 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from freeamateurhotties.com (port53gt.tube.com [216.18.85.63]) by hub.freebsd.org (Postfix) with SMTP id B1FC837B405 for ; Mon, 24 Dec 2001 14:50:53 -0800 (PST) Received: (qmail 93370 invoked by uid 0); 24 Dec 2001 22:49:48 -0000 Date: 24 Dec 2001 22:49:48 -0000 From: enchantress@freeamateurhotties.com To: freebsd-isdn@freebsd.org Subject: Did you take it? Message-ID: Organization: freeamateurhotties.com MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Accept-Language: en Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org FREE CHRISTMAS PORN!!! HERE’S A FREE PASSWORD TO FREE AMATEUR HOTTIES.COM http://www.freeamateurhotties.com/g1/ It’s instant access, 100% FREE, no bullshit, Christmas present from us to you. http://www.freeamateurhotties.com/g1/ Free porn is the gift that keeps giving! If you want us to stop sending you email then click here: http://www.freeamateurhotties.com/db/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Dec 24 16:13:31 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [62.49.12.213]) by hub.freebsd.org (Postfix) with ESMTP id 606D837B416 for ; Mon, 24 Dec 2001 16:13:24 -0800 (PST) Received: by arg1.demon.co.uk (Postfix, from userid 1002) id 2C49F9B07; Tue, 25 Dec 2001 00:13:23 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by arg1.demon.co.uk (Postfix) with ESMTP id 22AB85D25; Tue, 25 Dec 2001 00:13:23 +0000 (GMT) Date: Tue, 25 Dec 2001 00:13:23 +0000 (GMT) From: Andrew Gordon X-X-Sender: To: Gary Jennejohn Cc: Subject: ifpi2 problems Message-ID: <20011224235808.T86622-100000@server.arg.sj.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have been trying out the ifpi2 driver. I first tried in a -current machine and all worked OK (though I didn't thrash it particularly hard). I am now trying to use it in a 486 running -stable. The setup is (at present) just using the ISDN for single-channel outgoing calls with user-ppp/rbch. If I use it 'gently' it all works fine - I have been online for an hour or so reading mail via ssh with no problem. However, if I try web browsing to graphics-heavy sites, it stops working within about 2 minutes. The failure state is as if interrupts from the card have become disabled: the ppp process is still running and eventually times out the connection and attempts to redial, but isdnd thinks that the connection is in use, and if I make a voice call to the line, ISDND doesn't report anything. Only a reboot seems to clear the latched up state. Unfortunately my setup here is extremely inconvenient for debugging (this is a router for my parents' new home, where the ISDN line plus this 486 are in a cupboard in a different building from the room where the main PC is kept; the router has no console and I forgot to bring the right cable so I can't even plug in a laptop as console...). I will try to debug further tomorrow, but any hints would be gratefully received. PS. are you sure that having a device name ending in a digit is a good idea? It gives very confusing effects if you forget the quotes around the device "ifpi2" line in the kernel config file, as well as the rather odd ifpi20: blah messages on the console. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Dec 24 16:32:39 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from iafrica.com (cpt-dial-196-30-178-55.mweb.co.za [196.30.178.55]) by hub.freebsd.org (Postfix) with ESMTP id 63BA137B416 for ; Mon, 24 Dec 2001 16:32:34 -0800 (PST) Received: (from ayon@localhost) by iafrica.com (8.11.6/8.11.6) id fBP0X5X68057 for freebsd-isdn@FreeBSD.org; Tue, 25 Dec 2001 02:33:05 +0200 (SAST) (envelope-from ayon) Date: Tue, 25 Dec 2001 02:33:05 +0200 From: Francois Kritzinger To: freebsd-isdn@FreeBSD.org Subject: Re: i4b/isdnd panic on incoming call Message-ID: <20011225023305.A68034@noya> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I'd just like to report back on the problem I was having a couple of months ago (in the 04-Nov-2001 section of the list archives). I said I was going to dial up in Windows to see whether it was indeed my local phone exchange that was corrupting the incoming frames, or whether it was my setup. Well, I dialled in on Windows for many weekends after that, and the connection stayed open without a problem. However, I have since upgraded to FreeBSD 4.4 (I was using 4.3) which includes i4b 1.something (I was using i4b 0.96), and now the connection is pretty much perfect. Thanks again for the help, and sorry for not reporting back sooner. -- Francois To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Mon Dec 24 17: 5:51 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from iafrica.com (cpt-dial-196-30-178-55.mweb.co.za [196.30.178.55]) by hub.freebsd.org (Postfix) with ESMTP id A17BA37B41B for ; Mon, 24 Dec 2001 17:05:46 -0800 (PST) Received: (from ayon@localhost) by noya (8.11.6/8.11.6) id fBNJZtQ12833 for freebsd-isdn@FreeBSD.org; Sun, 23 Dec 2001 21:35:55 +0200 (SAST) (envelope-from ayon) Date: Sun, 23 Dec 2001 21:34:29 +0200 From: Francois Kritzinger To: freebsd-isdn@FreeBSD.org Subject: Re: i4b/isdnd panic on incoming call Message-ID: <20011223213429.A12821@noya> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I'd just like to report back on the problem I was having a couple of months ago (in the 04-Nov-2001 section of the list archives). I said I was going to dial up in Windows to see whether it was indeed my local phone exchange that was corrupting the incoming frames, or whether it was my setup. Well, I dialled in on Windows for many weekends after that, and the connection stayed open without a problem. However, I have since upgraded to FreeBSD 4.4 (I was using 4.3) which includes i4b 1.something (I was using i4b 0.96), and now the connection is pretty much perfect. Thanks again for the help, and sorry for not reporting back sooner. -- Francois To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Tue Dec 25 0:13: 0 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.freebsd.org (Postfix) with ESMTP id 0734937B405 for ; Tue, 25 Dec 2001 00:12:56 -0800 (PST) Received: from fwd11.sul.t-online.de by mailout04.sul.t-online.de with smtp id 16Imhi-0001Dz-03; Tue, 25 Dec 2001 09:12:54 +0100 Received: from peedub.jennejohn.org (520017439985-0001@[217.80.235.72]) by fmrl11.sul.t-online.com with esmtp id 16Imhe-1LmguOC; Tue, 25 Dec 2001 09:12:50 +0100 Received: by peedub.jennejohn.org (8.11.6/8.11.6) id fBP8Ckq52439 for isdn@freebsd.org; Tue, 25 Dec 2001 09:12:46 +0100 (CET) (envelope-from garyj) Message-Id: <200112250812.fBP8Ckq52439@peedub.jennejohn.org> Content-Type: text/plain; charset="iso-8859-1" From: Gary Jennejohn Reply-To: garyj@jennejohn.org To: isdn@freebsd.org Subject: Fwd: Re: ifpi2 problems Date: Tue, 25 Dec 2001 09:12:45 +0100 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Sender: 520017439985-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I forgto to send this to the list. ---------- Forwarded Message ---------- Subject: Re: ifpi2 problems Date: Tue, 25 Dec 2001 09:10:38 +0100 From: Gary Jennejohn To: Andrew Gordon On Tuesday 25 December 2001 01:13, you wrote: [snip] > The failure state is as if interrupts from the card have > become disabled: the ppp process is still running and > eventually times out the connection and attempts to redial, > but isdnd thinks that the connection is in use, and if I make > a voice call to the line, ISDND doesn't report anything. Only > a reboot seems to clear the latched up state. > > > Unfortunately my setup here is extremely inconvenient for > debugging (this is a router for my parents' new home, where > the ISDN line plus this 486 are in a cupboard in a different > building from the room where the main PC is kept; the router > has no console and I forgot to bring the right cable so I > can't even plug in a laptop as console...). > > I will try to debug further tomorrow, but any hints would be > gratefully received. Thanks, I'd greatly appreciate it since I don't have any -stable machine where I can plug in a controller. Be aware that the driver is based on a beta-quality Linux driver. The Linux driver is the only documentation available on the controller. > PS. are you sure that having a device name ending in a digit > is a good idea? It gives very confusing effects if you forget > the quotes around the device "ifpi2" > line in the kernel config file, as well as the rather odd > ifpi20: blah > messages on the console. I wanted to make it clear that this is for the version 2 controller. Putting a 2 in the name was the only way which occurred to me. I tried to make all the printf's look like "ifpi2-", but I guess I missed some :( -- Gary Jennejohn garyj@jennejohn.org gj@freebsd.org ------------------------------------------------------- -- Gary Jennejohn garyj@jennejohn.org 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 Dec 25 5:41: 8 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.RWTH-Aachen.DE [137.226.46.168]) by hub.freebsd.org (Postfix) with ESMTP id 272E237B417 for ; Tue, 25 Dec 2001 05:41:05 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.11.1/8.9.3) id fBPDf4U23694 for freebsd-isdn@freebsd.org; Tue, 25 Dec 2001 14:41:04 +0100 (CET) (envelope-from kuku) Date: Tue, 25 Dec 2001 14:41:04 +0100 (CET) From: Christoph Kukulies Message-Id: <200112251341.fBPDf4U23694@gilberto.physik.rwth-aachen.de> To: freebsd-isdn@freebsd.org Subject: i4bing.h not found in 4.4 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm recompiling a kernel (from a 4.2 system) and kernel compilation can't find i4bing.h in i4b_i4bdrv.c:73 Any clues? Frohe Weihnachten, Merry Chrismas, Joieux Noel, -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 28 3:35:40 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hale.inty.net (hale.inty.net [195.92.21.144]) by hub.freebsd.org (Postfix) with ESMTP id 7EA1637B417 for ; Fri, 28 Dec 2001 03:35:35 -0800 (PST) Received: from inty.hq.inty.net (inty.hq.inty.net [213.38.150.150]) by hale.inty.net (8.11.3/8.11.3) with ESMTP id fBSBZPf77850 for ; Fri, 28 Dec 2001 11:35:25 GMT Received: from davidh ([10.0.1.197]) by inty.hq.inty.net (8.12.1/8.9.3) with SMTP id fBSBZOfS001583 for ; Fri, 28 Dec 2001 11:35:24 GMT From: "David Hedley" To: Subject: RE: ifpi2 problems Date: Fri, 28 Dec 2001 11:35:25 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20011224235808.T86622-100000@server.arg.sj.co.uk> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Sender-IP: 10.0.1.197 X-suppress-rcpt-virus-notify: yes X-Skip-Virus-Check: yes X-Virus-Checked: 39851 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > I have been trying out the ifpi2 driver. I first tried in a -current > machine and all worked OK (though I didn't thrash it particularly hard). > I am now trying to use it in a 486 running -stable. > > The setup is (at present) just using the ISDN for single-channel outgoing > calls with user-ppp/rbch. If I use it 'gently' it all works fine - I have > been online for an hour or so reading mail via ssh with no problem. > However, if I try web browsing to graphics-heavy sites, it stops working > within about 2 minutes. > > The failure state is as if interrupts from the card have become disabled: > the ppp process is still running and eventually times out the connection > and attempts to redial, but isdnd thinks that the connection is in use, > and if I make a voice call to the line, ISDND doesn't report anything. > Only a reboot seems to clear the latched up state. Hmm, well this probably doesn't help, but we've been testing the v2 Fritz card using Gary's drivers for a while now and haven't hit any major problems like this (this is with 4.4 and i4b from -stable). The only problem we've seen is when we plug both a v1 fritz and a v2 fritz into the same box, where you get an instant kernel panic when the v2 fritz card tries to dial out. (panics in avma1pp_set_linktab, so may not be specific to v2 fritz). What happens if you just restart isdnd? I occasionally see problems when user-ppp and isdnd stop talking to each other (ppp will be trying to dial out but isdnd won't respond for some reason), although this always goes away when isdnd is restarted. > > PS. are you sure that having a device name ending in a digit is a good > idea? It gives very confusing effects if you forget the quotes around the > device "ifpi2" > line in the kernel config file, as well as the rather odd > ifpi20: blah > messages on the console. > I second this. I actually ended up renaming the driver entirely - I didn't realise you could put quotes around it to get it to work! Happy New Year... David -- Dr David Hedley, R&D Director, Intelligent Network Technology Ltd, Bristol, UK http://www.inty.net/ ----------------------------------------------- Information in this electronic mail message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient any use, disclosure, copying or distribution of this message is prohibited and may be unlawful. When addressed to our customers, any information contained in this message is subject to Intelligent Network Technology Ltd Terms & Conditions. ----------------------------------------------- Take part in the intY 2001 Email Usage survey online at http://www.inty.net/email/survey.html ----------------------------------------------- intY has automatically scanned this email with Sophos Anti-Virus (www.inty.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 28 4:40:52 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [62.49.12.213]) by hub.freebsd.org (Postfix) with ESMTP id 0B32837B416 for ; Fri, 28 Dec 2001 04:40:49 -0800 (PST) Received: by arg1.demon.co.uk (Postfix, from userid 1002) id 025F29B07; Fri, 28 Dec 2001 12:40:47 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by arg1.demon.co.uk (Postfix) with ESMTP id ECC825D27; Fri, 28 Dec 2001 12:40:47 +0000 (GMT) Date: Fri, 28 Dec 2001 12:40:47 +0000 (GMT) From: Andrew Gordon X-X-Sender: To: David Hedley Cc: Subject: RE: ifpi2 problems In-Reply-To: Message-ID: <20011228123618.Q99457-100000@server.arg.sj.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 28 Dec 2001, David Hedley wrote: > > > The failure state is as if interrupts from the card have become disabled: > > the ppp process is still running and eventually times out the connection > > and attempts to redial, but isdnd thinks that the connection is in use, > > and if I make a voice call to the line, ISDND doesn't report anything. > > Only a reboot seems to clear the latched up state. > > Hmm, well this probably doesn't help, but we've been testing the v2 Fritz > card using Gary's drivers for a while now and haven't hit any major problems > like this (this is with 4.4 and i4b from -stable). Interesting. I have a suspicion (but with no evidence whatsoever!) that my problem is down to being a much slower machine. > What happens if you just restart isdnd? I occasionally see problems when > user-ppp and isdnd stop talking to each other (ppp will be trying to dial > out but isdnd won't respond for some reason), although this always goes away > when isdnd is restarted. I tried restarting isdnd, but it didn't help. I eventually gave up trying to fix it on-site, and have brought all the equipment home again. I will have another go at debugging later today. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Dec 28 13:30:32 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by hub.freebsd.org (Postfix) with ESMTP id 2556937B417 for ; Fri, 28 Dec 2001 13:30:29 -0800 (PST) Received: from fwd11.sul.t-online.de by mailout02.sul.t-online.de with smtp id 16K4Zx-0005mY-0G; Fri, 28 Dec 2001 22:30:13 +0100 Received: from peedub.jennejohn.org (520017439985-0001@[217.235.121.121]) by fmrl11.sul.t-online.com with esmtp id 16K4Zv-1nqVLUC; Fri, 28 Dec 2001 22:30:11 +0100 Received: by peedub.jennejohn.org (8.11.6/8.11.6) id fBSLUKt95840; Fri, 28 Dec 2001 22:30:20 +0100 (CET) (envelope-from garyj) Message-Id: <200112282130.fBSLUKt95840@peedub.jennejohn.org> Content-Type: text/plain; charset="iso-8859-1" From: Gary Jennejohn Reply-To: garyj@jennejohn.org To: "David Hedley" , Subject: Re: ifpi2 problems Date: Fri, 28 Dec 2001 22:30:20 +0100 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Sender: 520017439985-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Friday 28 December 2001 12:35, David Hedley wrote: > Hmm, well this probably doesn't help, but we've been testing > the v2 Fritz card using Gary's drivers for a while now and > haven't hit any major problems like this (this is with 4.4 and > i4b from -stable). The only problem we've seen is when we plug > both a v1 fritz and a v2 fritz into the same box, where you > get an instant kernel panic when the v2 fritz card tries to > dial out. (panics in avma1pp_set_linktab, so may not be > specific to v2 fritz). > Yeah, the panic is in the v. 1 driver. Really weird. I've never seen this with the v.1 controller alone in a box. Why doesn't anyone tell me about these things ? I just replaced my old v. 1 card with the v. 2 card. I guess I could also plug in the v.1 card and try them out together. > > PS. are you sure that having a device name ending in a digit > > is a good idea? It gives very confusing effects if you > > forget the quotes around the device "ifpi2" > > line in the kernel config file, as well as the rather odd > > ifpi20: blah > > messages on the console. > > I second this. I actually ended up renaming the driver > entirely - I didn't realise you could put quotes around it to > get it to work! > Well, I _did_ mention in a mail that this is necessary. Unfortunately, I've already committed the driver in -current as ifpi2 and don't think it'd be a good idea to import it under a different name into -stable. The "ifpi20" problem is easily fixed: in i4b_ifpi2_pci.c replace the string "ifpi2" in the ``driver_t avma1pp2_pci_driver'' with "ifpi2-". Yes, it's ugly, but what-the-hey. -- Gary Jennejohn garyj@jennejohn.org 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 Sat Dec 29 0:25:31 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id 3C7CF37B41C for ; Sat, 29 Dec 2001 00:25:29 -0800 (PST) Received: from fwd01.sul.t-online.de by mailout06.sul.t-online.de with smtp id 16KEnz-0006PA-00; Sat, 29 Dec 2001 09:25:23 +0100 Received: from peedub.jennejohn.org (520017439985-0001@[217.228.210.189]) by fmrl01.sul.t-online.com with esmtp id 16KEnr-0abhgGC; Sat, 29 Dec 2001 09:25:15 +0100 Received: by peedub.jennejohn.org (8.11.6/8.11.6) id fBT8POR33524; Sat, 29 Dec 2001 09:25:24 +0100 (CET) (envelope-from garyj) Message-Id: <200112290825.fBT8POR33524@peedub.jennejohn.org> Content-Type: text/plain; charset="iso-8859-1" From: Gary Jennejohn Reply-To: garyj@jennejohn.org To: "David Hedley" , Subject: Re: ifpi2 problems Date: Sat, 29 Dec 2001 09:25:23 +0100 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Sender: 520017439985-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Friday 28 December 2001 12:35, David Hedley wrote: > > PS. are you sure that having a device name ending in a digit > > is a good idea? It gives very confusing effects if you > > forget the quotes around the device "ifpi2" > > line in the kernel config file, as well as the rather odd > > ifpi20: blah > > messages on the console. > > I second this. I actually ended up renaming the driver > entirely - I didn't realise you could put quotes around it to > get it to work! > OK, after reconsidering this I don't think it would be so bad to change the name. Does anyone have good ideas for a device name which does not contain a digit but makes it clear that this is for the Fritz!Card PCI version 2 ? -- Gary Jennejohn garyj@jennejohn.org 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 Sat Dec 29 3:11: 3 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from liliput.tmp.com.br (liliput.tmp.com.br [200.244.62.12]) by hub.freebsd.org (Postfix) with ESMTP id 7AA1837B429 for ; Sat, 29 Dec 2001 03:10:54 -0800 (PST) Received: (from prallon@localhost) by liliput.tmp.com.br (8.8.8/8.8.8) id JAA07119; Sat, 29 Dec 2001 09:10:48 -0200 Date: Sat, 29 Dec 2001 09:10:48 -0200 From: Sergio de Souza Prallon To: Gary Jennejohn Cc: freebsd-isdn@freebsd.org Subject: Re: ifpi2 problems Message-ID: <20011229091048.A6911@tmp.com.br> References: <200112290825.fBT8POR33524@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200112290825.fBT8POR33524@peedub.jennejohn.org>; from garyj@jennejohn.org on Sat, Dec 29, 2001 at 09:25:23AM +0100 X-URL: http://www.tmp.com.br Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [Snip] > > OK, after reconsidering this I don't think it would be so bad to > change the name. Does anyone have good ideas for a device name > which does not contain a digit but makes it clear that this is > for the Fritz!Card PCI version 2 ? > Perhaps the Sun's way: ifpitwo (after the bwtwo, cgsix they used). []'s -- Prallon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Dec 29 9: 5:12 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by hub.freebsd.org (Postfix) with ESMTP id EBE6B37B416 for ; Sat, 29 Dec 2001 09:05:08 -0800 (PST) Received: from fwd04.sul.t-online.de by mailout10.sul.t-online.de with smtp id 16KMux-0003DP-06; Sat, 29 Dec 2001 18:05:07 +0100 Received: from peedub.jennejohn.org (520017439985-0001@[217.80.236.110]) by fmrl04.sul.t-online.com with esmtp id 16KMut-13uVoOC; Sat, 29 Dec 2001 18:05:03 +0100 Received: by peedub.jennejohn.org (8.11.6/8.11.6) id fBTH56e00459; Sat, 29 Dec 2001 18:05:06 +0100 (CET) (envelope-from garyj) Message-Id: <200112291705.fBTH56e00459@peedub.jennejohn.org> Content-Type: text/plain; charset="iso-8859-1" From: Gary Jennejohn Reply-To: garyj@jennejohn.org To: "David Hedley" , Subject: Re: ifpi2 problems Date: Sat, 29 Dec 2001 18:05:04 +0100 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Sender: 520017439985-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Friday 28 December 2001 12:35, David Hedley wrote: > The only problem we've seen is when we plug > both a v1 fritz and a v2 fritz into the same box, where you > get an instant kernel panic when the v2 fritz card tries to > dial out. (panics in avma1pp_set_linktab, so may not be > specific to v2 fritz). > OK, I've figured out what was causing this. I'll post a patch to the list later. -- Gary Jennejohn garyj@jennejohn.org 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 Sat Dec 29 9:27:17 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout09.sul.t-online.com (mailout09.sul.t-online.com [194.25.134.84]) by hub.freebsd.org (Postfix) with ESMTP id E150437B41A for ; Sat, 29 Dec 2001 09:27:09 -0800 (PST) Received: from fwd05.sul.t-online.de by mailout09.sul.t-online.de with smtp id 16KNFh-0003c8-03; Sat, 29 Dec 2001 18:26:33 +0100 Received: from peedub.jennejohn.org (520017439985-0001@[217.228.220.196]) by fmrl05.sul.t-online.com with esmtp id 16KNFY-0Nu9bsC; Sat, 29 Dec 2001 18:26:24 +0100 Received: by peedub.jennejohn.org (8.11.6/8.11.6) id fBTHQeY00526; Sat, 29 Dec 2001 18:26:40 +0100 (CET) (envelope-from garyj) Message-Id: <200112291726.fBTHQeY00526@peedub.jennejohn.org> From: Gary Jennejohn Reply-To: garyj@jennejohn.org To: "David Hedley" , Subject: Re: ifpi2 problems Date: Sat, 29 Dec 2001 18:26:30 +0100 X-Mailer: KMail [version 1.3.2] References: <200112291705.fBTH56e00459@peedub.jennejohn.org> In-Reply-To: <200112291705.fBTH56e00459@peedub.jennejohn.org> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_6G84V11SYSYUYFNT9Z1H" X-Sender: 520017439985-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --------------Boundary-00=_6G84V11SYSYUYFNT9Z1H Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit On Saturday 29 December 2001 18:05, Gary Jennejohn wrote: > On Friday 28 December 2001 12:35, David Hedley wrote: > > The only problem we've seen is when we plug > > both a v1 fritz and a v2 fritz into the same box, where you > > get an instant kernel panic when the v2 fritz card tries to > > dial out. (panics in avma1pp_set_linktab, so may not be > > specific to v2 fritz). > > OK, I've figured out what was causing this. I'll post a patch > to the list later. Here's the patch. -- Gary Jennejohn garyj@jennejohn.org gj@freebsd.org --------------Boundary-00=_6G84V11SYSYUYFNT9Z1H Content-Type: text/x-diff; charset="iso-8859-1"; name="diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="diff" LS0tIGxheWVyMS9pZnBpL2k0Yl9pZnBpX3BjaS5jLm9yaWcJU2F0IERlYyAyOSAxODoyMjoxOSAy MDAxCisrKyBsYXllcjEvaWZwaS9pNGJfaWZwaV9wY2kuYwlTYXQgRGVjIDI5IDE4OjIyOjQyIDIw MDEKQEAgLTEyOTEsOCArMTI5MSw4IEBACiAJLyogYXZvaWQgb3ZlcndyaXRpbmcgaWYgYWxyZWFk eSBzZXQgKi8KIAlpZiAoY3RybF90eXBlc1tDVFJMX1BBU1NJVkVdLnNldF9saW5rdGFiID09IE5V TEwpCiAJewotCQljdHJsX3R5cGVzW0NUUkxfUEFTU0lWRV0uc2V0X2xpbmt0YWIgPSBhdm1hMXBw X3NldF9saW5rdGFiOwotCQljdHJsX3R5cGVzW0NUUkxfUEFTU0lWRV0uZ2V0X2xpbmt0YWIgPSBh dm1hMXBwX3JldF9saW5rdGFiOworCQljdHJsX3R5cGVzW0NUUkxfUEFTU0lWRV0uc2V0X2xpbmt0 YWIgPSBpNGJfbDFfc2V0X2xpbmt0YWI7CisJCWN0cmxfdHlwZXNbQ1RSTF9QQVNTSVZFXS5nZXRf bGlua3RhYiA9IGk0Yl9sMV9yZXRfbGlua3RhYjsKIAl9CiAKIAkvKiBsb2NhbCBzZXR1cCAqLwot LS0gbGF5ZXIxL2lmcGkyL2k0Yl9pZnBpMl9wY2kuYy5vcmlnCVNhdCBEZWMgMjkgMTg6MjE6NTgg MjAwMQorKysgbGF5ZXIxL2lmcGkyL2k0Yl9pZnBpMl9wY2kuYwlTYXQgRGVjIDI5IDE4OjIyOjI2 IDIwMDEKQEAgLTEyMjQsOCArMTIyNCw4IEBACiAJLyogYXZvaWQgb3ZlcndyaXRpbmcgaWYgYWxy ZWFkeSBzZXQgKi8KIAlpZiAoY3RybF90eXBlc1tDVFJMX1BBU1NJVkVdLnNldF9saW5rdGFiID09 IE5VTEwpCiAJewotCQljdHJsX3R5cGVzW0NUUkxfUEFTU0lWRV0uc2V0X2xpbmt0YWIgPSBhdm1h MXBwMl9zZXRfbGlua3RhYjsKLQkJY3RybF90eXBlc1tDVFJMX1BBU1NJVkVdLmdldF9saW5rdGFi ID0gYXZtYTFwcDJfcmV0X2xpbmt0YWI7CisJCWN0cmxfdHlwZXNbQ1RSTF9QQVNTSVZFXS5zZXRf bGlua3RhYiA9IGk0Yl9sMV9zZXRfbGlua3RhYjsKKwkJY3RybF90eXBlc1tDVFJMX1BBU1NJVkVd LmdldF9saW5rdGFiID0gaTRiX2wxX3JldF9saW5rdGFiOwogCX0KIAogCS8qIGxvY2FsIHNldHVw ICovCg== --------------Boundary-00=_6G84V11SYSYUYFNT9Z1H-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message