Date: Tue, 11 Apr 2006 18:39:36 +0200 From: Max Laier <max@love2party.net> To: freebsd-net@freebsd.org Cc: hellbinder@gazeta.pl, "Zane C.B." <zanecb@midwest-connections.com> Subject: Re: inter pro wireless problems Message-ID: <200604111839.43439.max@love2party.net> In-Reply-To: <20060411091516.6d489ea9@zerda> References: <14002189.19331144748304428.JavaMail.webadm@ew11> <20060411091516.6d489ea9@zerda>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1449887.ZdOLOEPyW7 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 11 April 2006 16:15, Zane C.B. wrote: > On Tue, 11 Apr 2006 11:38:24 +0200 (CEST) > > <hellbinder@gazeta.pl> wrote: > > I have a problem setting up Intel PRO / Wireless 2200BG on Asus > > A3500N machine running FreeBSD 6.0. I tried to follow instructions > > at http://damien.bergamini.free.fr/ipw/ipw-freebsd.html but they are > > ok up till some point. I've installed iwi-firmware as needed and > > dmesg shows right wireless adapted at booting. > > First problem: No iwicontrol installed and I can't find anywhere. > > But the interface is up anyway. > > Second problem: sysctl dev.iwi.0.radio shown my card is running but > > the led on the computer is not on - so is it really on? I guess yes > > if ifconfig iwi0 returns: > > iwi0: flags=3D8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 > > inet6 fe80::212:f0ff:fe86:724c%iwi0 prefixlen 64 scopeid 0x2 > > inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > > ether 00:12:f0:86:72:4c > > media: IEEE 802.11 Wireless Ethernet autoselect > > status: no carrier > > ssid mcstudio channel 1 > > authmode OPEN privacy ON deftxkey UNDEF txpowmax 100 > > protmode CTS > > Final problem when I tried to connect to AP by: > > ifconfig iwi0 ssid mcstudio wepkey 0x6f73696f6c wepmode on > > I received: > > ifconfig: SIOCS80211: Invalid argument > > > > What's that how to solve these problems?? > > iwicontrol is provided by the net/iwi-firmware port. Just install it > and put iwi_enable=3D"YES" in rc.conf. I would honestly suggest running > with iwiNG and the iwi-firmware-kmod port though. You can find iwiNG on > the list here recently. I've had a problem with data corruption with > current iwi driver on releng_6. I've also had problems with the device > becoming unresponsive after a scan is done. IwiNG fixed both problems. The data corruption was an independent problem in the net80211 layer that h= as=20 been fixed in HEAD and RELENG_6 about one month ago. The "iwiNG" can be=20 found here: http://people.freebsd.org/~mlaier/new_iwi/ and needs=20 net/iwi-firmware-kmod as well as a recent RELENG_6 or CURRENT machine (one= =20 that installs firmware.ko), but - due to the data corruption - it's not a b= ad=20 idea to update anyway. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1449887.ZdOLOEPyW7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEO9vPXyyEoT62BG0RAgN/AJ4twu58cguYJnRj0xG6rc9wMW/a4wCdGlIT e/lllYmwRH8Q6cENAIv6kuk= =eYM9 -----END PGP SIGNATURE----- --nextPart1449887.ZdOLOEPyW7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604111839.43439.max>