From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 1 20:36:15 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1A4F16A4BF for ; Mon, 1 Sep 2003 20:36:15 -0700 (PDT) Received: from ms-smtp-03.southeast.rr.com (ms-smtp-03.southeast.rr.com [24.93.67.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83B7B43FF7 for ; Mon, 1 Sep 2003 20:36:14 -0700 (PDT) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (cpe-024-211-116-193.sc.rr.com [24.211.116.193])h823Xsxk016018; Mon, 1 Sep 2003 23:33:54 -0400 (EDT) Received: from localhost (morganw@localhost [127.0.0.1]) h823Zxum043985; Mon, 1 Sep 2003 23:35:59 -0400 (EDT) (envelope-from morganw@chemikals.org) Date: Mon, 1 Sep 2003 23:35:59 -0400 (EDT) From: Wesley Morgan To: Marcel Moolenaar In-Reply-To: <20030901164525.GB562@dhcp01.pn.xcllnt.net> Message-ID: <20030901233221.U41366@volatile.chemikals.org> References: <002d01c3709d$3bac7480$093d1581@rehash> <20030901.103852.122081183.imp@bsdimp.com> <20030901164525.GB562@dhcp01.pn.xcllnt.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: neo@csh.rit.edu cc: "M. Warner Losh" cc: freebsd-mobile@freebsd.org Subject: Re: Lucent Technologies Orinoco Gold X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2003 03:36:15 -0000 On Mon, 1 Sep 2003, Marcel Moolenaar wrote: > On Mon, Sep 01, 2003 at 10:38:52AM -0600, M. Warner Losh wrote: > > In message: <002d01c3709d$3bac7480$093d1581@rehash> > > "Michael Goffin" writes: > > : I posted a week or two ago about having issues with my Orinoco Gold wireless > > : card not working in 5.1-current. It was suggested that I update the > > : firmware. The firmware upgrade did not work. Has anyone had issues with this > > : card in 5.1-current that they were able to resolve? > > > > You might also want to try the owi driver. It isn't supported, and > > may disappear soon, but it was created to try to fix the lucent > > support in the wi driver. You can't have both the owi and wi drivers > > in the kernel at the same time. owi is supported only as a module. > > If it doesn't work, then oh well. > > What are the problems? I'm happily using my Lucent card without > problems. That is, I have less problems with it than I had with > an embedded PRISM3. > > wi0: at port 0x100-0x13f irq 9 function 0 config 1 on pccard0 > wi0: 802.11 address: 00:02:2d:09:71:2b > wi0: using Lucent Technologies, WaveLAN/IEEE > wi0: Lucent Firmware: Station (6.6.1) > wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > wi0: bad alloc 3d2 != ff, cur 0 nxt 0 Mine works fine as well: wi0: at port 0x100-0x13f irq 11 function 0 config 1 on pccard1 wi0: 802.11 address: 00:02:2d:04:e2:41 wi0: using Lucent Technologies, WaveLAN/IEEE wi0: Lucent Firmware: Station (8.72.1) wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps And I see this when it tries to get an address: wi0: bad alloc 205 != 202, cur 0 nxt 0 Everything works perfectly (although I do NOT use WEP, which used to cause me tons of problems) talking to my linksys AP. All that is required to start the card up is "ifconfig wi0 media autoselect ssid linksys". I was going to do some experiments on getting peer-peer working between 4.x and 5.x (which I have used in the past), but my test box seems to have expired in storage. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!