From owner-freebsd-hardware@FreeBSD.ORG Sun Feb 3 19:12:06 2008 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAF3316A41A for ; Sun, 3 Feb 2008 19:12:06 +0000 (UTC) (envelope-from jpalmer@totaldiver.net) Received: from mail.smugglers.com (mail.smugglers.com [209.26.221.26]) by mx1.freebsd.org (Postfix) with ESMTP id B597D13C4CC for ; Sun, 3 Feb 2008 19:12:06 +0000 (UTC) (envelope-from jpalmer@totaldiver.net) Received: from [192.168.1.30] (fl-76-3-162-23.dhcp.embarqhsd.net [76.3.162.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jpalmer@totaldiver.net) by mail.smugglers.com (Postfix) with ESMTP id 095A617124; Sun, 3 Feb 2008 13:52:13 -0500 (EST) Message-ID: <47A60DA2.60200@totaldiver.net> Date: Sun, 03 Feb 2008 13:53:22 -0500 From: Jeff Palmer User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Wael Nasreddine , hardware@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: I need some help trying to make Intel 3945ABG wireless card working. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2008 19:12:07 -0000 Wael Nasreddine wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello, > > I'm new to FreeBSD and I have a Toshiba Satellite A135-S4427 equipped > with an Intel 3945ABG wireless card. I searched a bit and I added > these to /boot/loader.conf > - ----CUT > if_wpi_load="YES" > wlan_load="YES" > wlan_amrr_load="YES" > firmware_load="YES" > wpifw_load="YES" > - ----CUT > > Now I have a wpi0 interface I tried doing > - ----CUT > ifconfig wpi0 ssid eMxyzptlk wepkey "0xC1C731EA92AC05B1E7BA6186CF" > - ----CUT > > but it doesn't associate with the AP all I see in ifconfig is > - ----CUT > wpi0: flags=8802 > metric 0 mtu 1500 > ether 00:19:d2:42:91:3f > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid eMxyzptlk channel 1 (2412 Mhz 11b) > authmode OPEN privacy OFF wepkey 1:104-bit txpower 50 bmiss 7 > scanvalid 60 bintval 0 > - ----CUT > > my AP is channel 11 so tried to switch manually > - ----CUT > ifconfig wpi0 ssid eMxyzptlk wepkey "0xC1C731EA92AC05B1E7BA6186CF" channel 11 > - ----CUT > but it didn't associate this way either > > - ----CUT > wpi0: flags=8802 > metric 0 mtu 1500 > ether 00:19:d2:42:91:3f > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid eMxyzptlk channel 11 (2462 Mhz 11g) > authmode OPEN privacy OFF wepkey 1:104-bit txpower 50 bmiss 7 > scanvalid 60 protmode CTS bintval 0 > - ----CUT > > I don't know where to go from here, I appreciate your help guys > > Thanks. > > - -- > Wael Nasreddine > http://wael.nasreddine.com > PGP: 1024D/C8DD18A2 06F6 1622 4BC8 4CEB D724 DE12 5565 3945 C8DD 18A2 > > .: An infinite number of monkeys typing into GNU emacs, > would never make a good program. (L. Torvalds 1995) :. > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.4 (FreeBSD) > > iD8DBQFHpgLEVWU5RcjdGKIRAiOWAJ9FNxOgy4DrLhi0acswvdefP5m3QwCg3qt8 > lqR0npPnfg7V4/XJavhNH/Y= > =PKGu > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > > Wael, you didn't mention what version of the driver you are using, so I'll assume you're using the one in 7.0-RC1. To make you aware, I have a toshiba satellite A135-S4517, and the wpi driver included in RELENG_7_0 doesn't work for me either. Attempts to work through the issue with the person originally porting the driver seem to have stalled, but in following current@ it seems as though others are submitting patches for it recently. My advice? Hang in there. at some point the hardware will be supported. It seems to work for several implementations of th 3945abg chipset. I can't assume ours is that drastically different. Jeff