At 2009-01-24 13:16 -0800?Derek Olsen wrote? > Hello. > I am running snv_101b on a lenovo T61 laptop. The laptop has the intel > 4965 AG/AGN nic using the iwk driver. I've tried various versions of the > SUNWiwk package and I'm currently using revision VERSION: > 11.11,REV=2008.10.15.11.28 (from pkginfo). > > So my story goes like this. When ever I connect to a wireless AP I never > get an IP address. Well I shouldnt say never because it has worked 2 or 3 > times out of say 500 attempts. I've tried multiple access with the same > results. I get connected to the AP but cannot get an IP address. dladm > show-wifi shows I'm connected to the AP. > > Often time I get messages like this on boot or during the time I connect > to the AP > > Jan 24 13:01:24 ld2 iwk: [ID 375329 kern.warning] WARNING: iwk_rx_sens(): > can't make rx sensitivity calibration,because has not enough rx time > This message doesn't indicate any problem. It has been removed from snv_102. > These messages continually fill the messages file every few minutes > > Jan 24 12:50:43 ld2 net80211: [ID 924358 kern.warning] WARNING: rc4_init > failed (49) > You have connected to an AP with WEP or WPA, right? This message is a sign of frame encryption failure (so DHCP fails). This is a good chance rc4_init fails on boot. It's a problem of Kernel Encryption Framework (KCF). There has been a bug for this for sometime. > > So after typing all sorts of random things to get DHCP working I've > finally come up with this series of commands to get an IP address via DHCP. > > svcadm disable -t nwam > pfexec ifconfig iwk0 unplumb > modinfo |grep -i iwk > pfexec modunload -i 234 > svcadm enable nwam > > I've tested this about 10 times and it works every time so I'm confident > it's not just coincidentally working. Does the above command sequence give > anyone an idea of what the underlying problem is? Does calibration have > to occur before the module get's loaded (talking above my skill set here). > Anyhoo if anyone has any ideas of what I may be doing wrong I would > appreciate it. > Thanks. Deet. So, driver unloading/reloading solves the problem.
You can workaround this problem by disabling nwam on boot and start it later after your login. -- Tim
