On Tue, 24 May 2005, Josef Karthauser wrote:
I tried that:
genius# ifconfig iwi0 up
genius# ifconfig iwi0
iwi0: flags=8802 mtu 1500
I've seen the same problem - with certain access points (or a certain
ordering of commands to bring the interface up?) the driver wouldn't
associate.
On Tue, May 24, 2005 at 09:47:15AM +0200, Jeremie Le Hen wrote:
> >
> > Any idea how easy it is to port over to 5.x?
>
> I think it's mostly impossible as the iwi(4) should be using the new
> Sam Leffler's net80211 framework which is not going to be MFC'd to
> RELENG_5. I believe you should defi
Hi Josef,
> > What is the output of iwicontrol iwi0 -r ?
>
> genius# ifconfig iwi0 up
> genius#
> /tmp/wireless/iwi-freebsd-1.3.4/src/usr.sbin/iwicontrol/iwicontrol iwi0
> -r
> Radio is ON
> genius# ifconfig iwi0
> iwi0: flags=8802 mtu 1500
> inet6 fe80::20e:
On Mon, May 23, 2005 at 12:52:36PM +0200, Jeremie Le Hen wrote:
>
> What is the output of iwicontrol iwi0 -r ?
genius# ifconfig iwi0 up
genius#
/tmp/wireless/iwi-freebsd-1.3.4/src/usr.sbin/iwicontrol/iwicontrol iwi0
-r
Radio is ON
genius# ifconfig iwi0
iwi0: flags=8802
On Mon, May 23, 2005 at 02:26:42PM -0700, Darren Pilgrim wrote:
>
> The interface isn't in the UP state. At least with the iwi driver, the NIC
> won't associate to the AP until the interface is brought up. Usually this
> is done the first time something tries to send a packet (typically
> dhclie
From: Josef Karthauser
> I'm trying to get the iwi driver working on my sony A290 laptop. It's
> got a BG2200 chipset in it and the driver probes and finds
> the adapter, but it doesn't appear to work.
>
<...>
> iwi0: flags=8802 mtu 1500
> media: IEEE 802.11 Wireless Ethernet autoselect
>
Hi Josef,
> iwi0: flags=8802 mtu 1500
> inet6 fe80::20e:35ff:fe38:1e14%iwi0 prefixlen 64 scopeid 0x2
> ether 00:0e:35:38:1e:14
> media: IEEE 802.11 Wireless Ethernet autoselect
> status: no carrier
> ssid tao 1:tao
> channel -1 authmode OPEN powersa
I'm trying to get the iwi driver working on my sony A290 laptop. It's
got a BG2200 chipset in it and the driver probes and finds the adapter,
but it doesn't appear to work.
This is the probe message:
iwi0: mem 0xff6fd000-0xff6fdfff
irq 7 at device 2.0 on pci2
iwi0: Ethernet address:
