Excerpts from David Coppa's message of Tue Jul 06 01:10:00 -0700 2010: > On Tue, Jul 6, 2010 at 4:14 AM, Anders Langworthy <lagrang...@gmail.com> > wrote: > > On Mon, Jul 5, 2010 at 4:37 PM, Christopher Zimmermann > > <madro...@zakweb.de> wrote: > > > >> The only thing I find funny is that the network link only comes > >> up after I have run the 'ifconfig iwi0 scan' a second time. See > >> below. > > > > Yeah, this is a quirk with my iwi device[1] also. A scan needs to be > > run after you change nwid or the network will not come up as active. > > It does work without a scan the first time you connect to a network > > after the machine has been booted, though. > > > > [1]: iwi0 at pci2 dev 2 function 0 "Intel PRO/Wireless 2915ABG" rev 0x05 > >
I just want to add that i am also using iwi0 in a thinkpad T41p and have noticed the necessity to ifconfig iwi0 scan before network will actually become active probably for a year now. slap me for not saying anything sooner. i have tried various iwi cards i have laying around and its usually the same, i haven't tried any of my ralink or atheros cards since last year however. yes first boot always allows connect, as if the card being brought up fresh is fine however after the initial initialization it holds onto data too long and forgets to drop and retry actuating access point connection until a scan forces it to. -ryan
