From owner-freebsd-current@FreeBSD.ORG Sun Feb 20 23:26:24 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C208F16A4CE for ; Sun, 20 Feb 2005 23:26:24 +0000 (GMT) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D27943D31 for ; Sun, 20 Feb 2005 23:26:24 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen ([70.21.133.122])0.04 <0IC8007C5H3ZN610@vms046.mailsrvcs.net> for freebsd-current@freebsd.org; Sun, 20 Feb 2005 17:26:23 -0600 (CST) Date: Sun, 20 Feb 2005 18:25:40 -0500 From: "Alexandre \"Sunny\" Kovalenko" To: freebsd-current@freebsd.org Message-id: <1108941940.958.30.camel@RabbitsDen> MIME-version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-type: multipart/mixed; boundary="Boundary_(ID_hD9UbEWw66XXxWBjRfT87g)" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: [Fwd: Re: MA401 worked w/5.3 - No go under CURRENT] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Feb 2005 23:26:24 -0000 --Boundary_(ID_hD9UbEWw66XXxWBjRfT87g) Content-type: text/plain; charset=iso-8859-5 Content-transfer-encoding: 8BIT -------- Forwarded Message -------- > From: Alexandre "Sunny" Kovalenko > To: Chris > Subject: Re: MA401 worked w/5.3 - No go under CURRENT > Date: Sun, 20 Feb 2005 18:18:32 -0500 > On Sun, 2005-02-20 at 12:05 -0600, Chris wrote: > > Alexandre "Sunny" Kovalenko wrote: > > > On Sat, 2005-02-19 at 16:56 -0600, Chris wrote: > > > > > >>John Birrell wrote: > > >> > > >>>On Tue, Feb 15, 2005 at 06:16:58PM -0600, Chris wrote: > > >>> > > >>> > > >>>> I'm just starting to follow the CURRENT branch and popped that > > >>>> latest snapshot on my laptop. Under 5.3 my NetGear MA401 worked with just > > >>>>adding something like this to /etc/rc.conf: > > >>>> > > >>>>ifconfig_wi0="inet xxx.xxx.xxx.xxx netmask 255.255.255.0 ssid XXX > > >>>>wepmode on wepkey 0xxxxxxxxxxxxxxxxxxxxxxxxxxx" > > >>>> > > >>>> And everything came up just dandy. Has something changed? > > >>> > > >>> > > >>>I hadn't tried to use my wireless stuff for months until a few days ago. I have > > >>>the hostap running on current and I was trying to connect with wepmode on from > > >>>a RELENG_5 laptop without success. I read the recent messages suggesting the > > >>>explicit setting of the wepkey and default key, but that didn't solve the problem. > > >>> > > >>>I'll be away from the current box for 5 weeks and unable to debug anything, so I > > >>>know this message is virtally useless. I just wanted to say "me too". > > >>> > > >> > > >>Ok folks, I added the suggested stuff in /etc/rc.conf: > > >> > > >>ifconfig_wi0="inet xxx.xxx.xxx.xxx netmask 255.255.255.0 ssid XXX > > >>wepmode on weptxkey 1 wepkey 1:0xxxxxxxxxxxxxxxxxxxxxxxxxxx" > > >> > > >>And /boot/loader.conf: > > >>wlan_wep="YES" > > >> > > >>Still a no-go. Light on the wireless nic just blinks. > > >>I'm pretty much at a loss - anyone? > > >> > > > > > > Here is what I have working under -CURRENT as of 2/19 circa 11:00 AM > > > EST: > > > > > > sunny:RabbitsDen>dmesg | grep -i netgear > > > pccard0: CIS info: NETGEAR MA401RA Wireless PC, Card, ISL37300P, > > > Eval-RevA > > > pccard0: CIS info: NETGEAR MA401RA Wireless PC, Card, ISL37300P > > > wi0: at port 0x100-0x13f irq 10 > > > function 0 config 1 on pccard0 > > > sunny:RabbitsDen>grep ifconfig `which wi0` > > > ifconfig ${NIC} ssid XXX 10.0.0.1 netmask 255.255.255.0 wepmode on > > > wepkey 0x00000000000000000000000000 deftxkey 1 > > > sunny:RabbitsDen>grep wlan /sys/i386/conf/AVERATEC > > > device wlan # 802.11 support > > > device wlan_wep # WEP support (needs to be compiled in > > > for now) > > > sunny:RabbitsDen>kldstat > > > Id Refs Address Size Name > > > 1 15 0xc0400000 4496ec kernel > > > 2 1 0xc084d000 3064 powernow_k7.ko > > > 3 1 0xc0851000 1ccc io.ko > > > 4 1 0xc0853000 482c mem.ko > > > 5 1 0xc1de9000 6000 linprocfs.ko > > > 6 1 0xc1def000 18000 linux.ko > > > 7 1 0xc2560000 1e000 if_wi.ko > > > sunny:RabbitsDen> > > > > > > I guess you can start by checking whether your card is the same revision > > > as mine, and then bring your configuration in line with mine > > > dot-for-dot. > > > > > > If this does not work, we can trade outputs from dmesg with > > > hw.cbb.debug=1 and hw.pccard.debug=1. > > > > > > Should all of it fail you can always hope that someone who knows > > > wireless stuff will reply ;) > > > > > > > Is it possible to see your /etc/rc.conf file? Unless your doing > > something else instead of that. > > I don't do rc.conf as I roam a lot with this machine. I have attached script, I use to configure this card on as-needed basis. BTW: E-mail replies sent to you address bounce so I am replying to current@ and apologize to the readers for extra noise. -- Alexandre "Sunny" Kovalenko (Олександр Коваленко) --Boundary_(ID_hD9UbEWw66XXxWBjRfT87g)--