From owner-freebsd-hardware Sat Sep 23 15:37:10 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id 2469B37B422 for ; Sat, 23 Sep 2000 15:37:07 -0700 (PDT) Received: (qmail 37451 invoked by uid 1000); 23 Sep 2000 22:43:38 -0000 Date: Sun, 24 Sep 2000 00:43:38 +0200 From: Andreas Braukmann To: freebsd-hardware@FreeBSD.ORG Subject: Lucent Wavelan vs. wi-driver Message-ID: <20000924004338.B37311@cage.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there, ... since I've read many success stories about using the Lucent WaveLan cards with FreeBSD, I aquired a "Lucent Orinoco Residential Gateway" (RG 1000) and a Lucent WaveLan pccard for testing purposes. The other hard- and software: Sony Vaio 505X FreeBSD 4.1-RELEASE [ As an aside: The combo is working fine under Win98 (I'm sitting in the living room watching the olympic games on tv andtyping this mail through a ssh-session to my regular workstation). ] The pccardd recognizes the wavelan card and binds it (as expected) to the the wi driver. I tried my very best to deduce the 'right' parameters for wicontrol. I set up the right network name, the infrastructure mode, the encryption key etc. Bringing up the interface with ifconfig results in "wi0: tx buffer allocation failed" messages. This smells like kern/17821. I was able to reproduce the behaviour with an ELSA AirLancer MC-11 from my "test pool", too. Any hints? Any patches available, yet? TIA, Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message