From owner-freebsd-mobile Mon May 29 10:46:45 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id B5B6837BA12 for ; Mon, 29 May 2000 10:46:41 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 12wTcZ-000573-00 for freebsd-mobile@FreeBSD.ORG; Mon, 29 May 2000 13:46:35 -0400 Date: Mon, 29 May 2000 13:46:34 -0400 From: Peter Radcliffe To: freebsd-mobile@FreeBSD.ORG Subject: Re: TI1225 + ORINOCO aka WaveLAN IEEE 802.11 11Mb Message-ID: <20000529134634.B18825@pir.net> Mail-Followup-To: freebsd-mobile@FreeBSD.ORG References: <200005281938.MAA20158@mina.sr.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from acid@cn.ua on Mon, May 29, 2000 at 05:21:43PM +0300 X-fish: < Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Grisha Vasilyev probably said: > All hardware detects fine, but when I try to do ifconfig or ping, I've got > > wi0: tx buffer allocation failed > wi0: device timeout > ... > > Looks like initialization of PCI bridge isn't complete and/or correct > > -- I get the same effect with an old 486 laptop with a Standard ethernet cards (the 3com and New Media ones I have kicking around, certainly) work fine, first or second, but if it detects the WaveLAN card second, it fails with the long list of allocation failures. I fiddled with memory locations, irqs, etc, the usual, nothing seems to help. My temp hack was to power off both slots with pccardc and then power them up in the other order (the wavelan card has to go in slot 1 because of the form factor). It also refuses to detect insertion/removal events :/ The machine is my wavelan router, so hacked up static configs are ok for now, but it's still a pain - this box worked fine with 3.4-pao. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message