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