Search Linux Wireless

RE: iwl3945: disassociating from current AP on rescan with kernels > 3.0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Problem looks more like software scanning issue, which we enable
> by default on 2.6.39. Can you check if disable_hw_scan=0 module
> parameter helps?

Wow, this appears to have fixed my problem, at least so far. I'm a little
worried because I had the module parameter set /on/ (disable_hw_scan=1) from
way back when I first built this laptop and couldn't stay connected to our
work LAN. I didn't realize that was on by default. I've switched it to be
off now and hopefully it won't be a problem.

Thanks for the heads up!

--Mike

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux